Why the Gap Exists
Jordan didn't fall through the cracks.
Jordan didn't fall through the cracks.
The building had no pathway built to catch them.
A concern is raised
Jordan transferred in October. A teacher flagged a concern — submitted the form, noted it in a meeting, entered it in the system.
The pathway doesn't exist
No named owner. No timeline. No handoff protocol. No one confirmed the flag was received — because the building had no mid-year entry pathway built to hold it.
By January, still waiting
Not because anyone failed. Because when there is no pathway, the flag disappears — and the student waits for support that was never formally assigned to anyone.
The diagnostic names what the system can't see
It doesn't evaluate your leadership. It gives your team the visibility and language to understand exactly where the pathway is breaking — and what to address first.
One student. One school year. Watch what the system misses.
OCT
Arrives quietly
New student. Fall screening already happened. File hasn't transferred yet. Sits in class. Says little. Nobody flags it.
NOV
Still waiting
No pathway triggered. No one assigned. The building has no mid-year entry protocol. The student is present — and invisible.
DEC
Break
Two weeks gone. Still no file. Still no plan. Still no named person responsible for this student's support pathway.
JAN
Mid-year diagnostic runs
Universal screening finally catches what should have been caught in October. Results show significant reading gaps. Data goes to the team.
FEB
How far behind becomes clear
Four months in. The team finally sees the full picture. An intervention plan is written. Support begins — 16 weeks after arrival.
MAR
Intervention starts
Real support — finally. But the window is narrow. Five months of grade-level instruction already missed. The team works hard.
MAY
Intervention ends. Test prep begins.
The calendar takes over. Seven months after arriving, this student never had a real runway. The pathway was never built.
