Sooner or later a board member asks for a dashboard. Usually it's the trustee who came from the corporate world, who spends Monday morning in a performance dashboard at work and can't understand why the district he governs runs on a packet that shows up three days before a meeting.
Most superintendents hear that as a request for more access, and get nervous. Reasonably so. Board members govern, they don't manage. A trustee with a live feed into campus data is a trustee who might call a principal directly on a bad afternoon.
But listen to the request again. He's usually not asking to go deeper. He's asking for somewhere to go at all.
The problem isn't access
Think about his options when a question occurs to him.
He can wait for the board packet. It's slow, and it arrives already interpreted.
Or he can ask you. And that costs him something, because every question draws down a relationship he needs for the votes that actually matter.
So he doesn't ask. He sits on it for a month, and by the time the packet lands he's built a theory without any data in it.
That's the real problem. Not too little access. Nowhere to look.
The ceiling is the feature
A superintendent described what he wanted to me this way: a place where a board member "can only go so deep, and only sees what stays in his lane."
That's the whole design brief. Not an open window into your data warehouse. A defined room with a wall at the back.
Which means you're not building a data tool. You're building a governance artifact — a curated public view of the measures your board actually adopted, at the altitude a governing body should be looking. The limits aren't a compromise. They're the product.
A board dashboard should let a trustee answer three questions at ten at night without calling anyone:
- What did we say we'd do?
- How are we doing on it?
- What's the evidence?
And it should make a fourth question structurally impossible: how is this teacher's class performing?
Mirror the line your plan already has
Most strategic plans already mark this boundary. The strong ones mark it explicitly — some label entire columns as never board-adopted, separating what trustees voted on from what staff owns.
That line is your governance model, written down. Build it into the dashboard.
Top level: your board-adopted objectives, numbering intact. If your board debates Objective 4.2, the dashboard should say 4.2.
One click down: the key actions. Clearly staff-owned.
Two clicks down: campus execution. Real, visible, far enough from the surface that nobody confuses it for a governance matter.
Now depth matches ownership. A trustee who stays on the surface is governing correctly. One who goes two levels deep had to choose to get there — and he's reading, not directing.
You probably don't need logins
Districts assume a board dashboard needs roles and permission tiers. Most don't.
If the measures are the ones your board adopted in open session, they're already public. They're in your minutes. Putting them on a page anyone can reach doesn't expose anything — it just means your trustees, your families, and your local paper are working from the same numbers.
It also kills the permissions argument entirely. There's no tier a board member sees that a parent doesn't, so there's nothing to negotiate. The depth limit comes from what you published, not from who logged in.
Where role-based access genuinely matters — personnel, individual student data, anything in executive session — a dashboard is the wrong tool. That's what the packet and closed session are for.
What to say when he asks
Don't answer yes or no. Ask him which decisions he's trying to make.
The answer is almost always budget season, the annual review of the plan, or a question from a neighbor he couldn't answer. Each one points at a small, specific set of measures.
That set is your dashboard. Build it, publish it, tell him it's there — and then stop briefing him on it. The whole point is that he doesn't need you in order to look.
He's not trying to run your district. He's trying to do his job with better information than he has. Give him a room for it, and put a wall at the back.