DNACPR and ReSPECT in Dementia: Making Treatment Escalation Plans Work in Day-to-Day Care

February 25, 2026

DNACPR and ReSPECT documentation is common in dementia end of life care, but paperwork alone does not prevent crisis admissions or conflict. Plans only work when they are operational: visible to staff, aligned to capacity and best-interests decision-making, understood by families, and linked to escalation routes that function out of hours. This article sits within dementia end-of-life and advance care planning guidance and connects directly to dementia service models and operational delivery, because treatment escalation fails when roles, records and communication are not designed into the daily running of the service. The focus here is day-to-day governance: how you make escalation decisions consistent, defensible and person-led.

Start with the purpose: what the plan is (and isn’t)

DNACPR decisions relate to cardiopulmonary resuscitation only; they do not mean “do not treat”. ReSPECT (or equivalent treatment escalation planning) captures broader preferences and clinical recommendations: what to do in deterioration, what to avoid, and what matters to the person. In dementia, the key risk is drift: staff interpret a DNACPR as a blanket ceiling of care, or families think a plan blocks comfort treatments. Your operational job is to prevent misunderstandings by translating plans into clear actions and thresholds.

Commissioner expectation (explicit)

Commissioners expect clear escalation pathways and decision records that reduce inappropriate conveyance while protecting safety. They look for evidence that staff know when to call clinical support, what information to provide, and how decisions are documented and reviewed.

Regulator / inspector expectation (explicit)

CQC inspectors expect person-centred, lawful decision-making that reflects the Mental Capacity Act, demonstrates involvement of the person (where possible) and family/representatives, and shows that staff understand and apply escalation plans consistently, including out of hours.

Make escalation plans usable: “what staff do at 03:00”

The best plans are written in clinical language, but frontline staff need an operational version. A practical approach is to create a one-page “escalation summary” within the care record that includes:

Baseline and red flags: what is usual for the person and what indicates deterioration.
Do / don’t list: actions to take immediately (comfort measures, observations) and treatments to avoid (where clinically agreed).
Contacts and order: who to call first, second, third, with expected response times.
Information to share: current symptoms, recent infections, medication changes, hydration, and plan status.
Family communication rules: who is contacted, when, and what is recorded.

This is not extra paperwork for its own sake: it is how you make a plan functional across shifts and agency staff.

Capacity and best interests: build a repeatable pathway

Dementia services often face fluctuating capacity, especially during infection, delirium or distress. Services score well (and stay safe) when they can evidence a consistent decision pathway:

Capacity is decision-specific: assessed for the particular choice at the time it needs to be made.
Best-interests decisions are documented: who was involved, what options were considered, and how the least restrictive option was chosen.
Known wishes are surfaced: past statements, values, cultural needs, and what “good comfort” looks like for the person.

Operationally, this means staff know what to record and who to escalate to when uncertainty arises, rather than improvising or deferring until crisis.

Operational Example 1: Preventing “DNACPR means no treatment” drift

Context: A person with dementia has a DNACPR in place. They develop a suspected chest infection and become breathless. A new staff member suggests “we shouldn’t call anyone because they are DNACPR”.

Support approach: The shift lead uses the escalation summary: DNACPR does not restrict treatment for infection. The plan states the thresholds for clinical contact (increased respiratory rate, reduced intake, new confusion) and the preferred route (community nursing/GP review before 999 unless severe distress).

Day-to-day delivery detail: Staff complete observations, implement comfort measures (positioning, mouth care, calm environment), and contact the agreed clinical service within 30 minutes. The family is updated using a consistent script: what has changed, what actions are being taken, and what the plan means in practice.

How effectiveness is evidenced: The manager reviews the record the next day, logs the near-miss “DNACPR misunderstanding” as a learning item, and uses it in a team briefing. Monthly sampling tracks whether DNACPR plans are being referenced correctly during deterioration episodes.

Communication with families: prevent conflict by designing routine updates

End of life care in dementia breaks down when families feel surprised, excluded or distrustful. A robust approach builds communication into the model rather than relying on goodwill:

Planned conversations: schedule review points (after hospital discharge, after significant deterioration, after a major medication change).
Single named lead: a consistent staff role responsible for coordinating updates and documenting decisions.
Clear language: avoid euphemisms; explain what comfort-focused care involves and what escalation still looks like.

