The 10-minute roof-capture routine that prevents desk-review kickbacks

A kickback almost never means you wrote a bad report. It means you got back to the truck without something the desk reviewer needed — and no amount of careful writing that night can add a photo you didn't take or a count you didn't get.

The report is decided on the roof, not at the desk. So the fastest way to stop losing evenings to re-inspection trips isn't better writing. It's ten disciplined minutes of capture, the same way, every inspection. Here's the routine.

Why reports get kicked back

Put yourself in the desk reviewer's chair. They weren't on the roof. They can only approve what's in front of them. When a file lands with "hail damage observed on the roof" and no per-slope test squares, they can't tell whether you found eleven hits or two — so they send it back and ask. When three slopes are documented and the fourth isn't mentioned at all, they don't assume it was clean; they assume it wasn't inspected.

Every kickback traces to the same root: a gap between what you saw and what you can prove you saw. Close the gap on the roof and the file has nothing to send back.

The routine, minute by minute

Minutes 0–2: establish the property

• Risk photo with the house number in frame. This is your anchor — it ties every photo that follows to this address, at this loss.
• All four elevations. Front, both sides, rear. The clean elevations matter as much as the damaged one; they're your evidence that damage is directional and storm-consistent, not old and general.

Two minutes, and the file already establishes where and what before anyone argues about how much.

Minutes 2–6: every slope, every time

This is where files are won or lost. Chalk a test square on every slope — north, south, east, west — and photograph each one twice: a wide shot that shows which slope it is, then a close-up of the hits inside the square.

The habit that saves the most trips: document the clean slopes too. A slope with zero hits isn't nothing. Photographed and counted, it's proof that the damage follows the storm track — the single strongest piece of causation evidence you can hand a reviewer. A blank where a slope should be is a re-inspection. A photographed zero is an argument in your favor.

Minutes 6–8: damage in pairs

For each damage item — a bruised mat, a dented gutter, a cracked boot, a totaled turbine — shoot it as a pair: an overview that shows where it is on the structure, then a close-up that shows what it is. Put a tape measure or a hail gauge in the close-up frame so scale is never in question.

A close-up with no overview is an orphan; the reviewer can't place it. An overview with no close-up doesn't prove the damage. Pairs prove both at once.

Minutes 8–10: the 90-second voice memo

Before you climb down, while it's fresh, talk through the inspection the way you would on the drive home. Four rules make the memo usable instead of vague:

1. Name the location first. "On the north slope…" then the finding. A finding with no location is a finding a reviewer can't map.
2. Speak numbers as numbers. "Eleven hits per square." "Eight years old." "Twenty-eight squares." Ranges and hedges read as guesses.
3. State the negatives out loud. "South and west slopes clean, no hits. No interior leaks observed." Negative findings are what prevent supplement disputes later.
4. Close with cause and intent. One sentence on what caused the loss, one on repair versus replace. That's the spine the whole narrative hangs on.

Type the numbers that have to be exact

A few values can't survive being "about right" — they get audited. Enter them as numbers, on site, before you leave:

• Per-slope test-square counts (enter 0 for inspected-and-clean — a zero is evidence, a blank is a trip back)
• Roof age, size in squares, pitch, number of stories

Typed exact values should override anything fuzzy you said into the memo. Get them down while you're still standing on the proof.

What desk reviewers actually kick back

If you want a pre-climb-down checklist, it's the inverse of the routine above. A file gets sent back when it's missing:

• A test square on one or more slopes (including the clean ones)
• Impact counts you can point to, per slope
• Overview-plus-close-up pairs with something for scale
• Explicit negative findings
• A stated cause tied to the storm, and a repair-vs-replace call

Document all six and there is, quite literally, nothing left to ask for.

The point

Ten minutes of the same routine, every roof, turns "hail damage was observed" into a file that approves on the first pass. The writing gets easier too — but the writing was never the bottleneck. The capture was.

---

This routine works no matter what you write your reports in. If you want to see what a clean capture turns into, read a full sample report or grab the complete field guide — shot list, memo script, and kickback checklist. LossNarrative turns the photos and the memo above into a carrier-formatted narrative, but the ten minutes on the roof are what make either one hold up.