Blog
/
Workflow automation

First notice of loss (FNOL) workflow: Intake to efficient triage

Table of Contents
In this article

Most claim problems start long before settlement. They start at first notice, when details arrive by phone, text, and email in different shapes, and nobody owns the file yet. Re-keyed data, unchecked coverage, and a general queue turn a stressful day for the policyholder into a week of silence. By the time an adjuster opens the case, the evidence is scattered and the customer has called twice.

That first step is the first notice of loss (FNOL) workflow, and it shapes every step after it. This guide defines FNOL, lists what a report should include, and lays out the FNOL process flow step by step. It then covers intake channels, evidence, coverage checks, severity scoring, and status updates. It also shows where AI can help while adjusters keep the decisions.

Key takeaways

  • Definition: FNOL is the first report to an insurer that a loss has happened. It starts the claim and sets its direction.
  • Process flow: Report, capture details and evidence, verify identity and coverage, score severity, assign, acknowledge, then start the investigation.
  • Data quality: A complete, structured report at intake prevents re-keying and wrong assignments later.
  • Triage: Severity scoring sends simple claims down a fast path and complex ones to experienced adjusters early.
  • People decide: Rules and AI agents can draft the routing and chase missing items, while adjusters approve coverage, severity, and assignment.

What is first notice of loss (FNOL)?

First notice of loss (FNOL) is the first report to an insurer that a covered loss may have happened, such as a car accident, a burst pipe, or a workplace injury. It opens the claim, captures the basic facts, and starts the insurer's process. FNOL is the intake step that every later decision depends on.

Who can file: The policyholder, a claimant, a broker or agent, a third-party administrator, or sometimes a repair shop acting for the customer.

When to file: As soon as possible after the loss. Most policies require prompt notice, and the exact deadline depends on the policy and the line of business.

What an FNOL report includes

A good FNOL report captures the facts an adjuster needs to act without calling back.

Policy details: Policy number and the name of the insured.

Loss details: The date, time, and place of the loss, with a short description of what happened.

People involved: Claimants, drivers, witnesses, and any injuries.

Evidence: Photos, video, police or incident reports, and repair estimates where available.

Contact preferences: How and when the policyholder wants updates.

The FNOL process flow, step by step

Most insurers follow the same core FNOL process flow, even when the tools differ. The order matters, because each step depends on the one before.

  1. Report the loss: The policyholder or an agent reports the loss through phone, web, app, text, email, or a connected device.
  2. Capture details and evidence: Intake collects the report fields above, plus photos, statements, and documents.
  3. Verify identity and coverage: The insurer confirms who is reporting, that the policy was active, and what it covers.
  4. Check for duplicates and flags: The system looks for an existing claim on the same loss and for early fraud signals.
  5. Score severity: Rules and models rate the claim by loss type, injuries, coverage, and amount.
  6. Assign the claim: The claim goes to the right adjuster, team, or fast-track path based on severity and line of business.
  7. Acknowledge and set expectations: The policyholder gets a claim number, the next steps, and a time frame.
  8. Start the investigation: The adjuster reviews the file and begins the claim.

The exception path: Some claims leave the standard flow. Coverage may fail, data may be missing, a duplicate may appear, or a catastrophe may cause a surge in volume. Each exception needs a named owner and a deadline, or it sits in a queue. For what happens after triage, see this claims processing guide.

Why the FNOL workflow matters

When a policyholder files a claim, the clock starts. The speed and accuracy of FNOL set the tone for the whole claims journey. Yet many insurers still rely on handwritten call notes, crowded email inboxes, and legacy systems that do not share data.

Volume is steady, and capacity is tight. In 2023, "5.3 percent of insured homes had a claim," according to ISO data published by the Insurance Information Institute. Meanwhile, the US Bureau of Labor Statistics projects employment of claims adjusters, appraisers, examiners, and investigators "to decline 6 percent from 2025 to 2035." Fewer people will handle the same flow of claims, so triage has to route well the first time.

That gap creates a chain of problems:

Unnecessary delays: Manual data entry, re-keying, and searching across sources slow every claim.

