For behavioral health providers

Run the school program.
See the coordination work.

For program directors, operations leaders and clinical directors responsible for service delivery across a school network.

Let’s talk about your program ↗Explore this page ↓

A CLEARER PROGRAM VIEW

From schools to the whole program

Referrals

Consent

Assignments

Care starts

Service delivery · Delays · Capacity

Conceptual view · No live program data

Explore this page

At a glance

SchoolSpan is designed for regional U.S. behavioral health providers that already have clinicians and an EHR, serve roughly 10–75 schools and need to coordinate referrals, families, capacity and school relationships across locations.

Which organizations is SchoolSpan for?

SchoolSpan fits the coordination needs of nonprofit community mental health organizations, specialized school-based agencies and multi-site group practices delivering school-based or school-linked behavioral health services.

The common pattern is operational complexity across schools: referrals arrive through different channels, families need repeated follow-up, waitlists live in spreadsheets and schools need updates. The clinical team already has an EHR, but the school-facing work is difficult to see in one place.

You serve multiple school partners or districts.
Your coordinators repeatedly reconstruct referral status from separate systems.
Your program leaders need school-level visibility for service delivery and contract conversations.

If your primary need is to replace clinical documentation or billing software, SchoolSpan’s coordination focus is a different scope.

What does each provider leader need to see?

Role	Operational question	Relevant SchoolSpan capability
Operations director	Where is the next action missing?	Referral tracking, consent flags, assignments and follow-ups
School-based program director	How are our schools and districts being served?	School and district reporting; waitlist and capacity views
Clinical director	What is waiting for assignment or a care handoff?	Assignments and capacity context alongside the existing EHR
COO or founder	Where does coordination consume time and affect school relationships?	Program visibility and consistent reporting

These are operational views. Clinical judgment, staffing decisions and contract commitments remain with your organization.

How should a provider evaluate the value?

Build the business case from the work your team does today. Coordinator time saved is one part of the picture; a clearer referral journey and more consistent school communication are also useful pilot goals.

Measure	Baseline to collect	What to review during a pilot
Referral-to-first-appointment time	Dates for referral received and first appointment scheduled	Whether operational waiting time changes; track attendance separately
Consent follow-up effort	Time spent on incomplete forms and reminder outreach	Whether the team can identify missing steps more easily
School status requests	Volume of repeated update emails or calls	Whether authorized staff can find useful status themselves
Reporting effort	Time to assemble a school or district report	Whether the report can be prepared with consistent definitions

SchoolSpan does not claim a proven percentage reduction or guaranteed financial return. Compare pilot results with your own baseline, accounting for school calendars, staffing changes and referral volume.

Keep your existing EHR and clinical workflow

Your clinicians continue using the provider’s EHR for clinical documentation and billing. SchoolSpan focuses on the operational coordination between the provider team, schools and families.

During discovery, identify which information must pass between systems and who owns each step. Confirm whether a clean operational handoff is sufficient or whether a light integration is required. Specific EHR connectivity must be scoped rather than assumed.

See the SchoolSpan and EHR comparison →

What should a school-program pilot include?

A defined group of schools and a representative referral workflow.
An operational owner and the staff who handle consent and assignments.
Agreed referral stages and definitions for reporting.
School permissions and information-sharing expectations.
EHR handoff requirements and implementation scope.
A baseline, review period and a small set of success measures.

A useful pilot tests the daily workflow and gives both teams evidence for an implementation decision. Discuss scope and terms before treating a pilot as an available package.

Questions, answered

Frequently asked questions

Is SchoolSpan for providers or school districts?

The primary customer is the behavioral health provider organization responsible for services across multiple schools. Authorized school staff participate through appropriate referral and status workflows.

How many schools is SchoolSpan designed for?

The target customer serves roughly 10–75 schools. Organizations outside that range should discuss their workflow and reporting complexity during discovery.

Does SchoolSpan supply clinicians?

No. SchoolSpan provides software only. Providers bring their own clinicians and remain responsible for clinical services.

Will SchoolSpan guarantee faster appointments?

No specific timeline or improvement is guaranteed. The product is designed to reduce coordination friction; actual time-to-service depends on staffing, family response, program processes and other factors.

How is pricing structured?

Planning guidance is $1,000–$3,000 per month per provider organization, depending on school count and feature depth. Final scope and any additional fees should be confirmed in a proposal.

Let’s map your program’s next step.

Start with your schools, your current workflow and the coordination gaps you want to close.

Plan a conversation ↗

SchoolSpan works alongside your existing EHR.