The operating answer
For an in-scope product, connect the customer journey to evidence of the four outcomes: products and services, price and value, consumer understanding, and consumer support. A board report should support a decision about outcomes and improvements, not merely record that policies exist. [FCA] [FCA]
The workflow below is our editorial synthesis. Regulatory statements link to primary sources. Examples are hypothetical, and applicability requires a firm-specific assessment.
Start with a product and a customer group
Choose one product, one distribution route and one customer group. Write the product promise as a sentence a customer would recognise. “A payment account that lets a sole trader pay suppliers” is a useful start; “a customer-centric ecosystem” is not. Record who the product is intended for, who should not use it and what makes the customer dependent on it.
The scope assessment comes first. A payment institution should not assume that every service, relationship and customer sits inside the same Consumer Duty analysis. Keep the legal assessment beside the product file and show which services it covers. The FCA's payments review is a useful sector-specific starting point, not a substitute for that assessment. [FCA]
Walk the journey before selecting metrics
Follow the process from discovery to closure. Include onboarding, pricing, authentication, payment initiation, blocked transactions, complaints and access to support. Ask where a customer might misunderstand a condition or be unable to complete an important action.
For each stage, pair a possible harm with evidence that could reveal it. A support phone number is a feature; successful access to support is an outcome. A clear-looking fee table is an artefact; whether customers understand the circumstances in which the fee applies is a question to test. These distinctions stop the report becoming a catalogue of webpages.
Build a compact evidence matrix
For every outcome, record the question, the population, the data source, the owner and the action threshold. Use a mixture of quantitative measures and file review. A low average complaint rate can hide serious problems affecting a smaller group, while a high complaint count can reflect a change in recording rather than a change in harm.
Document the denominator. If the measure is the share of customers abandoning an authentication step, state whether it counts sessions, unique customers or attempts. Record exclusions and missing data. A reviewer should be able to recreate the number without asking the analyst to remember a spreadsheet transformation.
Test price and value in context
List the benefits a customer can actually use, the total charges and relevant non-financial costs. Separate a comparison of fees from a fair-value assessment. A cheaper headline price is not, by itself, proof of a better outcome.
Examine the circumstances that trigger additional charges. A product may be inexpensive for one use pattern but costly for another. Keep worked examples, the assumptions behind them and the rationale for any product changes. Where evidence is weak, describe the gap rather than filling it with a favourable conclusion.
Do not average away vulnerability
Compare the experience of customers in vulnerable circumstances where the firm has relevant, lawfully handled evidence. Consider practical barriers: an authentication process that assumes access to a particular device, a support route that relies on a long call, or a deadline that is not explained in an accessible way.
The FCA publishes observations specifically about payment firms and vulnerable customers. Use those observations to challenge the firm's own design and monitoring, without treating the examples as an exhaustive checklist. Keep sensitive customer information out of a general board appendix. [FCA]
Turn findings into decisions
Each material finding needs a proposed response, an accountable owner and a measure of success. Distinguish the action from the outcome it is intended to improve. “Rewrite the email” is an action; fewer customers misunderstanding a restriction is the test of whether it worked.
The board should see unresolved trade-offs. For example, stronger checks may reduce fraud while adding friction for legitimate customers. Show the evidence and the decision, including why a particular balance was chosen. Retain dissent and challenge where it changed the conclusion.
Make the annual review usable between meetings
The FCA expects the governing body to review and approve the firm's report on customer outcomes at least annually. Its published review of board reports highlights the quality of evidence, challenge and actions rather than a single required layout. [FCA]
Use a stable document structure so that a change is visible from one reporting period to the next. Carry open actions forward, explain changed metrics and distinguish a new issue from a newly discovered old issue. Do not wait for the annual pack to escalate an urgent customer harm.
Close the loop with a repeat test
After a change, run the same outcome test with a comparable population. Record whether the issue improved, whether a different problem emerged and what remains uncertain. Keep the original baseline, not only the successful result.
The working output is a traceable chain: customer need, product design, evidence, decision, change and follow-up. That chain is more useful than a dashboard with every indicator coloured green. The checklist below is an editorial aid for organising the work, not a statement that completion proves compliance.
| Outcome question | Example evidence | Decision owner |
|---|---|---|
| Can customers understand restrictions? | Tested wording and comprehension findings | Product and compliance |
| Can customers obtain support? | Contact attempts, successful resolution and file samples | Customer operations |
| Does the product offer fair value? | Benefits, total charges and customer-use scenarios | Product governance |
| Did a change improve the outcome? | Comparable before-and-after test | Named action owner |
Working checklist
Progress is saved only in this browser when local storage is available. Ticks record your work; they are not a compliance score.
Method, assumptions and limits
We use official sources for regulatory facts and label our suggested workflows as editorial methods. Illustrative examples are hypothetical. The content does not establish the position of any individual firm and is not a prescribed regulator template.
Source review date: 12 November 2026. No automatic monitoring is running. Check the underlying document, applicable entity, activity and jurisdiction before using this material.
Read the full methodologyQuestions, answered.
Is a board report template enough?
No. A template can organise the file, but the report needs evidence of outcomes, a reasoned assessment, governing-body review and follow-through.
Does this site certify Consumer Duty compliance?
No. It offers an editorial operating framework. Applicability and compliance require assessment against the current rules and the firm’s circumstances.
Can complaint data be the only measure?
A single metric is unlikely to describe the whole journey. Pair complaints with journey-specific data, file reviews and evidence of customer understanding.
Sources & scope
Primary sources used for this research edition. Document dates and commencement dates are different fields. Recheck the issuing authority before acting.
- FCA: Consumer Duty information for firmsGuidance · source reviewed 12 November 2026
- FCA: Consumer Duty board reports: good practice and improvementReview · source reviewed 12 November 2026
- FCA: Payments Consumer Duty multi-firm reviewReview · source reviewed 12 November 2026
- FCA: Payments firms: outcomes for consumers in vulnerable circumstancesReview · source reviewed 12 November 2026