What Your BCBA Needs From the ABA Intake Handoff to Clinical

What "ready for assessment" means

A good ABA intake handoff to clinical means the clinical team can run the first visit without chasing anyone for anything. In practice, five things are true: the family is reachable, the right documents are on file, the payer path is known, a BCBA owns the case, and an assessment date is held. If any one of them is missing, the packet is not ready, and the handoff should not happen yet.

Most clinics treat "intake complete" as a status the intake coordinator sets. We think it should be a status the clinical team accepts. That single change turns a forwarded folder into a handoff with an owner and a clock. This post explains why handoffs stall, walks through a realistic example with numbers, and gives you the card, the rules and the weekly routine to fix it. For the whole journey from first call to first session, see the full ABA intake process.

Why handoffs stall: the evidence and what it means

Three gaps cause most stalled handoffs, and none of them is about effort.

Missing documents. The packet looks complete until the BCBA opens it and finds no referral or no insurance information.
No owner. Intake thinks the case is with clinical. Clinical has not looked at it. Nobody is wrong, and nothing moves.
No clock. Without a deadline, a packet can sit in a queue for days while the family waits and other clinics call back.

Four published facts explain why these gaps matter, and what each one means for an operator.

Demand is large and steady. The CDC's Autism and Developmental Disabilities Monitoring Network estimated that about 1 in 31 eight-year-olds was identified with autism spectrum disorder in its 2022 sample, which covered more than 270,000 children in 16 US communities. The page does not report wait times, so we do not claim any. What it means for you: families have options, and a slow handoff is a reason to take one. Every week a ready family waits is also a week of clinical capacity that could have been used.

Payer rules vary, so the packet must record the payer path. Medicaid.gov describes EPSDT as Medicaid's comprehensive health benefit for enrollees under 21, and says states determine medical necessity case by case. What it means: never assume one state's or one plan's process applies to the next family. Field 6 on the card below exists so the payer path is written down for each child, not remembered.

Clinical judgment belongs to the BCBA. Behavior analysts work under the BACB's Ethics Code for Behavior Analysts, which took effect on January 1, 2022. The page does not describe intake workflows, so this is our reading: intake should support the professional's decisions, not pre-empt them. That is why the card has a clinical acknowledgment and why intake never decides what a family needs clinically.

Handoffs are management work and need an owner. The Bureau of Labor Statistics lists the duties of medical and health services managers as including supervising staff, creating work schedules and keeping records of facility services. What it means: the handoff clock should belong to a named manager, such as the operations director or clinical director, not to "the team." Someone has to read the weekly numbers and act on them.

A worked example with numbers

Example (illustrative; not a real clinic or family). A three-location ABA group receives about 40 referrals a month. Roughly 28 reach "intake complete" each month. The group's definition of complete is whatever the intake coordinator decides, and the BCBAs open packets on their own schedule.

Over a typical month, 9 of the 28 packets turn out to be missing something that only surfaces when the BCBA tries to schedule the assessment. The gaps are ordinary: no referral on file, an unsigned consent form, a member ID photographed but never entered. Each gap takes an average of 6 business days to resolve, because the request travels from BCBA to a shared inbox to intake and back. Four of those families stop answering calls.

Now apply the card and the one-business-day rule. The same 28 packets come in. Intake fills the ten fields, and the BCBA acknowledges each packet within one business day. Three packets bounce back with the gap named. Each is fixed in an average of 1.5 business days, because the request goes straight to the person who owns it, with a due date. One family is lost instead of four.

Measure	Before the card	After the card
Packets with a gap	9 of 28	3 of 28 caught at acknowledgment
Average delay per gap	6 business days	1.5 business days
Total delay days (gaps × average)	54	4.5
Families lost	4	1

The arithmetic is simple: 9 × 6 = 54 days of delay before, and 3 × 1.5 = 4.5 after. Three families are still in the pipeline who would have gone quiet. Every number above is invented to show the method. Your own figures will differ, which is why the measurement section below tells you to collect four weeks of your own data first.

One stalled packet, step by step

Take one family from the "before" month. The coordinator marks intake complete on Monday. The packet has a signed consent form, but the referral order is a fax cover sheet with no attachment, and the insurance card photo is in a text thread rather than the record.

Tuesday: the BCBA opens the packet, notices there is no referral, and emails a shared inbox.
Thursday: intake sees the email, calls the referral source, and gets voicemail.
The following Monday: the document arrives. The assessment slot that was open last week has been taken.
The family: has heard nothing for a week, and calls another clinic.

With the card, the same packet is caught on Tuesday morning. The BCBA marks field 4 "diagnosis documentation missing," the card returns to intake with a due date of Thursday, and intake calls the referral source the same day. The family receives a short message saying one item is being collected. The slot stays held.

The same packet handled the usual way and with a named gap, owner and due date.

The Ready-for-Assessment card

Use one card per family. Intake fills in the first ten fields. The BCBA confirms the last three. The fields below are our suggested starting point; adjust them to your payers and your state, and copy the table straight into your own tracker.

#	Field	Owner	Check
1	Guardian name and two working contact methods	Intake	Reached by one method in the last 3 business days
2	Best contact times and preferred method	Intake	Recorded
3	Referral or prescription on file, if your payer requires one	Intake	File attached
4	Diagnosis documentation on file	Intake	File attached
5	Insurance details and member ID captured	Intake	Entered, not just photographed
6	Benefits and authorization path noted (who submits, when)	Intake / Billing	Named owner
7	Consent and intake forms signed	Intake	Signed copies on file
8	Location, hours and availability the family can commit to	Intake	Recorded as ranges
9	Language, access or scheduling needs	Intake	Recorded
10	Assessment slot proposed	Intake	Held on the calendar
11	Assigned BCBA	Clinical	Named
12	Packet reviewed	Clinical	Confirmed within one business day
13	Anything missing	Clinical	Listed, or "none"

