What Should a Children's Home Daily Log Include?

Read six months of daily logs from two different homes and you'll often find the same standard of care described in completely different ways. One reads as a genuine record of a child's day: specific, observed, honest about what was difficult. The other reads as a formality someone completed because the shift required it. Same care, different evidence, and inspectors judge on the evidence in front of them, not the day they didn't see.

A daily log in a children's residential care setting isn't paperwork that happens alongside the job. It's the primary record of what a child's life in that home actually looked like, day by day, and it's usually the single most-read document when anyone, an inspector, a social worker, a reviewing officer, tries to understand how a child is really doing. Get the log wrong and everything built on top of it, care plans, Reg 45 reviews, safeguarding decisions, is built on thin ground.

This guide covers what a daily log actually needs to capture, the difference between an entry that holds up and one that doesn't, and where logs most often fall short at inspection.

The legal basis

The Children's Homes (England) Regulations 2015 require every registered home to keep specific records for each child, set out in Schedule 3, and Regulation 36 places a duty on the registered person to maintain them accurately and keep them up to date. A daily log sits underneath this requirement as the day-to-day mechanism most homes use to evidence it, alongside care plans, incident reports, and health records.

There's no prescribed template for a daily log in the regulations themselves. What exists instead is an expectation, tested constantly through the SCCIF, that records taken together give an accurate, current picture of a child's experience. A daily log that's vague, inconsistent, or clearly written to satisfy a shift requirement rather than to inform anyone reading it later fails that test, even if nothing in it is technically false.

This matters beyond inspection. Daily logs get pulled during safeguarding reviews, referenced in Regulation 45 reviews, and read by social workers preparing for statutory visits. A log written only with Ofsted in mind, rather than with the actual reader in mind, tends to fail all three purposes at once.

What a daily log actually needs to capture

A strong daily log covers four things for every shift, not just whatever felt notable at the time.

What actually happened. Meals, school or activities, appointments, contact with family, time spent with staff. The ordinary shape of the day, not just the exceptions to it. A log that only records incidents gives no picture of what a normal day looks like for that child, which makes it impossible to spot when something starts drifting.

The child's presentation and mood. Observable behaviour, not a diagnosis. "Withdrawn during the afternoon, declined to join the group activity, spent most of the evening in her room" tells a reader something real. "Seemed a bit off today" tells them nothing they could act on.

Anything that happened around health, education, or wellbeing. A missed dose, a school call, a comment about not sleeping. These details are often the first sign of something building, and they're the ones most likely to get left out because none of them felt significant enough on their own at the time.

Contact with anyone outside the home. Family calls, social worker visits, contact with friends. Who initiated it, roughly how it went, and anything the child said afterwards. This is frequently the thinnest part of a weak log, even though it's often the part a social worker actually wants to read.

None of this needs to be long. A well-written daily log entry is often three or four short paragraphs. The standard isn't length, it's whether someone who wasn't on shift that day could read it and actually understand what the child's day was like.

Recording health, education, and wellbeing detail properly

This is the category most likely to get under-recorded, because on any single day none of it feels dramatic enough to write up in full. A missed dose on its own seems minor. A single quiet morning seems unremarkable. It's only when these details accumulate across weeks that a pattern becomes visible, and that only happens if each individual entry actually recorded them.

Medication. Not just whether it was administered, but anything unusual: a refusal, a delay, a changed dose, a side effect the child mentioned. "Medication given as prescribed" is fine on an ordinary day. "Refused morning medication, said it made her feel sick yesterday, staff spoke with her about it and she agreed to take it after breakfast" is what actually helps a reviewing clinician or the next shift understand what's going on.

School and education. A call from school, a comment about a difficult lesson, an unexplained drop in attendance, a change in how a child talks about a particular teacher or subject. These are frequently the earliest visible sign of something wider going on, and they're easy to leave out because they happened over the phone or in passing rather than as a discrete event on shift.

