The problem
A governing board receives an inspection-data report, an inspection outcome and a school improvement plan every year. Each is dense, each is a PDF, and each is read once by the people who already understand it. The board is supposed to question, prioritise and follow up. Mostly it files.
What I built
Four connected workflows, each written up separately as a note.
Inspection-data PDFs become reviewable measures with page provenance and short views for different board audiences. One recorded example extracted a hundred and sixteen measures and chose thirteen for the short view, with cohorts, dates and uncertainty kept visible.
Inspection reports become priorities and practical questions that keep their report dates and source links. Evidence from a predecessor school is handled separately, because an academy conversion can otherwise make an old finding look current.
Improvement plans go through extraction, operator review and explicit release. Governors receive the reviewed plan, while a later revision stays separate until it is ready. Each priority gets a generated page with milestones, leads and questions.
Delegation closes the loop. Private task links let a governor save progress, supply evidence and record an outcome without onboarding to the portal. The school reviews the submission before it counts, and the work links back to the plan and the board record.
What you can see
A priority page generated from a synthetic school's plan. One sheet a governor can take into a meeting.
The result
The transformation from document to evidence a governor can inspect and question. The publishing lifecycle around extraction, so a half-finished revision never reaches a board. The handling of chronology and identity, which is what separates this from a generic summariser.