Making Safeguarding Personal in Practice: Outcomes, Voice and Positive Risk-Taking

“Making Safeguarding Personal” isn’t a slogan. It is a commitment to start with what matters to the individual — not just what the process requires. Too often, it is interpreted as asking a person’s view after decisions have effectively already been made. That is procedural, not personal. This guide sets out what good practice looks like day to day, and how to evidence it for tenders and assurance. It aligns Making Safeguarding Personal with confident positive risk-taking, so safeguarding is both protective and rights-based — visible in records, supervision, governance, and outcomes.


🧭 What “making safeguarding personal” really means

MSP is outcome-led. It starts with the person’s own definition of safety, control and dignity, then builds a plan that reduces harm without automatically removing independence. In practice, MSP means staff can demonstrate three things consistently:

  • Outcome clarity: the person’s desired outcomes are captured in their words and revisited during reviews.
  • Involvement: the person is involved at every stage that is reasonably possible — from initial concern to protection planning to closure.
  • Proportionality: the response is the least restrictive option that still reduces harm, with positive risk-taking used deliberately and reviewed.

MSP is not “doing nothing” and it is not “leaving people at risk”. It is balancing rights, safety and wellbeing through transparent decision-making.


🔍 What MSP does not mean

Services sometimes worry MSP will be misunderstood as “the person chooses risk, so we step back”. That is not defensible. MSP does not mean:

  • Ignoring immediate danger or delaying action when someone is at serious risk.
  • Handing responsibility back to the person without support, information and options.
  • Recording “capacity assumed” without evidence, or using consent language without a clear conversation.

Instead, MSP means the person’s wishes are treated as central evidence in the safeguarding record — alongside professional curiosity, clear escalation thresholds and governance oversight.


Commissioner expectation

Commissioner expectation: evaluators want to see that outcome-led safeguarding is a repeatable method, not an individual staff member’s style. In tenders, they look for how you capture the person’s desired outcomes, how advocacy is accessed, how positive risk-taking is negotiated, and how decisions are reviewed and audited. Strong answers show timeframes, ownership, and how effectiveness is measured — not just policy statements.


Regulator / inspector expectation

Regulator / Inspector expectation (CQC): inspectors typically test whether safeguarding is person-centred and proportionate in practice. They look for evidence that people are involved, that restrictive responses are justified and reviewed, that staff understand escalation and information sharing, and that leaders can demonstrate learning after concerns. The “feel” of MSP is often visible in care records, staff language, and whether the person recognises themselves in the plan.


📝 How to record MSP so the person’s voice is unmistakable

MSP fails quietly when recording is generic. The safeguarding record should make it easy for an auditor or commissioner to see what the person wanted, what options were explored, what was agreed, and what changed. Practical recording standards include:

  • Direct voice: short quotes or “in my words” summaries (without jargon) capturing what safety means to the person.
  • Options log: what choices were offered, and why particular options were accepted or declined.
  • Risk negotiation notes: what the person understands about the risk, what support will reduce it, and what review trigger will prompt reconsideration.
  • Review cadence: dates, named roles, and what “success” will look like for the person (not only for the service).

This is what turns “we involve people” into evidence of lived practice.


✅ Operational examples that demonstrate MSP with positive risk-taking

Operational example 1: Co-produced safety planning after controlling behaviour

Context: A person in supported living reports feeling pressured and monitored by a relative. They do not want a complete ban on contact, but they want visits to feel safe and respectful.

Support approach: Staff explore the person’s desired outcomes (what they want to change), offer advocacy, and explain confidentiality and escalation boundaries in plain language. The safeguarding lead supports staff to keep the person involved while planning proportionate protective steps.

Day-to-day delivery detail: The service co-produces a safety plan with the person’s words: agreed visit times, preferred locations, a “pause phrase” the person can use, and a step-by-step response if pressure escalates. Staff record each contact factually and debrief with the person afterwards, focusing on how they felt and whether boundaries held.

How effectiveness is evidenced: Weekly review notes track whether the person reports increased control, reduced distress, and fewer pressured interactions. Any breaches trigger an immediate review and, if threshold is met, external safeguarding contact with the person informed of what will be shared and why.

Operational example 2: Positive risk-taking to rebuild independence

Context: After a fall and a safeguarding concern about community vulnerability, staff become risk-averse and begin discouraging independent outings. The person feels restricted and starts refusing support.

Support approach: The team agrees the person’s outcome (independence and confidence) and uses risk enablement rather than blanket restriction. Staff identify the least restrictive steps that still reduce harm and restore routine.

Day-to-day delivery detail: The plan includes graded goals: accompanied route practice, agreed check-in points chosen by the person, and a simple help-seeking plan that fits their communication style. Review triggers are set (missed check-ins, increased falls risk, signs of targeting) and ownership is assigned to a named lead with timescales.

How effectiveness is evidenced: The service tracks outcomes: successful journeys, confidence ratings, incidents/near misses, and plan adjustments. Governance sampling checks that restrictions have not “drifted” back in without rationale and that reviews happened on time.

Operational example 3: Information sharing that respects consent while protecting safety

Context: A professional raises concerns about possible financial pressure. The person wants support but is worried that everyone will be told and they will lose control of the situation.

Support approach: Staff hold a structured conversation: what the person wants to happen, what they consent to share now, and what may need to be shared without consent if risk escalates. Advocacy is offered if the person finds professional discussions overwhelming.

Day-to-day delivery detail: The safeguarding lead records the person’s wishes, the options explained, and the agreed information-sharing approach (who, what, and purpose). Staff document every contact with external professionals, including responses, and schedule a follow-up conversation with the person after each step so they remain informed and involved.

How effectiveness is evidenced: Timeliness is measured (actions completed within agreed timescales), and the person’s feedback is captured (“I felt informed / I felt listened to”). Any deviation from agreed consent boundaries triggers a managerial review and a learning brief for the team.


📊 Governance and assurance mechanisms that make MSP auditable

MSP should be visible in leadership behaviour, not left to frontline goodwill. A robust model typically includes:

  • Monthly case sampling focused on: the person’s outcomes, involvement evidence, proportionality rationale, and review dates.
  • Supervision prompts exploring dilemmas (autonomy vs protection) and how staff used risk negotiation rather than restriction by default.
  • Quality reporting that tracks themes (e.g., repeat concerns, delays, restrictions introduced) and actions taken to improve practice.
  • Learning loops after concerns: what changed in the support plan, how staff were briefed, and how leaders verified change.

This is the difference between “we do MSP” and “we can prove MSP is how we work”.


📄 What to show in tenders

To score well, describe MSP as a method with evidence points. Strong tender content typically includes:

  • How people define and agree safeguarding outcomes in their own words.
  • How advocacy is accessed and recorded, including for communication needs.
  • How positive risk-taking is used to enable independence, with review triggers and governance oversight.
  • How recording captures voice, options explored, proportionality rationale and measurable outcomes.

Instead of saying “we keep people safe”, show how you co-create safety — and how you evidence that choice, dignity and protection were balanced through a supportive framework.