An operational framework for explaining referral progress, delays and capacity across a school-based behavioral health program.
A useful multi-school program report separates referral activity, operational waiting time and capacity. Define stages and reporting periods consistently, distinguish scheduled from attended appointments, and tailor the detail to the authorized audience.
A weekly coordination review and a district program conversation do not need the same level of detail. Start with the audience, the reporting period and the action you want the report to inform.
For internal operations, the question may be where the next follow-up is needed. For a school or district review, it may be how referrals are progressing and where capacity constraints affect the program. Confirm the appropriate detail for each audience.
| Reporting area | Example measure to define | Decision it can support |
|---|---|---|
| Referral activity | Referrals received during the period | Understand demand entering the program. |
| Consent and intake | Referrals waiting on a required family step | Focus follow-up and review common barriers. |
| Assignments and waitlists | Referrals waiting for assignment | Review coverage and available capacity. |
| Care starts | First appointments scheduled; attendance separately if needed | Understand movement toward service. |
| Operational delay | Time between consistently defined events | Identify where the workflow is slowing. |
This is a suggested reporting framework. Confirm specific report fields, data sources and availability for the implementation.
Choose a starting event, such as referral received by the provider, and an ending event, such as the date the first appointment is scheduled. If you want to measure time until the appointment takes place, use a separate definition.
Also decide how to treat referrals that remain open, are withdrawn or do not reach the end event during the period. Otherwise a report can appear to improve simply because unresolved referrals are excluded.
School calendars, staffing coverage, referral volume and family response can differ across locations. A school-level view is useful for identifying questions, but differences should not automatically be interpreted as differences in care quality.
Pair the numbers with the operational context. If a delay has increased, ask which step is waiting and what action is available. Report definitions should be stable even when the explanation changes.
Share reports only with appropriately authorized audiences. Aggregated presentation is not by itself proof that all information-sharing requirements have been met.
SchoolSpan is designed to report service delivery, delays, capacity and results by school or district, alongside referral, consent and waitlist coordination. It complements the provider’s EHR rather than replacing clinical or billing reporting.
Confirm standard versus advanced reporting needs, district structure and any EHR handoff requirements during discovery.
Explore SchoolSpan program reporting →Review reporting tiers →A useful operational framework covers referral activity, consent and intake progress, assignments and waitlists, movement toward first appointments, operational delays and capacity, with definitions matched to the audience and period.
Specify the start event and the end event. Referral received to first appointment scheduled differs from referral received to first appointment attended. Keep the definitions separate and consistent.
Reporting can identify where to investigate. Review staffing, calendars, referral volume, family response and the stage where referrals wait before drawing conclusions about the cause.
Start with your schools, your current workflow and the coordination gaps you want to close.
Plan a conversation ↗SchoolSpan works alongside your existing EHR.