Cue measures each client against their own history and shows you what moved, with the context beside it. The clinical reading, and the decision, stay yours.
Tuesday, March 3. Maya Rivera’s elopement is up. Moment by moment from opening her record to approving what her mother reads — on a tablet at the desk, and on the technician’s phone in the room.
The program in effect, the assessment it came from, and the sessions run since — on one screen rather than in multiple systems. You can see who has actually been delivering the sessions, and which version of the protocol each of them ran, before you form any view about the data.
D. Okafor, BCBA · BCBS of TX · 74 of 120 authorized hours used · reauthorization Mar 14
Elopement is above Maya’s own usual range across the last three sessions. Cue shows the rise and everything else that moved in the same fortnight — who ran the sessions, whether the protocol changed, what the technicians wrote, what her mother reported. It flags; it does not diagnose. Whether this is a program problem, a staffing problem or a hard fortnight is yours to decide.
Why a substitute ran those sessions →The coverage gap, from the owner’s chairPer hour, last 14 sessions · flagged Mar 2 · measured against her own range, not a fixed number
You lengthen the delay to 30 seconds and add a note on every transition. Publishing is also the handoff: the new version lands in Maya’s care team channel, where membership comes from her assignments. K. Reyes acknowledges at 9:22. When T. Alvarez picks up the 3:30 that afternoon, the assignment puts her in the same channel and she acknowledges the same version at 1:54 — on her phone, from the tablet you published on.
See it arrive on the phone →What T. Alvarez reads before the session startsMaya R. · takes effect when you publish · v3 stays on the trials collected under it
| Wait before delivering | 15s → 30s |
| Note the transition on every elopement | Added |
| Prompting gestural, after two unsuccessful trials | Unchanged |
| Mastery across two staff | 80% / 3 days |
By the time you open Maya again the trials from that afternoon are in the graph, stamped v4 so the change stays visible in the data. The note is in your queue with the session beside it, and the caregiver update is drafted from what happened — ready for you to edit and approve. Nothing goes to Elena that you have not read.
What this releases downstream →The note is what makes the claim readyT. Alvarez · submitted 5:33 PM · ran under Tolerating delay v4
Across those moments Cue measured Maya against her own history, put the confounds on the same screen as the signal, carried the version through to the trials, reconciled who was in the conversation, and drafted the note and the caregiver update from the session.
It did not interpret the data, choose the intervention, co-sign anything, or message a family. An acknowledgment records that a technician read a version. It is not a measure of how the session was run.
The assessment builder walks a protocol and scores as you go, setting the baselines. The treatment plan proposes goals and recommended hours for the payer. The progress report drafts what happened over a period from the trials already collected. They are not interchangeable, and Cue keeps them apart. Supervision hours, protocol versions, the co-signature queue and search across the whole record run on the same connections this story used.
The demo runs on sample data — the clinical walkthrough opens on the co-signature queue. Cue is invite-only while we onboard clinics one at a time.