Claims leakage: Incomplete or inaccurate details at FNOL lead to poor decisions later, such as overpayments or missed recovery from third parties.

Frustrated customers: Policyholders are often in a stressful moment when they file. A slow or confusing FNOL process adds to that stress and hurts loyalty.

Compliance risk: Inconsistent data capture and missing audit trails make it hard to show how each claim was handled. Role-based access and strong security controls matter as much as speed.

A structured FNOL workflow removes these pain points. Standard intake lets insurers verify identity and policy details, capture evidence, and triage cases to the right adjusters or specialist teams. It does that while keeping a clear record for the insurer and the policyholder.

Intake channels and verification: the gateway to an efficient FNOL workflow

A modern FNOL workflow starts with intake channels that fit how policyholders want to report a loss. Several entry points improve the customer experience and set up clean data for triage.

Phone or call centers: Still a primary channel, especially for complex claims and emergencies. Call notes should flow straight into the claim record.

SMS and messaging apps: Good for quick notice and fast photo or video uploads, which shortens the time to first evidence.

Email: Convenient for detailed accounts. Without a structured workflow, though, email submissions need manual data extraction.

Web and mobile forms: Guided forms capture complete, structured data from the start, which makes digital workflow automation and triage faster.

Connected devices and APIs: Telematics and smart home sensors can detect and report some incidents on their own, such as a collision or a water leak.

Once intake happens, identity verification comes next. It can be a simple policy lookup or a digital ID check. Good verification lowers fraud risk, avoids repeat questions, and speeds the claim.

Evidence capture: photos, statements, and beyond

Capturing complete, accurate evidence at the start is one of the most important parts of an FNOL workflow. Early evidence prevents disputes, cuts back-and-forth, and speeds the claim.

Consider hail damage to a car. The policyholder can upload photos from a phone and record a short statement, with no wait for an assessor. That evidence reaches the adjuster the same day.

Geo-tagged photos and videos: Visual proof with timestamps and locations, which adds context and authenticity.

Voice or text statements: The claimant's account of events, captured while it is fresh.

Third-party documents: Police reports, contractor estimates, or medical records, added straight to the claim file.

Software can now help with the first read of that evidence. The BLS notes that "computer software can evaluate photographs of damaged property and calculate an estimated claim amount." An estimate like that is a starting point. The adjuster still decides what the claim is worth. Keeping the evidence in one role-based record, with a full audit trail, lets adjusters decide faster.

Policy and coverage checks: the foundation for swift triage

After evidence capture, the next step in the FNOL workflow is to confirm policy eligibility and coverage. This used to mean manual lookups across several systems, which caused delays and errors. Today, integrations with the policy system can return the main details in real time.

Active coverage dates: Confirms the loss happened within the policy period.

Deductibles: Shows the policyholder's share of the loss.

Exclusions: Flags events or damage the policy does not cover.

Policy limits: Shows the maximum the policy can pay.

Previous claims history: Gives context for fraud checks and repeat losses.

Why these checks matter for efficient FNOL

Automated checks lighten the adjuster's workload, so adjusters can focus on judgment. Claims with confirmed coverage can move straight to severity scoring. Real-time data cuts errors, gives policyholders faster confirmation, and flags suspicious patterns early.

For example, a property claim with confirmed active coverage and no relevant exclusions can skip a manual review queue and go straight to severity assessment. A claim where coverage fails goes straight to a named person.

Severity scoring and assignment: automating triage at FNOL

After FNOL, the next step is triage. Not all claims are equal. Some can be settled quickly, while others need a deep investigation. Severity scoring and assignment send each case to the right resources from the start.

FNOL systems use rules and AI models to read the incoming data, such as loss type, injuries, policy details, and claim history. They then suggest a severity score, so claims go to the right place without delay.

Low-severity claims: A cracked windshield or minor property damage can often go down a fast-track path, with a light review.

Moderate-severity claims: These need an adjuster's review but can still move quickly, with automated first contact.

High-severity claims: Cases with serious injury, major property damage, or possible fraud go straight to specialist teams or senior adjusters.

