Governance Actions: How to Track Follow-Up Properly
An action without an owner is a wish. An action without a date is a suggestion. And an action that reappears in the minutes three meetings running is not an admin oversight - it's a pattern, and patterns are exactly what inspectors notice.
Most governing boards are reasonably good at recording actions. Far fewer are good at tracking them between meetings. The action gets written into the minutes, the meeting ends, and the log doesn't get looked at again until someone opens the previous minutes to check what was agreed last time. By then it's often too late to have done anything differently.
This matters more than it might seem. Ofsted inspectors and governance reviewers don't need to see a perfect action log - they need to see evidence that the governing board follows through on what it agrees to do. A well-maintained action log is one of the clearest, simplest pieces of evidence a clerk can produce. It shows oversight in practice, not just oversight on paper. For more on what inspectors look for in board records generally, see board minutes and inspection evidence.
What good action tracking looks like
Good action tracking isn't complicated, but it is disciplined. Every action needs four things: what, who, when, and what happened. Miss any one of these and the action is effectively untrackable - it exists in the minutes but not in any meaningful sense in the governing board's actual work.
The key mental shift is this: the action log is not a to-do list. It's a governance evidence trail. A to-do list can sit in someone's inbox and be forgotten without consequence. An action log that goes stale is a visible gap in oversight - the kind of gap that shows up when someone reviews six months of minutes side by side and finds the same three items unresolved.
The four elements of a well-recorded action
What. The action needs to be specific enough that anyone reading it later - not just the person who wrote it down - understands exactly what was agreed. "Review safeguarding" is not an action; it's a topic. "Clerk to confirm all governor safeguarding training is current and report to chair by 14 October" is an action. It has a clear scope and a clear output.
Who. Every action needs a named individual, not a role and not the whole board. "Clerk" is a person for these purposes; "governance team" is not. If an action is recorded against "headteacher/clerk" or "all governors," it usually means nobody is actually responsible, and it will be the first thing to drift.
When. A specific target date, not "next meeting." Meeting dates move, get postponed, or get forgotten - a calendar date doesn't. "Complete by 14 October" survives even if the next meeting is rescheduled; "next meeting" doesn't.
What happened. This is the step most logs skip entirely. Every action needs a resolution note once it's addressed - even if that resolution is "not yet done." Examples: "Completed 10 October: all training confirmed current, certificates on file." Or: "Overdue - rescheduled to 15 November because the training provider cancelled the September session." A status update alone ("in progress") is weaker than a status update with a reason.
Where the action log should live
The action log needs to be accessible between meetings - not buried on page 6 of a minutes PDF that nobody opens until the next agenda goes out. If the only record of an action is in the previous set of minutes, the log isn't really being used; it's being archived.
The clerk to governors is usually the natural custodian of the log. It should be a live, standalone document - a spreadsheet, a shared document, or a dedicated system - that the clerk updates as actions are completed, not just at the next meeting. It should be shared with the chair and headteacher between meetings, not only tabled at the next governor meeting. If the chair only sees the state of open actions once every six to eight weeks, there's no opportunity to intervene when something is at risk of drifting.
How to use the action log at meetings
Matters arising should be a standing first agenda item - not an optional one that gets skipped when time is short. It's often the single most useful five minutes of a meeting from an oversight perspective, because it's where the board checks its own follow-through.
The clerk should present the action log at the start of the meeting, organised into three groups: completed, in progress, and overdue. This takes the log from a passive record into an active governance tool.
Overdue actions need more than silent carryover. Each one needs a brief explanation - why it's overdue - and a revised date. "Carried to next meeting" with no explanation is exactly the pattern that looks weak on review; "overdue, rescheduled to 15 November because the training provider cancelled the session" shows the board is managing the issue, not ignoring it.
The minutes should then reflect a short action log summary, not just a restated list. Something like: "3 actions completed, 1 overdue - rescheduled to 15 November." This single sentence does a lot of work as evidence - it shows the board reviewed its own follow-through as a matter of course. This pairs well with the discipline covered in board meeting preparation, where a clean agenda and a clean action log go hand in hand.
Overdue actions: how to handle them without letting them drift
Not every overdue action is a problem. An action that's overdue by one meeting, with a clear reason and a revised date, is normal governance life - meetings get cancelled, staff go on leave, providers reschedule training. What matters is what happens next.
An action overdue across three consecutive meetings is a different matter. At that point it's no longer a scheduling issue - it's a governance issue, and it should be treated as one. This is exactly the kind of pattern that a reviewer or inspector notices when they read several sets of minutes together.
Between meetings, the chair has a role to play. If an important action is at risk of slipping, the chair - not just the clerk - should contact the action owner directly rather than waiting for the next meeting to raise it. This is one of the simplest ways a chair demonstrates active oversight rather than passive chairing.
If an action genuinely cannot be completed as originally framed, it should be formally closed with a note explaining why - not left open indefinitely as a kind of permanent unfinished business. A closed action with a clear rationale is far better evidence than an open action that's technically still "in progress" eighteen months later.
Safeguarding and statutory actions: higher priority
Not all actions carry equal weight, and the log should reflect that. Safeguarding-related actions - a link governor visit, a training renewal, a Single Central Record check - should be flagged as higher priority in the log, and tracked separately if the volume of general actions makes them easy to lose among routine items.
Statutory actions, such as a policy review or a publication compliance check, shouldn't be allowed to drift for more than one meeting without some form of escalation to the chair. These aren't discretionary items where a delay is a minor inconvenience; they sit closer to the board's core statutory duties.
Worth noting: if safeguarding or statutory actions are repeatedly delayed, that pattern is itself a governance signal worth raising with the chair directly, separate from the individual action. Repeated delay in this category tends to indicate a capacity or prioritisation issue that's bigger than any single overdue item. This connects directly to the kind of evidence gaps covered in common inspection readiness gaps in schools.
What the action log looks like in practice
A usable action log doesn't need to be elaborate. A simple table with five columns is enough:
| Action | Owner | Due Date | Status | Resolution Note |
|---|---|---|---|---|
| Confirm all governor safeguarding training is current and report to chair | Clerk | 14 Oct 2026 | Completed | Completed 10 Oct 2026: all training confirmed current, certificates on file |
| Complete link governor safeguarding visit and submit written report | J. Adeyemi (Link Governor) | 20 Nov 2026 | In progress | Visit scheduled for 5 Nov 2026; report to follow within 10 working days |
| Review and approve updated behaviour policy | Chair, with headteacher | 3 Sep 2026 | Overdue - rescheduled | Overdue: headteacher consultation with staff delayed by start-of-term pressures; new target 8 Oct 2026 |
Note the pattern in each row: a specific action, a named owner, a calendar date, and a resolution note that explains status rather than just labelling it. This is the level of detail that turns a log into usable evidence - the kind referenced in the school governance evidence checklist.
Common action tracking failures
- Actions recorded at the meeting but the log isn't touched again until the next agenda is being prepared
- Owner recorded as "all governors," "headteacher/clerk," or another shared or role-based label rather than a named individual
- Due date recorded as "next meeting" instead of a calendar date
- Overdue actions carried forward silently, with no explanation and no revised date
- Safeguarding and statutory actions tracked with the same priority - and the same casual tone - as routine administrative items
- No resolution note when an action is marked complete, so there's no record of what was actually done
Any one of these, on its own, is a minor gap. Several of them together, sustained across a school year, is the kind of pattern that shows up clearly when minutes are reviewed as a set rather than one meeting at a time - see how governors can demonstrate effective oversight for more on what that oversight looks like in practice.
Building an action tracking habit
The most reliable fix is establishing the habit at the start of the school year, before pressure builds. Agree as a board that matters arising is a standing first agenda item, not something that gets dropped when the agenda runs long. Agree that the clerk maintains the log continuously and circulates a brief written update to the chair and headteacher mid-cycle, between meetings - not just at the next meeting. Agree that the chair reviews overdue items before each meeting, so nothing arrives as a surprise on the day.
The single most useful discipline is this: inspection should never be the trigger for reviewing the action log for the first time in months. If the log is only opened and tidied up when an inspection is anticipated, that itself tends to be visible in the gaps between entries.
FAQ
Do we need special software to track governor actions, or is a spreadsheet enough? A spreadsheet is enough, provided someone - usually the clerk - keeps it current between meetings and it's genuinely shared with the chair and headteacher, not just stored on one person's laptop. The format matters less than the discipline of maintaining it.
Who should be responsible for maintaining the action log? The clerk to governors is the natural custodian, since they're present at every meeting and responsible for the minutes. The chair should still review it regularly rather than treating it purely as clerk's business.
How many meetings can an action be overdue before it's a concern? One meeting overdue with a clear reason and revised date is normal. Overdue across three consecutive meetings is generally the point where it becomes a governance issue worth discussing explicitly with the chair, rather than simply carried forward again.
Should every action go through the full board, or can some be delegated? Many actions sit naturally with a link governor, committee, or individual named person rather than the whole board. What matters is that the log names one accountable individual for each action, even where a group is involved in the work.
What should happen to an action that turns out to be unnecessary or overtaken by events? It should be formally closed in the log with a short note explaining why, rather than left open or quietly dropped. A closed action with a clear rationale is stronger evidence of active oversight than one that simply disappears from the list.
How Edvance helps
Edvance helps governing boards maintain a live action log that stays visible between meetings - owners, due dates, status, and a clear resolution trail that's ready to show as evidence, not reconstructed under pressure before an inspection. If your board's actions tend to lose momentum between meetings, book a governance readiness demo to see how Edvance supports action tracking and follow-through as part of everyday governance practice.
This article is intended as general practical guidance for UK maintained schools and academies and does not constitute legal advice. Governing boards should refer to current DfE statutory guidance, KCSIE, and their own scheme of delegation when establishing action tracking and governance procedures.
Frequently Asked Questions
Do we need special software to track governor actions, or is a spreadsheet enough?
A spreadsheet is enough, provided someone - usually the clerk - keeps it current between meetings and it is genuinely shared with the chair and headteacher, not just stored on one person's laptop.
Who should be responsible for maintaining the action log?
The clerk to governors is the natural custodian, since they are present at every meeting and responsible for the minutes. The chair should still review it regularly rather than treating it purely as clerk's business.
How many meetings can an action be overdue before it's a concern?
One meeting overdue with a clear reason and revised date is normal. Overdue across three consecutive meetings is generally the point where it becomes a governance issue worth discussing explicitly with the chair.
Should every action go through the full board, or can some be delegated?
Many actions sit naturally with a link governor, committee, or individual named person rather than the whole board. What matters is that the log names one accountable individual for each action.
What should happen to an action that turns out to be unnecessary or overtaken by events?
It should be formally closed in the log with a short note explaining why, rather than left open or quietly dropped. A closed action with a clear rationale is stronger evidence of active oversight.