The 13-stage ABA intake workflow

Why a stage model matters

An intake pipeline is useful only when a stage represents a verifiable operating condition. “Working” is not a stage. “Benefits verified” is a stage because the team can define what evidence is required, who owns it, and what must happen next.

The purpose is not to force every payer, location, or family into an identical path. It is to create a common management language while allowing documented exceptions. The model below keeps clinical and billing records in the system of record; it organizes the operational work around them.

The 13 stages

Use entry and exit criteria for each stage. A referral should not advance because someone is optimistic; it advances when the agreed condition is met.

• 1. New inquiry — the referral is captured and a response is due.
• 2. Contact attempted — outreach has begun, with an explicit follow-up date.
• 3. Connected — the family or responsible party has been reached.
• 4. Initial fit confirmed — service area, age, service model, and basic need align.
• 5. Benefits verification — coverage and benefit details are being confirmed.
• 6. Benefits reviewed — known financial and coverage implications are communicated.
• 7. Records requested — required referral and supporting documents are outstanding.
• 8. Clinical review — appropriate clinical staff are reviewing readiness and fit.
• 9. Assessment scheduled — a date, owner, and prerequisite plan exist.
• 10. Assessment complete — the assessment milestone is complete in the clinical record.
• 11. Authorization readiness — required submission elements are assembled or tracked.
• 12. Ready to staff — administrative prerequisites are complete and service constraints are explicit.
• 13. Start scheduled — a responsible start plan and confirmed date exist.

The controls that make it operational

For each stage, define an owner role, an expected time window, an exit condition, a blocker list, and an escalation path. Record one next action rather than a paragraph of notes. Notes preserve context; a next action drives work.

Review the pipeline by exception: oldest items, items without a next action, items past their target window, and items blocked by another team. That review is more useful than reading every referral row by row.

• Do not include diagnostic detail or clinical notes in the operating layer.
• Separate “not ready” from “not a fit” and record the decision reason.
• Keep location-specific variation as a rule, not tribal knowledge.
• Audit stage definitions quarterly and whenever a payer or workflow materially changes.

A sensible first implementation

Start with a two-week sample of active referrals and map each one to the proposed stages. Ambiguity reveals where definitions need work. Then pilot with one intake team, measure stage aging and missing next actions, and refine before organization-wide rollout.

The strongest outcome is not a prettier funnel. It is a shared answer to five questions: Where is this referral? How long has it been there? What is blocking it? Who owns the next action? When will that action occur?