Can Families Ask Who Wrote an ABA Session Note?

Authorship is part of the record's provenance

A useful note identifies the author, role, service date and time, entry time, setting, participants, and source of any information the author did not observe. Distinguish a direct observation from caregiver report, client report, imported data, and a prior record.

The RBT Ethics Code requires accurate documentation under supervisor direction.

Who wrote ABA session note content can vary

One person may deliver the service and write the note. Another authorized role may enter an addendum, attest to supervision, or document a separate clinical review. Keep each action and time attributable. A signature from a supervisor should not replace the original author's identity.

Ask about review and correction

If the note was changed, ask what the original showed, who made the change, why, which source supported it, and whether related data or reports were reviewed. Preserve the sequence rather than silently replacing one person's entry.

The BACB Ethics Code addresses documentation, accuracy, confidentiality, supervision, correction, and data evaluation for covered behavior analysts.

Record access has a defined scope

For a HIPAA covered entity, HHS access guidance explains access to PHI in a designated record set, subject to the rule's procedures and exceptions. That right can include clinical case notes in scope. It is not a general right to employee medical, disciplinary, or other unrelated personnel files.

The CASP public summary supports individualized evaluation in its autism-treatment scope without prescribing a note-authorship workflow.

Questions families can use

Ask who delivered the service, who observed it, who entered the note, when it was entered and signed, what came from another source, who reviewed it, whether any correction exists, and who can explain its clinical meaning.

Build the note-provenance map

The note-provenance map should show who delivered, observed, entered, reviewed, attested to, or corrected each part of a session record. Capture service date and time, entry time, author, role, observer, setting, participants, direct observation, client or caregiver report, imported data, supervisor action, signature meaning, addendum, correction, source, and explanation owner. Add the source, actor, actual date and time, current state, responsible owner, and next action so the family can reconstruct the record without relying on a generic completed label.

Use states suited to the note-provenance map: created, entered, signed, reviewed, transmitted, held, corrected, disputed, superseded, or closed with reason. Keep service delivery, documentation, clinical validity, authorization, claim release, adjudication, payment, privacy rights, and personnel matters in separate lanes.

Preserve source, authorship, and chronology

For the note-provenance map, identify who directly observed, who supplied reported information, who entered the record, and who later reviewed or changed it. Preserve actual service, entry, signature, correction, transmission, and release times. A later action should not rewrite an earlier timestamp or hide the original author.

Within the note-provenance map, label client report, caregiver report, device data, schedule, time record, clinical interpretation, and payer correspondence by source. Each note-provenance map source supports limited facts. A planned appointment does not prove every service event, and a signature does not prove that every statement is accurate.

Follow the record in order

1. Identify the service and original author. Open the note-provenance map with the exact record, event, and question.
2. Label every direct and reported source. Preserve the original and relevant source artifacts.
3. Separate entry, signature, review, and correction actions. Compare definitions, times, roles, and applicable requirements.
4. Trace clinical interpretation to the qualified role. Make any authorized change traceable.
5. Explain the family-access route without exposing unrelated personnel information. Record downstream review, family communication, and prevention.

Every rate in the note-provenance map needs a defined due or eligible cohort. Report raw counts, missing items, invalid events, late records, and unresolved discrepancies. Avoid calculating a success rate only from records that happened to be complete.

Prepare for the main complication

A supervisor signature can be mistaken for authorship, or an administrative entry can appear to be a direct observation. Keep the original writer and source visible even when another authorized person reviews or corrects the record.

When that issue occurs, return to the note-provenance map. Preserve what was originally documented, the new evidence, the person who made the decision, the effective date, and every affected graph, report, payer submission, safety action, or family update. Keep uncertainty visible until disposition.

Work through a concrete example

Amir's technician provides the service and enters observations at 4:25 p.m. The BCBA later adds a separate clinical interpretation and signs that review. A caregiver statement about sleep is labeled by source. The map lets the family see all three contributions without treating the supervisor as the original observer.

The example illustrates how to organize the note-provenance map. It does not establish a universal note field, signing deadline, correction right, payer requirement, or privacy outcome. The practice must apply the current law, payer source, professional duty, contract, and record policy that governs the actual event.

Questions families can ask about the note-provenance map

• Who delivered and directly observed the service?
• Who entered each part and when?
• Which facts came from the client, caregiver, device, or prior record?
• What did a later signer actually review?
• Who can explain the clinical meaning or correction history?

Request a written answer tied to the note-provenance map when it affects service date and time, entry time, author, role, observer, setting, participants, direct observation, client or caregiver report, imported data, supervisor action, signature meaning, addendum, correction, source, and explanation owner. If an answer remains unknown, record the source checked, responsible role, next action, due date, and consequence for any clinical, privacy, payer, or record decision.

Review downstream impact and closure

Before closing the note-provenance map, check current care, graphs, progress reports, treatment decisions, safety follow-up, supervision, authorization materials, claims, family communication, and privacy obligations that used or depended on the information. Mark reviewed and unaffected items as well as changed ones.

The note-provenance map should let another reader reconstruct how the record was built. Authorship supports accountability without proving that every statement is accurate.

Prepare the family's next action

Use the note-provenance map to tell the family what can be requested next: an explanation, accessible copy, factual correction, formal amendment review when applicable, clinical discussion, payer reconciliation, privacy review, or complaint escalation. Give the responsible contact, required information, expected response milestone, and any deadline that comes from the governing source. Keep an urgent safety or medical route separate from routine record correspondence.

Give the client or family a concise, accessible note-provenance map explanation of the disposition and available next route. Preserve the dated note-provenance map explanation, original record, and later change so another reviewer can reconstruct the sequence without exposing unrelated personnel information. Record when the explanation was delivered and whether a factual correction or unanswered question remains.

When the note-provenance map closes, identify the retained source records, applicable retention rule or policy, and future event that would reopen review. This prevents a corrected field or transmitted document from losing the history needed for later care, payer, privacy, or quality questions.