DISP Complaint Handling: Step-by-Step Regulatory Requirements

What this guide covers

This guide walks through the FCA DISP sourcebook as a step-by-step operational process. It is written for complaint operations teams, compliance officers, and quality assurance reviewers who need to translate regulatory text into daily procedure. The content reflects the DISP rules as at 31 March 2026.

DISP sits inside the FCA Handbook and applies to every FCA-authorised firm that deals with eligible complainants. The sourcebook covers complaint identification, acknowledgement, investigation, resolution, record keeping, and reporting. Firms that handle payment services or e-money complaints face additional obligations under PSD2 and the Payment Services Regulations, but DISP remains the structural baseline.

The practical goal is straightforward: identify complaints early, investigate them fairly, respond within regulatory deadlines, keep records that survive scrutiny, and make sure customers know how to escalate to the Financial Ombudsman Service when they are not satisfied.

Step 1: Identifying a complaint (DISP 1.2)

DISP 1.2 defines a complaint as any oral or written expression of dissatisfaction, whether justified or not, from or on behalf of a person about the provision of, or failure to provide, a financial services activity or a redress determination. The definition is deliberately broad. It does not require the customer to use the word "complaint" or to submit a formal form.

This breadth has direct operational consequences. Front-line staff in call centres, branch offices, email support, live chat, and social media teams must be trained to recognise complaints even when they arrive disguised as general feedback, account queries, or frustrated remarks. A customer who writes "I am unhappy with the charges on my account and want them reversed" is complaining, even if the email subject line says "Account query."

Firms that rely on customers to self-identify complaints will under-count and under-record, which creates both a DISP 1.9 record-keeping gap and a DISP 1.10 reporting gap. The safest approach is to build intake rules that flag expressions of dissatisfaction at the point of first contact.

• Train all customer-facing teams to recognise complaints regardless of the language or channel used.
• Do not require the customer to use a specific form, portal, or keyword to trigger the complaints process.
• Apply the DISP 1.2 definition to all channels including email, phone, chat, social media, and letter.
• Log the date, time, and channel of receipt immediately, as this timestamp starts the regulatory clock.

Step 2: Prompt acknowledgement

Once a complaint is identified, DISP requires the firm to send a prompt written acknowledgement. The rules do not define "prompt" with an exact hour count, but the FCA's supervisory expectation and accepted industry practice treat this as within one business day of receipt. Firms that wait several days to acknowledge a complaint risk both a poor customer experience and a supervisory finding.

The acknowledgement serves two purposes. First, it confirms to the customer that the firm has received the complaint and is treating it as such. Second, it establishes an auditable record of the start of the complaint-handling process. Without it, the firm's internal timeline is harder to defend if the case later reaches the ombudsman.

The content of the acknowledgement should be clear and specific. It should name the complaint handler or team responsible, provide contact details, and set a realistic expectation for next steps. Generic auto-replies that say "we have received your message" without referencing the complaint process are insufficient.

• Send a written acknowledgement within one business day of complaint receipt.
• Name the person or team handling the complaint and provide direct contact details.
• Confirm that the matter is being treated under the firm's formal complaints process.
• Include a reference number the customer can use in future correspondence.

Step 3: Summary resolution (DISP 1.5)

DISP 1.5 provides a lighter-touch resolution path for straightforward complaints. If the firm can resolve the complaint to the complainant's satisfaction by the close of the third business day after the day of receipt, the firm may send a summary resolution communication instead of a full final response. This path is designed for low-complexity cases where the fix is obvious and the customer agrees the matter is closed.

The summary resolution communication must explain that the firm considers the complaint resolved and inform the complainant that if they are dissatisfied with the resolution, they may refer the complaint to the Financial Ombudsman Service. It must include the FOS contact details and the website address. Critically, the communication must also tell the complainant that the FOS may not consider the complaint if they refer it more than six months after the date of the summary resolution communication.

Summary resolution is not a way to close complaints quietly. The customer must genuinely regard the matter as settled. If the customer has not explicitly accepted the outcome, the firm cannot treat the case as summary-resolved and must move it into the full eight-week complaint-handling track under DISP 1.6.

• The three-business-day window starts the day after receipt, not the day of receipt.
• The customer must be satisfied with the resolution before the firm can use this path.
• The summary resolution communication must include FOS referral rights and the six-month deadline.
• Log the summary resolution communication with the date sent and the customer's confirmation.
• If the customer does not respond or disputes the outcome, escalate to the full DISP 1.6 process immediately.

