A step-by-step guide to building a DISP-compliant complaints process that meets FCA timelines, captures root cause data, and reduces Financial Ombudsman referrals.
The FCA's Dispute Resolution sourcebook (DISP) sets out detailed requirements for how regulated firms must handle complaints. For insurance firms, the stakes are significant: missed deadlines trigger automatic Financial Ombudsman Service (FOS) referral rights, poor complaint outcomes attract supervisory attention, and complaints data feeds directly into the FCA's risk assessment of your firm.
Despite this, many insurance firms still rely on fragmented processes — emails, spreadsheets, and manual diary entries — to track complaints through DISP timelines. This creates real risk: a single missed 8-week deadline can result in a FOS referral, an upheld decision, and reputational damage. At scale, systemic failures in complaints handling have led to multi-million pound redress exercises.
The FCA has consistently identified complaints handling as an area where firms underperform. The regulator expects firms not just to resolve individual complaints, but to use complaints data to identify systemic issues and prevent future harm — a requirement reinforced by Consumer Duty.
A robust complaints framework maps every requirement in DISP 1 to a defined process, owner, and system control. It covers the full lifecycle: identification and logging, acknowledgement, investigation, resolution, final response, FOS referral handling, and root cause analysis. Each stage has specific DISP requirements that must be met.
The framework should be supported by workflow automation that enforces deadlines, escalates overdue cases, and captures the data needed for your biannual complaints data return and internal MI reporting. Manual processes simply cannot provide the consistency and audit trail the FCA expects.
Critically, the framework must connect individual complaint outcomes to broader patterns. Under Consumer Duty and SYSC 10A, firms must demonstrate they are learning from complaints and taking action to address root causes — not just resolving cases one at a time.
Follow these steps to build a complaints handling framework that meets every DISP requirement and turns complaints data into actionable business intelligence.
Under DISP 1.1.1R, a complaint is any expression of dissatisfaction — whether oral or written — about the provision of, or failure to provide, a financial service. Ensure all customer-facing staff understand this broad definition and can identify complaints even when the customer does not use the word "complaint". Train staff to distinguish between complaints and general enquiries, and err on the side of logging as a complaint when in doubt.
Log every complaint immediately with a unique reference number, the date of receipt, the customer's details, the nature of the complaint, and the product or service involved. Under DISP 1.6, firms must send a prompt written response or final response within the applicable timelines; acknowledgement timing should be firm-defined and prompt (best practice is within 1 business day). The acknowledgement should confirm the complaint has been received, provide the reference number, and set expectations for the investigation timeline.
DISP sets out specific deadlines: 3 business days for summary resolution (DISP 1.5), 8 weeks for a final response for most complaints (DISP 1.6), and 15/35 business days for payment services and e-money complaints where applicable. Build automated deadline tracking into your workflow system, with escalation triggers at key milestones — for example, at 4 weeks and 6 weeks — to ensure cases do not drift past the deadline.
Create clear investigation templates that ensure the handler considers all relevant evidence: policy documentation, call recordings, system records, and the customer's account of events. Define decision-making criteria aligned to DISP 1.4 (fair and consistent outcomes) and ensure handlers have appropriate authority levels for redress offers. Complex or high-value complaints should have a defined escalation path to senior staff.
Your final response must meet the requirements in DISP 1.6.2R: it must set out your final decision, explain the reasoning, detail any redress offered, and inform the customer of their right to refer the matter to the Financial Ombudsman Service within 6 months. Use approved templates to ensure consistent, compliant language — but personalise the explanation to the individual case.
When a complaint is referred to the FOS, you need a defined process for responding to the Ombudsman's enquiries within their timescales. Track FOS outcomes — upheld, partially upheld, or not upheld — and feed this data back into your root cause analysis. A high uphold rate signals that your internal decision-making is not aligned with the Ombudsman's approach.
Categorise complaints by root cause — product design, sales practices, claims handling, administration errors, communication failures — and analyse trends over time. Report findings to senior management and the board at least quarterly. Under Consumer Duty, you must demonstrate that complaints data informs product governance, fair value assessments, and customer outcomes monitoring.
Ensure your system can produce the data needed for the FCA's biannual complaints data return, including complaint volumes by product and cause, resolution timescales, redress paid, and FOS referral outcomes. Automate this reporting where possible to reduce manual effort and error risk.
Give front-line staff clear authority and guidelines to resolve straightforward complaints quickly. The DISP "next business day" rule allows early resolution without a formal final response, which improves customer experience and reduces the administrative burden on your complaints team.
The FCA expects complaints to be investigated fairly and objectively. Where practical, ensure the person investigating the complaint is independent of the team whose actions are being complained about. This is explicitly required for certain complaint types and is best practice for all.
Track complaints from customers who have been identified as vulnerable, and analyse whether their outcomes are consistent with those of other customers. Consumer Duty requires firms to deliver good outcomes for all customers, including those in vulnerable circumstances.
Do not wait for complaint volumes to spike before acting. Use trend analysis and early warning indicators — such as a sudden increase in complaints about a specific product or process — to identify and address issues before they become systemic.
Implement a quality assurance programme that reviews a sample of closed complaint files each month. Assess compliance with DISP requirements, consistency of outcomes, quality of investigation, and adequacy of the final response letter.
Final response letters and acknowledgement templates should be reviewed at least annually, or whenever DISP rules change, to ensure they remain compliant. Include Consumer Duty language where appropriate to demonstrate good outcomes focus.
Staff can recognise and escalate complaints in line with the DISP 1.1.1R definition.
Workflow system enforces milestones at 3 days, 4 weeks, 6 weeks, and 8 weeks.
Identify potential gaps in your fca compliance processes with our free self-assessment tool. Not a substitute for professional advice.
Try these related tools — no sign-up required.
Automated deadline monitoring ensures every complaint receives a final response within the FCA's mandatory 8-week timeframe, reducing FOS referral risk and regulatory exposure.
complaints handlingMove beyond individual complaint resolution to identify and address the systemic issues driving complaint volumes across your insurance operations.
fca complianceA definitive guide to meeting FCA record-keeping obligations under SYSC 9, COBS, ICOBS, and DISP — with practical retention schedules and storage recommendations.
SwiftCase provides automated deadline tracking, structured complaint logging, and root cause reporting — helping you meet every DISP requirement with confidence.
