If a compliance officer walked onto your campus today, would your front desk know exactly what to do -- and could they find the documentation within five minutes?

Your dismissal process might be one bad afternoon away from becoming a liability you can no longer normalize.

E-Rate funding is under review, and the rationale has nothing to do with network infrastructure -- it's about whether screen time can be justified educationally.

---

INVISIBLE EXCELLENCE

There's a question I've been sitting with this week: when compliance comes knocking, does your campus have an actual protocol -- not a vague sense of "we'd figure it out," but a written playbook that your staff actually knows exists?

In my experience, this is rare. And the cost of being unprepared tends to surface at precisely the moment you can least afford it.

Here's what I mean by a playbook: Who greets the official? Who gets notified, and how fast? Where does the required documentation live, and can anyone other than the one person who "knows the system" actually retrieve it?

This isn't about paranoia. It's about recognizing that compliance gaps don't announce themselves in advance. The moment a regulatory official shows up unannounced is not the moment to discover that your visitor policy has been improvised by whoever happens to be at the front desk.

The same logic applies to escalation clarity more broadly. When a staff member encounters a safety concern, a compliance issue, or an unexpected visitor with authority, do they know exactly who to notify? If the answer depends on who happens to be nearby, that's a gap worth addressing before it costs you.

Building a simple, visible escalation chain is low-effort and high-return. The hard part isn't creating it -- it's making sure people know it exists.

---

UNREASONABLE HOSPITALITY

Dismissal is one of the highest-risk moments of the school day. You're moving large numbers of students, vehicles, and families through a compressed window of time, and the margin for error is thin.

Here's the uncomfortable question: if an outside authority observed your dismissal today, would they see a controlled, documented process -- or a system held together by habit and goodwill?

I've noticed that campuses often develop workarounds over time that become routine without ever being examined for safety or legal exposure. The parent who always parks in the fire lane because "they're quick." The staff member who waves cars through without checking the pickup list because they recognize the faces. The bottleneck at the side gate that people just accept.

From a parent-trust perspective, dismissal is also one of the most visible moments of your operation. Parents see it every day. They form opinions about your competence based on whether it feels orderly or chaotic, whether their child is accounted for or not.

The question isn't whether your dismissal "works" most days. The question is whether it would hold up to scrutiny on a bad day -- and whether you've ever examined it with fresh eyes rather than letting habit stand in for policy.

---

THE WEEKLY BRIEFING

E-Rate Funding Under Review Over Screen Time Concerns (EdTech Magazine K-12)
The FCC is reconsidering E-Rate, and the rationale isn't about budgets -- it's about whether network-funded screen time can be tied to educational purposes. For operators, this matters because your connectivity infrastructure may depend on funding that's suddenly being questioned on philosophical grounds rather than fiscal ones. Worth tracking, especially if your tech stack assumes E-Rate continuity.

When In-House Break/Fix Works (and When to Call for Backup) (EdTech Magazine K-12)
Every campus has the closet of broken devices that no one has time to fix. This piece gets at a real operational tension: when does handling repairs internally make sense, and when does it become a liability? If your IT team is already stretched thin, those devices aren't just cluttering a room -- they're quietly accumulating into a maintenance debt that will come due eventually.

Michigan Schools Roll Out New Cellphone Restrictions (Chalkbeat National)
Michigan is implementing policies restricting student cellphone use during instruction for 2026-27. For operators, this isn't just a policy question -- it's a logistics question. Where do phones go? Who enforces it? What happens when a parent calls during class? The policy might come from above, but the operational reality lands on your desk.

Nebraska District Asks Police to Stop Using Electric Shock Gloves on Students (District Administration)
Omaha's Bellevue district is asking police to stop carrying electric shock gloves on campus; the police department said no. This is a stark example of the tension between campus authority and law enforcement protocols. If you have officers on campus, do you actually know what equipment they carry and under what circumstances they'd use it?

---

THE 2-MINUTE MOVE

Do this today: Audit one camera on your security system -- not to confirm it's on, but to confirm it would actually be useful.

Here's why it matters: Security camera systems often have more gaps than leadership realizes -- blind spots, image quality that won't hold up to scrutiny, settings that haven't been reviewed since installation.

Here's exactly how: Pick one camera that covers a high-traffic or high-risk area (main entrance, parking lot, dismissal zone). Pull up the live feed and recorded footage. Ask yourself: Is the image quality clear enough to identify a face or license plate? Is the angle actually capturing what you think it's capturing? When was the last time anyone reviewed whether this camera's placement still makes sense? Document what you find. Then decide if you need to do this for every camera before the semester gets away from you.

---

Want to know where your campus is leaking parent trust or failing compliance before regulators or parents find out? Take our Campus Risk & Trust Check. It gives you an instant Campus Intelligence Score with a breakdown across all 6 operational domains, plus your red-flag count.

---