What Makes a Good Key-Work Session?

A key-work session should be more than a scheduled conversation that produces a completed form. At its best, it gives a young person protected time with a trusted adult to think about something that matters to them, make plans, solve problems or simply be heard.

Start with relevance

The topic should connect to the young person’s life. Some sessions will be prompted by plans or identified needs, but leave room for what the young person wants to discuss. A perfectly completed worksheet is not useful if the conversation felt irrelevant.

Choose the right moment

A formal sit-down meeting is not always best. Some young people talk more easily while walking, cooking, driving or doing an activity. Services can maintain professional boundaries and recording standards while allowing flexibility in how conversations happen.

Do not turn every session into teaching

Key work can become a stream of advice from adults. Ask questions and listen first. What does the young person already know? What do they want? What feels difficult? Teaching is more effective when it responds to a real need.

Keep goals small enough to act on

‘Improve budgeting’ is broad. ‘Use £30 to plan three evening meals this week’ is concrete. Good sessions turn large goals into manageable steps and identify what support is needed.

Handle disagreement respectfully

The young person may disagree with the plan, the risk assessment or the service’s concerns. Do not force agreement into the record. Capture their view and explain any boundaries or decisions honestly.

End with a clear next step

A useful session usually produces something: an action, a decision, a question to take to another professional, a skill to practise or a topic to revisit. If there is no next step, the outcome may simply be that the young person felt heard, which can still be valid.

Record the conversation proportionately

The record should show the purpose, the young person’s views, what was discussed, any advice or support offered, agreed actions and follow-up. Avoid writing a transcript unless there is a specific reason.

Review whether it helped

At the next session, check what happened. Did the action get completed? Did the plan work? Does the young person want to change the approach? Key work becomes meaningful when sessions connect over time.

Putting this into practice

The most useful way to apply this to better key-work sessions 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 key-work sessions 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