How to Write About Difficult Behaviour Without Labelling the Young Person

The words used in care records shape how future readers see a young person. A label written during one difficult shift can follow them for months or years. Objective language does not minimise risk; it describes risk more accurately by focusing on observable behaviour, context and impact.

Replace labels with description

Instead of ‘aggressive’, describe the action: shouting, hitting a wall, throwing an object, moving toward someone quickly or making a threat. Different behaviours carry different levels of risk. Description helps the reader understand what actually occurred.

Avoid guessing motive

Words such as manipulative or attention-seeking assume why somebody behaved in a certain way. Staff may have hypotheses, but motives are rarely directly observable. Record what the young person asked for, what happened before the behaviour and what changed afterwards.

Describe context

Behaviour rarely happens in a vacuum. Was there disappointing news, family contact, a boundary being set, sensory overload, conflict with a peer or an unexpected change? Context does not excuse harmful behaviour, but it helps teams understand it.

Record impact without exaggeration

If others felt unsafe, property was damaged or a routine was disrupted, say so. Avoid dramatic language. Accurate impact is more useful for risk assessment than emotive description.

Include strengths and recovery

If the young person calmed, apologised, repaired damage, accepted support or reflected afterwards, include that too. Ending the record at the peak of the incident can create a distorted picture of the whole event.

Use agreed language consistently

Teams should discuss how they describe common behaviours so records remain consistent. If the service uses specific risk categories or behaviour definitions, staff should understand them. Consistency improves pattern recognition and reduces personal bias.

Challenge inherited labels

If old records repeatedly describe a young person in a particular way, new staff may start looking for evidence that confirms the label. Managers should challenge language that is unfair or unsupported and encourage staff to approach each interaction with curiosity.

Remember who may read the record

The young person may eventually read what has been written about them. That is a useful ethical test. Would the wording still feel fair if they were sitting beside you? If not, rewrite it without losing the facts.

Putting this into practice

The most useful way to apply this to non-labelling behaviour records 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 non-labelling behaviour records 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.

A final reality check

One final check is to ask whether the process remains workable on the busiest shift of the week. Standards that only work when staffing is ideal or the service is quiet will not be sustained. Good practice should be simple enough to use under pressure, clear enough for new staff to understand, and flexible enough to respond to the individual young person. If staff routinely create workarounds, that is useful feedback: either expectations are unclear, the workflow is too complicated, or the tools do not match the reality of the role. Treat those workarounds as signals to investigate rather than automatic evidence of poor attitude.

Key takeaway