Governor Board Pack
A test, a brief and a termly cadence for boards governing a technology estate.
Educave Research · August 2026 · Around 40 minutes of board time
The test
Twelve statements on visibility, challenge, provenance and continuity. Each governor answers alone, then the board compares. Where two governors disagree, the lower score is the more useful one.
The supporting brief
Read this before the meeting. It sets out what boards typically cannot see, and what to ask for instead.
- What boards can see
- In field research with trusts responsible for around 50,000 students, no board could state total technology spend across its schools to the nearest ten thousand pounds without asking the office first.
- Where exposure accumulates
- Contracts renew on a date the board rarely holds. By the time evidence of value arrives, leverage has passed. Renewal dates belong on the board calendar alongside audit and budget.
- What counts as evidence
- Task completion and staff enthusiasm are the weakest available proxies for learning. Ask for a baseline recorded before adoption, and for effect reported alongside cost, including staff hours.
- Where the human decision stays
- Model output entering a pupil record needs a named person who reviewed it. Write down which judgements the board will never delegate, and who holds them.
- What sovereignty means here
- Data residency is a location. Sovereignty is control: who holds the audit log, who chooses the model provider, and whether the institution could leave with its records intact.
Five questions to ask without notice
- What do we spend on technology across all our schools this year, to the nearest £10,000?
- Which tools are actually used, by how many staff, how often?
- What changed for pupils, measured against a baseline that existed before we bought it?
- Which contracts renew before our next meeting?
- Where does pupil data go when a tool calls an external model, and who holds the log?
Record who answers each one, and by when. If four of the five come back as we would have to ask the supplier, the board is hosting a technology estate rather than governing one.
Background reading: Brief for Decision-Makers and Extracts.
The cadence
Oversight of a technology estate holds when it has a date in the calendar. Three meetings a year is enough.
Autumn
First meeting of the year- Run the Governor Oversight Test as a board, individually, then compare scores.
- Agree the two or three improvement missions technology is expected to serve this year.
- Put every renewal date falling in the next twelve months on the board calendar.
Spring
Mid-year review- Take one unscheduled question and time how long a traceable answer takes to arrive.
- Review spend against usage for the three largest subscriptions.
- Record what the board will not delegate, in writing, and induct new governors into the estate.
Summer
Before renewal season- Run the tenancy test on the supplier the institution depends on most.
- Retake the Governor Oversight Test with the same people and compare against autumn.
- Publish what the year taught you, including null results, in a form a neighbouring school could use.
Take the test with the same people each autumn and summer. The movement is the measurement.
Download the full board pack as a PDF — test, brief and cadence in one printable document.