First Notice of Loss (FNOL) is the first step in the insurance claims lifecycle. It occurs when a policyholder reports an incident that may result in an insurance claim. Because FNOL triggers the entire claims handling process, it is critical that agencies and claims teams collect accurate information and document the loss correctly. A structured FNOL SOP ensures that claims are reported consistently, required details are captured, and the claim is initiated properly with the carrier. This procedure outlines the workflow used by insurance agencies, carriers, and insurance BPO claims teams to process the first notice of loss and begin the claims handling process. Learn how organizations structure process documentation.

Purpose of the First Notice of Loss SOP

The purpose of this SOP is to standardize how insurance claims are reported and documented when a loss occurs. A consistent FNOL process ensures that claims information is collected accurately and that the claim is initiated promptly with the appropriate carrier.

Following a structured FNOL workflow helps organizations:

Capture complete loss information from the policyholder
Verify policy coverage before initiating the claim
Submit accurate claims data to the carrier
Ensure claims are assigned quickly for investigation

Standardizing FNOL procedures helps reduce claims handling delays and improves the overall claims experience for policyholders. Understand how organizations preserve operational knowledge through knowledge transfer.

Scope of the Procedure

This procedure applies to all insurance claims reported by policyholders including personal lines and commercial insurance policies. FNOL reports may involve incidents such as property damage, auto accidents, liability claims, or other insured losses. The workflow may be performed by agency servicing teams, carrier claims departments, or insurance BPO claims operations depending on the organization’s structure. The SOP covers the process from initial claim notification through submission of the FNOL report to the carrier. Learn how operational runbooks support incident response.

Roles and Responsibilities

Policyholder

Responsible for reporting the loss and providing initial incident details.

Account Manager or CSR

Responsible for collecting claim information and initiating the FNOL process.

Claims Intake Specialist

Responsible for documenting claim details and submitting the FNOL to the carrier.

Carrier Claims Department

Responsible for creating the claim record and assigning an adjuster.

Tools and Systems Used

Agency Management System (AMS)

Carrier claims reporting portals
Claims management systems
Customer communication systems such as phone or email
Document management systems

First Notice of Loss Workflow

Step 1

Receive Loss Notification

Receive notification of the incident from the policyholder or authorized representative.

Step 2

Verify Policy Information

Confirm policy details including policy number, coverage type, and effective dates.

Step 3

Collect Incident Information

Gather key details related to the loss including date, time, location, and description of the event.

Step 4

Document Parties Involved

Record information about individuals involved in the incident including witnesses or third parties.

Step 5

Collect Supporting Documentation

Request supporting documentation such as photos, police reports, or incident descriptions.

Step 6

Submit FNOL to Carrier

Report the claim through the carrier’s claims reporting portal or claims intake system.

Step 7

Confirm Claim Number

Receive the claim number from the carrier and record it in the agency management system.

Step 8

Notify Policyholder

Provide the claim number and explain the next steps in the claims handling process.

Common Information Collected During FNOL

Policyholder contact information

Policy number
Date and time of loss
Location of incident
Description of the event
Estimated damages
Contact details for involved parties

Common Errors in FNOL Processing

Incomplete incident information

Incorrect policy verification
Failure to collect supporting documentation
Delayed submission of FNOL to carrier
Failure to communicate claim number to policyholder

Following a structured SOP helps claims teams avoid these errors and ensures that claims are initiated efficiently. Explore how SOP automation helps teams generate procedures faster. See how walkthroughs can be converted into documentation automatically.

Automating Insurance Claims SOP Documentation

Insurance agencies and claims teams often document FNOL workflows as part of their claims operations SOP libraries. Instead of writing procedures manually, organizations can record walkthroughs explaining how claims intake is handled. AI-powered documentation systems analyze these walkthroughs and convert them into structured SOP documentation. ProcessDeck allows agencies and insurance BPO teams to generate SOP documentation automatically from operational walkthrough recordings, making it easier to maintain claims process documentation.

Stop waiting weeks for SOPs

Record your FNOL claims intake walkthrough and generate a structured SOP automatically with ProcessDeck.

Upload your first process

First Notice of Loss SOP (Insurance FNOL Process)