Who writes the support plan?

A key support worker is usually the named author, but a good support plan is written with the resident rather than about them. Where capacity is a consideration, an advocate or family member may also contribute. The named worker is accountable for the final document.

How are support plan goals written?

Goals should be resident-driven, specific enough to work on, framed positively, and written in the resident's own words where possible. Abstract goals like improve independence are less useful than concrete ones like cook one new meal at home every week.

What is the difference between a support plan and a care plan?

A care plan, usually found in regulated care settings, focuses on clinical care, medication, and physical health needs. A support plan, used in supported housing, focuses on tenancy sustainment, independence, and outcomes across months or years. Both may contain overlapping content for residents with complex needs.

Does a support plan need to be signed by the resident?

Yes. The signature confirms that the resident has seen, understood, and agreed to the plan. Plans without a resident signature are routinely flagged during audits and inspections as incomplete.

What makes a poor support plan?

Generic language copied from a template, goals that never change across reviews, consent sections that were ticked but never explained, and a disconnect between the plan and what session records describe. Inspectors spot these patterns quickly.

Can a support plan be completed digitally?

Yes. Digital support plans signed with digital signatures are widely accepted by the Care Quality Commission and local authority auditors. The audit trail they produce is often stronger than a paper version because every change is attributable and timestamped.

How does the support plan relate to the risk assessment?

The risk assessment identifies risks to the resident or from the resident, and the support plan describes how those risks will be managed. Changes to one should usually trigger a review of the other. Good software links them automatically.

How long should a support plan be?

Long enough to cover the resident's real goals and needs, short enough for a new worker to read in ten minutes and understand what matters. Most plans run to four or five focused pages. Inflated plans are not better plans.

What is a Support Plan in Supported Housing? A Complete Guide

Q: How often should a support plan be reviewed?

Most providers review the support plan at twelve weeks after intake, then every three months, then annually once the placement is settled. A significant change in the resident's circumstances, such as a safeguarding concern, a hospital admission, or a major life event, should trigger a review regardless of the schedule.

The support plan is the most important document in a supported housing placement. It is where the initial needs assessment becomes real work, where the resident's voice is turned into action, and where the service's responsibility to the resident is written down clearly enough to hold everyone accountable. It is also the document most often written badly, because the temptation to treat it as a form to fill in is strong and the consequences of doing that do not show up for months.

This guide explains what a support plan is, who writes it, what it must include, how to frame goals, and how to review it. It is written for support workers, service managers, and the occasional inspector who wants a plain-language version of what good looks like.

What is a support plan in supported housing?

A support plan is the written record of the support a resident will receive during their placement. It turns the intake assessment into action by setting out goals, the support needed to achieve them, the worker and resident roles, the review schedule, and the consent framework.

The support plan sits at the centre of every other document in the tenancy. Session records reference its goals. Risk assessments influence its content. Review notes update it. Exit summaries describe what it achieved. Without a strong support plan, the rest of the documentation stack has no anchor.

It is distinct from a care plan, used in regulated care settings, which focuses on clinical care and medication. Supported housing is about independent living, tenancy sustainment, and personal outcomes. The plan should reflect that orientation. Where a service provides both personal care and support, the two plans may overlap but should remain identifiable.

Who writes a support plan?

A key support worker is usually the named author. In practice, a good support plan is written with the resident, not about them. The named worker is accountable for the final document, but the resident's voice should be audible in every section.

Other people who sometimes contribute:

An advocate where the resident wants or needs support understanding the plan
A family member where the resident has consented to their involvement
A referring agency or local authority contact where the placement is funded with specific outcomes
A senior worker or service manager providing quality oversight

The accountable author is whoever signed off on the document. That person should be named explicitly in the plan itself, not just implied by the system login.

When is a support plan created?

Most providers produce the first support plan within two to four weeks of move-in, flowing directly from the initial needs assessment. Producing it sooner risks writing a plan that reflects the resident's first day rather than a realistic picture of their needs. Producing it later creates a documentation gap where session records have no plan to reference.

A sensible sequence:

Intake conversation and initial needs assessment inside the first week
Immediate risk assessment, covering urgent concerns
First support plan drafted within two to four weeks
Plan signed and countersigned
Plan reviewed at twelve weeks and revised as needed

What must a support plan include?

At minimum, a support plan includes the resident's agreed goals, the support tasks that will help achieve them, the worker's role, the resident's role, the review cadence, consent to share information with named agencies, and signatures from both the worker and resident. In more detail:

Resident background and summary

A short paragraph that places the resident in context. Not a biography, just enough that a new worker can open the plan and understand who they are working with. Include age range, previous housing history in brief, referring agency if any, and anything the resident wants highlighted.

Goals

The heart of the plan. Three to six active goals at any one time is usually right. Fewer than three is thin; more than six tends to mean most of them get ignored.

Each goal should include:

A short title in plain language
The resident's words describing what success looks like
The support tasks needed to achieve it
The worker's role
The resident's role
A target timeframe or review date

Support tasks

