Keeping Published and Displayed School Policies Current
Publishing or displaying a school policy once is the easy part. Printing the Child Safeguarding Statement and pinning it to the noticeboard, or uploading a policy PDF to the school website, takes ten minutes. Keeping that displayed or published version current - so it always matches the version the Board of Management (BOM) most recently approved - is where most Irish schools struggle.
The problem is rarely a lack of policies. Most schools have the required policies, properly approved at some point. The gap opens later, when something changes: a scheduled review date arrives, a Department of Education circular requires an update, the BOM re-adopts the Child Safeguarding Statement (CSS) after its annual review, or a patron or trust body issues a new template. Each is a trigger that should prompt an update to the displayed and published version - and each is also a point where schools quietly fall behind.
Without a system for handling these triggers, updates happen reactively - usually under inspection pressure, and usually after the gap has already existed for months. This article sets out the four main triggers, a repeatable update workflow, and the version control basics that keep displayed and published policies aligned with what the BOM has actually approved.
Trigger 1: A scheduled review date arrives
Every school policy should carry a next review date, set when the BOM approves it. In principle, this makes the review cycle predictable: the date arrives, the policy is reviewed, updated if necessary, re-approved by the BOM, and the displayed or published version replaced.
In practice, the common failure is simple - the review date passes and nobody notices. The displayed and published versions become quietly overdue, and the gap is usually spotted by an inspector or a new BOM member rather than the school itself.
The fix is to stop relying on memory. Review dates belong in the governance calendar, not just on the policy document. When a review date is four to six weeks away, it should surface as an upcoming action for the principal - enough lead time to get it onto a BOM agenda before the date passes. Once the BOM approves the reviewed policy, the displayed and published version should be replaced within five working days. See creating a school governance calendar.
Trigger 2: A Department of Education circular
Circulars frequently require schools to review or update specific policies - admissions, attendance, health and safety, or safeguarding-related policies are common examples. The intended sequence: the circular arrives, the principal triages it, identifies which policy it affects, schedules a BOM review, and the updated policy replaces the displayed or published version.
The failure mode here is one of the most common gaps Edvance sees in Irish schools: the circular is received and noted, but the follow-through stops there. The school can point to the circular in an email folder, but the noticeboard and website still show the pre-circular version.
The fix is to make circular triage produce a written output every time, not just a mental note - recording which policy is affected, who will update it, when it goes to the BOM, and who updates the display and website once it's approved. See how schools can stay on top of Department of Education circulars.
Trigger 3: Annual CSS review and BOM re-adoption
The CSS must be reviewed at least annually and formally re-adopted by the BOM. It is one of the highest-stakes publication obligations any Irish school carries, being both legally required and expected to be physically on display and readily accessible to parents, staff and visitors.
The failure mode is specific and recurring: the BOM re-adopts the CSS on schedule, the minutes correctly record it - but the displayed copy in reception or on noticeboards remains the previous year's version. The governance step happened; the publication step didn't.
The fix is to treat the CSS display update as a standing post-BOM action, not a discretionary follow-up. Within five working days of re-adoption, the displayed CSS should be updated, and the Designated Liaison Person (DLP) should confirm and record that this has been done. See the annual child safeguarding governance review checklist.
Trigger 4: Patron or trust body template update
Patron and trust bodies - CPSMA, an ETB, diocesan trusts, Educate Together, and others - periodically issue updated policy templates. When a new template is issued, schools are expected to adopt it through the BOM and update their displayed and published version accordingly.
This trigger is the one most easily missed, because there is no automatic notification comparable to a circular arriving with an obvious deadline. Patron communications can arrive by letter or email and look routine, and the update can sit unactioned for a full term or more.
The fix is to fold patron and trust body communications into the same circular triage process used for Department of Education circulars - identify the affected policy, assign an owner, schedule BOM adoption, and update the displayed and published version once approved.
The update workflow
Whatever the trigger, the same seven-step workflow applies. Treating every policy update this way - rather than improvising each time - is what keeps the displayed and published version reliably aligned with what the BOM has approved.
- Trigger identified - a review date arrives, a circular is received, the CSS is re-adopted, or a patron template is updated.
- Policy updated by a named owner - the principal or the relevant staff member drafts the revised policy.
- BOM approval obtained and recorded - minutes note the approval date and the version being approved.
- Displayed version updated - the physical copy in the school (noticeboard, office, reception) is replaced.
- Website version updated - if the policy is published online, the website copy is replaced to match.
- Policy register updated - the new approval date and next review date are logged.
- Old version archived, not deleted - the previous version is kept on file with its own approval dates intact.
This checklist works equally well pinned in the school office or built into a policy register template - the point is that it applies uniformly, regardless of which trigger set it off.
Version control basics for Irish schools
Every published or displayed policy should carry four pieces of information: the title, a version number or date, the date of current BOM approval, and the next review date. This lets anyone - a staff member, a parent, or an inspector - see at a glance whether they're looking at the current version.
When a policy is updated, the old version should be archived rather than overwritten. Version history is something inspectors can reasonably ask about: if a Whole School Evaluation (WSE) inspector asks what the CSS looked like before the current version, the school should be able to produce it without difficulty.
A policy register is the practical tool that makes this manageable. A folder of files with similar names - "CSS_final," "CSS_final_v2," "CSS_final_v2_updated" - is not version control; it's a source of confusion at exactly the moment clarity is needed. A proper register tracks each policy's current version, approval date, next review date, and a link to archived prior versions in one place. See policy approval records: what Boards of Management should keep.
Common failure points and fixes
| Failure | Fix |
|---|---|
| Review date passes unnoticed | Review dates built into the governance calendar, with alerts 4-6 weeks ahead |
| Circular received but policy never updated | Written circular triage with a named action owner and BOM date |
| BOM approves new version but display isn't updated | Display update made a standing post-BOM action, actioned within 5 working days |
| Website policy is older than the displayed copy | Website update folded into the same post-BOM workflow, not a separate task |
| No version history kept | Old versions archived in the policy register, never overwritten or deleted |
These gaps account for most of the publication and display issues Edvance sees flagged in Irish schools - and each has a fix that takes minutes once the workflow exists. See common school policy publication gaps in Ireland.
FAQ
How often should displayed school policies be checked against the current approved version? At minimum, whenever a review date, circular, CSS re-adoption, or patron template update occurs. Many schools also run a termly spot-check as a safety net, particularly ahead of a known inspection window.
Who should update the displayed and published version after BOM approval? A named person - often the school secretary or principal - as a standing task, not left to whoever drafted the policy. Naming the role closes the gap between BOM approval and the physical or website update.
Does the previous version of a policy need to be kept once it's replaced? Yes. Archiving rather than deleting old versions gives the school a defensible version history, supporting governance readiness and WSE readiness if questions arise about when and why a policy changed.
What's the single biggest cause of displayed policies going out of date? The gap between BOM approval and the physical or website update. Approval is usually recorded reliably in minutes; actually swapping the displayed copy is the step most likely to be missed without a standing process.
Keeping the cycle running
Edvance helps Irish schools build the governance calendar, circular triage, and policy register habits that keep published and displayed policies aligned with BOM approval - turning a recurring source of audit findings into a routine, low-effort part of the school year. Book a governance readiness demo to see how Edvance supports that routine.
Jurisdiction note
This article relates to schools in Ireland. Specific publication and display requirements are set out in the Children First Act 2015, Department of Education circulars, and the Education Act, and patron or trust bodies may set additional requirements for schools under their patronage. This article provides general governance guidance and does not constitute legal advice. Schools should consult their patron, trust body, or legal adviser on specific compliance obligations.
Frequently Asked Questions
How often should displayed school policies be checked against the current approved version?
At minimum, whenever a review date, circular, CSS re-adoption, or patron template update occurs. Many schools also run a termly spot-check as a safety net, particularly ahead of a known inspection window.
Who should update the displayed and published version after BOM approval?
A named person - often the school secretary or principal - as a standing task, not left to whoever drafted the policy. Naming the role closes the gap between BOM approval and the physical or website update.
Does the previous version of a policy need to be kept once it's replaced?
Yes. Archiving rather than deleting old versions gives the school a defensible version history, supporting governance readiness and WSE readiness if questions arise about when and why a policy changed.
What's the single biggest cause of displayed policies going out of date?
The gap between BOM approval and the physical or website update. Approval is usually recorded reliably in minutes; actually swapping the displayed copy is the step most likely to be missed without a standing process.