Your emergency phone system probably hasn't been tested since it was installed -- and that gap will surface at the worst possible moment.

Diesel prices are up nearly $2 a gallon year-over-year, which means transportation budgets are about to get squeezed hard.

The undocumented knowledge living in your key staff members' heads is a liability you're carrying whether you realize it or not.

---

INVISIBLE EXCELLENCE

Phone infrastructure is one of those things that gets set up once and never revisited. I've been thinking about this lately: if a staff member needed to reach emergency services from any point on your campus right now, do you actually know how they'd do it? Not in theory -- have you walked it?

Most of us assume the systems work because we've never tested them under pressure. The gap between "it should work" and "it actually works" usually surfaces during the exact moment you can't afford a gap.

The principle here is simple but uncomfortable: critical systems that haven't been stress-tested recently aren't systems you can rely on. They're assumptions. Walk through your emergency communication chain this week. Pick a random spot on campus, pick a random staff member, and see what happens. The results might confirm your confidence -- or they might show you something you'd rather find now than later.

---

UNREASONABLE HOSPITALITY

Parent trust is built on consistency, particularly in high-stakes moments: injury notifications, incident communication, pickup procedures. The problem is these processes often live entirely in one person's head.

Here's the question worth sitting with: if your key coordinator were out today -- sick, family emergency, whatever -- which parent-facing processes would break?

Not "would be slower" or "would be a little rough." Would actually break.

Timely injury notification is a good example. Parents expect to hear from the school quickly and accurately when something happens to their child. If that workflow isn't documented well enough that a backup can execute it without dropping the ball, you're carrying reputational risk in a single point of failure.

This isn't about distrust of your key people. It's about honoring the trust parents have placed in you by making sure that trust doesn't depend on one person's presence on any given day.

---

THE WEEKLY BRIEFING

1. School districts face a back-to-school math problem: The high price of diesel (District Administration)
Diesel up nearly $2 a gallon year-over-year, and 90% of the country's 480,000 school buses run on it. If you're in a district that handles its own transportation, this is a line item that's about to blow past projections. If you're at a private campus contracting transportation services, expect those contracts to come up for renegotiation sooner than planned.

2. Chromebook Classroom Management Strategy for K–12 IT Teams (EdTech Magazine K-12)
Device fleets are still growing even as post-ESSER budgets tighten. The operational reality: more devices means more management overhead, more physical workflows, more maintenance tickets. If your IT team is stretched thin, the answer probably isn't better software alone -- it's clearer protocols for what happens when devices break, go missing, or need rotation.

3. How To Run a Successful K–12 Ed Tech Pilot Program (EdTech Magazine K-12)
The useful insight here isn't "do a pilot" -- it's that pilots only work when you define success criteria before you start. Too many campuses run a pilot, decide based on vibes, and then discover the full rollout doesn't work because nobody tested whether the tool actually integrated with existing systems.

4. NYC school board rejects $1.65 million tech deal in early setback for Mamdani (Chalkbeat National)
A reminder that big tech contracts for school systems face political scrutiny that has nothing to do with operational merit. If you're ever involved in a significant technology procurement, build your case documentation like it's going to be questioned publicly -- because it might be.

5. Pa. may ban cellphones in schools. Some educators say they're already seeing results—without pouches (District Administration)
The interesting operational note: early adopters say the difference is striking, and they're achieving it without the Yondr-pouch approach. Enforcement through clear expectations and culture might be more sustainable than enforcement through physical lockout -- and it's certainly cheaper.

---

THE 2-MINUTE MOVE

Do this today: Pull up your open safety observations or walkthrough findings and identify the three that have been open the longest.

Here's why it matters: Safety findings have a way of getting logged, acknowledged, and then quietly buried under daily operations. A finding without a clear owner and deadline is just a liability waiting.

Here's exactly how: Open whatever system or spreadsheet you use to track safety walkthroughs. Sort by date opened or date last updated. For each of the three oldest items, write down: who owns it, what the deadline is, and what's actually blocking closure. If you can't answer those questions, that's your task list for this week.

---

Want to know where your campus is leaking parent trust or failing compliance before regulators or parents find out? Take our 5-Minute 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.

---