FNOL automation: reading and checking loss notices before claim setup

FNOL automation uses software to read and check each first notice of loss as it arrives. FNOL means first notice of loss, the first report that tells an insurer about a loss. The notice can be an ACORD form or a carrier's own form, sent as an email attachment, a scan or an upload. Notices that pass every check go on to claim setup. A person sees only the notices that fail.

What FNOL automation covers#

In claims teams, FNOL means two things. It's the notice itself, and it's the intake work that turns the notice into a claim someone can handle.

Most writing on FNOL automation covers digital FNOL. In digital FNOL, the policyholder reports the loss through an app, a web form or a chatbot. Much FNOL software is built for that channel. Commercial carriers and third-party administrators (TPAs) also receive notices as documents. An insurance agent emails an ACORD form, or an employer sends a first report of injury. Sometimes the insured just forwards photos with a few lines about what happened.

Someone still has to read those notices before anyone can set up the claim. What happens after setup, from coverage to payment, is in our guide to insurance claims automation.

What arrives at first notice of loss#

In commercial lines, a notice often arrives as one of four ACORD loss notices. ACORD is the insurance standards body that publishes these forms. Many others arrive as emails that carry the same facts without a form.

A few details on these forms change how intake has to read them. An ACORD 1 has three policy sections, for property, wind and flood. Each has its own carrier and policy number, and your team needs the policy your company wrote. On newer editions, a description that's too long for its box continues on an ACORD 101, the Additional Remarks Schedule, attached to the notice.

The ACORD 4 tells the employer not to fill in the fields marked with an asterisk. Those fields are left for the claims administrator, meaning the carrier or TPA that handles the claim. They include the claim number and the state whose rules apply. They also include codes for the cause of injury, the part of body and the type of injury. The claims administrator may also have a legal deadline. In California, it has 10 business days from learning of a workers' compensation claim. By then, it must send data about the claim to the state.

The same form can also arrive in more than one layout. Carrier sites still post the 2006 and 2010 editions of the ACORD 1 for download, and some states have their own version, such as California's. Some carriers still ask for the forms by fax, so some notices arrive as faxed images.

What claim setup needs from one notice#

Here is a homeowners loss notice from Quillmere Mutual. The tabs show what software reads from each field.

The Policy tab gives the policy number, QHM-5561204, and the policy period, March 1, 2026 to March 1, 2027. The Loss tab gives the date of loss, September 14, 2026. It also gives the cause, a burst supply line, and the address on Linden Ave. With these values, your team can match the claim to the right policy.

The last field in the Loss tab, "Within policy period", isn't printed on the form. Software fills it in after checking that the date of loss falls inside the policy period. In Docsumo, a check like that is a step you set up in the workflow.

Three values are handwritten. They are the best time to call, the description and the $18,400 estimate. When you test any tool on your own notices, look at those fields first.

How FNOL automation works on a claims inbox#

Take one claim packet for a commercial property loss. It's a single PDF with the loss notice, a remarks page, a few photos and a roofer's estimate. The first job is to split that PDF into its documents. For mixed packets like this one, Docsumo's AI Split takes a plain-English definition of each document type. You write, for example, what a loss notice or a roofer's estimate looks like.

Next, each document is sorted by type. You give only the names of the document types you want, with no training set of sample documents. If a document fits none of your types, it waits as Unclassified until a person assigns it a type. Also name the document types that come in later for claims that are already open, such as police reports and estimates. Then a police report that arrives on its own is sorted as a police report, not as a new notice.

The fields are read next, handwriting included. Our post on OCR for claims processing explains that step. For each field, you set a confidence threshold. That is the lowest confidence score you accept for the field. Fields that score below it go to a person. The checks come last. In Docsumo, a notice that passes goes to your claims system through the API or a webhook, and a notice that fails waits for review.

• 99%99%field-level accuracy across 250+ document types
• 95%+95%+of documents processed straight through, without manual review

Checks to run before a claim is opened#

A notice can be read perfectly and still not be ready for setup. These checks decide whether it goes straight through or waits for a person.

• The policy is yoursAn ACORD 1 can list three policies from different carriers. Find the one your company wrote.
• The policy number matches a policyTwo digits in the wrong order can point the claim at the wrong policy, or at none. Look the number up in your own records.
• The date of loss falls inside the policy periodA loss dated before the policy started, or after it ended, needs a person before setup.
• The loss is newThe same loss can arrive twice, once from the agent and once from the insured. Search your claims system for an open claim with the same insured, date and place.
• Setup has what it needsLook for a date, a place, a cause and a way to reach the insured. For workers' compensation, add the date of injury and the part of body.

Docsumo runs the checks you set up as steps in the workflow, such as comparing the date of loss with the policy period. On the Enterprise plan, it can also look up values such as the policy number in your own records (master data lookup). It can compare values across a claim's documents too (cross-document validation). Whatever checks you set up, fields below their confidence threshold still go to a person.

When a notice needs a person#

Many notices stop at intake because something is missing, not because something is wrong. A notice names a police report that isn't attached. An ACORD 4 arrives without the treating doctor's name. Another notice leaves the policy number blank.

A missing document, such as that police report, is the easy case. In Docsumo, the Document Collection and Email agents ask for it. These AI agents email the sender for the missing document. A missing value is harder, because someone has to decide whether setup can go ahead without it. Other notices need a person to decide. For example, a notice may name another carrier's policy, or give a loss date outside the policy period.

Our take. An AI agent should check every notice before anyone on the team opens it. Notices that pass every check should go on to setup without waiting in a queue. The setup team should see only the notices that failed a check. Each one should show which check failed and the line on the form that caused the failure.

Where Docsumo fits in FNOL#

Docsumo is an intelligent document processing platform. At first notice of loss, it reads the notice forms and the documents attached to them. That includes the ACORD 1 to 4 and other ACORD forms. It handles any document type, so it isn't limited to pre-built models. It reads handwritten as well as printed text. Documents come in by email through its own inbox, by upload or through the API.

Sorting documents by type (classification) and splitting files are on the Business plan. The checks against your own records and across documents are on the Enterprise plan. When a reviewer clicks a field, the line it came from is highlighted in the document. The reviewer's corrections improve the model. Checked data goes to your claims system through the API and webhooks.

Docsumo runs in the cloud only. It's SOC 2 Type 2 audited and HIPAA compliant, and the security page has the details. It doesn't take phone reports or run a policyholder app. It isn't a claims system, so it doesn't set reserves or pay claims. It supplies the software, and your own staff review the notices that fail a check.

Start with last month's loss notices#

Pull a month of notices from the intake inbox, including the faxed and handwritten ones. Count how many a person had to retype, and how many were missing something when they arrived. Those two counts are your baseline. They also show which notice type to automate first.

Book a demo with a few of your own loss notices, or start a free trial.

Frequently asked questions#