Sleep, eating, and general wellbeing. A single disrupted night isn't necessarily significant. Three disrupted nights in a row, recorded individually rather than summarised as "still not sleeping well," gives whoever reviews the log later the actual evidence needed to decide whether something needs to change. The same applies to appetite, energy, and mood over time.

Appointments. GP, dentist, CAMHS, health visitor contact. Not just that the appointment happened, but roughly what was discussed and any follow-up action, since this is often the detail a social worker or reviewing officer specifically needs and can't easily get anywhere else.

Weak: "Health fine. Went to the dentist. No other issues."

Stronger: "Dentist appointment this morning, no problems found, next check-up booked for six months. Mentioned during the appointment that she's been having headaches most afternoons this week. Flagged to the on-call nurse, advised to monitor and record frequency, will follow up if it continues."

The stronger version doesn't take longer to write. It just treats a passing comment as information worth capturing, rather than something that only becomes relevant in hindsight once a pattern is already established and harder to trace back to when it started.

Writing objectively: the difference between a strong and weak entry

The single biggest quality gap in daily logs isn't missing information. It's language that describes a judgment instead of an observation.

Weak: "Had a difficult day. Was in a mood most of the evening. No real issues though."

Stronger: "Refused breakfast and said she wasn't hungry, which is unusual for her. Quiet through the morning, more responsive by the afternoon after a walk with a staff member. Declined to talk about school when asked directly but mentioned in passing that she'd argued with a friend."

The weak version is a summary of a staff member's impression. The stronger version is a record of what actually happened, specific enough that someone reading it three months later, with no memory of that particular Tuesday, can reconstruct a real picture of the child's day and decide for themselves whether it matters.

"No concerns" is the phrase to watch for most closely. Used honestly, it's fine. Used as a default because nothing felt worth writing, it becomes a pattern that erodes the log's value entirely. A month of entries that all read "no concerns, quiet evening" isn't reassuring to an inspector. It reads as evidence that logs aren't being written with any real attention, which raises the exact question good documentation is meant to answer: is anyone actually watching closely enough to notice if something changed?

The same discipline applies to positive entries. "Had a great day" says less than "asked to help cook dinner for the first time this month and seemed proud when the rest of the house enjoyed it." Specific, observed detail is what makes a log useful in both directions, not just when something goes wrong.

Recording incidents, not softening them

Every home has difficult shifts. How they get written up matters more than whether they happened.

A weak incident entry minimises: "Bit of an incident this evening, sorted quickly, all fine now." A strong one is factual and sequential: what led up to it, what happened, what staff did, how it was resolved, and how the child was afterwards. Not editorialised, not defensive, just an accurate account written close enough to the event that the details are still genuinely remembered rather than reconstructed later from memory.

This applies with particular weight to anything involving physical intervention, a missing episode, or a safeguarding concern. These entries get read the most closely, by inspectors, by the responsible individual reviewing the log, and potentially by external agencies. A log that's vague or defensive about a genuine incident reads as an attempt to manage the record rather than report it, and that impression is far more damaging than the incident itself usually is.

Write it as if the reader wasn't there, because they weren't. The most common failure in incident logging isn't dishonesty. It's writing in shorthand that made sense to the person on shift that night but leaves out the context anyone else would need to actually understand what happened and why staff responded the way they did.

A worked example: the same day, two ways

Every element covered so far reads differently in isolation than it does in a real entry, so it helps to see one shift written both ways.

The day: A 14-year-old girl declines breakfast, is quiet through the morning, has a disagreement with another young person during an afternoon activity, and mentions before bed that she's anxious about an upcoming review meeting.

Weak entry: "Bit of a mood today. Didn't want breakfast. Had a disagreement with another YP during art, sorted quickly. Fine by evening. No concerns."

