Concerts, sports days, open days, field trips and family events are where a school’s ordinary systems meet pressure: more people, different spaces, altered routines and a schedule that is hard to pause. A risk register helps the event team plan those changes early. It should be a decision tool, not a form completed after everything is already booked.
Direct answer
Schools run safer events by starting with a proportionate risk register at planning stage, identifying the event-specific hazards, assigning one owner to each control, briefing staff and vendors from the approved version, and reviewing the register whenever conditions change. The final question is not “is the paperwork complete?” but “are the agreed controls actually in place today?”
KPM’s current safe-school guidance and its student-visit guidance should be the starting point for schools within their scope. Private and international schools should also follow their own licensing, insurer, venue, transport, safeguarding and local-authority requirements. This guide is an operational framework, not a substitute for those obligations.
Start with the event profile
Before listing hazards, write a one-paragraph description of the event: purpose, date and times, locations, expected student and visitor numbers, age groups, activities, transport, vendors, weather exposure, staff roles and emergency contact point. This profile prevents the team from recycling last year’s document while missing what has changed.
| Event change | Risk question it creates |
|---|---|
| Larger audience | How will arrival, queuing, registration and emergency egress work? |
| Outdoor venue | What is the heat, lightning, rain and shelter decision rule? |
| Off-site travel | Who performs headcounts at every transition and how are late changes handled? |
| New activity provider | What competence, insurance, safeguarding and emergency information must be checked? |
| Younger or additional-needs participants | What supervision, accessibility, medication and handover arrangements are required? |
Build the register around decisions
A useful register is brief enough to use and specific enough to act on.
| Hazard or scenario | Who may be affected | Existing controls | Extra action needed | Owner / due date | Go-no-go check |
|---|---|---|---|---|---|
| Heavy rain during outdoor sports day | Students, visitors, staff | Covered hall available | Name weather monitor; communicate move decision by 7am | Event lead / day before | Hall unlocked, PA message ready |
| Child separated from group | Students | Group lists and staff ratios | Assign headcount lead for each transition | Class teacher / briefing | Every group lead has list and contact route |
| Crowd at exit | Families, students | Normal gate staff | Stagger release and place barriers/signage | Operations lead / event day | Staff positioned before final item |
| Food stall allergen confusion | Students | Approved vendors | Obtain ingredient information and family instructions; prevent informal food sharing | Vendor lead / one week before | Menu and role briefing confirmed |
Avoid vague controls such as “be careful” or “monitor.” A control is useful only when someone can confirm it has happened. Where an action is incomplete, leave the risk visible and decide whether the event can proceed, not whether the spreadsheet looks tidy.
Include the risks that sit between teams
The easiest risks to miss happen at handovers: bus to venue, class teacher to activity leader, kitchen to event volunteer, or student to authorised adult. For each transition, decide who has custody of the group, how attendance is checked, how exceptions are communicated and who receives an escalation.
This is particularly important for younger children. Use the same distinction as the authorised-child pickup SOP: an adult who is reachable in an emergency is not automatically authorised to collect a child.
Set a simple weather and change-control rule
Most events change. The control is not predicting every change; it is deciding who can make a safe change and how it reaches everyone.
- Name the decision-maker for weather, venue, activity and schedule changes.
- Set the information they will use: official weather alerts, venue conditions, supplier updates, headcount or first-aid capacity.
- Write the trigger: for example, “pause outdoor activity when lightning is observed or official warning requires it; move to the approved shelter plan.”
- Identify how staff, families and vendors receive the updated instruction.
- Record the decision and time so the post-event review is factual.
Do not improvise sensitive parent communication in a large chat group. Use a documented route and give families the action they need: whether to arrive later, use a different gate, bring a named item, or wait for confirmation.
Brief the people doing the work
The event lead may understand the register perfectly; the usher, relief teacher and vendor may never see it. Before the event, use a role-specific briefing that covers:
- arrival time, reporting line and staff identification;
- assigned zone or group, roster and handover point;
- headcount and missing-child procedure;
- first aid, emergency exit and emergency communication route;
- weather/change decision-maker and how updates are announced;
- privacy expectations for photos, student lists and parent contact details; and
- the exact point at which staff must call the event lead or emergency services.
Give each group lead the current approved version, not a screenshot from an earlier planning meeting. The school relief-cover SOP has a useful principle for any short-notice adult joining a workflow: a focused operational brief is safer than assuming they will “work it out.”
Run a final readiness walk-through
On the day, walk the real route with the people responsible. Check gates, access routes, toilet arrangements, assembly points, shaded or sheltered areas, first-aid location, radios/phones, barriers, signage and the location of lists or emergency records. A table-top plan can be sound and still fail when a gate is locked or a temporary structure changes the exit route.
The lead should make a documented proceed, proceed-with-actions or postpone/cancel decision. Do not let sunk cost determine a safety decision.
Learn after the event
Within a few days, gather the small facts that improve the next event: incident and near-miss reports, crowd-flow notes, weather decisions, late staffing, parent questions, vendor issues and what staff had to improvise. Review the controls, not just the outcome. An event without an incident may still reveal a weak handover or an unrealistic timetable.
Keep the completed register and review in the school’s approved retention location. Do not keep unnecessary attendee lists or sensitive notes in personal drives and chat histories.
Event risk-register checklist
- The event profile reflects this year’s venue, people, programme and transition points.
- Every material risk has a named owner, deadline and observable control.
- Transport, entry/exit, headcount, collection and missing-child processes are clear.
- Weather and change decisions have an owner, trigger and communication route.
- Relevant vendors and relief staff receive a role-appropriate briefing.
- Emergency contacts, first aid and escalation routes are checked on site.
- A leader records the final proceed, amend or postpone decision.
- Incidents and near misses feed into the next event plan.
How Oodlins can help
Oodlins helps schools keep student information, attendance, staff responsibilities and parent communication connected, so event-day coordination starts from a clearer operational record. Explore school management, parent communication, and our emergency-contact audit guide.