Where disagreement exists, record the different views, confirm what is clinically recommended, and escalate to appropriate professionals for review rather than allowing conflict to sit unaddressed.

Operational Example 2: ReSPECT used to reduce avoidable admissions

Context: A person has recurrent falls and episodes of agitation in the evenings. The family repeatedly calls 999 during distress, leading to A&E conveyance and long waits that worsen delirium.

Support approach: The service works with the GP/community team to update the ReSPECT plan with clear deterioration triggers and preferred actions. The plan states that, unless there is suspected fracture, uncontrolled bleeding or severe head injury signs, the first response is comfort measures, observation, and clinical advice rather than automatic conveyance.

Day-to-day delivery detail: Staff follow a structured post-fall routine: pain cues check, mobility observation, neuro red flags screening, and a timed re-check schedule. The on-call lead contacts clinical advice for borderline cases and documents the decision rationale. The family receives a same-day summary explaining the checks completed and why hospital was or wasn’t needed.

How effectiveness is evidenced: Over a defined period, the service tracks the number of 999 calls, A&E attendances, and the reasons for conveyance. The governance meeting reviews whether decisions matched the plan and whether the plan needs refinement. The evidence is not “we avoided hospital” but “we followed a safe pathway and can show it”.

Records that stand up to scrutiny: what good looks like

Escalation plans are legally and emotionally high-stakes. Your records need to show that actions were proportionate and person-led. Strong documentation typically includes:

What changed: specific observations, not “declining”.
What the plan said: the relevant part of DNACPR/ReSPECT/escalation summary referenced in the note.
Who was contacted: names/roles, times, and advice given.
Decision rationale: why this option was chosen, including capacity/best interests where relevant.
Follow-up: monitoring schedule, comfort actions, and next review point.

If you use digital systems, specify how staff can access the plan quickly, how alerts work, and how you manage temporary outages without losing access to critical decisions.

Operational Example 3: Out-of-hours deterioration with a defensible decision trail

Context: At 02:30, a person with dementia is drowsier than usual, eating less and breathing faster. The staff member is unsure whether to call 999.

Support approach: The staff member follows the escalation summary and uses the out-of-hours decision tree: observations first, comfort measures, call the on-call lead, then contact the agreed clinical line unless red flags are present.

Day-to-day delivery detail: The on-call lead checks the ReSPECT summary: the preferred approach is community management where possible, with specific red flags that would trigger emergency services. The lead contacts clinical advice, relays the minimum dataset, and records the guidance received. Staff implement the monitoring schedule (e.g., re-checks at agreed intervals), document symptom changes, and update the family at an appropriate time with the facts and next steps.

How effectiveness is evidenced: The next day the manager verifies that the plan was accessible, followed and recorded. The case is included in monthly escalation sampling, and any gaps (e.g., missing observation fields, delayed call) become action items with re-check dates.

Governance: how you prove the system is consistent

Commissioners and inspectors respond to assurance loops. A practical governance package for DNACPR/ReSPECT includes:

Monthly sampling: review a set number of deterioration episodes where the plan was relevant.
Consistency checks: are staff decisions aligned with the plan, and are rationales recorded?
Family feedback themes: was communication timely, clear and respectful?
Training linkage: do audit findings drive refreshers, scenario practice and supervision prompts?

Where the service operates across multiple sites or teams, compare patterns: inconsistent decision-making is often a supervision and handover issue, not an individual issue.

Common failure modes (and the fixes that score)

Plans exist but aren’t used: fix by creating the operational one-page escalation summary and testing it in handovers.
Staff fear getting it wrong: fix with scenario drills, clear thresholds, and on-call support that is documented.
Family conflict escalates late: fix with planned review points, named lead responsibility, and documented best-interests pathways.
Records don’t show decision-making: fix with minimum record fields (change, plan reference, advice, rationale, follow-up).

When escalation plans are operationalised, they protect dignity, reduce crisis transfers, and make decision-making defensible under scrutiny. The goal is not to avoid hospital at all costs, but to ensure every escalation decision is safe, person-led and evidenced.