What Does a Really Good Support Note Look Like?

A support note is useful when a colleague can read it and understand what happened, why it mattered and what needs to happen next. Weak notes usually fail because they are too vague, too opinionated or too focused on the task staff completed. Strong notes give context without turning into essays.

The vague note

Consider: ‘Sam had a good day and engaged well.’ This sounds positive but tells the reader almost nothing. What made the day good? What did Sam do? What did engagement look like? Could another staff member use this information to support Sam tomorrow? Probably not.

The overloaded note

At the opposite extreme, staff sometimes document every conversation, meal, television programme and small movement. Detail can be useful, but excess detail can hide what matters. A strong note selects information based on relevance to wellbeing, plans, risk, progress, relationships and future support.

The useful note

A better example might be: ‘Sam attended college for the full day after missing Monday. He told staff he felt nervous before leaving but did not want support with the journey. On return he said the day went better than expected and asked staff to help him check tomorrow’s timetable. Staff printed the timetable with him. No further action outstanding.’ This gives context, voice, action and outcome.

Describe, do not label

Avoid labels such as lazy, manipulative, attention-seeking, aggressive or difficult. These words interpret motive or character. Describe the behaviour instead. If there is a professional formulation or known trigger relevant to support, reference it carefully and distinguish it from direct observation.

Include staff action

A record should show what staff did, not only what the young person did. If a young person was distressed, what support was offered? If they declined, how was that respected and monitored? If a concern was escalated, to whom? This creates accountability and helps the team understand the response.

Show the outcome

Many notes stop after the action. Add what happened next. Did the young person settle? Was an appointment booked? Did they remain upset? Did the issue move to the next shift? Outcomes make the note useful for continuity.

Use proportionate detail

Significant events deserve more detail than routine events. A casual conversation about dinner does not need the same level of recording as a disclosure, missing episode or serious conflict. Proportionate recording protects staff time and makes important information easier to identify.

Ask the future-reader test

Before saving a note, ask: if I knew nothing about today, would this entry help me understand what matters? If the answer is yes, the note is probably doing its job.

Putting this into practice

The most useful way to apply this to better support notes 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 support notes 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