Task Management for ABA Intake Teams: Nothing Falls Through

Ask an intake coordinator what happened to a referral that went cold and the answer is almost never "I decided not to follow up." It is "I meant to call back Thursday," or "I thought the clinical team was handling the eval scheduling," or "the fax came in while I was out." Referral leakage is rarely a decision. It is a forgotten action.

Task management for ABA intake teams exists to make forgotten actions structurally impossible: every piece of work has an owner, a due date, and a visible state, and the work is generated by the process rather than remembered by a person. This guide covers how that works in practice and how TargetFlo's Operations & Tasks module connects tasks to the intake pipeline.

What is task management in an ABA intake context?

Intake task management is the practice of breaking each referral's journey into discrete, assignable actions — contact the guardian, run eligibility, request the diagnostic report, send the POC for signature — and tracking each one to completion with an owner, a priority, and a due date. It sits underneath the pipeline: the pipeline says where a family is, tasks say what has to happen to move them.

The key design choice is where tasks come from. Ad hoc task lists depend on someone remembering to create the task. Process-generated tasks appear automatically when a referral enters a stage.

Why stage checklists should generate tasks

A stage checklist is a definition of "done" for that stage. In TargetFlo's intake pipeline, the Insurance stage might carry: eligibility run, plan type recorded, prior-auth requirement noted. When a card enters Insurance, each checklist item becomes a task assigned to the card's owner, with a due date derived from the stage's target duration.

This does three things at once:

• Nothing has to be remembered. The task exists the moment the work becomes necessary.
• New coordinators inherit the process. They see exactly what to do without a shadowing period.
• Stage age becomes diagnosable. If a card sits in Pending Documents for three weeks, the open tasks tell you which item is stuck.

For the checklists themselves, see 9-Stage ABA Intake Pipeline: Best Practices for Therapy Centers.

The four properties every intake task needs

TargetFlo tasks carry all four, plus a checklist of sub-steps for multi-part work. A task like "Collect intake documents" can hold sub-items for insurance card, IEP, and diagnostic report, each ticked independently.

Assigning work: one owner, visible handoffs

Intake is collaborative. The coordinator owns the family's progress, but a BCBA schedules the ADOS-2, front office handles the packet, and a billing specialist may check authorization requirements. The mistake is letting ownership become ambiguous during those handoffs.

Keep the referral card owned by the coordinator throughout, and assign individual tasks to whoever does the work. The BCBA owns "Schedule ADOS-2"; the coordinator still owns the family. When the BCBA's task is overdue, both see it. When the task completes, the coordinator is notified and the card's checklist advances. Handoffs are explicit, not assumed.

Priorities that reflect ABA reality

Not all follow-ups are equal. A priority scheme for intake tasks should reflect what actually costs families and the center:

1. Urgent: authorization deadlines, expiring eligibility, a family who called twice
2. High: referrals in their first week — first contact speed predicts conversion
3. Normal: scheduled follow-ups, document chases within cadence
4. Low: cold lead check-ins, administrative cleanup

A coordinator starting their morning should be able to sort by priority and due date and work from the top. If the top of the list is always full of urgent items, that is a staffing or process signal, not a tool problem.

Due dates and follow-up cadence

Pending Documents is the stage where cadence matters most. A family actively collecting paperwork needs a touch every two or three days; a waitlisted family needs a check-in every two weeks; a cold lead perhaps monthly. Each contact should close one task and create the next, with the due date set by cadence.

When the pipeline generates the initial task and the coordinator's completion of it creates the follow-up, the cadence maintains itself. The failure mode of "I meant to call back Thursday" disappears because Thursday's task exists and shows up as overdue on Friday.

Tasks beyond the pipeline

Intake tasks are the highest-volume use, but the same structure serves the rest of operations:

• Fax triage: an unlinked fax in the fax inbox older than one business day generates a triage task
• Parent portal follow-up: a POC sent for signature but unsigned after five days creates a reminder task
• Compliance: an expiring certificate or an unsigned SOP version produces a task for the employee and their supervisor
• Onboarding and offboarding: each step in the employee lifecycle is a checklist item with an owner

Because these all live in one task system, a site coordinator's daily view is complete — not intake in one tool, faxes in another, and compliance in a spreadsheet.

Reviewing tasks as a team

A daily ten-minute standup around the task board — overdue, due today, blocked — is the single most effective operational habit for intake teams. It surfaces the stuck items while they are hours old rather than weeks old, and it gives the coordinator a forum to ask for help on a difficult family without escalating formally.

Weekly, the intake lead should look at task completion rate, average overdue duration, and open tasks per coordinator. These become dashboard KPIs alongside pipeline stage counts; how they roll up across sites is covered in Managing Multi-Location ABA Centers Without Spreadsheet Chaos.

The standard to aim for

Every open referral has at least one open task with an owner and a due date. No task is more than two days overdue without a note explaining why. Every stage checklist is complete before a card advances. When those three conditions hold, referrals do not fall through — not because the team is trying harder, but because the system does not allow the gap to exist.