What changes in a file when a client is flagged vulnerable: a concrete checklist
Flagging a client as vulnerable changes four things in the file. Each must be visible to a reviewer reading cold.
What the FCA says about adjusting for vulnerability
The Consumer Duty's expectations for vulnerable customers are not satisfied by the flag itself — the firm must respond to the characteristics identified and record the response. The FCA's Consumer Duty pages and the Consumer Duty publications library carry the guidance and the good-practice examples that show what that response looks like in a file.
The pattern in review findings is consistent: the flag is recorded but nothing else changes, or the changes happen and are never documented. This checklist closes both gaps in one pass.
The four adjustments
Suitability evidence
The vulnerability consideration is documented — outcomes, reasoning, and mitigations — not left as an unrecorded judgement.
Communication
Plain language, larger text, more time for decisions, or a named contact — the adjustments the driver calls for, recorded.
Charges
Any impact on cost or fair value — for example, a client who cannot absorb losses needs a recommendation that matches their capacity.
Reviews
The review frequency and next date, adjusted if the client's circumstances warrant more frequent check-ins.
Worked example: one client, four changes
The same flagged client, two files. Anonymised and illustrative.
Before
The client was flagged vulnerable in one line. The file is otherwise unchanged — same recommendation, same standard charge, same review date, nothing recorded about communication or capacity.
After
Suitability evidence updated with the consideration and reasoning; communication adjusted (simpler wording, more time, a named contact); charges reviewed against capacity — fees spread over two quarters; reviews moved to quarterly with the next date recorded. Four changes, all visible in the file.
Common mistakes when a client is flagged
- The flag with no changes. Vulnerability identified and the file carries on as if nothing happened.
- Changes made, none recorded. The adviser adjusted the process in conversation; the file shows none of it.
- Charges untouched regardless of capacity. A recommendation and fee structure that take no account of the client's ability to absorb loss.
- Review frequency never revisited. The annual date stands even though the client's circumstances warrant more frequent check-ins.
The file-change checklist
| Area | What changes in the file | The evidence |
|---|---|---|
| Suitability evidence | Consideration, outcome, reasoning recorded. | A reviewer can follow the judgement. |
| Communication | The adjustment the driver calls for. | The response, not just the label. |
| Charges | Cost and value checked against capacity. | Fair value is visible in the file. |
| Reviews | Frequency and next date adjusted. | Monitoring continues beyond the flag. |
Related reads
This checklist is the practical branch of the vulnerable customers hub. Write the adjustments with the one-paragraph documentation wording and keep the record live with the monitoring loop guide.
Frequently asked questions
Does flagging vulnerability always change the recommendation?
Not necessarily. The process changes first — communication, timing, charges, review frequency — and the recommendation only changes where the client's circumstances genuinely require it. Either way, the response is recorded.
Must every adjustment be documented?
Yes. An adjustment that exists only in conversation is invisible to a reviewer. The file must show the flag, the outcome, and the response — that is what makes the difference between a label and evidence.
Is a vulnerable client a compliance problem?
No. Vulnerability is a client circumstance, not a failing. The problem is an unrecorded one — a flag with no documented response reads the same as no flag at all.
Your next step
Take one flagged client and run the four adjustments through their file — evidence, communication, charges, reviews — and record each change. Start a free trial or see pricing.