FNOL stands for First Notice of Loss: the moment the insurer becomes aware that an accident covered by a policy has occurred. In motor insurance, the FNOL is almost always the accident statement, or the policyholder's call describing what happened.
It is an insurance industry concept, but it affects everyone involved in the claim. For a fleet, the FNOL is the moment the company learns it has a damaged vehicle. For a broker, it is the moment the claim file they will have to manage begins. For the workshop, it is the notice that a car may be coming in.
Why the FNOL decides the cost
Because everything that follows is sized around it. A complete FNOL, with both versions, photographs and the correct number plate, allows the claim file to be opened, a loss adjuster assigned, a workshop authorised, and, in minor claims, resolved with no further exchange. An incomplete FNOL generates a request for information, a phone call, a wait and, often, a second version of events that no longer matches the first.
The cost is not in the notification itself, but in every extra interaction an incomplete notification forces. And the time is not in the repair, but in the days that pass until someone has enough information to decide.
The three dimensions of a good FNOL
Time. How long passes between the accident and the notification. Hours, in the best case; days, typically. Every day without notification is another day with the vehicle off the road and nobody having decided anything about it.
Completeness. Whether the notification brings what is needed to act: data on both vehicles, circumstances, sketch, photographs of the damage and the scene, both parties' signatures.
Structure. Whether the notification arrives as data that can be loaded into a system, or as a document someone has to read and transcribe. A scanned PDF of a handwritten report is an FNOL; a claim file with fields by segment is too. The cost of handling them is not the same.
The FNOL as a neutral layer
There is an idea that clarifies the problem a great deal: the FNOL does not belong to the insurer. It belongs to the claim. The fleet needs it to manage the vehicle, the broker to manage the claim file, the insurer to process it, the workshop to repair it, and the loss adjuster to value it. Each one needs a different part of the same information.
That is why it makes sense for FNOL capture to be a neutral layer, sitting before processing and separate from it: a system that captures the data once, at the source, and delivers it to each party according to what concerns them, with no one having to resend, transcribe or ask. Acciparte is built on that idea: the claim file as the unit, the segment as the boundary, and permission as the rule.
What changes when the FNOL is born structured
- The insurer receives the official report and, if it integrates it, the data by segment. Fewer requests for information and fewer contradictions.
- The broker receives the complete claim file from day one and stops having to rebuild it with the policyholder.
- The fleet knows within minutes what happened, with photographs, and decides on the vehicle the same day.
- The workshop and the loss adjuster work against a single reference and contribute their documentation to the same claim file.
- Everyone knows how much time passed between the accident and the notification, because it is recorded.
The FNOL is not an administrative formality. It is the design decision that most determines what a claim costs. You can see how Acciparte delivers it to each party on the insurers page, and the detail of the claim file model in how it works.