Your Note Describes the Session. Does It Defend the Bill?

Here's a scenario that plays out more often than most ABA leaders realize. A behavior technician runs a solid three-hour session. The kid makes real progress. The clinical work is genuinely good. The note gets written, the claim gets submitted, the payment comes through. Everyone moves on.

Then, months or even years later, a payer pulls that same note for audit. And suddenly the question isn't "was this good therapy?" It's "does this note, on its own, prove the service that was billed?" Those are two very different questions, and a lot of clinically excellent notes can't answer the second one.

That gap has a name worth understanding: the difference between documenting what happened and substantiating what was billed. It's the single highest-stakes documentation issue in our field right now, and it's worth unpacking, because the fix is more straightforward than most people expect.

Two readers, two standards

When your clinical team reviews a note, they're asking clinical questions. Was the intervention implemented correctly? Were the treatment goals addressed? Does this reflect sound care? Reasonable questions, and a good note usually answers them.

A payer's reviewer is asking something else entirely. Does this documentation independently support the billed CPT code? Are the required service elements clearly present? Is medical necessity explicitly supported in the record? Would this note stand on its own under scrutiny?

The reviewer has no clinical context. They have just the note, the code, and a checklist. Your clinician can answer yes to every question on their side and still fail every question on the reviewer's side. The note isn't wrong. It's just written for the wrong reader.

This matters because audit activity targeting ABA has climbed sharply. Recent OIG reviews found that somewhere between 64% and 96% of ABA service months they examined lacked sufficient documentation, and those weren't agencies doing bad clinical work. They were agencies getting paid without interruption, right up until someone looked closely. I won't belabor the numbers. The point is simply that "we've always been paid" is not the same as "our notes are defensible."

What this looks like in a real note

The abstract version is easy to nod along to. The concrete version is where it clicks. A few patterns we see constantly when we audit notes:

Activities with no link to the treatment plan. A note that says "Kevin enjoyed playing board games today" describes something pleasant and entirely non-billable. Board games and lunch aren't payable on their own under a medical necessity model. The defensible version connects the activity to a goal: "BT implemented the 'asking peers questions' goal during a board game activity. Kevin appropriately asked 3 questions." Same session. One version reads like childcare; the other reads like treatment.

Time billed that the note doesn't justify. Picture a three-hour session that documents five completed activities and nothing else. A reviewer has no way to judge whether that's a full session of work or a slow afternoon. The fix is to give them a reference point, like a standard line noting roughly how many goals the BCBA expects implemented in a session of that length, and, when barriers got in the way, to document them. "Roxy engaged in 4 tantrums lasting 10+ minutes each. BT implemented response strategies from the behavior support plan to support de-escalation. As a result, we were unable to implement 4 planned goals." That note defends three hours. The bare list doesn't.

Supervision work that goes uncaptured. This one costs BCBAs constantly. A 97155 note that says "I reviewed and modified 3 of the client's programs" while billing two hours leaves most of the actual work invisible. When a BCBA reviews twelve protocols and decides eleven should continue unchanged because the client is progressing but not yet ready to advance, that is billable clinical analysis, and it needs to be on the page. Documenting "I determined the current protocols should be continued after reviewing the data and observing the client" gives the BCBA credit for the judgment they actually exercised.

Notice what every one of these has in common. The service was real. The clinician did the work. The note just didn't say enough to prove it. That's a fixable problem, and it doesn't require changing how anyone practices.

Why this isn't a training problem (exactly)

The instinct is to say "we'll train harder on documentation." But most documentation training is built around clinical accuracy: correct implementation, fidelity, supervision standards. That training is essential and it's not what's failing here. The gap is that very few clinicians have ever been shown how a payer actually evaluates a note under audit, because that standard lives outside clinical training entirely.

What closes the gap is a shared standard, one set of CPT-aligned expectations that every clinician, supervisor, and internal reviewer works from, built around the same criteria a payer applies. When everyone's writing and reviewing against the same target, internal audit findings start to reflect real external risk instead of clinical opinion. (This is exactly what we built our ABA Session Note Frameworks around: a short, CPT-specific standard your team can actually use day to day. More on that below.)

Where to start this week

You don't need a system overhaul to start narrowing the gap. Pick one CPT code and pull a small sample of recent notes. Then read them the way a payer would, with no clinical context, just the note and the code. Ask: does this prove the service? Does it justify the time? Is the medical necessity visible on the page, or is it living in your head?

That exercise alone tends to surface the patterns above pretty quickly. From there it becomes about building a consistent standard so the gap doesn't keep reopening with every new hire and every busy week.

To make that first read-through easier, we put together a free one-page self-audit you can use right now. It walks you through the exact checks a payer's reviewer applies, organized by CPT code, so you can pressure-test a sample of your own notes in about a minute each.

If you want a structured way to close the gaps across your whole organization, our ABA Session Note Frameworks walk through exactly this, one CPT code at a time, with real examples and non-examples. It's the kind of shared reference point that holds up whether it's your internal reviewer reading the note or someone else's.

When the question doesn't have a checkbox answer

Here's the honest limitation of any checklist: documentation questions rarely show up neatly. They show up as "this client's situation is unusual and I'm not sure how to document it," or "our payer just changed a policy and I don't know what it means for our notes," or "I think we have a gap but I don't know how big it is." Those are the questions that keep compliance-responsible people up at night, and they don't fit on a one-pager.

That's the thinking behind the ABA Compliance Collective. It's an ongoing, expert-guided community built specifically for ABA leaders carrying compliance without a formal compliance background. When a documentation question lands on your desk and you're not certain of the answer, you have somewhere to bring it, and get guidance grounded in both how ABA actually operates and how payers actually evaluate it, not a peer-group guess that varies by who happens to reply. Members also get compliance alerts when payer and regulatory expectations shift, a curated reference library, quarterly live sessions with Rose and me, and the Session Note Frameworks themselves are included inside. It's the difference between facing these questions alone and having a structured way through them.

The services you deliver are real. Make sure your notes can prove it, and don't feel like you have to figure out how on your own.

Michael