Stronger entry: "Declined breakfast without giving a reason, which is unusual for her, though she ate lunch normally. Quiet through the morning, more talkative by early afternoon. During the art group, disagreement with another young person over shared materials, raised voices but no physical contact. Staff separated them, spoke to each individually, and both apologised to each other before dinner. Before bed, mentioned she's worried about her review meeting next week and isn't sure what will be discussed. Reassured her and confirmed with her key worker that the agenda will be talked through with her beforehand."

Read side by side, the weak version isn't dishonest. Everything in it technically happened. But it gives a reader nothing to act on: no context for the breakfast refusal, no detail on what actually caused the disagreement or how it was resolved, and no record at all of the comment about the review meeting, which is arguably the most important thing that happened that day. The stronger version takes barely longer to write and gives every future reader, the next shift, a Reg 44 visitor, the child's social worker, something they can actually use.

Making sure the child's own voice is in the log

A daily log written entirely in the third person, describing what was done to and around a child without ever recording what the child actually said, misses something inspectors are specifically trained to look for.

This doesn't mean transcribing every conversation. It means capturing the moments where a child's own words or reactions are relevant: what they said about their day, how they responded when something difficult came up, whether they raised anything themselves that staff then acted on. "Told staff he was worried about seeing his dad this weekend, staff reassured him and confirmed the contact plan with him" is a stronger entry than a log that simply notes contact took place, because it shows the child's perspective was actually heard, not just logistically managed.

This is also where a log demonstrates something the 9 Quality Standards test directly: whether children's views genuinely shape their care, or whether that's a value stated in the statement of purpose but not evidenced in the day-to-day record.

Handover and shift-to-shift consistency

A daily log only does its job if the next shift actually reads it and acts on what it says. Two failure patterns show up repeatedly here.

The log that isn't read. Staff coming on shift who haven't reviewed the previous entry miss context that changes how they should approach the child that day. A robust handover process, where reading the log is a genuine step rather than a formality, is what turns individual entries into a continuous record rather than a series of disconnected notes.

The log that contradicts itself across shifts. One entry says a child had a calm day, the next says staff were managing ongoing distress from the same day with no explanation of what changed in between. Inconsistency like this usually isn't dishonesty, it's usually a handover gap, but inspectors can't tell the difference from the page. Whatever caused a shift in presentation needs to be visible in the record, not left for the reader to guess at.

Daily logs and Regulation 44 visits

The monthly independent visit required under Regulation 44 routinely draws on daily logs as primary evidence, and it's often the first place gaps in logging get flagged before they ever reach a full inspection.

An independent visitor reviewing a home for a Regulation 44 report will typically sample daily logs across the period since the last visit, looking for the same things an inspector looks for: specificity, consistency, and whether the child's own voice comes through. A pattern of thin entries picked up here becomes a documented finding in the visitor's report, which then has to be addressed in the home's response and tracked until it's resolved. Catching the same pattern internally, before the visitor does, is far less costly than explaining it after the fact.

This is also where logging quality compounds. A Regulation 44 report that repeatedly flags weak daily logs, without visible improvement between visits, becomes evidence in its own right that leadership isn't acting on external feedback, which is a very different and more serious finding than an isolated month of thin entries. The SCCIF's guidance on inspecting children's homes treats this kind of pattern, feedback given and not acted on, as a leadership and management concern in its own right, separate from the underlying documentation gap.

Daily log readiness checklist

Experiences and progress of children

Does the log capture the ordinary shape of the day, not just incidents?
Are the child's own words or reactions recorded where relevant, not just what was done around them?
Would someone who wasn't on shift understand what this child's day was actually like?

How well children are helped and protected

Are incidents, including physical intervention or missing episodes, written factually and completely, close to the time they happened?
Are health, education, and safeguarding-relevant details captured even when they didn't feel significant at the time?
Is language objective and specific, rather than a summary judgment like "difficult day" or "no concerns"?

Effectiveness of leaders and managers

