The answer arrives as an email thread.
You write to every school for the current safety statement. The replies come back over a fortnight, in as many formats as there are schools, and one of them is on a laptop belonging to someone on leave.
For Education and Training Boards
Compliance in an ETB school is run locally and carried centrally. Ark HQ gives the centre a current view of every school without taking the work, or the decisions, away from the people doing it.
Nothing in the structure is broken. The schools do the work, the Boards of Management approve it, and the ETB holds the duty. The problem is that the centre’s only instrument for seeing any of it is a request.
You write to every school for the current safety statement. The replies come back over a fortnight, in as many formats as there are schools, and one of them is on a laptop belonging to someone on leave.
A policy approved centrally last year is live in some schools, in draft in others, and in a folder in the rest. Nothing in the usual setup tells you which is which.
An HSA inspector or a Department of Education query lands at the centre. The evidence that answers it is in each school.
The reason estate software gets refused in schools is that it reads as management from the centre. This is built the other way round: the office gets the view, the school keeps the decisions.
Current state per school, per policy, per requirement — read from the work the schools are doing, not from a return they filled in for you.
A principal logs in and sees their school. Not a league table, and not the school down the road.
Policies are adopted by the school’s own Board, and the record shows who approved what and when. The estate view reports that record; it does not override it.
Procurement happens once, at ETB level. Each new school is an onboarding against that agreement rather than a negotiation of its own.
Each one stands alone. They share a design and a team, so an estate running more than one gets the joins without paying for integration work.
Drafting, consultation, Board approval and staff acknowledgement, with a sealed record of every version. At estate level you can see which schools are current on which policy.
An annual cycle of risk assessments, health-and-safety statement work, committee meetings and inspection readiness — led by our people in each school, not handed over as software.
Courses for school staff, with completion recorded per person instead of per spreadsheet. The office can see where a mandatory course has not landed.
Safe, compliant, human-led AI for teachers, SNAs and administrators — grounded in Irish education law and curriculum, and in the school’s own approved policies.
There is no estate-wide pilot. If something does not work in one school it will not work in twelve, so that is where we would start.
Usually the Director of Schools, the head of corporate services, or whoever in the Chief Executive’s office answers for health and safety. We ask what you run now and where the gaps are. If what you have is working, we will say so.
Pick the school where the problem is most obvious and the product that addresses it. Nothing else in the estate changes while that runs.
School by school, or term by term, in whatever order suits the office. The agreement is already in place, so each school after the first is an onboarding.