Who Picks up the Dropped Baton?

Autism care is delivered across multiple systems.

They don’t function as one.

That’s the problem.

"Why Autism Care Coordination Breaks" showed that no system connects care across disciplines, environments, or time. A natural question follows:

if no system connects care, can one domain—like ABA—expand to fill that gap?

ABA Organizes Work — But Only Within Its Own Boundaries

ABA providers have built highly structured operations. They coordinate intake, scheduling, authorizations, staffing, clinical programs, and billing within a shared operating structure.

Within ABA, this works—not because everything naturally aligns, but because it is actively managed to do so.

But autism care doesn’t stay within ABA.

The Moment Care Crosses a Boundary, Someone Has to Translate It

Care moves constantly—from diagnosis into ABA, from ABA into school, from therapy into the home, and from childhood into adulthood.

Each transition is a handoff.

Each handoff requires answering a simple set of questions: what is being worked on, what has changed, what matters next, and who needs to know.

That is coordination.

Not integration.

Handoffs Are Where Coordination Actually Happens

Autism care doesn’t fail because systems aren’t integrated.

It fails because handoffs don’t work.

At those boundaries, context is lost, priorities aren’t aligned, and responsibility is unclear. So coordination becomes manual, inconsistent, and dependent on whoever steps in.

In practice, that “whoever” is usually the parent.

They carry information between providers, reconcile conflicting guidance, and decide what matters next.

The system doesn’t support them.

It relies on them.

ABA Doesn’t Solve This — It Runs Into It

ABA systems usually manage workflows inside ABA well.

But their outputs don’t carry forward cleanly.

An ABA session note works inside ABA.

It doesn’t translate easily to a teacher, a speech therapist, or a pediatrician.

So the handoff still has to be created.

Platform Choice Doesn’t Remove the Problem

ABA providers structure their systems in different ways.

Many legacy SaaS platforms took a monolithic approach—bringing scheduling, clinical workflows, billing, and staffing into a single environment. That creates alignment through constraint. Everything follows the same structure, which makes coordination inside ABA easier.

Others take a more flexible approach—a spine of capabilities connected across tools. Scheduling, clinical data, and operations may live in different systems, linked through integrations or shared data. This allows more flexibility, but shifts the burden. Coordination has to be maintained across those connections.

In both cases, the focus is the same: coordinating work within ABA.

Some platforms extend beyond that—supporting multiple service lines like speech or occupational therapy in the same environment. That expands the boundary.

But it introduces trade-offs. Workflows often have to bend to fit a shared model, and the system still doesn’t extend to other parts of care—like the pediatrician or school.

So the core dynamic doesn’t change.

Coordination still depends on what happens at the boundary between modalities.

Adding Services Doesn’t Solve Handoffs

A provider expanding into OT, ST, diagnostics, or mental health increases scope.

It does not automatically improve coordination.

Because the challenge isn’t proximity.

It’s translation.

Even within the same organization, each discipline defines progress differently, use different documentation models, and operate on different timelines.

So handoffs still have to be created.

What This Means

ABA didn't solve coordination. It organized work within a boundary.

Platforms didn't solve coordination. They shaped how the work is managed.

Architecture didn't solve coordination. It changed where the burden sits.

But in every case, coordination happens in the handoffs—and today, those handoffs are inconsistent and often owned by the parent.

But the parent carrying it alone — that part doesn't have to be permanent.

If coordination is really happening in the handoffs, then improving coordination doesn't require replacing systems—or forcing them into one model.

It requires something that can sit alongside them.

Something that makes those handoffs usable.

Closing

Autism care spans systems that don’t function as one.

This is the implication:

Coordination doesn’t resolve inside a platform or architecture.

It resolves—or fails—in the handoffs between them.

Today, those handoffs are held together by parents.

The next question isn’t how to connect systems.
It’s how to make those handoffs work—without relying on parents to do it alone.