There's a Google Site somewhere in your district that someone built four years ago with the best of intentions.

It has a tab for HR documents. Maybe a staff handbook. A page that says "Welcome Back!" with a photo from the 2021 school year. And somewhere buried in the navigation, a link to a form that probably no longer works.

Nobody checks it. Nobody updates it. And yet, when someone asks where staff go for internal information, that's the answer.

This is the state of internal communication in most K-12 school districts and it's not because districts don't care. It's because the tools they've been handed were never actually built for the job.

Walk into almost any district communications team and you'll find a version of the same setup: a static webpage or shared drive acting as the "staff hub," a few email threads that have become the de facto communication channel for important updates, and a collection of documents scattered across platforms that no single person is fully responsible for maintaining.

It works, until it doesn't. Staff stop checking the static page because it's never current. Important updates get buried in inboxes. A new employee has no idea where to find the staff handbook. A building principal sends a campus-wide update through a text chain because there's nowhere better to put it.

The information is out there. Somewhere. But finding it requires knowing who to ask, which platform to check, and whether what you find is actually still accurate.

That's not an intranet. That's information scattered across five tools, stitched together with good intentions and a lot of manual effort.

The cost of this setup isn't always visible and that's part of what makes it so persistent. Nobody files a complaint that the Google Site is out of date. Staff just stop using it. Nobody reports that the all-staff email didn't land. Leaders just assume it did.

But the costs are real:

Staff miss critical updates because there's no single trusted source of truth. Important policy changes, calendar updates, and operational announcements get lost in inboxes or never reach the people who need them.

Leaders have no way of knowing whether communication is working. Did staff read that update about the new safety protocol? Was the HR policy change seen by everyone? Without any data, there's no way to know and no way to improve.

Ad-hoc tools create security and compliance risk. When sensitive HR information lives in a shared Google Drive or gets discussed over personal email, you lose control of who sees what and when.

Adoption stays low because no one trusts the system. Staff learn quickly that the intranet is outdated, so they stop checking. When they stop checking, it becomes more outdated. The cycle continues.

The definition of an intranet is simple: a private, internal network for an organization's staff. But the way that's been interpreted in K-12 for the past decade — a static webpage with some documents on it — falls dramatically short of what that actually means in practice.

A real staff intranet isn't a page. It's a hub. And the difference matters.

A hub is where staff go not just to find a document, but to stay connected to what's happening in their district or school. It's where a superintendent can share an important update and know (actually know) that it reached the people who needed to see it. It's where a principal can post a campus-specific announcement without it flooding district-level feeds. It's where a new staff member can find everything they need on day one without asking five different people.

It's organized. It's current. And critically — it's somewhere staff actually go, because the information there is reliable enough to be worth checking.

Here's the piece that most "intranet" tools have never had: a way for staff to participate, not just receive.

Every tool districts have used for internal communication; Google Sites, SharePoint, email, shared drives, flows in one direction. Information goes out. Leaders send and hope. There's no reaction, no response, no feedback loop.

That's not how communication actually works. And it's a big part of why internal communications feel so disconnected from the culture districts are trying to build.

When staff can react to an announcement, comment with a question, or message a colleague directly — communication stops being a broadcast and starts being a conversation. Adoption goes up because the tool feels alive. And leaders gain something they've never had before: real visibility into whether the message landed.

The best internal communication tool in the world doesn't work if nobody uses it. And getting staff to adopt a new platform is one of the hardest things a communications team can ask of a district.

The single biggest driver of adoption is convenience. Staff will use the tools that are already part of their day and they'll ignore the ones that require a separate login, a new workflow, or a mental shift to remember to check.

This is why where an intranet lives matters as much as what it does. A staff hub embedded in a platform staff already use for communication, for updates, for staying connected to the district has a fundamentally different adoption curve than a standalone tool that requires staff to go somewhere new.

Most K-12 districts don't have an intranet problem. They have a definition problem. The tools being used for internal communication were never built for genuine two-way staff engagement and the gap shows up every day in missed updates, disengaged staff, and leaders who have no idea whether their communication is working.

Fixing it doesn't require a massive technology overhaul. It requires a different kind of tool, one built around how K-12 districts actually communicate, organized around real org structures, and designed for the staff who need to use it every day.

That's what a real staff intranet looks like. And it's long overdue in K-12.