School Policy Publication in Ireland: Public, Internal and Inspector Access

Most Irish schools have policies in multiple places: on the school website, in a shared folder, attached to emails sent months ago. The result is that the version a parent reads on the website may not match the version the board approved last term, and the version shared with an inspector may include an advisory note that was never meant to leave the building.

Getting policy publication right is a governance question: who should see which version, at which point in the policy lifecycle, and through what channel. This article sets out a practical framework for what to publish publicly, what to keep internal, and what to make available to inspectors.

Why Policy Visibility Matters

Under the Education Act 1998 and associated regulations, Irish schools have specific obligations around making certain policies available — to parents, to staff, and to inspectors. The Child Safeguarding Statement, for example, must be made available to parents and to any person who requests it, and must be displayed in a prominent position in the school. Admissions policies are required to be publicly available under the Education (Admission to Schools) Act 2018.

Beyond the statutory requirements, publication matters because:

  1. Parents and prospective families expect to be able to find current policies on your school's website
  2. Inspectors may check whether the version on the public website matches what is held in the governance record
  3. Sharing outdated or unapproved versions creates a credibility problem that is difficult to explain

The publication question is not just "is this policy online?" — it is "is the version online the one the board approved, and does it reflect the school's current practice?"

Public Policies vs Internal Governance Documents

Not every document produced during a policy review should be in the public domain. Schools need to distinguish between three categories:

1. Publicly published policies — finalised, board-approved versions the school is required or chooses to make publicly available. Examples: Child Safeguarding Statement, Anti-Bullying Policy, Admissions Policy, Code of Behaviour, Data Protection Policy.

2. Internal governance documents — records that support the governance process but are not for public consumption: board minutes, finance reports, consultation records, policy analysis notes, and draft versions under review.

3. Inspector-accessible documents — finalised and approved policies where the full governance record, including approval history and review evidence, is relevant for inspection. These sit between public and internal.

Why Drafts and Advisory Notes Should Not Be Published

During a policy review process, a school may generate drafts, AI-assisted analysis, consultation summaries and advisory notes. None of these should appear on a public website or be handed to an inspector as the current policy.

There are two specific risks:

The credibility risk. A draft policy circulated for consultation is not the school's position. If it is accessible publicly or included in an inspector access pack, it creates ambiguity about what the school actually does.

The governance record risk. Advisory notes and intake analysis are generated to support the principal in making decisions. They are not governance decisions. Publishing them implies they carry an authority they do not have.

The rule is straightforward: only finalised, board-approved versions of policies should be published externally. Drafts, working documents and advisory analysis stay internal.

Inspector Access: A Safer Alternative to Email Attachments

The traditional approach to sharing policies with an inspector involves emailing documents, attaching a ZIP file, or printing everything for a table. Each creates problems: email attachments leave you with no control over what version is circulating; printed copies may be out of date before the inspection; shared drives often contain a mix of drafts and approved documents with no clear indication of which is current.

A more structured approach is a dedicated, read-only access link that surfaces only finalised, approved versions of the policies relevant to the inspection — created for the inspection, showing only what the school has explicitly included, and revocable when the inspection concludes.

Edvance provides an inspector access link feature (/inspect/policies/:token) that allows principals to select finalised policies and generate a secure, time-limited share URL. The inspector sees a curated, read-only view of approved policies — no drafts, no advisory notes, no unrelated internal documents. Access can be reviewed and revoked from the principal dashboard.

This approach is both safer and more professional than email-based document sharing.

How to Keep Published Policies Aligned with Approved Versions

The most common gap in school policy publication is version drift: the policy on the website was approved two years ago, but a revised version was approved at the October board meeting and never uploaded. The website version is the one parents read. The approved version is in a folder on the principal's desktop.

To prevent this:

  1. Establish a single publication workflow. When the board approves a policy, the principal or secretary should update the published version as a standard step — not a separate task that gets deferred.
  2. Keep a record of which version is published. "Uploaded to website 3 Nov 2024" should appear alongside "Approved by board, October board meeting."
  3. Review your published policies list at least annually. Check that what is on the website matches what has been approved.
  4. Remove superseded versions. An older version remaining publicly accessible after a new one has been approved is a governance problem.

Edvance's public portal (/public/:tenantSlug/policies) publishes only the versions that a principal has explicitly marked for public visibility — it does not surface drafts, superseded versions or internal documents by default.

Common Mistakes Schools Make When Sharing Policies Online

Based on the patterns that emerge during inspections and governance reviews, the most frequent errors are:

  1. Publishing a draft instead of the approved version. This happens when the version used for consultation is uploaded to the website without going through the formal approval step.
  2. No date of review visible. Parents and inspectors cannot tell whether a policy is current if there is no review date. A policy published in 2019 with no indication of when it was last reviewed raises an immediate question.
  3. Inconsistent policy names. A policy called "Behaviour Management Policy" on the website but "Code of Behaviour" in the board minutes makes it harder to confirm the two are the same document.
  4. Advisory analysis included in inspector packs. Notes produced during the review process — particularly any AI-assisted intake analysis — should never be shared externally.
  5. Sharing policies by email for every request. Each email creates a new copy outside your control. Inspector access links solve this problem without creating a document management burden.

How Edvance Supports Policy Publication

Edvance separates the policy governance record from the publication layer. Principals work through policy review, consultation and board approval in the governance workflow. Only when a policy version is finalised and explicitly published does it appear in the public portal.

Inspector access links are generated from within Edvance, selecting specific finalised policies to include. The inspector receives a read-only view of approved versions only. Access is logged, and the principal can revoke it when the inspection ends.

For a broader view of your school's policy compliance position, see the School Policy Review Checklist for Irish Schools and School Inspection Preparation in Ireland.

Use Edvance to publish approved policies and create secure inspector access links — register at app.edvance.ie.