You followed the story.
Here's the system behind it.

She transferred in October. Reading two years below grade level. Attended every day. Never referred. Never flagged. Never supported. By February, she was three years behind and the referral finally came — not because the system caught her, but because a teacher stayed late and noticed something felt off.

The problem wasn't care. The problem was no flagging protocol for incoming transfers. No trigger. No owner. No timeline. The flag that should have appeared on Day 1 disappeared before it was ever written.

This is Checkpoint 1. The infrastructure that sees every student — including the ones who are quiet, compliant, and easy to miss.

She knew AI was already happening. Teachers were using it to draft communications, generate reports, summarize meeting notes. She wasn't against it — she could see the time it saved. But she was the one responsible for staff and student safety, and she had a growing sense that someone was going to do something they shouldn't, and no one would know until it was too late.

She wanted to get ahead of it. She just didn't know what, specifically, to caution against. "Don't use AI with student data" was too broad — staff would ignore it or work around it. She needed something concrete. What counts as student data? Which tools are safe? What does a violation actually look like before it happens?

The answer isn't a policy. It's a protocol. The three questions that determine whether any AI use is safe: What data is in the prompt? Who can see the output? Where does it go after? When staff can answer those three questions before they hit send, the risk drops to near zero — and the principal has something she can actually teach, monitor, and enforce.

This is Checkpoint 2. The STRIP · STRUCTURE · SEND™ protocol gives every staff member a decision framework they can run in 30 seconds — and gives the principal the language to lead the conversation before something goes wrong.

The referral was submitted. The team meeting was scheduled — four weeks out. The assessment took two weeks. The placement decision took another two. He started receiving support 47 days after the flag was raised, and by then he had missed six weeks of instruction he needed.

No one was slow. No one was negligent. The system just had no deployment timeline. No named owner. No hard start date. No accountability protocol. The 47 days were entirely predictable — and entirely preventable.

This is Checkpoint 3. The 5-day deployment protocol that moves students from identified to supported before the window closes.

She was in a Tier 2 reading intervention. Twice a week. Pull-out. The interventionist was dedicated. The materials were research-based. Twelve weeks later, the quarterly data review showed she had made no measurable progress.

The intervention team was surprised. The data wasn't — it had been there the whole time. But nobody had a weekly review protocol. Nobody was watching. The system assumed "placed" meant "supported." It doesn't.

This is Checkpoint 4. The Leader Line of Sight protocol that tells you — in 15 minutes per week — exactly who is progressing, who is plateauing, and who needs a plan change right now.