First Notice of Loss (FNOL) Intake Call Checklist
Use this First Notice of Loss (FNOL) Intake Call Checklist to capture claim facts, verify policy details, and set up the claim correctly on the first call. It helps intake reps avoid missing required fields and reduces rework after the call.
Trusted by frontline teams 15 years of frontline software
Built for: Insurance · Claims Operations · Call Centers
Overview
This First Notice of Loss (FNOL) Intake Call Checklist standardizes the information captured when a claim is first reported. It is built for intake representatives who need to verify the policy, document the loss details, identify the people and property involved, and complete the initial claim setup without missing required fields.
Use this template when your team handles live FNOL calls and needs a repeatable checklist item sequence that supports accurate claim creation, cleaner handoffs, and fewer follow-up calls. It works well for auto, property, liability, and workers' compensation intake, as long as you customize the fields to match the line of business and jurisdiction. The checklist is especially useful when multiple reps handle the same queue, when claim setup depends on a specific verification step, or when you need a clear record of what was confirmed on the call.
Do not use this template as a substitute for the full investigation, coverage determination, or adjuster workup. It is also not the right fit for informal reporting channels where no claim is opened, or for purely post-loss documentation after the intake window has passed. If your process includes emergency response, fraud screening, or catastrophe triage, those steps can be added, but the core purpose should remain the first report call and the data needed to start the claim correctly.
Standards & compliance context
- This template supports consistent intake documentation, which helps align with internal claims-handling procedures and audit expectations.
- If used in regulated lines of business, customize the checklist to reflect applicable notice, disclosure, and record-retention requirements.
- For workers' compensation or injury claims, include any required escalation or emergency-response steps without turning the checklist into a medical assessment.
- Do not collect unnecessary sensitive information during intake; capture only what is needed to open and route the claim correctly.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
How to use this template
- 1. Configure the checklist with the policy, loss, party, and claim setup fields your intake team must capture for the specific line of business.
- 2. Assign the intake rep as the DRI for the call and set the task type to checklist so each required item is completed in sequence.
- 3. Use the checklist during the live FNOL call to verify policy details, document the loss facts, and record all involved parties and contact information.
- 4. Mark any non-applicable items as N/A, and flag blocking issues such as missing policy verification or unclear loss location before closing the call.
- 5. Review the completed checklist against the claim record after the call to confirm the claim was opened correctly and route any follow-up tasks to the right owner.
Best practices
- Keep each checklist item atomic so the rep can answer yes, no, or N/A without combining multiple facts in one step.
- Verify the policyholder identity and policy number before collecting detailed loss facts to avoid documenting the wrong claim.
- Capture the loss date, time, and location as separate items so later coverage and liability review has clean data.
- Use a blocking flag only for issues that prevent claim setup, such as no active policy match or an unidentifiable loss event.
- Record third-party names, phone numbers, and roles during the call, because callback gaps are hard to reconstruct later.
- Add line-of-business-specific verification steps, such as vehicle information for auto or damaged premises details for property, instead of relying on a generic script.
- Close the checklist with a claim setup verification step so the intake rep confirms the claim number, assignment, and next action before ending the call.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What does this FNOL intake call checklist cover?
This checklist covers the core information needed to open a claim from the first report of loss. It typically includes policy verification, loss date and location, loss description, involved parties, injuries or damage, and claim setup actions. It is designed for the intake call itself, not for later investigation or adjuster follow-up.
Who should use this checklist?
Intake representatives, claim handlers, and call center staff should use it when taking a first notice of loss. A DRI can be assigned to the intake role or queue owner so each call is completed consistently. If your process separates intake from adjudication or investigation, this checklist should stay with the intake team.
How often should this checklist run?
This is a recurring operational task that should run every time a new claim is reported. It is not a one-time setup checklist, because each FNOL call can involve different policy details, loss facts, and parties. If your team handles high volume, use it as a standard call script and verification step for every intake.
Is this checklist meant for all claim types?
It can be adapted for auto, property, liability, workers' compensation, or specialty claims, but the exact fields should match the line of business. Some claim types need extra items such as injury details, vehicle information, or emergency service status. If a field does not apply, the checklist should allow a clear N/A answer rather than forcing a guess.
What are the most common mistakes this checklist helps prevent?
The most common issues are incomplete policy verification, missing loss timestamps, unclear descriptions of what happened, and omitted contact details for involved parties. Another frequent problem is opening the claim before confirming whether the loss is actually covered or whether a duplicate claim already exists. A structured checklist reduces these gaps and makes the intake record easier to hand off.
How does this help with compliance or audit readiness?
A documented FNOL checklist creates a repeatable record of what was asked and what was captured during the first report. That supports internal audit trails, complaint handling, and consistent treatment of claims. It also helps teams show that required verification steps were completed before claim setup.
Can I customize this checklist for my workflow?
Yes, and you should tailor it to your policy forms, claim system fields, and line-of-business requirements. You can add or remove checklist items for jurisdiction-specific disclosures, catastrophe events, or special handling queues. Keep each item independently verifiable so the intake rep can answer yes, no, or N/A without ambiguity.
How does this compare with an ad-hoc intake call?
An ad-hoc call depends on memory and usually produces uneven documentation across reps and shifts. This checklist standardizes the sequence of questions and the claim setup verification step, which makes handoffs cleaner and reduces back-and-forth after the call. It is especially useful when multiple teams touch the claim after intake.
Related templates
Ready to use this template?
Get started with MangoApps and use First Notice of Loss (FNOL) Intake Call Checklist with your team — pricing built for small business.
