School leaders are careful with money. That's just the nature of the job: superintendents answer to elected boards, while independent school trustees answer to parents who pay tuition and expect transparency. Fiscal caution in K–12 and independent schools is accountability.
So when a communications modernization project stalls — and they stall often — it's easy to read that as a failure of vision. It usually isn't.
The fact is, the case for modernizing phone systems and communications infrastructure is almost always a capital expenditure argument: here's what new looks like, here's what it costs, here's a three-year ROI projection.
That framing puts the burden of proof on the new thing. And in school environments where budgets are tight and the existing system is, technically, still working, that's a hard case to win.
There's a better argument. It just requires asking different questions.
The Cost That Doesn't Show Up on a Budget Line
Legacy communications infrastructure has a carrying cost that most institutions don't calculate explicitly. Here’s where that cost lives:
- IT labor hours spent maintaining systems the vendor no longer supports
- In the workarounds staff have built over years (the group texts, the personal cell phones used for parent calls, the email chains substituting for real-time coordination)
- In the training time spent on tools that don't integrate with anything else
According to Frost & Sullivan research, 72% of education IT decision-makers identify the burden of managing too many fragmented communication tools as a barrier to efficiency. That's a pretty accurate description of what accumulated non-decisions look like from the inside: a patchwork of systems no one deliberately chose, each adding a small tax on everyone who uses them.
When you add up the tax consisting of staff time, IT maintenance, duplicate licensing fees, and the administrative overhead of systems that don't talk to each other, the cost of the current state often rivals or exceeds the cost of moving to something more coherent. The difference is that one cost is invisible and distributed, while the other shows up as a line item requiring board approval.
That asymmetry is what makes legacy infrastructure so persistent: the cost of keeping it rarely needs to be formally justified.
Safety Has Changed the Calculation
When a lockdown is called, a teacher needs to reach the office. A principal needs to reach every classroom. A district coordinator needs to reach first responders. In that moment, no one is thinking about infrastructure. They're thinking about the kids in front of them.
School safety expectations have raised the floor on what communications infrastructure must be able to do.
That means no dropped calls during a lockdown, no cloud outage taking down the phones when a weather event closes three campuses simultaneously, and no lag between an incident and a district-wide notification.
Older architectures were not designed for these requirements. Many cloud-dependent systems lack local survivability, meaning that if the internet goes down, so does the phone system. That's an acceptable trade-off in some business contexts, but in a school, it's a different kind of risk entirely.
Recognizing this frames the modernization conversation in a way that a budget discussion can't, because it means the fundamental question is whether the current system meets the safety and governance expectations the institution is now operating under.
For school board members and independent school trustees, communications resilience is no longer just an IT conversation, but a governance question. Boards that haven't had a direct conversation with their technology leadership about what happens when the system fails during a crisis probably should.
A Framework for the Conversation That Needs to Happen
For technology leaders preparing to bring this issue to a superintendent or board, the most common mistake is leading with the solution. A new platform, a managed services model, a migration path — these are answers to questions the board hasn't asked yet. Starting there usually produces a procurement conversation when what's actually needed is a risk conversation.
Three questions tend to move that conversation forward:
- What is the current system actually costing us? What is the full cost, including IT labor, workarounds, duplicate tools, and the time staff spend compensating for things the system can't do? If that number has never been calculated, doing so is a worthwhile exercise before any vendor conversation begins.
- What does a failure look like, and what’s our exposure? This question is most useful when it's specific. Not "what if the phones go down" but "what happens during a lockdown if the phones go down." Boards respond to concrete scenarios in a way they don't respond to abstract risk ratings.
- What does modernization at our pace actually mean for us? Not every institution needs to migrate everything at once. Over 65% of education IT leaders expect hybrid models (i.e., combining on-premises infrastructure with cloud services) to remain the dominant architecture through 2028, precisely because the choice between "keep everything" and "replace everything" is a false one. Understanding what's reversible, what's interoperable, and what the multi-year path looks like gives boards a direction they can actually approve.
The budget argument for modernization keeps losing because it asks institutions to justify a new cost against an invisible one. The better argument is both simpler and harder: when a parent drops their kid off in the morning, they're trusting that if something goes wrong, the people responsible will be able to reach each other. Is the current system actually good enough for that?
If you're not sure, it's worth a conversation. Get in touch with a Mitel education communications specialist now.