First notice of loss is the most compressed workflow in carrier operations. When a commercial policyholder calls to report a loss, the intake conversation has to accomplish three things at once: collect enough information to open the claim, verify that coverage exists, and create a record that downstream adjusters, coverage counsel, and potentially the reinsurance desk can work from. Most small carriers do this in a phone call, on a notepad, and then re-key the information into whatever system they use for policy records. That process has a failure rate that scales directly with call volume and shifts coverage.
This article looks at three approaches to FNOL automation that carriers are actually using in 2025, what each one does well, and where each one breaks down. The goal is not to argue that any single approach is correct — it is to give carrier ops teams a realistic picture of what "automation" means at the FNOL stage for commercial lines.
Why Commercial Lines FNOL Is Harder Than Personal Lines
Personal lines FNOL is a tractable automation problem. A homeowner calling to report storm damage to a residential property presents a bounded set of coverage questions: the policy is straightforward (HO-3 form or equivalent), the coverage sections are known, and the intake can follow a scripted decision tree with reasonable confidence that the right questions are being asked.
Commercial lines FNOL does not work that way. A single BOP policy covering a small manufacturing operation might include: General Liability (CGL ISO CG 00 01 or equivalent), Commercial Property (Building and Personal Property Coverage Form ISO CP 00 10), Business Income coverage, Equipment Breakdown, and an Inland Marine rider for tools in transit. A loss event at that account — a fire in a warehouse — might implicate GL, property, and business income simultaneously. The FNOL intake has to capture enough detail to route the claim to the right coverage section, which requires the intake person to understand what coverage the account actually carries and to ask the right questions based on that coverage map.
When FNOL is handled by a general call center without access to the policy record, that coverage mapping doesn't happen at intake. The claim is opened on whatever coverage the caller describes, and coverage clarification happens later — often after the adjuster has already invested time in a claim that turns out to belong on a different coverage part.
Approach 1: Digital FNOL Intake Forms
The most common first step toward FNOL automation for smaller carriers is a digital intake form — a web form or mobile-accessible form that the policyholder or their agent submits to open a claim without a phone call. FNOL forms have the advantage of being asynchronous: the carrier's team reviews submissions during business hours, and the policyholder has a record that the notice was filed.
The effectiveness of digital FNOL forms depends almost entirely on whether the form is connected to the policy record. A standalone form that collects incident description, contact information, and a loss date creates a claim record that still requires a human to look up the policy, verify coverage, and manually populate the claim fields. That is not materially more efficient than a phone intake — it just moves the work from the phone to a queue.
A connected digital FNOL form — one where the policyholder authenticates with their policy number, and the form pre-populates with their coverage parts and locations — changes the workflow. Now the form can ask targeted questions based on actual coverage: if the account carries a commercial auto endorsement, the form includes vehicle and driver fields; if it does not, those fields do not appear. The claim opens against the correct coverage section, and the adjuster receives a structured record with coverage verification already done.
Consider a specialty surplus-lines carrier in Florida writing commercial habitational risks — apartment complexes and mixed-use buildings. The carrier runs four or five FNOL calls per week, each averaging 20–30 minutes of intake time, followed by 15 minutes of re-keying into the policy system. A connected digital intake form eliminates the re-keying step and reduces the average intake handling time significantly. The caveat: the surplus-lines policy forms are non-standard, and the coverage sections require custom field mapping that a generic digital form builder cannot accommodate without policy-system integration.
Approach 2: Structured Phone Intake with Real-Time Policy Lookup
Many commercial losses still come in by phone — particularly from policyholders who are in a stressful situation and want to speak with a person. The question for carriers is not how to eliminate phone intake but how to make phone intake more structured and reduce the re-keying burden afterward.
Real-time policy lookup during the intake call changes the quality of the FNOL record significantly. If the intake person can pull up the policy in the same system they are using to create the claim record, coverage verification happens during the call rather than after. The adjuster note is structured: the intake person selects the loss type from a controlled vocabulary, selects the coverage part from the policy's coverage schedule, and enters a loss description into a free-text field. The system captures the timestamp of the call as the FNOL date, which matters for timely reporting obligations under state reporting requirements.
We are not claiming that structured phone intake eliminates coverage disputes — coverage determinations at FNOL are preliminary, and whether a loss is ultimately covered depends on investigation and policy interpretation that cannot be completed at intake. What structured intake does is ensure that the initial record is accurate enough to route the claim correctly and that the FNOL date is documented against the policy record rather than existing only in a phone log or a handwritten note.
For a commercial-lines carrier writing $35M in DWP with a mix of GL, property, and workers' compensation, a shift to structured intake with real-time policy lookup typically surfaces another problem: the policy record in the legacy system is often incomplete. Endorsements that were processed but not fully reflected in the coverage schedule, additional insured certificates that were issued but not tied to the master policy, locations added mid-term but not updated in the property schedule. The FNOL intake process becomes, inadvertently, a data quality audit on the policy records — which is uncomfortable but useful.
Approach 3: Rules-Based FNOL Routing
The third approach — and the most operationally effective one for carriers with consistent loss patterns — is rules-based routing after FNOL intake. Once a claim record is opened with a structured loss type, coverage part, and loss description, routing rules determine which adjuster or adjuster team receives the claim.
Routing rules in commercial lines are typically based on a combination of: LOB (GL vs. property vs. WC vs. auto), loss amount (estimated loss value at intake), geography (for carriers with regional adjustment offices), and policy type (standard admitted vs. surplus lines). A carrier that handles its own GL claims but uses a TPA for workers' compensation needs those claims routed to different queues automatically — not sorted manually by a supervisor who looks at each claim in the morning.
The complication in commercial lines is that multi-coverage losses — a slip-and-fall at a commercial property that involves both GL and the lease agreement's tenant liability coverage — require routing decisions that a simple rule cannot make. In those cases, the routing logic needs to open the claim on the primary coverage, flag it for multi-coverage review, and assign it to an experienced adjuster rather than routing automatically to a less-senior queue.
A Midwest mutual carrier writing $80M in GWP across commercial property, GL, and farm package lines has these routing decisions embedded in its adjuster assignment logic: property losses above a certain estimated value route to a property specialist; GL losses involving a named additional insured route to the coverage team before being assigned to a field adjuster; farm claims with livestock or equipment breakdowns are assigned by county rather than by random rotation. That routing logic, built into the claim system rather than administered manually, eliminated a class of supervisor time that was previously spent on daily claim triage.
What the Three Approaches Have in Common
All three automation approaches deliver their value through the same mechanism: they connect FNOL intake to the policy record, reduce the gap between when notice is received and when a structured claim record exists, and create an auditable trail of the intake process. None of them replace adjuster judgment about coverage or damages.
The failure mode for each approach is also consistent: they fail when the policy record they are connecting to is incomplete or out of sync with the actual coverage in force. Digital intake forms that pre-populate from a policy record are only as accurate as that record. Structured phone intake that verifies coverage at call time only verifies what the policy system shows. Rules-based routing that assigns a GL claim to the right adjuster only works if the claim's LOB field is accurate.
This means that FNOL automation is downstream of data quality in the policy-admin system. Carriers that treat FNOL automation as a standalone initiative — buying a claims intake product without addressing the policy data that feeds it — typically see modest efficiency gains and persistent coverage routing errors. Carriers that address both simultaneously see the larger gains.
The Timely-Filing Obligation
One dimension of FNOL that gets less attention in automation discussions is the state-mandated timely reporting requirement for certain loss types. Workers' compensation claims, for instance, are subject to state-specific employer reporting timelines — in Texas, under Texas Labor Code §409.005, an employer must file notice with the carrier within specific timeframes. The carrier's obligation to report to the state carrier depends on the type of injury and the facts of the loss.
A claim system that captures the FNOL date, the loss date, and the reported date as distinct fields — and that flags claims approaching reporting deadlines — reduces the compliance risk from late filing. This is particularly relevant for carriers that have grown their WC book faster than their claims handling capacity and where a claim that sits in the intake queue for 48 hours before being opened can approach a reporting deadline without anyone noticing.
Irys builds FNOL intake directly into the policy-admin workflow rather than treating it as a separate claims module. When a claim is opened, the system looks up the policy record in real time, populates the coverage schedule, and routes the claim based on LOB and loss type rules that the carrier configures. The FNOL date, reported date, and initial coverage determination are all captured at intake — not reconstructed later from notes. For commercial carriers at early stages of operational maturity, that integration removes the data quality problem at the source rather than trying to fix it downstream.