Consumer Duty outcomes monitoring in practice: what good firms actually measure
The FCA's good and poor-practice publications keep pointing at the same difference: firms that measure their outcomes, and firms that measure their intentions. Here is what the former actually track.
Where good-practice examples come from
The FCA's Consumer Duty publications library keeps publishing good and poor-practice examples of outcomes monitoring. The examples below are anonymised composites of the patterns those publications describe — not case studies of any named firm.
The four outcome areas under the Consumer Duty — products and services, price and value, consumer understanding, and consumer support — are how the FCA frames what good looks like. Monitoring is judged on evidence: what the firm can demonstrate it measured and changed. the Consumer Duty pages set out those outcome areas in full.
What good firms measure
Four recurring patterns separate good monitoring from paper monitoring. Each is listed with the indicator behind it.
The board pack that shows the loop closing
A firm whose board report shows last quarter's ambers with their fixes and owners — the loop visible, not just the count.
The vulnerability log that survives a cold read
A firm that logs vulnerability signals with the outcome and mitigation, so a reviewer can see consideration happened — not just that it was claimed.
The quarterly hour made repeatable
A small firm running the same fixed rubric every quarter — graded logs, gap list, one page to the board — producing comparable data quarter over quarter.
The fee-for-no-service signal caught early
A firm whose service record flags a client who did not receive the promised review, before a complaint or a file review finds it.
The pattern is the same: structured, repeated, evidenced — and translated to file-level indicators. That is the evidence an information request or a board report can carry.
Worked example: one theme, two firms
The same theme — whether reviews are finding real issues — looked very different in two firms' records. Compare the two versions (anonymised composites).
Before
“The compliance calendar is on track; oversight meetings were held as scheduled. No issues identified.” — activity reported as if it were outcomes.
After
“Same quarter: pass rates by check area — product governance 92%, cost disclosure 78%. Three amber themes with fixes and owners. Vulnerability outcomes logged per file.”
Common mistakes in choosing indicators
- Measuring activity, not outcomes. Reviews completed says nothing about whether customers got good outcomes; the indicator has to say what the review found.
- Indicators untraceable to a file. A metric that cannot be tied back to a specific file field cannot be audited — and it is the file that carries the evidence.
- Changing indicators every quarter. New indicators each quarter destroy the trend; the same checks over time are what make the comparison honest.
- Taking indicators to the board without fixes. Numbers without the actions attached leave the “so what” unanswered.
Translating examples to file-level indicators
Each example pattern maps to an indicator a firm can compute from its own files — and the file field that produces it.
| What the firm wanted to know | Indicator | File-level source |
|---|---|---|
| Are reviews finding real issues? | Fail rate by check area | The grade column in the review log |
| Are fixes actually landing? | Amber re-score rate | The re-scored row in the next log |
| Is the service record covering the fee? | Reviews delivered vs reviews due | Delivered and next-review dates in the service record |
| Were vulnerable clients considered? | Adjustments logged per vulnerability signal | The vulnerability field in the client file |
Related reads
This is one lens on the monitoring cycle — start at the outcomes monitoring hub for the framework, then the audit-ready evidence list for the artefacts a cold read needs, and the one-page board summary for where the pattern lands.
Frequently asked questions
Can a small firm copy these examples directly?
The pattern can be copied — structured, repeated, evidenced, and translated to file-level indicators — but the indicators should fit the firm's own files. A one-adviser firm's proof of the loop closing is a one-page board summary, not a reporting suite.
Where do these examples come from?
The FCA's publications library carries good and poor-practice examples of outcomes monitoring, and the four outcome areas the duty covers. The firms in this guide are anonymised composites of the patterns those publications describe.
Your next step
Pick one outcome area and one theme from your own files, translate it into a file-level indicator, and report it with the fix attached. Proven Duty produces the graded logs and the indicator table from the same file review. Start with a free trial or see pricing.