First Notice of Loss (FNOL) Intake Call Checklist
Use this First Notice of Loss (FNOL) Intake Call Checklist to capture the facts of a new claim call, verify policy details, document the loss, and set clear next steps before the call ends.
Trusted by frontline teams 15 years of frontline software
Built for: Insurance · Third Party Administration · Claims Operations
Overview
This First Notice of Loss (FNOL) Intake Call Checklist is a claim-opening template for the first conversation after an incident is reported. It helps intake teams capture the policyholder or claimant details, verify the policy, document the loss facts, identify involved parties, note immediate damage or injury concerns, and record the next step before the call ends.
Use it when a new claim is being reported by phone and you need a consistent intake flow that supports accurate claim setup. It is especially useful when multiple agents handle calls, when the line of business has required intake fields, or when supervisors need a clear record of what was confirmed versus what still needs follow-up. The checklist format keeps the work atomic: each item should be answerable yes, no, or N/A, and each verification step should stand on its own.
Do not use this template as a substitute for a full investigation, coverage determination, or legal review. It is not the right fit for post-loss adjustment work, complex fraud review, or open-ended narrative note-taking. If your team needs to capture extensive evidence, medical details, or jurisdiction-specific disclosures, add those fields as separate checklist items rather than packing them into one line. The goal is a clean FNOL record that reduces rework, supports handoff, and makes the next claim step obvious.
Standards & compliance context
- This template supports consistent claim intake documentation, which helps with internal audit trails and claim handling standards.
- If your workflow includes required disclosures or recorded-call rules, add those as explicit checklist items so they are not missed during intake.
- Use the checklist to separate verified facts from caller statements, since claim records should not treat unconfirmed information as established fact.
- For regulated claim programs, align the checklist with your organization’s retention, notice, and escalation procedures before rollout.
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 claim line of business, required intake fields, and any jurisdiction-specific questions before the first call is taken.
- 2. Assign the intake representative as the DRI for the call and define which responses are blocking, which are non-blocking, and which require escalation.
- 3. During the call, verify policy details, capture the loss facts, document involved parties, and complete each checklist item as a separate, independently verifiable step.
- 4. Record any missing information, follow-up commitments, and urgent exceptions so the claim file shows what was confirmed and what still needs action.
- 5. After the call, route critical issues to the appropriate handler, send the promised communication, and review the checklist for missing fields or unclear notes before closing intake.
Best practices
- Keep each checklist item to one fact or one verification step so the intake rep can answer it clearly during the call.
- Use normal priority for routine intake items and reserve critical only for safety, compliance, or immediate escalation triggers.
- Separate policy verification from coverage discussion so the record shows what was confirmed versus what was only discussed.
- Capture the loss date, location, and cause of loss in distinct items to avoid ambiguous claim setup later.
- Document contact preferences and callback commitments before ending the call so follow-up does not depend on memory.
- Mark missing information as non-blocking only when the claim can safely move forward without it.
- Add line-of-business-specific fields as separate items instead of embedding them in a single free-text prompt.
- Review the checklist after a few live calls and remove any item that is repeatedly skipped or duplicated.
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, claimant and insured details, loss date and location, description of what happened, involved parties, immediate safety or damage concerns, and the next communication step. It is designed to make the intake call complete enough for claim setup without turning the call into a full investigation.
Who should use a First Notice of Loss checklist?
Intake representatives, claims adjusters, call center agents, and TPA staff can use it to standardize claim intake. It is especially useful when multiple people handle first contact and you need consistent documentation across shifts or locations. The DRI is usually the person taking the call, while a supervisor may review exceptions or escalations.
How often should this checklist be used?
Use it for every new claim call or first report of loss, not just for complex claims. FNOL is a one-time intake event for each incident, so the checklist should be completed during the initial contact and then attached to the claim record. If the caller provides partial information, the checklist can be reopened for follow-up, but the original intake should still show what was known at the time.
Is this checklist meant for auto, property, or liability claims?
It can be adapted for auto, property, liability, workers' compensation, or specialty claims, but the exact fields should match the line of business. For example, auto FNOL may need vehicle and driver details, while property FNOL may need occupancy and cause of loss. The template is a starting point, so you can add or remove checklist items based on your claim type and intake workflow.
What are the most common mistakes when using FNOL intake forms?
The most common mistake is capturing the story but missing the operational details needed to move the claim forward, such as policy confirmation, contact preferences, or loss location. Another issue is using compound checklist items that make it unclear whether each fact was verified. A third pitfall is treating every issue as critical, which can hide the truly urgent claims that need immediate escalation.
Does this checklist help with compliance or audit readiness?
Yes, it supports consistent documentation and helps show that the intake team asked the same core questions on each call. That matters for internal audit trails, claim handling standards, and regulated workflows where timely, accurate documentation is important. It should be used alongside your organization’s claim handling procedures, not as a substitute for legal or regulatory requirements.
Can I customize the checklist for different claim programs or carriers?
Yes, and customization is expected. You can add carrier-specific coverage questions, jurisdiction-specific disclosures, catastrophe triage steps, or special handling fields for fraud indicators and litigation risk. Keep each checklist item independently verifiable so the intake record stays clear and easy to review.
How does this compare with ad hoc note-taking on a claim call?
Ad hoc notes are faster in the moment, but they often miss key facts or bury them in free text. A checklist creates a repeatable call flow, reduces rework, and makes it easier for the next handler to understand what was confirmed, what was still unknown, and what action comes next. It also helps supervisors spot missing information before the claim moves downstream.
What should happen after the checklist is completed?
After the call, the intake rep should confirm the claim record is complete, route any urgent issues for escalation, and send the promised follow-up communication. If the loss involves safety, severe damage, or potential coverage complications, the checklist should trigger the appropriate blocking or critical handoff. Otherwise, it should feed the normal claim setup and assignment process.
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.