For RBTs & behaviour technicians

Your whole day,
in one hand.

The hardest job in the building usually gets the worst tool. This one is a real app for the phone in your pocket — and it keeps collecting when the signal does not.

One afternoon, on the phone in your pocket.

You are T. Alvarez. At 1:52 on Tuesday a session you were not expecting appears on your Today page, with an instruction that changed this morning. Moment by moment to the end of the day.

01

Get the assignment, and the instructions with it.

The clinic confirmed you for Maya’s 3:30 at 1:44; it is on your phone by 1:52. You did not ask anyone for access to her chart and nobody added you to a group — both came with the assignment. Your Today page still shows only what you are assigned to: no client list to search through.

Who confirmed this, and why you →The coverage gap from the clinic’s side
Cue for iPhone · also Android, iPad and the shared clinic tablet
1:52▮▮▮ ⌁
TodayTuesday Mar 3 · T. Alvarez
Eli T.Done
9:00–11:00 AM
Maya R.Added 1:44
3:30–5:30 PM · Room 2
Changed today · Tolerating delay v4
Wait 30 seconds before delivering
Note the transition on every elopement. Was 15 seconds until this morning.
Read v4 — acknowledge
TodayClientsChatNotesMe
Maya’s chart opened to you at 1:44with the assignment — you did not request it, and it closes when the assignment does
You are in her care team channelmembership comes from the assignment; nobody had to add you
The protocol travels with the sessionthe live document, not a screenshot in a group chat
Starting the session clocks you inyour hours and drive time are counted from the sessions you ran
The assignment connects the rest.
02

Read the change, and acknowledge the version.

The instruction changed at 9:14 this morning, and you are picking the session up at lunchtime. You read what changed and what stayed the same, side by side, then acknowledge — against v4 specifically, so your BCBA can see who has read this one rather than some earlier version. It records that you read it. It does not claim anything about how you run the session.

Why it changed →What D. Okafor saw in the data this morning
Cue for iPhone · Maya’s care team channel
1:54▮▮▮ ⌁
# maya-rCare team · 4 people
D. Okafor 9:14 AM
Wait 30 seconds before delivering, from this afternoon.
Program · live
Tolerating delay · v4
Opens the current version, not a copy
v3 → v4
Wait 15s → 30s
Add note the transition on every elopement
Prompting and mastery unchanged
Acknowledge v4
TodayClientsChatNotesMe
Acknowledged 1:54 PM · v4tied to the version, so nobody has to ask whether you saw the right oneSent
The attachment stays liveif the program changes again, the link opens what is current — but your acknowledgment stays against v4
The message keeps its datethe 9:14 AM message says what it said at 9:14 AM — history is not rewritten behind you
The update and the handoff stay connected. Published on a tablet at 9:14, read on your phone at 1:54.
03

Capture data as the session happens.

Trials, counts, timings and step-by-step tasks — one tap each, sized for a thumb. When something needs a second opinion you ask in the channel with the session attached, so nobody has to ask which session you mean. If you wear an Apple Watch you can stop a running timer from your wrist; the watch is optional and everything here works from the phone alone.

Cue for iPhone · in session · Apple Watch optional
4:07▮▮□ ⌁
Maya R.Waiting 30s · v4 · read at 1:54 PM
TrialsCountTimingSteps
7Asked on her own
2Elopement
0Aggression
4:12Tantrum · running
# maya-r · 4:07 PM
Both elopements were at the bell again. Count the second one?
Session · attached
Mar 3 · 3:30–5:30 PM
D. Okafor, 4:11 — Yes, count it and note the bell.
TodaySessionChatNotesMe
Cue · 4:07
Is the tantrum still happening?
Started 4:03 · 4:12
YesNo — ended
Optional. Tap no and the
timer ends at 4:07
The conversation has the context. The question carries the session, so the answer lands on the right one.
No signal in Room 2? Keep collecting.trials are stored on the phone and keep the time they happened, not the time they uploaded. The card shows Not yet synced until it reaches the server — a message you send offline waits with them.
04

Review the note, correct it, and send it.

Cue drafts the note from the trials you recorded, in the order they happened. You read it, correct what it got wrong, add what only you saw — the bell, in this case — and submit it for co-signature. It goes into your BCBA’s queue with the session data beside it. Whether they co-sign tonight or tomorrow is up to them.

Where it lands →How D. Okafor reviews and co-signs it
Cue for iPhone · session note · draft
5:33▮▮▮ ⌁
Review your noteMaya R. · 3:30–5:30 PM · draft
Waiting. Ran at 30 seconds, the new interval. She waited on 5 of 8.

Elopement. Twice, both at transitions. One tantrum, 4:12.

Asking. 7 times on her own, above her usual 5.
You added
Both transitions were the classroom bell, same as last week.
Submit for co-signature
TodaySessionChatNotesMe
The draft is built from your own trialsevery line traces to something you tapped — you are editing, not writing from memory
Submitted 5:33 PMinto D. Okafor’s co-signature queue, with the session data beside itSent
Your hours and drive time are countedfrom the session you ran — there is no second timesheetAutomatic
If you need to change it after sendingask your BCBA to return it — a submitted note is not silently editable, and the change is recorded
Run this session in the demo →Collect the trials yourself, on sample data

Six things, all used in a session or on the way to one.

Discrete trials, frequency, duration, interval and task analysis, one tap each. Offline collection that keeps the real time and shows you what has not synced yet. Whatever protocol version your BCBA published last. Your care team channel. Hours and drive time counted from the sessions you ran. And a note you review rather than write from a blank box.

What we are not going to promise: that a note never needs a correction, that a co-signature comes back the same evening, or that you will never think about work after five. Cue can make the writing shorter and the sync honest. The rest is your clinic’s to run.

The details that matter on a phone

Which devices, what works offline, how changes sync, whether the watch is required, and how a shared clinic tablet signs people out — the Apps page answers those directly.

Run a session yourself.

The demo runs on sample data — the session walkthrough puts you in the room with the trial buttons. Cue is invite-only while we onboard clinics one at a time.