In accident management, the first notification of loss triggers a chain of parallel actions — credit hire deployment, repair booking, and personal injury referral assessment. Getting FNOL right determines whether your client is mobile within hours or stranded for days.
Accident management companies operate under fundamentally different pressures to traditional insurers at the FNOL stage. When a non-fault driver calls in, the AMC must simultaneously assess fault liability, evaluate injury potential, determine vehicle drivability, and deploy a credit hire vehicle — often within the same phone call. Missing any of these triggers delays the entire claim lifecycle and erodes the margins that make the case commercially viable.
Many AMCs still operate FNOL through disconnected systems: a call handler captures details on a generic form, then emails the credit hire desk, separately notifies the repair team, and flags potential PI referrals manually. Each handoff introduces delay and data loss. A missed injury disclosure at intake means a PI referral opportunity lost. An inaccurate vehicle description means the wrong hire vehicle is deployed, generating complaints and additional cost.
The regulatory environment compounds these pressures. The FCA's CMC authorisation requirements (in force since 1 April 2019) mean AMCs that refer personal injury claims must demonstrate robust intake processes. The Consumer Duty (introduced July 2023) requires firms to evidence that customers receive good outcomes from first contact. Pre-Action Protocol compliance demands that key details are captured accurately at the outset to support any subsequent litigation.
An effective AMC FNOL workflow captures the incident details once and immediately fans out into parallel workstreams: credit hire deployment, repair booking, recovery and storage arrangements, and PI referral assessment. Rather than treating these as sequential handoffs, the system should trigger each workstream simultaneously based on the data captured during the initial call.
The intake form itself must be purpose-built for accident management. Generic claims forms miss AMC-critical fields like fault admission indicators, third-party insurer details, vehicle drivability status, and injury disclosure questions. A structured AMC FNOL form guides the call handler through the right questions in the right order, ensuring nothing is missed even under call-volume pressure.
Crucially, the triage logic must assess commercial viability alongside operational routing. Not every non-fault claim justifies credit hire deployment — the vehicle may be drivable, the claimant may have alternative transport, or liability may be disputed. The workflow should score each case and route it to the appropriate service pathway.
Follow these steps to design an FNOL process that captures the right data for accident management operations and triggers parallel workstreams without manual intervention.
Build an intake form that captures the fields essential to accident management — not just generic claims data. This includes: incident date, time and location; fault admission indicators (did the third party admit liability, were police called, is there dashcam footage); vehicle details for both parties including registration, make, model, and colour; drivability status; injury disclosure for all vehicle occupants; third-party insurer and policy details if known; and whether the claimant has existing alternative transport.
Create a scoring model that assesses likely fault status based on the incident description, any admissions, and the accident circumstances. Common scenarios (rear-end shunts, roundabout collisions, car park incidents) have well-established liability patterns. The triage score should categorise cases as clear liability, disputed liability, or split liability, and route each category to the appropriate handling pathway.
Configure the workflow so that a completed FNOL automatically triggers the relevant workstreams. For a non-fault, non-drivable vehicle with injuries: simultaneously create a credit hire deployment task, a repair/recovery booking task, a storage arrangement task, and a PI referral assessment task. Each workstream receives the relevant subset of FNOL data without requiring any re-keying.
AMCs authorised as Claims Management Companies must capture explicit consent before referring personal injury claims. The FNOL workflow should include scripted consent language that meets FCA requirements, record the consent with a timestamp, and store it against the case file. Additionally, capture Consumer Duty disclosures about the services being provided, any charges, and the claimant's right to use their own insurer instead.
Once fault liability is assessed and the case is accepted, the workflow should generate and dispatch a notification to the at-fault insurer or their claims handler. This notification should include the incident details, your client's details, and the services being provided (credit hire, repair). Early notification strengthens your recovery position and starts the Pre-Action Protocol clock.
Set measurable SLA timers for each action triggered by the FNOL: credit hire vehicle deployed within 4 hours, recovery arranged within 2 hours for non-drivable vehicles, repair booked within 24 hours, PI referral assessment completed within 48 hours. Each timer should escalate to a team leader if the deadline is at risk.
Track key metrics from the FNOL stage: what percentage of incoming notifications convert to active cases, where in the triage process do cases drop out, and what is the average time from FNOL to credit hire deployment. This data reveals bottlenecks and leakage points that directly affect revenue.
Injury disclosure is time-sensitive in accident management. The FNOL call handler should ask a clear, direct question about injuries to all vehicle occupants within the first few minutes of the call. Soft-tissue injuries often emerge hours after the incident, so the question should cover both current symptoms and developing pain. This protects the claimant and preserves the PI referral opportunity.
Before committing to credit hire deployment, verify the third-party vehicle's insurance status against the Motor Insurance Database. Deploying a hire vehicle against an uninsured driver changes the recovery pathway entirely (MIB rather than direct insurer claim) and affects commercial viability. A 30-second MID check at FNOL prevents costly recovery failures later.
Call recordings are critical evidence in accident management. They capture the claimant's first account of the incident, consent to services, and injury disclosures. Link each recording directly to the case file so that it is accessible to handlers, recoveries teams, and compliance auditors without a separate retrieval process.
The operational response for a drivable vehicle is fundamentally different from a non-drivable one. Drivable vehicles need a repair booking and a like-for-like hire vehicle at a convenient time. Non-drivable vehicles need immediate recovery, storage, and urgent hire deployment. The FNOL triage must distinguish between these pathways clearly to avoid deploying the wrong response.
Fault liability at FNOL is always a preliminary assessment. Document the specific evidence supporting your fault determination (admissions, witness details, police reference numbers, dashcam availability) so that the recoveries team has a solid foundation when pursuing the at-fault insurer. Undocumented fault assumptions create problems months later when the claim reaches litigation.
Incident details, fault admissions, vehicle drivability, injury status, and third-party insurer details are all mandatory.
Consent wording meets FCA CMC authorisation requirements and is stored with the case file.
Credit hire deployment within 4 hours, recovery within 2 hours for non-drivable vehicles.
Identify potential gaps in your accident management processes with our free self-assessment tool. Not a substitute for professional advice.
Try these related tools — no sign-up required.
Credit hire is the commercial engine of most accident management companies. Managing it well means deploying the right vehicle quickly, tracking hire duration rigorously, billing at GTA-compliant rates, and defending every hire day against insurer challenges.
accident managementThe repair stage is where the claimant's experience is made or broken. Managing a network of bodyshops requires rigorous SLA tracking, quality oversight, and clear communication so that vehicles are repaired correctly, on time, and to a standard that satisfies both the customer and the insurer.
accident managementThe LASPO 2012 referral fee ban fundamentally changed how accident management companies can work with personal injury solicitors. This guide explains the legal boundaries, compliant referral models, FCA requirements, and data protection obligations for PI referrals.
See how SwiftCase helps accident management companies capture FNOL data once and trigger credit hire, repair, and PI referral workstreams automatically.
