What a First Notice of Loss should include — and why speed matters

The First Notice of Loss is the opening move of the entire claim. It's the first structured record anyone — the property owner, the carrier, and eventually you — has of what happened. Get it complete and get it in fast, and the rest of the job runs on rails. Get it thin or slow, and you spend the next two weeks reconstructing details that were obvious on day one.

A First Notice of Loss (FNOL) is simply the initial report that a loss has occurred. For a restoration contractor it does two jobs at once: it starts the insurance clock, and it becomes the anchor your documentation, scope, and estimate all trace back to.

What belongs in a First Notice of Loss

A good FNOL answers the who / what / where / when before anyone argues about the how-much. At minimum:

• Who and where. Property owner or point of contact, the loss address, and the specific unit or area affected.
• What happened. The type of loss (water, fire, storm, sewage) and a plain description of the event and its apparent cause.
• When. When the loss was discovered, and when it likely started if that's different — that gap matters for how a loss is evaluated.
• Current condition. What's affected right now, whether the source is controlled, and whether anyone is displaced or at risk.
• First photos. Even a handful of clear shots of the source and the extent turns a phone-call summary into evidence.
• Immediate safety concerns. Energized water, suspected contamination, structural doubt, gas — anything that changes how a crew can safely enter.

Notice what a strong FNOL is not: it isn't a scope, and it isn't a price. It's the factual foundation those get built on later.

Who files it — and why that's changing

Traditionally the property owner or their agent notifies the carrier, and the contractor learns about the job somewhere down the line — often after critical time has passed. The problem is that the person closest to the loss in the first hour is usually the least equipped to document it well.

That's the case for giving your accounts a direct, structured way to report a loss to you the moment it happens. When a property manager or facilities team can file a first notice with photos through a portal you control, you get the details while they're fresh, you can flag safety before anyone walks in, and you're first on the scene instead of third in line. That's exactly what the Vigilince Client Portal is for.

Why speed matters more than most people think

Water keeps wicking. Smoke keeps setting. Contamination keeps spreading. The condition you document in hour one is not the condition anyone can document in hour forty-eight, which means a slow first notice quietly erases evidence you'll wish you had. Speed also shapes the human side of the claim: the faster a property owner sees a real, structured response, the more the whole process feels handled — and the fewer surprises land later.

Speed doesn't have to cost quality. The goal is a first notice that's both fast and complete — captured once, cleanly, at the moment of loss.

From first notice to first look

The most useful thing you can do with a good FNOL is turn it immediately into a first look — a structured read of the loss that tells you what you're walking into before you dispatch. That means the safety flags, the conditions that will drive the category and scope, and a documented starting point, all standing up within minutes of the report.

This is where Vigilince fits: a loss filed through your portal (or captured by your own tech) runs an automatic safety scan and base read, and lands in your inbox as a first look — so the leap from "something happened" to "here's what we're dealing with" takes minutes, not a site visit. From there, documenting the loss and building a defensible scope is a continuation of the same record, not a fresh start.

See how a filed loss becomes a first look in your inbox on the Client Portal, or read how water categories shape the scope once the first look is in hand.