What Inspectors Actually Ask About

The call comes in. An inspection is beginning.

Most of what needs to be demonstrated is in place. The policies exist. The meetings have been held. The board has been active and engaged.

But in the opening conversation, a specific question is asked. Can you show us the decision that formally approved the current safeguarding policy?

Not the policy itself. The decision.

The board meeting where it was adopted, the record of who approved it, and confirmation that the version currently in use is the one that was formally agreed.

The search begins. The policy is found quickly — clearly marked as approved. But the decision? Somewhere in the board meeting minutes from last year. Which meeting exactly — there were three in the period that feels relevant. The safeguarding policy appears on two agendas.

In one, it was discussed. In the other, it was on the consent list — approved as part of a block. Which meeting? Both? The minutes are read carefully. The policy was approved. That much is clear. But the link between that decision and the specific version currently published — the thread from resolution to document to live policy — is not explicit. It has to be inferred.

And inspectors do not work on inference. They work on evidence.

This is not unusual. Most schools have the decisions. Most schools have the documents. The gap — almost always — is the connection between them. A decision exists. A document exists. But the trail from one to the other requires reconstruction from separate records, assembled under time pressure, and presented with the quiet hope that the inference holds.

That is the wrong moment to be building the trail.

The issue is compounded by the way governance records accumulate. Three years of board meetings. Dozens of policies reviewed on rolling cycles. Some approved individually, some in blocks, some sent back for revision and reapproved at a later date. The decision trail is not a line. It is a web of minutes, agendas, and version histories that were never designed to be navigated under pressure.

Schools that handle this well do not prepare differently for inspections. They govern differently throughout the year. When a policy is approved, it is linked directly to the decision that adopted it — in the same system, in the same record. The decision holds the meeting, the date, who approved it, the outcome. The policy holds the version that was formally agreed.

When the inspector asks the question, the answer is one click.

Platforms like Loom make this structural. Every decision is linked to the documents it approved. Every document carries the decision that governs it. The trail is built at the moment of approval — not assembled afterwards, when it matters most.

Because inspection readiness is not a folder with the right files in it. It is a governance structure that leaves nothing to reconstruct.