Comparing safety information across a school trust

A trust report can put several schools in one table without making their information comparable. One school records every minor concern, another records only incidents that reach the office and a third has recently changed its form. Ranking their totals may look decisive while saying little about their actual position. Useful comparison begins with shared definitions and enough local context to understand the numbers.

The trust should establish its own governance responsibilities and reporting requirements. In England, the Department for Education's health and safety responsibilities guidance provides a primary reference. The approach below concerns how to organise information for an agreed oversight process, rather than defining the legal duties of any particular trust.

Agree what the report is trying to reveal

Start with the questions that central and local leaders need to answer. They may want to know where work lacks an owner, which sites need help with supplier capacity or whether repeated findings have a common explanation. These questions lead to different measures from a simple count of completed forms.

Choose a small initial scope. Comparing one type of inspection or one stage of corrective action is easier to understand than combining all safety activity immediately. Ask a local colleague from each school to explain how that process works in practice. Differences discovered now are useful design information.

Document exclusions. Some schools may not have the same facilities or activities. A site without a workshop should not appear to have missed workshop checks. Use an explicit not-applicable explanation where appropriate and avoid treating an empty cell as an answer. The central report needs to show the boundary of each comparison.

Define the terms before calculating totals

Agree what counts as a new finding, a repeat, an open action and a completed action. Include examples that distinguish similar cases. If one school closes an action when a contractor attends and another waits for review of the report, their completion figures describe different stages.

Keep reporting periods consistent and show the cut-off date. A report updated yesterday is not directly equivalent to one last refreshed several weeks earlier. Where information is late or incomplete, state that visibly. Filling the gap with an old value can make the comparison look more certain than it is.

Preserve local detail beneath the common definitions. A shared category can help aggregation while the original record explains what happened. The aim is a common language for oversight, not forcing every school to describe different buildings and activities in identical words. Staff should still be able to locate their own work.

Shared definitions are strongest when local staff help test them against real records. Photo: Kampus Production / Pexels.

Add context without burying the result

A short local note can explain a change in activity, a new reporting approach or a period of building work. Ask for the specific context that helps interpret the measure. A general narrative about how busy the school has been is less helpful than stating that a new inspection area was added during the period.

Be cautious with rates and denominators. A pupil count, staff count or building count answers different questions. Choose a denominator only if it meaningfully relates to the activity being compared, and explain its limitations. A more elaborate calculation is not automatically a fairer comparison.

Use unusual results to prompt inquiry. A school with very few reports may have fewer relevant events, incomplete reporting or a different definition. The table alone cannot determine which explanation is correct. Ask the local team and inspect a suitable sample before drawing a conclusion about performance.

Turn patterns into shared support

If several schools are waiting on similar supplier information, the trust may be able to coordinate the request or improve the specification. If one school has a clearer handover process, ask whether the approach would help others. Comparison is useful when it identifies practical support rather than merely assigning a position in a league table.

Keep ownership local where local action is required, and name the central owner for trust-level work. A shared concern can otherwise become everybody's problem and nobody's task. Record which decision belongs where so schools do not wait for a central response that was never agreed.

Do not assume a solution transfers unchanged. Different buildings, staffing and activities may require adaptation. Share the question, the arrangement tried and the evidence considered. Let the responsible local team assess its relevance under the trust's approved process, including competent input where needed.

Comparable reporting still depends on traceable local evidence and clear document scope. Photo: João Jesus / Pexels.

Protect the purpose of reporting

Avoid incentives that reward closing records regardless of outcome. If staff believe a high report count will be treated as failure, they may become reluctant to report ordinary concerns. Explain how the information will be used and invite questions about surprising results. Accuracy should be more valuable than a reassuring colour.

Keep sensitive personal information out of broad trust summaries unless the approved purpose and access arrangements require it. An operational comparison can usually discuss stages, owners and blockers without reproducing individual accounts. Use the appropriate restricted process for case information rather than treating every record as general management data.

Review the definitions after the first few cycles. Look at entries that schools classified differently and decide whether the definition or training needs improvement. Record the change so a new category does not create a misleading trend. If historical figures are not comparable, explain that break instead of presenting a seamless line.

Check a sample before broadening the report

Choose a few records from different schools and trace how each became part of the summary. Check the period, category, status and any exclusion. Ask the local owner to explain an unexpected classification. This can reveal a definition problem that would otherwise affect every chart built on the same field.

Keep corrections transparent. If a school changes a classification after review, explain whether the change affects previously issued figures. The aim is reliable information, not preserving a number solely because it has already appeared in a meeting pack. Use the trust's reporting process to communicate a material correction.

Only broaden the report when the initial scope is understood and useful. Adding more categories before resolving basic differences can multiply confusion. A smaller comparison that leads to practical support is more valuable than a comprehensive table whose apparent precision depends on inconsistent local entries and unexamined assumptions about what they mean.

Ask whether the report led to a useful decision: an owner assigned, a blocker removed or a local process improved. That is a stronger test than whether the dashboard contains more charts. Reporting within CerthixED can be discussed using these precise comparison questions. See School governor safety reports for turning the resulting evidence into a readable oversight paper.