8 Reasons RBTs Like Collecting Session Data in TargetFlo

Data collection happens at a small table, with a learner who isn't waiting for an app to load. The tool has to get out of the way. Here's what RBTs tell us makes TargetFlo easy to use in a real session.

1. Today's sessions are already on the screen

Tap the scheduled session to start. No searching for the client, no picking the program.

2. Targets load in program order

The client's active targets come up in the order the BCBA set, and parent-training sessions put caregiver goals first.

3. The organization's prompt hierarchy is built in

FP, PP, M, G, and V by default — or whatever hierarchy your organization uses.

4. One tap per response, one tap to undo

Big +, −, and no-response buttons, with an undo that doesn't make you hunt through a list.

5. Timers keep running

Duration and latency clocks are based on timestamps, so they survive target switches, screen lock, and app switching.

6. Interval targets beep at each boundary

Momentary and partial-interval targets prompt you at the right time.

7. A shaky connection doesn't lose data

Taps queue and retry until the server has them, without double counting.

8. Switch devices, keep going — and enter late when needed

If a tablet dies, the session continues on another device. Sessions up to five days old can still be entered, flagged as late.

---

When the session ends, the RBT submits the data and signs the note — and the session becomes billable. See Data Collection & Session Notes.