Strengths-Based Dementia Support Planning: Maintaining Independence While Managing Risk
Strengths-based planning in dementia care is easy to describe and hard to deliver consistently. In practice, “strengths-based” must show up in daily routines, risk decisions, staff prompts, and the way the service responds when cognition fluctuates. It is also one of the quickest areas where commissioners and inspectors spot drift: plans that say “encourage independence” while staff practice becomes task-led and risk-averse. This guide sits alongside our dementia person-centred planning resources and the wider dementia service models collection, focusing on how to translate “retained abilities” into a support plan that is safe, auditable, and real.
What “strengths-based” means in dementia services
In a dementia context, strengths-based planning means identifying what the person can still do (independently or with graded prompting), what conditions help them do it (time of day, environment, relationship, pacing), and what risks must be managed so the person is not over-restricted. It is not a vague value statement. It is a set of operational decisions that are reviewed as cognition changes.
Services typically operationalise strengths-based planning across three layers:
- Ability mapping: clear statements of retained skills (mobility, self-care steps, communication strengths, orientation cues, decision-making abilities).
- Enabling routines: staff prompts and set-ups that make ability more likely (layout, visual cues, time allowances, “first/then” sequences, consistent wording).
- Risk enablement: proportionate controls that keep the person as free as possible while reducing foreseeable harm (not blanket restrictions).
The documentation that makes strengths-based care “real” (and inspectable)
To stand up to scrutiny, strengths-based planning needs to be visible in three places:
- Care plan instructions: what staff do, how, and when (not just outcomes).
- Daily notes and handovers: evidence of prompting, attempts, adaptations, and learning from what worked.
- Risk decisions: rationale, least restrictive options considered, review triggers, and who signs off changes.
Where services fail is not usually missing policies. It is the gap between plan wording and shift-by-shift delivery: staff defaulting to “doing for” because it is faster, because supervision is light, or because risk decisions are unclear.
Operational examples (how strengths-based planning works day to day)
Example 1: Retained self-care steps supported through graded prompting
Context: A person in supported living is no longer reliably completing morning personal care. Staff have begun taking over to “get it done” before transport arrives, increasing dependence and distress.
Support approach: The plan is rewritten as a step-by-step enabling routine. It separates what the person can do, what needs set-up, and what needs hands-on support. The approach uses the same phrasing across staff to reduce confusion.
Day-to-day delivery detail: Staff prepare the bathroom in advance (towel visible, toiletries laid out in sequence). The prompt sequence is consistent (“Let’s start with face, then teeth”). Staff wait for response rather than repeating prompts rapidly. If the person pauses, staff offer a single choice (“shirt first or trousers first”). If time pressure builds, staff escalate to a pre-agreed contingency (partial assistance) rather than switching to full takeover.
How effectiveness is evidenced: Daily notes record which steps were completed independently, what prompts were used, and any patterns (e.g., best outcomes after breakfast). Weekly, the keyworker reviews the records and updates the plan (e.g., changing prompts, adjusting timing, adding a visual cue). A simple metric is tracked: “independent steps completed” over time, alongside incidents of distress during care.
Example 2: Mobility and falls risk managed without restricting activity
Context: A person has had two falls in a month. Staff respond by discouraging walking and suggesting constant supervision, which increases agitation and reduces mobility.
Support approach: The service completes a risk enablement review that distinguishes hazard reduction (environment and routines) from restriction. The aim is to keep the person mobile while reducing predictable triggers.
Day-to-day delivery detail: Environmental adjustments are made (clear routes, consistent lighting, chair height checked, footwear routine added to the morning plan). Staff introduce “walking windows” (short supported walks at predictable times) rather than ad-hoc rushing. If the person stands repeatedly, staff use an agreed redirection routine (offer drink, check pain, offer toilet) rather than repeated verbal commands. Night staff complete a brief mobility check-in at handover (pain, fatigue, medication side effects) so day staff can adjust pacing.
How effectiveness is evidenced: Falls records include time, location, activity, and preceding factors. The monthly governance meeting reviews patterns and actions taken, not just counts. The service tracks mobility indicators (e.g., distance walked with support) alongside falls outcomes, showing improvement without unnecessary restriction.
Example 3: Eating and drinking support that protects choice and dignity
Context: A person is losing weight and staff are focused on “getting calories in”. Meals become rushed, and the person refuses support.
Support approach: The plan identifies retained preferences and strengths (finger foods, familiar brands, eating better in a quiet space). It sets out the enabling environment and communication approach, and clarifies escalation to clinical advice.
Day-to-day delivery detail: Staff offer smaller portions more often, with choice presented visually. The person is supported to sit in a preferred chair, with distractions reduced. Staff use the same encouragement phrases and avoid arguing about “needing to eat”. If intake is low, the plan specifies the next steps: offer alternatives, record intake, and trigger the escalation pathway (GP/dietetic advice depending on local arrangements). Hydration is supported through routine prompts linked to activities the person enjoys (tea after a walk, water with a specific snack).
How effectiveness is evidenced: Weekly weight and intake summaries are reviewed by the senior on-call. The service records what was tried and whether the person engaged. Improvement is evidenced through stable weight trend, reduced refusal episodes, and notes showing the person’s choices were respected.
Commissioner expectation (explicit)
Commissioner expectation: Commissioners typically expect providers to evidence that care plans translate into measurable outcomes and that risk is managed proportionately. In practice this means: (1) clear goals linked to independence (not just tasks completed), (2) review cycles that show learning and adaptation, and (3) escalation routes that are used appropriately rather than delayed until crisis. Providers who can demonstrate consistent plan delivery (through audits, supervision, and outcomes tracking) build confidence and reduce contract performance challenge.
Regulator / Inspector expectation (explicit)
Regulator / Inspector expectation (CQC): Inspectors will look for person-centred care that is not contradicted by restrictive, convenience-led practice. They commonly test whether staff understand the person’s strengths, how they prompt and enable, and how risk decisions are made and reviewed. They also expect records to show “least restrictive” thinking and timely review when needs change (for example, after falls, increased distress, or a decline in self-care). The strongest evidence is alignment across plans, daily notes, and governance actions.
Governance and assurance: keeping strengths-based practice consistent
Strengths-based planning fails when it is not governed. Providers typically maintain consistency through:
- Plan quality audits: sampling plans for “instruction clarity”, prompt sequences, and review triggers.
- Observed practice: short, routine observations (morning routine, mealtimes, mobility support) with feedback logged.
- Supervision focus: requiring staff to bring one strengths-based decision to supervision (what they tried, what changed, what evidence exists).
- Incident-to-learning loop: falls, distress episodes, refusals and safeguarding concerns feed into plan updates and staff learning, not just reporting.
The key operational test is simple: if you remove the policy folder, can a new staff member deliver the plan safely and consistently using the plan content, handover notes, and supervision prompts? If not, the plan is not yet strengths-based in practice.