A policy nobody can explain isn't a policy

Regulation 10 requires the written policies and statements in Schedule 5, but a policy's existence isn't what makes it compliant. It needs to be current, specific to the actual service (not a template with the previous crèche's name still in it), approved, accessible to staff, and — the part that actually gets tested — implemented in daily practice. A policy that contradicts what staff actually do is worse than no policy, because it's evidence the service isn't managing itself against its own stated rules.

Safeguarding is the sharpest version of this. Every staff member needs to know how to recognise and respond to a concern, who the designated safeguarding lead is, how to record it, and — critically — what to do if that person isn't available. "Ask the manager" isn't an escalation route if the manager is on leave and nobody's rehearsed the alternative.

Complaints work the same way structurally: a policy is only as good as the log behind it. Receiving, recording, acknowledging, investigating, responding to, and closing a complaint, with the complainant kept informed throughout, is what an inspector actually checks — not whether a complaints policy document exists.

Records storage is the quieter cousin of all this. Child and staff records need to be secure, confidential, and retrievable by someone authorised to see them, on request, not after a search. Bloomffy's audit log exists for exactly this layer — who viewed, edited, or exported what, and when — because "the records exist" and "the records are demonstrably controlled" are different claims, and only the second one is what an inspector, or a parent making a subject access request, is actually asking about.

None of this is solved by writing better policy prose. Bloomffy's policy checklist tracks the 20 Schedule 5 policies and the 3 separately-required statements as a list an uploaded document either satisfies or doesn't — the point isn't to generate the policy, it's to make a missing or lapsed one visible before an inspection finds it, the same way a gap in a staff file should surface on a dashboard rather than in an inspector's notebook.