Documentation
ABA session notes: what goes in one
A session note has three readers, and none of them is the parent. It is written for the supervising analyst deciding whether a programme needs revising, for the technician who has the child tomorrow, and for a reviewer at a funder reading it two years later with no memory of the case and no benefit of the doubt.
Write for those three and the note is short, specific and defensible. Write for a general audience and it becomes a description of a nice afternoon, which is the most common form of a bad note.
The eight things a note has to contain.
Payer requirements differ in the details, so check your own contracts. Nothing below is unusual in any of them.
Who, when, where, how long
Client identifier, date, exact start and end times, place of service, and the rendering provider with their credential. This is the part a payer checks first and the part most commonly wrong — a note whose times do not reconcile with the units billed is a note that will be recouped.
What was actually run
The specific targets and programmes worked on during this session, named as they appear in the treatment plan. "Worked on communication" is not a target. If a goal in the plan was not addressed, the note does not need to explain itself, but the pattern across notes should show the plan being delivered.
The data
Trial-by-trial or summary data for each target run, at the prompt level used, with the measure named. This is the part that makes the note clinical rather than narrative, and it is the only part a supervisor can use to make a programming decision.
Behaviour that occurred
Instances of any behaviour on the plan, described against its operational definition, with the measure the plan specifies — frequency, duration or latency. Antecedent and consequence where they are informative.
What the technician did about it
The procedures implemented as written, and any point at which the plan was not followed and why. This is the paragraph people are most tempted to soften, and it is the one with the most clinical value.
Clinically relevant events
Illness, sleep, a new medication reported at drop-off, a change at home, an injury, a restraint if your setting uses them. These explain data that would otherwise look like regression, and they are what the next technician needs.
Caregiver contact, if any
What was communicated to the caregiver at handover and any information they gave you. Recorded because it is part of the clinical picture, not as a substitute for actually communicating with them.
Signature and time of entry
Signed by the person who delivered the session, dated when it was written. Many funders require same-day entry; almost all treat a note written a week later as evidence about the note rather than about the session.
The five ways notes fail.
Four of these are audit findings. The fifth is the one that costs you families.
It describes the session instead of documenting it.
"Ethan had a great day, he was in a happy mood and worked hard" is a sentence about the technician’s impression. It contains no target, no measure and no data, and it is unusable in supervision and indefensible in an audit. The test is whether a reader who was not there could tell what was taught and what happened.
It is copy-pasted from the last one.
Notes that are substantively identical across sessions are the single clearest audit flag in behavioural health, because they suggest the record was generated rather than observed. Templates for structure are good practice. Templates for content are the finding.
The times do not reconcile.
Start and end times must support the units billed, and must not overlap with another session by the same provider. Rounding to the nearest convenient block, or writing times from memory at the end of the week, is how a clean clinical record becomes a billing problem.
It records the plan rather than the delivery.
Listing the programmes that were supposed to run, without data or outcome, documents intent. A note has to show what was delivered and what happened when it was, including the trials that went badly.
It goes to the parent as-is.
The commonest and best-intentioned mistake. A clinical note is written for a supervisor, a colleague and an auditor, in the vocabulary those readers need. Handed to a family it reads as either impenetrable or alarming, and it is neither the reassurance nor the information they were looking for.
Two documents, one source.
The confusion between these is not a writing problem, it is a systems problem: most clinics have a place for the first and no place for the second.
Session note
Written for the supervisor, the next technician and the funder. Uses the clinical vocabulary deliberately. Includes data at the prompt level, procedural fidelity and anything a reviewer would need. Retained for years and produced on request.
Parent update
Written for the person who has had no idea how the afternoon went since drop-off. Says what happened in the words a family uses. Names one thing that was new and one thing that was hard. Arrives the same day, not at the next review.
If your answer to parent communication is currently “the BCBA summarises at the monthly meeting”, the family has gone four weeks without knowing what happened. That gap is the single largest driver of the drift that ends in cancellation, and it is covered in parent engagement and retention.
What Cliqit does and does not do.
Cliqit does not write your session notes and it is not a data collection system. Your practice management system owns the clinical record and should keep owning it — that is covered in running parent communication alongside it.
What Cliqit does is the second document: it turns what staff logged during the day into a parent-facing update that goes out the same day, without asking a technician to write anything twice.
Questions clinics ask about this.
What should an ABA session note include?
Client identifier, date, exact start and end times, place of service, and the rendering provider with credential; the specific targets and programmes run; the data collected for each, at the prompt level, with the measure named; instances of behaviours on the plan described against their operational definitions; the procedures the technician implemented and any deviation from the plan; clinically relevant events such as illness, sleep or a medication change; caregiver contact; and a signature dated when the note was written.
Can you show me an example of an ABA session note?
A usable one reads roughly: "3:00–5:00pm, clinic. Ran mand training (12 trials, 8 independent, 4 at partial physical), receptive identification of body parts (20 trials, 75% independent), and tolerating transitions (4 opportunities, 3 without protest). Two instances of the target behaviour, both at transition to table work, duration 45s and 20s, escape-maintained per plan; DRA implemented as written and both resolved without escalation. Caregiver reported four hours’ sleep at drop-off. Signed, 5:15pm." Every clause there is a target, a measure or an event. That is the difference between a note and a description.
What is the difference between a session note and a daily note for parents?
Audience, and therefore everything else. The session note is a clinical and billing record for the supervisor, the next technician and the funder, written in the technical vocabulary because those readers need it. The parent-facing daily note is written for a family who has had no visibility since drop-off, in the words they actually use. The second should be derived from what staff already logged, but it is not a simplified copy of the first.
How long should an ABA session note take to write?
Minutes, if the data were captured during the session, and half an hour if they were not. The clinics where notes take a long time are almost always the ones where the technician is reconstructing the session at the end of the day from memory and a paper sheet, which costs time and makes the record less accurate at the same time.
Do session notes have to be written the same day?
Many funders require it and most state Medicaid programmes are explicit about it, so check your own payer contracts rather than a general rule. Regardless of the requirement, a note written on the day is a better record: recall degrades fast, and a reviewer reading a note entered four days later is being asked to trust a reconstruction.
Are session notes PHI?
Yes, entirely. A session note is health information about an identified individual held by a covered entity, which is the definition. That places it inside both the Privacy Rule and — since it lives in software — the Security Rule, and it is why a note being drafted in a personal notes app or emailed from a personal address is a problem regardless of how careful the person was.
Can parents ask to see session notes?
A parent exercising a child’s right of access can generally request records the clinic holds, and the Privacy Rule sets out how that request is handled and the narrow grounds for denial. It is a formal access request rather than a routine part of communication, and the practical answer to a family who wants to know what is happening is not to hand them clinical notes — it is a daily update they can actually read.
Should technicians write both a session note and a parent update?
Asking for both, by hand, is how the second one stops happening by Thursday. It is not a discipline problem: the technician has thirty seconds between transitions and two documents to produce, and the one nobody audits is the one that gets dropped. The workable arrangement is that the parent update is generated from what was already logged for the clinical record, so writing it is not a second task.
Related
Show us what you are using now.
Fifteen minutes. If what you have works for your caseload, we will tell you to keep it.