What an inspector asks for, and where it should already live

Nobody fails at inspection because they could not find a document. But the evening spent looking for it is an evening not spent on anything else, and a home that cannot lay its hands on its own records is telling the inspector something whether it means to or not.

What follows is not a checklist of duties — your regulator publishes those, and we are not the people to interpret them for you. It is a list of the requests that come up again and again, and an honest question about each one: if it were asked for this afternoon, how long would it take?

The staff list, and one file behind each name

The first request is almost always about people. Who works here, since when, and what is on their file. The hard part is rarely the list — it is that the file behind a name is spread across an email thread, a filing cabinet and somebody's memory of a conversation.

The test: pick the newest member of staff and the longest-serving one. For each, can you produce their background check and its date, their right-to-work evidence, their induction record and their most recent supervision, without asking anyone?

The recurring checks, and who signed them off

Fire, water, equipment, the medication audit, the health-and-safety walk. Each of these is a thing that happened on a date, done by a person, with something that proves it. The proof is usually the weak link: the check happened, and the certificate is in an inbox.

The test: for your last three completed checks, can you show what was done, who signed it off, when, and the document that proves it — with all four together rather than in three different places?

The rota, for a week you did not choose

Any home can produce this week's rota. The interesting question is a week three months ago, including who actually worked it rather than who was originally rostered, and what happened when somebody called in sick.

A child's record, end to end

Not a daily log, and not a care plan — the whole thread. What was planned, what happened, what the child said about it, what changed as a result. This is the request that most exposes a records system that is really several systems: the plan is in one place, the logs in another, and the connection between them is in a keyworker's head.

The test: take one goal from one child's plan and follow it forward. Can you show the sessions that worked on it, the child's own view of it, and where it got to?

The independent visit, and what you did about it

The visit report itself is usually easy to find. The follow-up is the part that goes missing: the visitor raised three things, and the evidence that anything happened next is a conversation nobody wrote down.

The test: take the last visit report. For each point raised, can you show one named person, one date, and what was done?

The pattern

Every one of those tests fails in the same way. The thing happened; the record of it went somewhere the next person would not think to look. The fix is not more paperwork — it is that the record is created by the work rather than after it, and that it is stored against the thing it is about rather than in a folder organised by date.

That is the whole design brief for Careframe, and it is why our Inspection ready page reads your existing records rather than asking you to fill in anything new. If the work is recorded where it happened, being ready is not a project.

Careframe organises and evidences the work a children's home already does. Nothing here is legal or regulatory advice, and nothing here is a statement of what your regulator requires of you — for that, go to your regulator.