Documentation

How to document a water-damage loss for the insurance claim

For reference only. This article is general education for restoration professionals — it is not professional, legal, insurance, or safety advice, and it is not a substitute for the judgment of a qualified professional evaluating actual conditions on site. Practices and requirements vary by loss, building, and jurisdiction. Vigilince and TM+ LLC make no warranty as to accuracy or completeness and accept no liability for actions taken in reliance on this content; use is subject to our Terms.

Most water jobs aren't lost on the drying floor. They're lost weeks later, when a reviewer looks at a thin folder of photos and can't tell where the water came from, how far it traveled, or why you removed what you removed. Good documentation isn't paperwork — it's the record that keeps your category call and your scope defensible after everyone's memory has faded.

Here's a way to document a water loss that stands up to a second look, built around a simple idea: capture the loss as a story a stranger could follow — source, path, extent, and what you did about it — not just a pile of "wet" pictures.

Start with the source and the cause of loss

The single most common gap we see is documentation that proves there was water, but never proves where it came from. The cause of loss is what a carrier keys on, so photograph it first and photograph it clearly: the failed supply line, the backed-up drain, the roof penetration, the appliance connection. Get a wide shot that shows the location in context, then a tight shot of the actual failure point.

If the source has been shut off or repaired by the time you arrive, note that in writing — who stopped it, roughly when, and what the evidence on site still shows. A claim that can't establish the origin invites questions no amount of drying logs will answer.

Map moisture like you'll have to prove it

Water doesn't stop at what's visibly wet. It wicks up drywall, tracks under flooring, and hides behind cabinets and baseboards. Your documentation should show the true affected area, not just the puddle. Walk the perimeter with a moisture meter and mark where readings transition from wet to dry — that transition line is what justifies your removal and your equipment placement.

Capture affected materials by type, because materials dry differently and get scoped differently: gypsum board, insulation, framing, subfloor, cabinetry, contents. If you flood-cut, photograph the cut line and note the height. The goal is that anyone reviewing the file can reconstruct your category and class reasoning without being in the room.

Reference, not a determination. Nothing here assigns a water category or authorizes a scope for you — those are your professional calls, made on site. This is about capturing the evidence behind them cleanly.

Photograph in a sequence, not a shotgun

A folder of 80 unlabeled photos is nearly as useless as no photos at all. Shoot in a repeatable order so the set reads like a walkthrough:

  • Establishing shots — the address/unit and each affected room from the doorway, so location is never ambiguous.
  • The source — wide, then tight, as above.
  • Extent — the wet-to-dry transition on each affected surface, with a meter in frame where it helps.
  • Materials and contents — what's affected and its condition before you disturb it.
  • Hazards — anything that changes how the crew works: standing water near outlets, suspected contamination, compromised structure.
  • Progress — equipment set, demolition, and daily condition, so the drying timeline is visible.

Timestamps and, where your device allows it, location metadata turn a photo from "a wet wall" into "this wall, in this unit, on day one." That context is exactly what a supplement reviewer looks for.

Log the readings that actually matter

Numbers make a file credible. Capture the moisture content of affected and unaffected reference materials, the ambient temperature and relative humidity, and — as drying progresses — the trend toward your drying goal. You don't need a dissertation; you need enough of a record that the equipment you placed and the days you billed are obviously reasonable. Our free air-mover and dehumidifier sizing calculators give you fast, defensible starting targets to document against.

Write down what you did and when

The mitigation timeline is the connective tissue of the claim: arrival, source control, extraction, demolition, equipment set, daily monitoring, and the readings that justified pulling equipment. When mitigation is documented as a sequence with times, "why did this take four days" answers itself. When it's a single "dried the structure" line, every day becomes negotiable.

The gaps carriers push back on

If you close only a handful of gaps, close these — they're the ones that generate the most friction:

  • No clear cause of loss. Damage without an origin is the fastest route to a denied or reduced claim.
  • Removal that isn't justified by a reading or a photo. If you took it out, show why it had to come out.
  • No unaffected reference reading. A drying goal is only meaningful against a dry standard from the same materials.
  • A category that isn't supported by the conditions shown. The photos and notes should point to your call, not contradict it.
  • Prices with no basis. Line items should trace to your own price book, not to numbers that appeared from nowhere.

The short version

  • Prove the cause of loss before you prove the damage.
  • Document the true affected area, including where water hid.
  • Shoot photos in a repeatable sequence a stranger could follow.
  • Log readings and a mitigation timeline so scope and days are obvious.
  • Tie every removal and every price to a reason on the file.

None of this has to slow you down. The point of a good first look is to capture this record as you work, not to reconstruct it later from memory. That's what Vigilince is built to do: read your capture photos and structure the conditions, the scope to verify, and the documentation an adjuster will respect — so the defensible version is the default version. See how it reads a water loss, or what a clean First Notice of Loss should include.

Document the loss as you work it

Beta invites go out in waves — join the waitlist, and when yours arrives you'll capture a real water job and get a first-look report with the conditions, the scope to verify, and a branded export built in.