Step 4: Investigation and the 8-week final response (DISP 1.6)

For complaints that are not resolved under summary resolution, DISP 1.6 sets the core deadline: the firm must send a final response within eight weeks of the date it received the complaint. This is the single most important operational deadline in UK complaint handling. Missing it does not merely create a process failure; it gives the complainant an automatic right to refer the matter to the Financial Ombudsman Service, even if the firm is close to completing its investigation.

During the investigation period, the firm should keep the complainant informed of progress. If it becomes clear that the eight-week deadline cannot be met, the firm must send a holding response before the deadline expires. The holding response must explain why the firm is not yet in a position to provide a final answer and must inform the complainant of their right to refer the complaint to the FOS immediately.

Operationally, the eight-week clock should be treated as a hard control, not a target. Complaint management systems should trigger escalation alerts at week four and week six to give handlers enough time to either close the investigation or prepare a compliant holding response. Firms that treat the deadline as aspirational will find that a significant proportion of cases breach it, resulting in FOS referrals on procedural grounds alone.

• Calculate the eight-week deadline from the date of receipt, not the date of acknowledgement.
• Set internal escalation triggers at week four and week six.
• If the deadline will be missed, send a holding response before week eight expires.
• The holding response must include FOS referral rights and contact details.
• Never send a holding response as a substitute for completing the investigation; it buys time, not indefinite delay.

Step 5: Final response content requirements

The final response is the firm's definitive answer to the complaint. DISP sets out specific content requirements that go beyond simply stating whether the complaint is upheld or rejected. A final response that omits any of these elements is non-compliant and may be challenged at the ombudsman stage.

The response must be written in plain, clear language. It should read as the output of a genuine investigation, not as a compliance-drafted form letter. The complainant should be able to understand what happened, what the firm found, what the firm is doing about it, and what the complainant can do next if they disagree.

Firms should implement quality assurance checks on final response letters before they are sent. The most common ombudsman criticism is that firms bury the FOS referral rights in small print, attach them as a separate leaflet, or use language that discourages escalation. The referral rights should be prominent, clear, and presented as a genuine option rather than a legal footnote.

The final response must contain the following elements:

• A clear summary of the complaint as the firm understands it.
• An account of the investigation steps taken and the evidence reviewed.
• The firm's decision: whether the complaint is upheld, partly upheld, or rejected.
• The rationale for the decision, tied to specific findings rather than generic policy language.
• Details of any redress offered, including the amount, calculation basis, and payment timeline.
• A statement that the complainant has the right to refer the complaint to the Financial Ombudsman Service if dissatisfied.
• The six-month deadline for FOS referral, the FOS contact details, and the FOS website address.

Step 6: Ombudsman referral rights and the FOS handoff

The complainant's right to refer to the Financial Ombudsman Service is a central feature of the DISP framework. It exists as a safeguard, not as a failure state. Firms that treat FOS referrals as adversarial events rather than a normal part of the dispute resolution system tend to produce defensive final responses that increase rather than decrease the likelihood of an ombudsman investigation.

Once a final response is sent, the complainant has six months to refer the complaint to the FOS. If the firm sends a holding response because it could not meet the eight-week deadline, the complainant can refer to the FOS immediately and does not need to wait for the final response. This is an important distinction that holding-response letters must make clear.

The FOS will generally not consider a complaint if it is referred more than six months after the final response, unless the firm consented to the FOS considering it, or the FOS considers that the failure to comply with the time limit was as a result of exceptional circumstances. Firms should not rely on the time limit as a defence; the FOS applies the exceptional circumstances test broadly.

Operationally, the handoff to the FOS should be treated as a structured process. When a complainant notifies the firm that they intend to refer, the firm should prepare its case file, ensure all evidence is accessible, and designate a point of contact for FOS correspondence.

• Include the six-month FOS referral deadline in every final response and every holding response.
• Do not use language that discourages or obstructs FOS referral.
• Prepare the case file for FOS review as soon as a referral is notified.
• Designate a single point of contact within the firm for all FOS correspondence on the case.

Step 7: Record keeping (DISP 1.9)

DISP 1.9 requires firms to keep a record of each complaint received and the measures taken for its resolution. The rule is not limited to the final response letter. It covers the entire complaint lifecycle: intake, acknowledgement, investigation, customer communications, internal notes, evidence, redress calculations, and the final or holding response.

