Contents

FNOL claims intake document workflow

FNOL claims intake document workflow

FNOL is a document scramble

When a policyholder reports a claim, the broker's first job is often intake — collecting the documents the insurer needs to open the file.

For auto claims, that may include accident photos, a police report, witness information, and a completed proof of loss. For property claims, photos of damage, receipts, and contractor estimates arrive in mixed formats.

Clients send photos by text. The police report comes by email. The adjuster asks for something the client already sent but nobody can find. The producer searches three threads while the client waits.

FNOL is not policy admin — but disorganized intake still costs brokerages time and erodes client trust during a stressful moment.

Typical FNOL checklist items

Requirements vary by carrier, claim type, and line of business. A practical Ontario FNOL intake checklist often includes:

  • Date, time, and location of loss
  • Description of incident (client statement)
  • Photos of damage or accident scene
  • Police report (if applicable)
  • Witness names and contact information
  • Current policy dec page
  • Proof of loss form (signed)
  • Repair estimates or invoices (property)
  • Rental vehicle information (auto)
  • Correspondence log with client and insurer

Why email fails at FNOL

Claims intake is time-sensitive and emotional. Clients may send unclear photos, wrong documents, or multiple messages across channels.

Email does not:

  • Show which FNOL items are still missing
  • Let you reject a blurry photo with a reason and ask for a retake
  • Keep claim documents scoped to the policyholder's client record
  • Give CSRs visibility when the producer is unavailable

A checklist on the existing client record solves the organization problem without a separate claims system.

FNOL workflow with Hivi-X

  1. Open the policyholder's client file — the record your team already manages.
  2. Attach an FNOL checklist template — auto collision, property water, etc.
  3. Collect documents — client uploads through the my-id.ca portal; CSR adds insurer correspondence as it arrives.
  4. Track gaps — see outstanding items before forwarding to the adjuster.
  5. Export the package — PDF summary for your BMS claims folder or internal handoff.

Voice notes help document the initial client call — what happened, what coverage was discussed, what the client was advised to do next. Self-hosted AI summarizes the recording on the client file without sending data to third-party AI providers.

What Hivi-X does not do

Hivi-X does not:

  • Open claims in insurer systems
  • Reserve losses or negotiate settlements
  • Replace your BMS claims module
  • Communicate with adjusters on your behalf

It organizes the document collection layer on the broker-controlled client file — the same role it plays for new-business intake.

General information only

This page is operational guidance, not legal or claims-handling advice. Follow carrier FNOL requirements and your brokerage claims procedures.

Start a free trial and build an FNOL checklist for your next claim intake.

Answers are general operational information only — not legal, tax, regulatory, clinical, privacy, immigration, or professional advice. Requirements vary by matter, client, and regulator.

Frequently asked questions

What documents are collected at FNOL?
Typically incident photos, police report (if applicable), proof of loss, policy dec page, witness details, and correspondence with the client and insurer. Requirements vary by claim type and carrier.
Does Hivi-X adjust claims or communicate with insurers?
No. Hivi-X organizes document collection on the broker-controlled client file. Claims handling, reserving, and insurer communication stay in your BMS or carrier systems.
Can clients upload claim photos through Hivi-X?
Yes. Clients upload through the my-id.ca portal on checklist items. Your team approves or rejects submissions and can request corrections.

Organize broker client files without the email chase

Hivi-X helps Ontario insurance brokers collect application documents with reusable checklists, a Canadian-hosted client portal, self-hosted AI summaries, and exportable PDF packages for Applied, Epic, SIG, or your BMS. Hivi-X is document-collection software — it does not replace your BMS or guarantee RIBO compliance.

FNOL Claims Intake Document Workflow Ontario Brokers | hivi-x Docs