Plans fail in two predictable ways. They are written in service language rather than the person’s, so the person does not recognise their own life in them. And they list aspirations without owners or dates, so nothing is ever late and nothing is ever done. Both are fixable in the writing.

What a usable plan contains

  1. The outcomes the person wants — in their words. “I want to be able to get to my sister’s on my own” is an outcome. “Increased community participation” is a category.
  2. The needs the plan addresses — linked to the assessment.
  3. Actions — each one specific, with a named owner (including the person themselves where appropriate) and a date.
  4. Who does what — services, family, the person. Contact details where a relative or new worker would need them.
  5. Risks and how they are managed — the contingency: what happens if a support falls through, who to call.
  6. Review — a date, and what success looks like at that date.
  7. Agreement — the person’s view of the plan, and their signature or recorded agreement where your setting requires it.

Support plan example (extract)

SUPPORT PLAN — EXAMPLE EXTRACTDRAFT
REFERENCE: SP-2026-164 PERSON: Ms T., 42 PLAN DATE: 2 September 2026 REVIEW DATE: 14 October 2026 WORKER: H. Petrescu, Social Worker, Cluj Community Support OUTCOME 1 (Ms T.’s words): “I want to get back to work at least two days a week without my anxiety stopping me at the door.” Need: Anxiety limiting participation; no current treatment; supportive employer willing to phase return. Actions: 1. Ms T. to attend GP appointment booked for 5 September to discuss referral to psychological therapy — Ms T. 2. Worker to contact employer (with consent given 2 Sept) to agree a phased return starting mid-October — H. Petrescu, by 12 September. 3. Ms T. to practise the graded exposure plan from the anxiety workbook, starting with a 20-minute visit to the workplace café — Ms T., first visit by 16 September. Contingency: If the therapy waiting list exceeds 8 weeks, worker to refer to the community wellbeing service (self-referral, 2-week wait). OUTCOME 2 (Ms T.’s words): “I don’t want my son to keep being the one who does everything.” Need: Son (16) carrying household and caring tasks; young carer’s assessment not yet offered. Actions: 4. Worker to refer son for a young carer’s assessment — H. Petrescu, by 9 September. 5. Ms T. and son to agree a shared task list at home — Ms T., by 16 September. SUCCESS AT REVIEW: Ms T. has attended the workplace at least three times; GP referral made; young carer’s assessment underway. MS T.’S VIEW: “This is what I asked for. The work bit scares me but I want to try.” Agreed 2 September.

Try CaseworkAI free

CaseworkAI drafts the home visit summaries and case notes that show whether a plan is working. Structured records make review a comparison, not a reconstruction.

Generate your first document →

Free for individual social workers, forever  ·  ICO registered  ·  GDPR compliant

Common mistakes

Free support plan template

CARE / SUPPORT PLAN TEMPLATE

Reference: [reference code only]
Plan date: [date]   Review date: [date]
Worker: [name, role, organisation]

OUTCOME [n] (person’s words)
[“…”]
Need
[linked to assessment]
Actions
[numbered; specific; owner; date]
Contingency
[if X fails, then Y; who to call]

[repeat per outcome]

SUCCESS AT REVIEW
[what will be true on the review date]

PERSON’S VIEW AND AGREEMENT
[own words; date]

Related guides

Frequently asked questions

How many outcomes should a plan have?

Three to five. More than that and none of them get the attention that makes them happen.

Should the person write the plan with me?

Yes where at all possible. A plan co-written in the person’s words is one they recognise and one they will hold you to.

How often should plans be reviewed?

Settings vary; six to twelve weeks is common for active support. The date matters less than having one, with a definition of success attached.