Category: Claims fundamentals · Reviewed by Tim Roche, Director · PI & Commercial · Last reviewed 2026-06-11
A claim file is the complete record of an insurance claim — comprising all documents, communications, decisions, expert reports, reserves and payments relating to the claim — maintained by the insurer (or its delegated administrator) as the authoritative repository for regulatory, evidential and operational purposes.
Category: Claims fundamentals Also known as: Claims file, claim record, case file Related concepts: Claims handling, Claim form, FNOL, Loss reserve
The claim file is the canonical record of everything that happens on a claim from notification to closure. It is the documentary backbone of claims handling: every action taken, every decision made, every communication sent or received, every expert report instructed, every reserve set or moved, and every payment made is captured in the file.
In contemporary practice, the claim file is almost universally electronic. Insurers operate claims management systems (CMS) that combine structured data fields (parties, dates, amounts, status), document repositories (PDFs, photos, video, correspondence), workflow (tasks, diary dates, approval queues) and management information. Specialist platforms such as Guidewire ClaimCenter, Sapiens, Insurity, and EIS Group dominate the enterprise market, with bespoke and SaaS platforms used by smaller insurers and MGAs.
The claim file has several distinct audiences. The claim handler uses it operationally. The handler’s manager uses it for supervision and quality assurance. The actuarial team uses it for reserving and rate-setting. The internal auditor uses it for compliance review. External auditors and the FCA may inspect it. In litigation, the file may be disclosed to the claimant or to coverage counsel. After settlement, it may be relevant in subrogation, contribution or reinsurance recovery.
Because of these multiple audiences, the standard for claim-file maintenance is high. Files must be contemporaneous, complete, accurate and defensible. Notes must reflect actual reasoning, not retrospectively constructed narratives. Decisions must be supported by evidence. Privileged communications must be properly marked. Personal data must be handled lawfully.
The legal duty to maintain a claim file derives from several sources. The FCA’s Senior Management Arrangements, Systems and Controls Sourcebook (SYSC 9) requires firms to keep orderly records of their business sufficient to enable the FCA to monitor compliance. Records relating to insurance claims must be kept for at least three years (and longer in some classes); long-tail personal-injury claims may require retention indefinitely in practice because of disease latency.
ICOBS 8.1.1R requires insurers to handle claims promptly and fairly, which in practice means maintaining sufficient records to demonstrate compliance. ICOBS 8.5 contains specific record-keeping requirements for binding authorities and delegated claims.
The Civil Procedure Rules require parties to litigation to disclose documents relevant to the issues in dispute. CPR Part 31 imposes standard disclosure obligations, and the claim file is frequently subject to disclosure orders in coverage disputes and in subrogated actions. Communications subject to legal professional privilege (legal advice privilege and litigation privilege) may be withheld; the file must clearly distinguish privileged from non-privileged material.
The UK GDPR and Data Protection Act 2018 impose obligations on the processing of personal data in the file. Data subjects have rights of access under Article 15 UK GDPR, which can require the insurer to disclose the file (subject to exemptions, including the exemption for legal proceedings in Schedule 2 of the Data Protection Act 2018).
In subrogated recovery actions, the claim file is the principal source of evidence on causation, quantum and prior contributory factors. In Vincent v Northwood [2020] EWHC 3645 (Comm) and similar cases, courts have considered the proper handling of claim-file evidence in insurance disputes.
For Solvency II reporting, the claim file underpins the calculation of technical provisions and is subject to actuarial sign-off and external audit.
A typical claim file is opened at FNOL when the insurer’s claims management system creates a record keyed to the policy and assigns a unique claim reference. The opening data — date, parties, cause, estimated quantum, initial reserve, status — is captured in structured fields.
From this point, every interaction is recorded. Inbound correspondence (emails, letters, third-party communications) is uploaded as PDF or other document format and tagged. Outbound correspondence is generated through the system, copied to the file, and date-stamped. Telephone calls are logged with a brief note, and increasingly are recorded in full and indexed against the file. Internal notes capture the handler’s reasoning at each decision point.
Expert reports — loss adjuster reports, surveyor reports, accountant reports, counsel’s opinions, medical reports — are added to the file as they are received. Each is indexed and any actions required are diarised in the workflow.
The file maintains a running reserve history: each reserve change is captured with the date, the reason for the change, and the prior and new amounts. This permits later analysis of reserving accuracy and provides an audit trail.
Payments are recorded against the file with date, amount, payee, payment method, currency and supporting documentation. For partial settlements, the file shows running totals against the agreed quantum.
The file is also used for management reporting. Aggregated across many files, the data feeds KPIs (claim frequency, average severity, indemnity-versus-expense ratios, settlement timescales, customer satisfaction), regulatory returns (PRA Solvency II quantitative reporting templates, FCA conduct returns), and actuarial reserving exercises.
On closure, the file is archived but remains accessible for the regulatory retention period. Records of personal injury claims under the Limitation Act 1980 may need to be retained for many years owing to the long-stop limitation periods.
Claim files come in several variants. Master files consolidate all aspects of a single claim. Sub-files are used where a single loss event gives rise to multiple individual claims (for example, a major fire with separate property and business-interruption sub-files). Cumulative files are used for catastrophe events, where many policyholder claims arise from a single insured peril.
Coverholder files are held by managing general agents under delegated authority, with periodic data feeds to the insurer’s central system. TPA files are held by third-party administrators handling claims under delegated authority. Reinsurance files mirror the direct claim file but record reinsurance recoveries, with separate reserves and payment streams.
Legal files are typically maintained by panel solicitors handling defence and indemnity matters and are linked to (but distinct from) the insurer’s claim file. Privileged communications are usually held in the legal file rather than the main claim file to preserve privilege.
Catastrophe response files are used for major loss events with hundreds or thousands of individual claims, with workflow and reporting tuned to high volumes.
In Lloyd’s, the Electronic Claims File is the market-standard digital file shared between syndicates, brokers and TPAs.
A retail chain, NorthHigh Ltd, suffers an arson attack on its central distribution warehouse on 17 March 2026. The fire destroys stock worth approximately £2.4 million and damages the building. The company holds property, business interruption and stock policies with a panel of three insurers led by Insurer A on 50 percent line, with Insurers B and C each on 25 percent.
The broker submits FNOL on 18 March. Insurer A opens a claim file (CL-2026-04417) and instructs a chartered loss adjuster. Over the next nine months, the file accumulates: the FNOL notification; the broker’s loss narrative; eight progress reports from the loss adjuster; reports from the insured’s accountants on business-interruption quantum; a fire investigator’s report; the local fire and rescue service incident report; correspondence with the Crown Prosecution Service in respect of the arson investigation; coverage opinions from panel counsel; an expert report on the warehouse construction; weekly handler diary notes; reserve movements (initial £1.8m, increased to £2.6m, then £3.0m, finally settled at £2.85m); interim payments of £400,000, £600,000 and £800,000; the final settlement memorandum; and the reinsurance recovery file in respect of the company’s catastrophe excess-of-loss treaty.
When proceedings are issued against the arsonist’s employer (alleged failure of security) in 2027, the claim file is disclosed under CPR Part 31. The handler is called as a witness. The file’s contemporaneous notes — captured carefully throughout the claim — support the insurer’s case on causation and quantum. Subrogated recovery of £1.1 million is achieved by mid-2028, reducing the net claim cost.
This entry is part of the Apex Insurance Wiki. Last reviewed by Matt Bartlett on 2026-06-11. Next review: 2026-12-11.
Apex Insurance Brokers Limited. Authorised and regulated by the Financial Conduct Authority, FRN 724952. Registered in England and Wales, Companies House 07014570. This entry provides general information about UK insurance concepts and is not regulated advice. Consult your insurance broker on your specific position.
Apex Insurance Brokers serves UK professional services firms and commercial businesses. Call 0117 325 0027, email info@apexinsurancebrokers.co.uk, or request a quotation.
Get a quote