What Is FNOL? First Notice of Loss Explained for Collision Shops

FNOL stands for First Notice of Loss. It is the first formal notification an insurance company receives from its policyholder (or another party) that an incident has occurred that may result in a claim. The FNOL captures the date, time, and location of the loss, the parties and vehicles involved, a description of the damage, the policyholder's contact information, and any preliminary documentation such as photos or a police report number. The carrier converts the FNOL into a claim, assigns a claim number, routes it to an adjuster, and triggers the claim handling timeline. Every collision repair claim begins with an FNOL whether the shop sees it directly or not, and the quality of the FNOL data shapes how quickly the rest of the claim moves. Most disputes that surface weeks into a repair trace back to gaps in the original FNOL.

A complete FNOL contains:

• Date and time of loss
• Location of loss (street, city, state)
• Policyholder name and policy number
• Driver name (if different from policyholder)
• Vehicle details (year, make, model, VIN, license plate)
• Description of the loss
• Other parties involved (name, vehicle, contact, insurance)
• Police report number (if applicable)
• Initial photos of damage
• Driveable / non-driveable status
• Tow company and storage location (if towed)

When a customer arrives at the shop without yet having reported the loss, the shop often gathers all of this information first and walks the customer through reporting it.

Three numbers travel with every claim. They are not the same thing.

• Policy number: the customer's insurance contract identifier. Stays the same for the life of the policy.
• FNOL reference number: a transient identifier assigned when the loss is reported. Some carriers convert it directly to the claim number.
• Claim number: the durable identifier the carrier uses to track this specific loss event. This is the number every supplement, payment, and communication references.

When the shop talks to the carrier, the claim number is the number that matters. The policy number confirms coverage but does not move the file forward.

Most policies require the policyholder to report a loss as soon as reasonably possible. Carriers sometimes deny claims when reporting is delayed without explanation, when the damage description in the FNOL does not match the damage at inspection, when the location, time, or circumstances reported in the FNOL contradict police report data, or when photos provided at FNOL show damage that the carrier later argues is unrelated. The FNOL is the carrier's first impression of the loss. A clean FNOL leads to a clean claim. A messy FNOL invites scrutiny across the entire repair.

When the customer arrives, ask:

1. Have you reported this loss to your insurance company yet?
2. If yes, do you have a claim number?
3. If no, would you like help reporting it now while we have the vehicle in front of us?

If the customer has not reported, the shop can help by taking complete pre-repair photos, recording the customer's description while it is fresh, helping the customer call the carrier from the shop, and capturing the FNOL reference number as it is generated. Shops that do this routinely see fewer 'the customer reported it differently than the damage looks' disputes weeks later.

The FNOL captures whether the vehicle is driveable. This single data point shapes a lot of downstream decisions: tow assignment and storage charges, rental authorization start date, adjuster scheduling priority, customer urgency level. Driveable claims often get put behind non-driveable claims in the adjuster's queue. Shops should make sure the driveable status in the FNOL matches the actual condition of the vehicle.

Capturing FNOL data on paper or in a spreadsheet at intake means the data has to be re-keyed into the carrier's system, the shop's system, and any DRP-specific portal. Each re-key creates an opportunity for a typo that derails the claim. Shops that scan the VIN at intake and capture FNOL fields once into a structured workflow are set up to catch intake errors that paper or spreadsheet intake lets through. Inside Claimory, an FNOL intake takes 30 seconds. The VIN scan decodes the vehicle, the FNOL fields capture the loss data, and the claim number is recorded once and travels with the file through every supplement, photo, payment, and communication.

Use this at every intake:

1. Confirm whether the loss has been reported to the carrier
2. Capture or verify the claim number
3. Record the FNOL date and the loss date (often different)
4. Take a complete pre-repair photo set before any work
5. Note driveable / non-driveable status and storage location
6. Document any discrepancies between FNOL data and observed conditions
7. Give the customer the claim number and your shop contact in writing

The FNOL is the foundation of the claim. A solid foundation makes everything that follows simpler.