Template

FNOL template for public adjuster intake and claim kickoff.

This first notice of loss template gives PA teams a practical structure for collecting the details that matter before a claim moves into assignment, evidence, and execution workflows.

Who this template is for

  • Teams standardizing first-notice capture across multiple people or intake sources.
  • Firms that want cleaner intake handoffs without relying on memory or freeform notes.
  • Operations leads building a repeatable intake command center.

Core FNOL fields

Use these fields as the minimum structure for first notice of loss.

  • Claimant name, address, phone, and preferred contact method.
  • Date of loss, reported date, and high-level event summary.
  • Carrier, policy number, claim number, and assigned contact if known.
  • Current urgency, inspection status, and immediate next step.

Context that improves downstream execution

These details prevent the next team member from restarting intake work.

  • Initial documentation already collected and what is still missing.
  • Any promised follow-up, deadline, or inspection window.
  • Special property, access, or claimant context that affects field work.

How to use the template operationally

The template works best when it is paired with assignment and next-action discipline.

  • Use one owner for completion so the template does not become half-filled metadata.
  • Flag unknowns explicitly rather than burying them in notes.
  • Do not move the file forward until the next action and owner are clear.

Related next steps

These pages help turn the workflow lesson into a buying decision, rollout path, or live operating rhythm without leaving the public-adjuster wedge.

First notice of loss software

See how claimOS turns FNOL into a live workflow instead of a static form.

Open page

Intake command solution

See the workflow page behind the intake command center approach.

Open page

FAQ

Questions teams ask before standardizing the workflow

Should FNOL live in a document or inside software?

The template is useful either way, but software is stronger because the intake record can immediately feed ownership, evidence, and next-action workflows.

Can smaller teams still benefit from a formal FNOL template?

Yes. Smaller teams often rely on memory and ad hoc notes, which is exactly where a simple template can reduce missed details and rework.

Next step

Turn the process into a live operating rhythm.

If this resource matches the workflow you want to standardize first, use it as a rollout conversation starter and then map it into the right claimOS workflow page.