Structured case file assembly ensures your firm presents the strongest possible position when complaints are referred to the Financial Ombudsman Service.
When a complaint is referred to the Financial Ombudsman Service, the quality of your case file often determines the outcome. Adjudicators and ombudsmen rely heavily on the documentary evidence provided by both parties. Firms that submit disorganised, incomplete, or poorly structured case files put themselves at a significant disadvantage, even when their original decision was reasonable and well-founded.
Common failings include missing call recordings, incomplete complaint chronologies, unsigned documents, and a lack of clear rationale linking the evidence to the decision. These gaps do not just weaken your position on the specific case; they signal to the FOS that your complaints handling governance may be inadequate, potentially inviting closer scrutiny of your broader practices.
The financial stakes are substantial. The FOS case fee alone is several hundred pounds per referral, and upheld complaints result in redress awards that can significantly exceed the original claim value. Firms that consistently lose at the FOS also face reputational damage and increased regulatory attention.
Effective FOS preparation does not start when the referral arrives. It starts at the point of complaint receipt, with systematic evidence gathering and documentation built into every stage of the complaints handling workflow. When a complaint is eventually referred, the case file should already be substantially complete.
A workflow-driven approach ensures that every complaint automatically accumulates the evidence needed for a robust FOS file: timestamped communications, call recordings linked to the case record, policy documents, investigation notes, decision rationale, and the final response letter. When referral occurs, the handler simply reviews and organises material that already exists.
Standardised file assembly templates and checklists ensure consistency across handlers and teams, reducing the risk that critical evidence is overlooked. Pre-referral quality reviews catch gaps before the file is submitted, giving your firm the best possible chance of a favourable outcome.
Follow these steps to build a case file preparation process that gives your firm the strongest possible position when complaints reach the Financial Ombudsman.
Configure your complaints workflow to automatically capture and link all relevant evidence as the complaint progresses. This includes inbound and outbound correspondence, call recordings with timestamps, policy documents, claims files, system screenshots, and internal investigation notes. Every piece of evidence should be date-stamped and linked to the complaint record.
Create a standardised chronology template that captures every significant event in the complaint journey: date of incident, date complaint received, acknowledgement sent, investigation steps taken, information requested, responses received, decision made, and final response issued. This chronology should be auto-populated from workflow events and supplemented by the handler.
Require handlers to record a clear, structured rationale for their complaint decision at the point of final response. This should reference the specific policy terms, regulatory requirements, or factual findings that support the decision. The rationale should be written as if it will be read by an FOS adjudicator, because it may well be.
Develop a comprehensive checklist of documents and evidence required for FOS submission. This should include: the original complaint, acknowledgement letter, all correspondence, call recordings with transcripts, policy schedule and wording, claims file extracts, investigation notes, decision rationale, final response letter, and any redress calculations.
When a FOS referral notification is received, route the case through a quality review before the file is submitted. A senior handler or complaints quality team member should review the file against the assembly checklist, verify the decision rationale is sound, and identify any gaps that need to be addressed before submission.
Write a clear, factual summary (no more than two pages) that sets out your firm's position. This summary should guide the adjudicator through the key facts, your decision rationale, and why you believe your handling was fair and reasonable. Structure it logically and avoid defensive or adversarial language.
The FOS typically requests the business file within a specified timeframe. Late submissions delay the case and can create a negative impression. Set up automated reminders for the submission deadline and ensure the file is submitted promptly, ideally within a few days of the request.
Record the outcome of every FOS referral and analyse patterns in upheld decisions. Identify whether certain complaint types, products, or decision approaches are consistently overturned. Feed these insights back into handler training and decision-making guidance to improve future outcomes.
Your final response letter is often the single most important document in a FOS case file. Write it as if an adjudicator will read it: be clear, factual, empathetic, and thorough. Explain your reasoning, reference the evidence, and set out the complainant's FOS referral rights clearly.
Complainants have six months from the date of the final response to refer to the FOS (or six years from the event in some circumstances). Ensure your retention policies preserve all complaint-related evidence for at least six years, regardless of when the complaint was closed.
FOS adjudicators are not advocates for either party. Present your case file objectively, acknowledge where things went wrong if applicable, and focus on demonstrating that your overall decision was fair and reasonable. Attempting to minimise genuine failings undermines your credibility.
If the complainant was unresponsive during your investigation, document every attempt to make contact. Unanswered calls, unreturned letters, and missed appointments should all be evidenced in the file. This context is valuable if the complaint was delayed due to the customer's non-engagement.
Include transcripts or detailed notes for key calls
Identify potential gaps in your complaints handling processes with our free self-assessment tool. Not a substitute for professional advice.
Try these related tools — no sign-up required.
Automated final response letter generation ensures every complaint closure meets DISP requirements with consistent quality, complete mandatory content, and clear FOS referral rights notification.
fca complianceA step-by-step guide to building a DISP-compliant complaints process that meets FCA timelines, captures root cause data, and reduces Financial Ombudsman referrals.
complaints handlingAutomated deadline monitoring ensures every complaint receives a final response within the FCA's mandatory 8-week timeframe, reducing FOS referral risk and regulatory exposure.
See how SwiftCase automates evidence gathering and case file assembly so your firm is always prepared when complaints reach the Financial Ombudsman.