The score is a recommendation. A claims lead or adjuster should confirm it, especially near a threshold. This is the human-in-the-loop pattern: the system drafts the routing, and a person approves it. For more on that model, see human-in-the-loop automation.

Status communication and SLAs: building trust from the first interaction

The FNOL stage is also the first chance to set clear expectations with a policyholder in a stressful moment. Their first questions are usually "Did you get my claim?" and "What happens next?"

Real-time status updates: A mobile-friendly portal lets policyholders check claim status at any time, which cuts inbound calls.

Automated reminders: Reminders for missing documents or deadlines keep the claim moving toward triage.

Service-level agreements: Clear SLAs tell policyholders when they will hear back and what comes next. Internally, an SLA timer can escalate a claim before it goes late.

Preferred channels: Updates by SMS, email, or in-app notification, based on what the policyholder chose.

A well-structured FNOL workflow means no policyholder is left wondering. It also sets up the rest of claims processing on clean, complete data.

Build your FNOL workflow in Moxo

Fast intake and confident triage depend on who carries each step in the first hours after a loss is reported. Moxo orchestrates adjusters, intake staff, and AI agents together, giving claims operations one governed process for that stretch.

Hand Moxo your FNOL SOP, or simply describe the intake, and it builds the flow with forms, file requests, approvals, and e-signatures. Branching rules route each claim by line, severity, and coverage result, with an SLA timer on every step. AI agents prefill the report from submitted evidence, flag gaps, and chase the policyholder or broker until the file is complete. Adjusters approve the severity score, the assignment, and every exception.

Policyholders, brokers, and repair shops respond through a magic link, without registering for an account. Integrations connect policy and claims systems, and every decision lands in a timestamped audit log. Forward-deployed engineers help wire it to your claims stack.

Who it isn't for: carriers that only want a data feed between two systems, where no person ever touches the claim.

See your FNOL intake and triage shared between agents and adjusters. Book a demo

Give every claim the right start

The FNOL stage shapes the whole claims journey. When intake, verification, evidence, coverage checks, severity scoring, and communication run as one structured workflow, claims move faster and policyholders trust the process. The claims that go wrong are usually the ones where nobody owned the next step.

A final thought: map your current FNOL flow and mark every place where a person re-keys data or waits for a reply. Those are your first fixes. Moxo can run that flow with agents on the routine steps and adjusters on the decisions.

Try it on your own FNOL intake. Request free trial

FAQs

What is FNOL in insurance?

FNOL, or first notice of loss, is the first report to an insurer that a loss has happened. It can come from the policyholder, a claimant, a broker, or an agent. The report captures the policy number, what happened, when and where, who was involved, and early evidence. It opens the claim and starts triage.

What information do you need to file a first notice of loss?

Have the policy number, the date, time, and place of the loss, and a short description of what happened. Add the names of anyone involved, any injuries, and contact details for witnesses. Photos, videos, and police or incident reports help the adjuster act faster. Missing details are the most common cause of early delays.

What is the difference between FNOL and a claim?

FNOL is the first report that a loss happened. The claim is the full process that follows, including investigation, the coverage decision, and payment. Proof of loss is a separate, later document that sets out what the policyholder is claiming. A complete FNOL makes each later step faster and more accurate.

What happens after FNOL is filed?

The insurer verifies identity and coverage, checks for duplicate claims, and scores severity. The claim is then assigned to an adjuster or a fast-track path. The policyholder gets a claim number and the next steps. The adjuster reviews the evidence and starts the investigation. Exceptions go to a named owner.

How do SLAs improve FNOL and claims processing?

SLAs set time-bound expectations for each step, such as acknowledgment, first contact, and assignment. When an SLA timer is about to run out, the workflow can escalate the claim to a lead before it goes late. Policyholders know when to expect an update, and managers can see which steps miss their targets.

Does Moxo replace my claims system?

No. Moxo works alongside policy administration and claims systems as the orchestration layer. It runs the process around them: intake, evidence requests, approvals, and updates to policyholders, brokers, and vendors. AI agents handle routine steps, adjusters keep the decisions, and the claims system stays the system of record.

Describe your business process. Moxo builds it.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Make your business flow

See it in action
_______