Keep personal health details out of the card's free-text fields. The card tracks whether things exist and who owns them, not what they say.

The one-business-day acknowledgment and the bounce-back rule

The card only works with two rules.

Clinical acknowledges within one business day. The assigned BCBA, or a named delegate, marks the packet "reviewed" and lists anything missing. This is a check on completeness, not a clinical decision.
Incomplete packets bounce back with a reason. If the BCBA lists a gap, the card returns to intake with the gap named and a new due date. It does not sit in the clinical queue.

A packet returns to intake with the gap named and a due date, then goes back to the BCBA for acknowledgment.

Decision table: what to do with each packet

Use this table when a card arrives. The deadlines are our suggested defaults, not an industry standard.

Packet state	Action	Owner	Deadline	What the family is told
Complete, all 13 fields confirmed	Book the assessment	Intake	Same day	The date, the location and who to call
One item missing	Bounce back with the item named	BCBA to intake	Within 1 business day	"We need one more item: [item]. Here is how to send it."
No referral or order on file	Request from the referral source	Intake	Within 1 business day	That the request is out and who is following up
Payer or plan unclear	Verify the payer path before booking	Intake / Billing	Within 2 business days	That coverage details are being confirmed, with no promises
Family unreachable after 3 attempts over 5 business days	Send a final message by the family's preferred method, then pause the packet	Intake	Day 5	How to restart when they are ready

The playbook: who does what, and when

Intake coordinator, day 0: complete fields 1 to 10 and mark the card "submitted to clinical." Do not submit with a field open.
Intake lead, day 0: spot-check five percent of cards, or at least one a day, before they go to clinical. This catches the error pattern early.
BCBA or delegate, within one business day: fill fields 11 to 13. Acknowledge, or bounce back with the gap named.
Intake coordinator, within one business day of a bounce-back: resolve the item or tell the family what is pending.
Intake coordinator, every two to three business days: send the family a short status message until the date is booked.
Operations director, on day 3 of any open gap: step in, remove the blocker, or decide to pause the packet.
Operations director, weekly: review the three numbers below and pick one fix for the week.

Keeping the family informed while they wait

Families drop off when silence replaces progress. Set a cadence before the handoff happens.

At handoff: tell the family which step is next and who their contact is.
While waiting: send a short status message every two to three business days until the date is booked, even if the message is "still working on it."
When something is missing: ask for one item at a time, with a simple way to send it.

Do not promise dates you do not control. If a payer step is pending, say what is pending and who is following up. Avoid any statement about coverage you have not confirmed, and confirm EPSDT and plan specifics for each family before you tell them what to expect.

A simple message rhythm that keeps a waiting family informed until the assessment date is booked.

Common mistakes and how to fix them

Forwarding a folder instead of a defined packet. It happens because folders are easy and definitions take a meeting. Fix: agree the card once, and refuse handoffs that do not use it.
No named owner on the clinical side. Clinical teams share an inbox, so everyone assumes someone else has it. Fix: every packet gets a named BCBA or delegate in field 11 before intake submits it.
Discovering gaps at the assessment. Staff assume the paperwork is fine because intake said so. Fix: the one-business-day acknowledgment moves the discovery to day one.
Silence to the family while waiting. Staff feel they have nothing to say until the date is booked. Fix: a status message every two to three business days, even if it says "still working on it."
Measuring the wrong number. Counting "intake complete" rewards speed on the intake side and hides the delay. Fix: measure intake-complete to scheduled assessment.

Measuring the handoff, and what good looks like

You need three numbers, reviewed weekly. They fit neatly in the weekly scorecard.

Days from "intake complete" to scheduled assessment. The headline number.
Bounce-back rate. The share of packets the BCBA returns. A high rate means intake's definition of complete is wrong; fix the card, not the people.
Acknowledgment time. How long clinical takes to review. This keeps the one-day rule honest.

Set your own targets after four weeks of your own data. We have no independent source for an industry benchmark, so we do not publish one. As a starting point, here is our recommendation, not a standard:

Most packets acknowledged within one business day.
A bounce-back rate that falls week over week as intake learns what clinical needs; under 10 percent is a reasonable first aim.
Every open packet has a named owner and a due date.
No family hears nothing for more than three business days.

What software can and cannot do

Software can track the fields, remind owners about due dates, and show which packets are stuck. It cannot decide whether a family is clinically appropriate, and it should not try to. The BCBA owns that call. Use tools to keep the handoff visible, and keep the human review in the loop.

Intake handoffs also depend on your calendar. When assessment slots open up because someone cancelled, a clear process for filling open assessment slots keeps the pipeline moving. And when the family's coverage needs approval, a clean pass-off to billing matters; see authorization handoffs.

This article is for informational purposes and is not legal, billing or clinical advice.

Questions

What documents does an ABA clinic need before scheduling a family's first assessment?

It depends on your payers and state, so confirm with each payer. Most clinics need guardian contact details, insurance information, diagnosis documentation, a referral where the payer requires one, and signed consent forms. The card in this post lists them as fields so nothing is assumed.

Why do families drop off between the intake call and the first session?

Usually because the process goes quiet or asks for too much at once. Set a status message every two to three business days, name one contact, and ask for one missing item at a time. Silence is the part you can control.

How do I cut the time from referral to first ABA session at a multi-location clinic?

Measure the gaps between stages first. Many delays are in the handoff, so a definition of ready, a named owner and a one-business-day acknowledgment remove the waiting. Set targets after four weeks of your own data.

Who decides whether a family is ready clinically?

The assigned BCBA. Intake checks that documents and logistics are complete; the clinical team makes every clinical decision.