Is there a genuine handover process where staff read the previous log before starting a shift?
Do logs read consistently across staff and across shifts, without unexplained contradictions?
Is anyone actually reviewing logs regularly, rather than only when something goes wrong?

What happens when an inspector pulls your daily logs

Inspectors typically ask to see daily logs early in an inspection, often for a specific child or a specific period, and read them alongside care plans and any relevant incident reports. They're checking for three things: whether the log is specific enough to be useful, whether it's honest about what was difficult, and whether it's consistent with what staff and the child say when they're spoken to directly.

A mismatch between what the log says and what a child tells an inspector in conversation is one of the most damaging findings a home can produce, because it suggests the record isn't a reliable account of the child's actual experience. This is precisely why generic, softened, or incomplete logs create risk that has nothing to do with the quality of care itself. The care might genuinely be strong. If the record doesn't reflect it accurately, the inspector has no way to know that.

Where logs raise questions, inspectors will typically ask staff and managers directly why an entry is vague, why an incident wasn't fully written up, or why days appear to be missing. Being able to answer honestly, ideally because the gap has already been identified and addressed internally, lands far better than being caught unaware of a pattern in your own records.

Most common daily log failures

Generic entries that could describe any child on any day. "Had a good day, no concerns" repeated with minor variation across weeks tells an inspector nothing and actively suggests logs aren't being written with attention.
Incidents written defensively rather than factually. Minimising language around a difficult event reads as an attempt to manage the record, which damages trust more than the incident itself.
Missing entries with no explanation. Gaps in the log, even short ones, raise the question of what happened during that time and why nobody recorded it.
No evidence of the child's own voice. Logs that describe what was done around a child without ever capturing what the child said or how they responded.
Entries written well after the shift ended. Details written from memory days later lose specificity and consistency, and inspectors can often tell the difference between a log written close to the event and one reconstructed afterwards.
No real handover process. Logs that exist but aren't actually read by the next shift, so information doesn't travel and inconsistencies go unnoticed until someone external reads them together.

Frequently asked questions

What should a daily log in a children's home include? A factual account of the child's day, including meals, activities, presentation and mood, any health or education issues, contact with family or professionals, and a record of the child's own words or reactions where relevant.

Is there a legal requirement for daily logs in children's residential care? The Children's Homes (England) Regulations 2015 require accurate, up-to-date records under Regulation 36 and Schedule 3, and daily logs are the standard mechanism most homes use to evidence a child's day-to-day experience against that requirement.

How detailed does a daily log entry need to be? Detailed enough that someone who wasn't on shift could read it and understand what actually happened, typically three or four short paragraphs covering the shape of the day, presentation, and anything notable, written in specific rather than generic language.

Why is writing "no concerns" repeatedly in a daily log a problem? Used as a default rather than an honest observation, it suggests logs aren't being written with genuine attention, which is exactly the concern good documentation is meant to rule out.

How soon after a shift should a daily log be written? As close to the end of the shift as possible, since details written from memory days later lose specificity and are more likely to be inconsistent with what actually happened.

Should a daily log record what a child said, not just what staff did? Yes. Capturing a child's own words or reactions where relevant shows their perspective genuinely shaped their care, which inspectors specifically look for under the 9 Quality Standards.

What happens if an inspector finds gaps in daily logs? They'll typically ask staff and managers directly why an entry is missing or vague, and being able to explain a gap honestly, ideally one already identified internally, is far better than being caught unaware of a pattern in your own records.

Do daily logs need to be consistent across different staff and shifts? Yes. Unexplained contradictions between entries, such as one shift recording a calm day and the next describing ongoing distress with no context, read as a handover failure even when they aren't intentional.

How CareClarity supports your daily logs

CareClarity's Daily Log Review gives instant feedback on a shift or daily log: whether the language is objective and specific, whether the child's own voice comes through, and whether anything significant has been softened or left out, before it becomes the version an inspector reads.

Start your free 7-day trial and get feedback on your next daily log before it's the one that gets pulled at inspection.