What should go in a daily log or key-work record

Daily logs serve two audiences at once: the next member of staff coming on shift, who needs to know what actually happened and what to be aware of, and anyone reviewing the file later — a manager, an inspector, a court — who needs an honest, dated account.

What a strong entry includes

• –What happened, factually, before any interpretation
• –How the young person seemed, in observable behaviour rather than a diagnosis-flavoured guess
• –What staff did in response
• –Anything that needs following up, clearly flagged rather than buried in prose

Key-work sessions need more than attendance

Key-work sessions specifically should record more than attendance. A note that a session "took place" is barely more useful than no note at all — what was actually discussed, what the young person said in their own words where possible, and what (if anything) was agreed for next time, is what makes the record worth having, and what a good care plan actually depends on to stay current.

The most common failure mode isn't dishonesty, it's vagueness under time pressure — a rushed "had a good day, no concerns" written at the end of a long shift. It's not wrong, but three months of identical entries like that tell an inspector, or a new keyworker, almost nothing about the actual young person.

How a strong entry differs from a weak one

Weak: "Good evening. No incidents. Had dinner and watched TV." Strong, covering the same actual evening: "Quiet evening. X mentioned unprompted that they're nervous about a school trip next week — said they've never been away from the home overnight before. Reassured X and said we'd talk it through properly at tomorrow's key-work session. No other concerns." Both entries are honest and both took about the same time to write. The difference is that the second one gives the next shift, and the key worker tomorrow, something real to act on — a specific thread they can pick up rather than a blank page.

Structuring records for a home with multiple young people

In a home with several children, the temptation under time pressure is to write one combined shift note covering everyone briefly, rather than a proper entry per child. That's usually a mistake — a shared note makes it much harder to trace one young person's pattern over time, and it tends to be where the vaguest, most generic writing ends up, because nothing forces real attention onto any one child specifically. Keeping entries per child, even briefly, protects against that drift far better than any amount of good intention.

Handovers depend on these records more than most staff realise

The daily log's most immediate reader isn't a manager or an inspector — it's whoever comes on shift next, often just hours later. A verbal handover fades and gets simplified with each retelling; a written log doesn't. A staff member arriving for a night shift who reads a clear, specific note about a difficult conversation earlier that day walks in with real context. One who gets a rushed thirty-second verbal summary at the door, because the log was thin or unfinished, is working with far less than they should be. Treating the log as the primary handover mechanism, not a formality that happens alongside the real handover in conversation, changes how seriously it tends to get written.

It's worth training new staff explicitly on what a good log looks like, with real (anonymised) examples, rather than assuming they'll pick up the standard by osmosis from whatever's already in the system. Left to guess, a new starter tends to mirror whatever style is most common around them — which is fine if the existing standard is genuinely strong, and a quiet way to propagate vagueness if it isn't.

A manager reviewing logs regularly should also give direct, specific feedback rather than only flagging problems in the abstract — pointing to one genuinely strong entry a staff member wrote and saying plainly why it worked tends to shift behaviour faster than a general reminder to "write more detail," because it gives a concrete, achievable standard to aim for rather than a vague instruction to try harder.

It's worth keeping a small, shared bank of genuinely strong (anonymised) examples for exactly this purpose — new starters learn faster from seeing what good actually looks like than from a written standard alone, however clearly it's worded.

The investment pays off quickly, too — once a team has a genuinely shared sense of what a strong entry looks like, the whole conversation about record quality shifts from vague reminders to specific, concrete feedback, which is both easier to give and easier to actually act on.

None of this is about writing more for the sake of it — a home with genuinely strong daily logs often writes about the same amount as one with weak ones. The difference is entirely in where the attention goes.

What to do when very little actually happened

• –It's fine for an entry to be short on a genuinely uneventful day — brevity isn't the problem, vagueness is
• –Note the ordinary, positive detail too (what they ate, what they enjoyed, who they spent time with) — it builds a fuller picture over time, not just a log of problems
• –If a key-work session was cancelled or shortened, say so and why, rather than writing as if it happened as planned
• –Flag anything that needs following up clearly, even briefly, rather than letting it sit buried in a paragraph of prose