A daily log should help the next person understand what mattered during a young person’s day. It is not a diary for staff, and it is not a place to dump every small detail. The best daily logs are clear, respectful, factual and useful. They create continuity between shifts, help managers understand patterns, and preserve the young person’s story without reducing that story to incidents and problems.
Start with purpose, not volume
A useful daily log answers a simple question: what would another member of the team need to know in order to support this young person well? That usually includes significant events, changes in presentation, appointments, education, contact with family or professionals, medication issues, key conversations, progress, concerns and any action that still needs follow-up. A long record is not automatically a good record. Ten lines of precise information can be more valuable than a page of vague description.
Separate observation from interpretation
Staff should describe what they actually saw and heard before adding interpretation. Instead of writing ‘Jay was aggressive’, write what happened: ‘Jay raised his voice, pushed the chair back and left the kitchen after being told the Wi-Fi would be turned off at midnight.’ The second version gives context. It allows another reader to understand the behaviour without labelling the young person. Where professional interpretation is necessary, make it clear that it is an interpretation rather than a fact.
Record the young person’s voice
A daily log should not read as if the young person was absent from their own day. Where appropriate, include what they said, what they wanted, what they disagreed with and what they were proud of. If they declined support, say so respectfully and record any follow-up. If they made a choice, record the choice rather than only the staff response. This helps preserve agency and gives a fuller picture of their experience.
Include progress, not just problems
Teams naturally record incidents because incidents demand attention. The quieter signs of progress are easier to miss. A young person cooking independently, attending college after a difficult week, returning on time, keeping an appointment, apologising after conflict or asking for help are all meaningful. Positive recording does not mean exaggerating small achievements. It means documenting evidence of growth and independence so that the record reflects the whole person.
Make follow-up visible
A strong log makes unfinished business obvious. If a young person needs a prescription collected, a social worker has requested a call back, or a maintenance problem needs escalation, record the action and who is expected to take it forward. Avoid vague phrases such as ‘to be followed up’ with no owner. A record is much more useful when the next shift can see what remains outstanding.
Write for a future reader
Assume the person reading the entry in six months will not remember the context. Use full names or clearly defined roles where appropriate, avoid unexplained abbreviations, and include enough background to understand why an event mattered. At the same time, do not include gossip, irrelevant personal opinion or unnecessary sensitive detail. The test is whether the information helps care, safeguarding, continuity, accountability or understanding.
A simple daily-log structure
A practical structure is: what happened; what the young person said or did; what staff did; what the outcome was; and what needs to happen next. Teams can use this as a mental checklist without making every entry sound robotic. The aim is consistency, not identical writing styles.
Putting this into practice
The most useful way to apply this to better daily logs is to start with one real, anonymised example from the service rather than trying to redesign everything at once. Choose a recent shift, record, handover, incident or support interaction and walk through what actually happened. Ask staff where they had enough information, where they had to guess, where work was duplicated and whether the young person’s experience was visible. Then identify one change that would make the next similar situation clearer or easier. That might be a better prompt on a form, a clearer handover category, a named action owner, a more consistent phrase for recording observations, or a scheduled management review. Keep the change small enough to test. Large policy rewrites can feel productive while leaving day-to-day practice untouched. A small workflow improvement that staff understand and use consistently is often more valuable. After a week or two, review whether the change improved clarity, reduced repeated questions, helped staff act sooner or made the record more useful. If it did not, adjust it. Good practice develops through observation, feedback and refinement rather than one perfect template. Where the issue touches safeguarding, legal duties, medication, restraint, confidentiality or another regulated process, the service should always check its current policy and relevant professional guidance before changing practice.
Questions for supervision and team discussion
Managers can also use better daily logs as a supervision or team-meeting discussion rather than only a written standard. Ask staff what good practice looks like when the shift is busy, what usually gets missed under pressure and what would make the right action easier. Use examples rather than abstract criticism. If a record is too vague, rewrite one paragraph together. If actions are being lost, trace one action from the moment it was created to the point it was completed. If the young person’s voice is missing, ask what question staff could have asked or what part of the conversation should have been captured. It is also worth asking how the process feels from the young person’s perspective. Do they have to repeat themselves? Do different staff give different answers? Does the record focus mostly on things going wrong? Are decisions explained to them? These questions move quality improvement beyond paperwork and back toward the experience of care. Finally, agree what ‘good enough’ looks like. Staff need practical examples and clear expectations, not vague instructions to ‘record better’ or ‘communicate more’. A shared standard makes feedback fairer and gives new staff something concrete to learn from.
Key takeaway
Good daily logs are not about writing more. They are about making the important things easy to understand. When records are factual, balanced, outcome-focused and written with the young person in mind, they become useful tools for support rather than just evidence that a shift took place.
