Measuring Recovery Without Medicalising It: Practical Outcome Domains for Community Mental Health Services
Outcome measurement in community mental health can drift into two unhelpful extremes: either it becomes overly clinical and alienating, or it stays so narrative-led that it cannot be audited. The aim is a middle ground: outcomes that reflect real life, stay rooted in personal goals, and can still be evidenced through routine delivery records. This article sits within the wider collections on mental health outcomes and recovery and mental health service models and pathways, because outcome domains only work when they align with pathway design and the realities of commissioned support.
What “not medicalising recovery” actually means
Not medicalising recovery does not mean avoiding measurement. It means:
- Measuring functioning and self-management (what people can do and sustain), not only symptoms.
- Using indicators people recognise (sleep routine, leaving the house, managing bills, attending appointments) rather than clinical language as the default.
- Keeping goals in the person’s words, while adding an “observable translation” so staff can evidence change consistently.
Commissioners and contract managers typically accept this approach because it produces auditable evidence from routine records while staying aligned with person-centred delivery.
Practical outcome domains for adult community mental health
A small number of domains should be used across the service. Indicators are personalised within each domain, but the domains themselves stay stable so cohort reporting remains meaningful.
Domain 1: Safety, risk and crisis prevention
Indicators that avoid medicalisation: frequency of crisis contacts, early warning signs recognised and acted on, safety planning followed, escalation thresholds met appropriately, safeguarding concerns identified and addressed.
Evidence sources: crisis logs, risk reviews, safeguarding records, step-up/step-down notes, supervision entries confirming oversight when risk increases.
Domain 2: Stability and daily routines
Indicators: sleep/wake consistency, self-care tasks completed, meal routines, household management, medication routines where relevant, attendance at key appointments.
Evidence sources: structured care notes (what was done, support level), routine checklists, appointment confirmation recorded at reviews.
Domain 3: Meaningful activity and roles
Indicators: participation in chosen activities, steps towards education/volunteering/employment readiness, sustained engagement over weeks, independence level increasing.
Evidence sources: weekly plans, attendance records, graded independence tracking (“with support” versus “independent”).
Domain 4: Connection and community participation
Indicators: planned contact with supportive networks, time spent in community settings, confidence ladder progress, coping strategies used outside the home.
Evidence sources: activity records, debrief notes, updates to risk assessments based on real-world experiences.
Domain 5: Self-management and skills
Indicators: coping tools used between visits, problem-solving steps taken, reduced reliance on staff prompts, early help-seeking before escalation.
Evidence sources: skills practice notes, prompting plans, review notes showing step-down in staff input.
How to build person-centred indicators that remain measurable
A reliable method is to write each indicator using three components:
- Frequency (how often it happens)
- Quality (what “success” looks like)
- Support level (independent, prompted, supported, co-delivered)
For example, “attends GP appointment” becomes: “attends one planned GP appointment in the month, stays for the full consultation, asks two pre-agreed questions, and travels with prompts only.” This keeps the indicator rooted in real life and reduces inconsistent recording across staff.
Operational examples (day-to-day delivery and evidence)
Example 1: Measuring stability through routines, not symptom scores
Context: A person experiences fluctuating anxiety and low mood, with missed appointments and frequent day–night reversal. Traditional reporting focuses on mood, but commissioning review wants to know whether stability improved.
Support approach: The team agrees routine anchors: a consistent wake time, a morning self-care sequence, and one scheduled community task weekly. Coping tools are embedded (breathing routine, “reset plan” if sleep slips).
Day-to-day delivery detail: Staff record the routine as completed/partially completed with the support level required (independent/prompted/supported). When the routine slips, staff record the barrier (rumination, fatigue, avoidance) and apply the reset plan rather than simply noting “struggled”. Reviews occur every four weeks and explicitly compare the baseline fortnight to current fortnight.
How change is evidenced: improved appointment attendance, reduced day–night reversal, and reduced staff input required to re-establish routine. Evidence is drawn from routine logs, appointment records, and review notes showing the step-down in prompts over time.
Example 2: Confidence and community participation without vague claims
Context: A person has not left home alone for months, but case notes have become repetitive (“encouraged to go out”). Commissioners want evidence of progression and the service wants to avoid pressuring the person.
Support approach: A confidence ladder is co-produced: standing outside the front door, short walk to a local landmark, then a low-demand community venue. Each rung has a coping plan and a “stop rule” that protects choice and safety.
Day-to-day delivery detail: Each attempt is documented with duration, support level, coping strategy use, and a debrief in the person’s words. Staff record whether the stop rule was used and why, and the plan is adjusted (timing, route, accompaniment level). Risk assessment is updated based on observed triggers rather than static assumptions.
How change is evidenced: increased frequency and duration of community activity, reduced need for accompaniment, and consistent use of coping strategies recorded in debrief notes. Progress is tracked by rung achieved and sustained for two consecutive weeks.
Example 3: Self-management skills evidenced through reduced escalation
Context: A person engages well in sessions but still escalates to crisis when overwhelmed. The risk is that the service reports “engagement” but cannot show impact.
Support approach: The service implements an early warning checklist and trains the person in a short “decision tree” (what to do at early, mid and late warning stages). Step-up thresholds are agreed with partner services where relevant.
Day-to-day delivery detail: At each contact, staff review whether early warning signs were present since the last visit and whether the decision tree was used. Staff record the exact action taken (e.g. used coping plan, contacted support, applied distraction routine) and whether escalation thresholds were reached. A senior reviews patterns weekly for high-risk cases to ensure responses are timely and consistent.
How change is evidenced: earlier help-seeking, fewer late-stage escalations, and shorter destabilisation periods. Evidence is triangulated from crisis logs, care notes referencing the early warning checklist, and monthly summaries comparing baseline escalation patterns with current patterns.
Explicit expectations that must be met
Commissioner expectation
Commissioners expect outcome domains to translate into auditable reporting that shows attributable impact. They will look for baselines, defined indicators, and a consistent review rhythm. They also expect providers to explain variance across a cohort (why some people improve quickly and others need sustained intensity) using delivery detail and governance evidence, not generic statements.
Regulator / Inspector expectation (e.g. CQC)
Inspectors expect person-centred care that is safe, rights-respecting and responsive. Measurement must not become coercive, and it must not drive restrictive practice without justification. Inspectors will test whether plans are implemented consistently, whether risk is managed proportionately (including positive risk-taking), and whether learning from incidents or safeguarding concerns feeds back into planning and outcomes review.
Governance: keeping measurement credible without adding burden
To sustain outcome domains, build them into existing processes:
- Supervision prompts to check staff can explain goals, indicators and evidence in the file.
- Monthly outcomes governance reviewing cohort trends, exceptions and data quality (including missing baselines).
- Case audits testing whether reported progress matches routine notes, risk reviews and recorded pathway events.
When these mechanisms are in place, services can evidence recovery without medicalising it, because measurement becomes a structured reflection of everyday practice rather than an external scoring exercise.