Creating a School Governance Calendar
A meeting schedule tells you when your governing board meets. A governance calendar tells you what needs to be done, by when, and by whom - across the whole school year, not just on meeting nights.
Most schools have the first. Far fewer have the second. That gap is where governance stops being planned and starts being reactive: an agenda item added because someone remembered it the week before, a policy review flagged because it's already overdue, a safeguarding check chased because the link governor happened to ask.
A proper school governance calendar for maintained schools in England brings together several cycles that usually live in separate heads, folders and spreadsheets: full governing board and committee meetings, the policy review cycle, the safeguarding governance cycle, the finance governance cycle, website and publication compliance checks, DfE guidance tracking, and inspection readiness activity. Mapped onto one calendar, these stop competing for attention in the same busy week and start running to a rhythm.
This guide sets out how to build that calendar - term by term - with a practical starting template you can adapt for your own governing board.
Section 1: The building blocks of a governance calendar
Before mapping dates, it helps to be clear on what actually needs to go into the calendar. Most maintained school governance calendars are built from eight recurring elements.
Full governing board (FGB) meetings. Typically three to six per year depending on the school's constitution. Each meeting has a set of minimum standing items - headteacher's report, safeguarding update, finance/budget monitoring, pupil outcomes, health and safety - alongside items specific to that point in the year.
Committee meetings. Finance, pay, and pupil discipline committees are the most common, though structures vary by school. Committee meeting dates need to sit ahead of the FGB meetings they report into, so recommendations can be ratified in good time.
Policy review cycle. Taken from the school's policy register, this sets out which policies are due for review each term, who owns the review, and when governor approval is required.
Safeguarding governance cycle. This includes DSL/DDSL confirmation, safeguarding training review, governor assurance on the single central record (SCR), the safeguarding link governor's reporting schedule, KCSIE review and approval following the annual update, and the annual safeguarding review. For a full walk-through of this cycle, see our annual safeguarding governance review checklist.
Finance governance cycle. Budget setting, regular budget monitoring reports, the Schools Financial Value Standard (SFVS) return where applicable, and year-end reporting. See our guide to finance governance best practice for schools for more on structuring this cycle.
Website and publication review. At least once a year, someone needs to check that statutory information on the school website is current and correctly published. Our school website governance checklist sets out what to check and how often.
DfE guidance and regulatory tracking. A regular slot for triaging significant DfE updates and deciding whether any trigger an unplanned policy review. See how schools can stay on top of DfE guidance for an approach to this.
Inspection readiness. Evidence pack review, link governor visits, and periodic checks that governance documentation is in order, so the board is not assembling evidence from scratch when an inspection is announced.
Section 2: Mapping the autumn term
September
The term starts with a constitution check - are there any governor vacancies, and which terms of office are expiring soon? New governors should go through a proper welcome and induction. The first FGB meeting agenda typically covers school improvement priorities for the year, a safeguarding update, and initial budget monitoring. This is also the point to confirm DSL/DDSL details are current on the SCR, and to review the policy register for which policies fall due in the autumn term.
October/November
The finance committee should receive its first full budget monitoring report of the year. The safeguarding link governor should carry out a visit and report back. Because KCSIE is typically updated each September, this is the natural window to check whether any policy updates are triggered by the summer's DfE publications. It's also a sensible point to check website publication compliance, particularly after any summer changes to staffing, policies or statutory information.
December
The final FGB meeting of the term should cover a safeguarding update, a finance report, and a review of outstanding actions. Before the break, it's worth doing a short autumn term governance review: what's been completed, what's outstanding, and what needs to carry into spring.
Section 3: Mapping the spring term
January
Return to the policy register to identify which policies are due for spring term review. This is also a good point for a governor training review - checking who needs refresher training and scheduling it - and for collecting any outstanding link governor reports.
February/March
The finance committee should carry out a mid-year budget review. Where the school has a pay committee, this is a common point in the year for it to meet. A further website compliance check is worth scheduling here, particularly given how often statutory guidance changes mid-year.
March/April
The spring FGB meeting covers a safeguarding update, a finance report, and an actions review, followed by a short spring governance review to check progress against the annual plan.
Section 4: Mapping the summer term
April/May
For maintained schools where it applies, this is when the Schools Financial Value Standard (SFVS) return is completed. It's also the point for the annual website and publication review, and for a first look at the policy calendar for the following year.
June
The summer FGB meeting typically includes the annual safeguarding governance review, a finance year-end report, and a review of actions. This is a natural point to link into a fuller year-end governance review, assessing how the year's governance has run overall.
July
The final FGB meeting of the year should produce a carry-over list of anything unresolved, confirm next year's governance calendar, and close out any outstanding policy approvals. The governor register should be updated to reflect any changes in membership or roles ahead of September.
Section 5: Assigning ownership to calendar items
A governance calendar only works if every item has a named owner - not a generic "headteacher" label, but the specific person responsible for preparing it, presenting it, and following up afterwards.
A practical ownership split for most maintained schools looks like this:
- The clerk to governors owns the meeting cycle - scheduling, agenda preparation, and ensuring papers go out in good time.
- The SBM owns the finance reporting cycle - budget monitoring reports, SFVS preparation, and year-end figures.
- The DSL owns preparation of the safeguarding update for each FGB meeting and liaises with the safeguarding link governor.
- The headteacher owns the policy review programme, ensuring reviews happen on schedule and come to the board with a clear recommendation.
- The chair owns the governor development cycle - induction, training needs, and skills audits.
Naming owners against each calendar item, rather than leaving them as general board responsibilities, is what turns a calendar from an aspiration into something that actually gets delivered.
Section 6: Keeping the calendar live
A governance calendar drawn up in July and not looked at again until September isn't a governance tool - it's a plan that sits in a drawer.
To stay useful, the calendar needs to be treated as a live document. The clerk should flag upcoming items at the start of each term, so nobody is surprised by what's due. Any change - new DfE guidance triggering an unplanned policy review, a governor vacancy that reshapes committee membership, a safeguarding concern that brings a review forward - should be reflected in the calendar immediately, not retrofitted at the next scheduled update.
Reviewing the calendar briefly at every governor meeting, rather than only at the start and end of the year, is what keeps the board working to a rhythm instead of catching up.
A sample governance calendar template
Use this as a starting template and adapt the specific dates and owners to your school's own meeting pattern.
| Term | Month | Governance area | Specific item | Owner | Deadline |
|---|---|---|---|---|---|
| Autumn | September | Board meetings | Constitution check; first FGB meeting (school priorities, safeguarding, budget) | Clerk / Chair | Mid-September |
| Autumn | September | Safeguarding | DSL/DDSL confirmation on SCR | DSL | End of September |
| Autumn | September | Policy | Policy register review - autumn term policies due | Headteacher | End of September |
| Autumn | October/November | Finance | First budget monitoring report | SBM / Finance committee | End of October |
| Autumn | October/November | Safeguarding | Safeguarding link governor visit; KCSIE-triggered updates review | Safeguarding link governor / DSL | Mid-November |
| Autumn | October/November | Policy | Website publication compliance check | Headteacher / SBM | End of November |
| Autumn | December | Board meetings | FGB meeting - safeguarding update, finance report, actions review | Clerk / Chair | Mid-December |
| Autumn | December | Governance review | Autumn term governance review; carry-over list to spring | Chair / Clerk | End of term |
| Spring | January | Policy | Policy register review - spring term policies due | Headteacher | Mid-January |
| Spring | January | Governance | Governor training review; link governor reports due | Chair / Clerk | End of January |
| Spring | February/March | Finance | Mid-year budget review | SBM / Finance committee | End of February |
| Spring | February/March | Governance | Pay committee meeting (where applicable) | Chair / Pay committee | March |
| Spring | February/March | Policy | Website compliance check | Headteacher / SBM | March |
| Spring | March/April | Board meetings | FGB meeting - safeguarding update, finance report, actions | Clerk / Chair | End of March |
| Spring | March/April | Governance review | Spring term governance review | Chair / Clerk | End of term |
| Summer | April/May | Finance | SFVS completion (where applicable) | SBM / Headteacher | End of April |
| Summer | April/May | Policy | Annual website and publication review | Headteacher / SBM | May |
| Summer | April/May | Policy | Policy calendar review for next year | Headteacher | May |
| Summer | June | Board meetings | FGB meeting - annual safeguarding review, finance year-end, actions | Clerk / Chair | Mid-June |
| Summer | June | Governance review | Year-end governance review | Chair / Clerk | End of June |
| Summer | July | Board meetings | Final FGB meeting - carry-over list, next year's calendar confirmed | Clerk / Chair | Mid-July |
| Summer | July | Governance | Governor register updated | Clerk | End of term |
Keeping the calendar working for you, not just on paper
Building the calendar is the easy part. The harder part is keeping policy owners, review dates, board reporting cycles and evidence records connected as the year moves on - especially when governor membership changes or DfE guidance shifts mid-year. Edvance gives clerks, chairs and SBMs a structured way to hold the governance calendar as a live operating document: owners assigned against each item, review cycles tracked automatically, and an audit trail of what was reviewed, when, and by whom. Book a governance readiness demo to see how Edvance supports schools running governance to a planned annual rhythm.
FAQ
How many full governing board meetings should we have each year? Most maintained school governing boards meet three to six times a year, set out in the school's constitution and instrument of government. What matters more than the exact number is that each meeting has a clear, planned agenda built from the governance calendar rather than assembled at the last minute.
Who should be responsible for maintaining the governance calendar? The clerk to governors typically holds day-to-day responsibility for the calendar - scheduling, flagging upcoming items and keeping papers on track - but ownership of individual items sits with the person best placed to deliver them: the SBM for finance, the DSL for safeguarding, the headteacher for policy review, and the chair for governor development.
How does a governance calendar differ for academies and multi-academy trusts? Single-academy trusts can generally follow a similar structure to maintained schools. Multi-academy trusts have additional reporting cycles - trust board meetings, scheme of delegation reviews, and cross-trust safeguarding and finance reporting - that need to be layered onto the local governing body's own calendar.
How often should the policy review cycle be checked against the wider governance calendar? At least once a term. Policies fall due at different points in the year, and DfE guidance updates can trigger unplanned reviews outside the normal cycle, so the policy register should be checked against the calendar at the start of every term, not just annually.
What happens if something on the calendar is missed? A missed item should be logged and carried forward immediately, with a revised date and owner, rather than left to be picked up "at some point." Treating the calendar as a live document - reviewed briefly at every meeting - makes missed items visible early rather than surfacing them at year-end or ahead of an inspection.
Jurisdiction note
This guide is written for maintained schools in England and is also suitable for single-academy trusts following a similar governance structure. Multi-academy trusts have additional governance layers - trust-level board meetings, scheme of delegation arrangements, and cross-trust reporting cycles for finance and safeguarding - that sit alongside, and in some cases replace, elements of the local governing body calendar set out here. MATs should adapt this template to reflect their own scheme of delegation and trust-level reporting requirements.
Frequently Asked Questions
How many full governing board meetings should we have each year?
Most maintained school governing boards meet three to six times a year, set out in the school's constitution and instrument of government. What matters more than the exact number is that each meeting has a clear, planned agenda built from the governance calendar rather than assembled at the last minute.
Who should be responsible for maintaining the governance calendar?
The clerk to governors typically holds day-to-day responsibility for the calendar - scheduling, flagging upcoming items and keeping papers on track - but ownership of individual items sits with the person best placed to deliver them: the SBM for finance, the DSL for safeguarding, the headteacher for policy review, and the chair for governor development.
How does a governance calendar differ for academies and multi-academy trusts?
Single-academy trusts can generally follow a similar structure to maintained schools. Multi-academy trusts have additional reporting cycles - trust board meetings, scheme of delegation reviews, and cross-trust safeguarding and finance reporting - that need to be layered onto the local governing body's own calendar.
How often should the policy review cycle be checked against the wider governance calendar?
At least once a term. Policies fall due at different points in the year, and DfE guidance updates can trigger unplanned reviews outside the normal cycle, so the policy register should be checked against the calendar at the start of every term, not just annually.
What happens if something on the calendar is missed?
A missed item should be logged and carried forward immediately, with a revised date and owner, rather than left to be picked up "at some point." Treating the calendar as a live document - reviewed briefly at every meeting - makes missed items visible early rather than surfacing them at year-end or ahead of an inspection.