Records must be kept for a minimum of three years from the date the complaint was received. For firms subject to other regulatory retention requirements, the three-year minimum may be superseded by longer periods, but three years is the DISP floor. The records must be sufficient in detail and quality to enable the FCA to carry out its supervisory functions, which means a bare complaint register with dates and outcomes is not enough.

Strong DISP 1.9 compliance means building record keeping into the complaint workflow rather than treating it as an after-the-fact archive task. Every communication, every status change, every piece of evidence reviewed, and every internal decision should be captured at the point it occurs. Retrospective file-building before an FCA visit or an FOS referral is a sign that the underlying process is broken.

• Retain all complaint records for a minimum of three years from the date of receipt.
• Capture intake details, investigation notes, customer communications, and outcome records in a single complaint file.
• Ensure records are detailed enough to allow the FCA to reconstruct the complaint-handling process.
• Implement access controls so that complaint records are secure but available for compliance review and FOS case preparation.

Step 8: Complaints reporting (DISP 1.10)

DISP 1.10 requires firms to submit complaints data to the FCA through regular returns. The returns cover complaint volumes, product categories, the causes of complaints, the outcomes reached, and the total redress paid. The FCA uses this data for supervisory purposes, including identifying firms with unusual complaint patterns and tracking sector-wide trends.

The reporting frequency depends on the firm's size and regulatory permissions. Most firms submit returns twice per year, covering six-month reporting periods. Larger firms or those with significant complaint volumes may be required to report more frequently. The FCA specifies the reporting format and submission deadlines, and late or inaccurate returns can result in supervisory action.

The data quality of DISP 1.10 returns depends entirely on the quality of the underlying complaint records. If the firm's complaint register is incomplete, inconsistent, or poorly categorised, the returns will be unreliable. This creates a direct link between DISP 1.9 record keeping and DISP 1.10 reporting: firms that get record keeping right will find reporting straightforward, and those that do not will struggle with every return cycle.

• Submit complaints data returns to the FCA in accordance with the prescribed frequency and format.
• Categorise complaints accurately by product, cause, and outcome at the point of resolution, not retrospectively.
• Reconcile return data against the complaint register before submission to catch gaps and inconsistencies.
• Treat late or inaccurate returns as a compliance incident and investigate the root cause.

Step 9: Complaint handling as management information

DISP is not only a complaint-handling rulebook; it is also a source of management information that firms should use to improve their products, processes, and customer outcomes. The FCA expects firms to analyse complaint data for root causes and to act on the patterns that emerge. A firm that resolves every individual complaint competently but never addresses the systemic issues driving those complaints is not meeting the spirit of the rules.

Root-cause analysis should happen at a regular cadence, not only when complaint volumes spike or the FCA asks questions. Complaint themes such as recurring product failures, unclear terms and conditions, poor customer communication, and processing errors should be reported to senior management with recommendations for remediation. The complaints function should have a direct reporting line into governance structures that can authorise changes.

Vulnerable customer patterns deserve specific attention. If complaint data shows that a disproportionate number of complaints come from customers in financial difficulty, with accessibility needs, or in other vulnerable circumstances, the firm should investigate whether its products or processes are causing or contributing to harm for those groups.

• Conduct root-cause analysis of complaint data on a monthly or quarterly basis.
• Report complaint themes, trends, and systemic issues to senior management and relevant governance committees.
• Track whether remediation actions actually reduce complaint volumes in subsequent periods.
• Monitor complaint data for patterns affecting vulnerable customers and escalate findings to product and conduct risk teams.

Common operational failures

Most DISP breaches are operational rather than conceptual. Firms understand the rules in principle but fail to execute them consistently under the pressure of daily complaint volumes. The following failures appear repeatedly in FOS decisions and FCA supervisory findings.

• No clear complaint owner assigned at intake, leading to cases that drift without progress until the eight-week deadline is imminent.
• Weak complaint identification at the front line, causing complaints to be logged as general queries and handled outside the DISP process.
• Acknowledgement letters sent days or weeks after receipt, undermining the "prompt" requirement and creating a poor first impression.
• Investigation notes that exist internally but never appear in the final response, leaving the customer unable to understand how the firm reached its decision.
• Final response letters that use generic boilerplate language rather than addressing the specific complaint and evidence.
• FOS referral rights buried in attachments, footnotes, or small print instead of being stated clearly in the body of the final response.
• Complaint records that are incomplete, scattered across multiple systems, or impossible to reconstruct when the FOS or FCA requests the file.

Checklist: DISP compliance at a glance

Use this table as a quick reference for the core DISP steps, the applicable rule, and the key requirement at each stage.