How the plan will actually get delivered. Specific, practical, and attributable to a worker. Generic phrases like provide emotional support are less useful than phone the resident on Tuesday mornings to plan the week.

Risk summary

A cross-reference to the full risk assessment, with a short summary of the key risks and the controls described in the plan. The risk assessment is the detailed document; the support plan carries the summary.

A specific record of what the resident has agreed to. Not a generic yes-to-everything consent. Named agencies, named purposes, and the option to revoke. The Information Commissioner's Office guidance on UK GDPR is the right reference for how consent should be framed.

Review cadence

When the plan will next be reviewed, by whom, and what would trigger an early review. Do not leave this vague.

Signatures

The resident signs. The key worker signs. A manager may also sign as part of a quality check. Digital signatures with timestamps are fine, arguably stronger than paper.

How should support plan goals be written?

Goals should be resident-driven, specific enough to work on, framed positively, and written in the resident's own words where possible.

Poor goals to avoid:

Too abstract. Improve independent living skills. What does that mean, exactly?
Too provider-flavoured. Will engage positively with support. This is language a funder likes; it is not a goal a resident can work on.
Too many at once. Nine or ten goals, none of which anyone has capacity to actually work on.
Never changing. If a goal has survived three reviews unchanged, it is probably not being worked on.
Deficit-framed. Stop drinking by the end of the year is a useful thing to work towards, but Identify three situations where I can ask for help instead of drinking works better as a support plan goal.

Good goals share four properties: they come from the resident, they are specific, they describe a positive action or outcome, and they can be worked on between reviews.

A good support plan reads like a conversation between the worker and the resident about what matters, turned into a document. A bad one reads like a form filled in by a worker on behalf of a resident who was not really consulted.

How often should a support plan be reviewed?

Most providers review the support plan at twelve weeks, then every three months, then annually once the placement is settled. A significant change in the resident's circumstances should trigger a review regardless of the schedule. Examples of trigger events:

A safeguarding concern raised
A hospital admission or discharge
A change in benefits or income
A relationship breakdown that affects housing
A new diagnosis or treatment
An incident recorded against the resident
A resident request for a review

The review should be a real conversation, not a desk exercise. Pull out the goals, read them with the resident, and ask what has changed. If a goal has been achieved, celebrate it explicitly. If a goal is stuck, ask why. If a goal no longer matters, remove it.

How does the support plan relate to other documents?

The support plan is the hub, and the other documents sit around it.

| Document | Relationship to support plan |

|---|---|

| Initial needs assessment | Source document. The support plan is written from it. |

| Risk assessment | Parallel document. Changes in either should trigger review of the other. |

| Session records | Operational. Each session should reference the goals being worked on. |

| Review notes | Update the plan. Every review updates the goals, tasks, or cadence. |

| Safeguarding log | Cross-reference. Safeguarding actions may result in plan changes. |

| Exit documentation | Summary of outcomes achieved against the plan. |

A documentation platform that links these automatically saves hours of cross-checking.

Common mistakes to avoid

Four patterns that appear repeatedly in plans flagged at audit and inspection:

Templates masquerading as plans. If three residents' plans look substantially identical, the plans are not about those residents. Use templates as a scaffold, not a script.
Consent buried in a tick box. A single tick covering consent to all information sharing with all agencies is not meaningful consent. Break it out by purpose and by recipient.
Missing reviews. Every missed review review shows up in the audit trail. Missing one is human. Missing six suggests a service-level issue.
Plans that diverge from session records. If the plan says the resident is working on independent shopping and the session records all describe worker-led shopping trips, the plan has drifted from reality. Update one or the other.

How the Care Quality Commission views support plans

Where the Care Quality Commission regulates the service, inspectors look at support plans as evidence under several of the five key questions. They expect to see personalised content, clear goals, evidence of review, and alignment between the plan and what session records describe. The Single Assessment Framework's Quality Statements elevate the weight given to personalisation and resident voice, which raises the bar on plan quality.

For providers who are not CQC-regulated, the same expectations apply under commissioner audits and, increasingly, under local authority licensing introduced by the Supported Housing (Regulatory Oversight) Act 2023.

How does a documentation platform change the work?

A support plan produced on paper is typically written by a worker in the evening, based on notes taken during a session earlier in the day. The resident is not present. The sections are dictated by whatever template the provider uses. Signatures are often chased later.

A support plan produced through a conversational platform like Residoc runs differently. The worker has the planning conversation with the resident, the platform structures the conversation into the plan as it happens, the resident reviews and signs the draft before leaving, and the completed plan is in the system that evening.

The difference in time is real. The difference in quality is bigger. A plan written during the conversation reflects what the resident actually said. A plan written afterwards reflects what the worker remembers.

Quick test

Hand a support plan to someone who has never met the resident and ask them to describe the person and their goals in two sentences. If they struggle, the plan needs rewriting around the resident. If they nail it, the plan is doing its job.

Sources and further reading

Produce support plans in a conversation, not an afternoon

Residoc turns a single conversation with the resident into a structured support plan with goals, consent, review schedule, and signatures. No blank forms, no evening write-ups.

Book a demo