Direct answer. In the first 24–72 hours of a storm event, the estimator’s job is to triage which losses get scoped first, capture the scene before mitigation changes it, and write a file that survives desk review while volume is still rising. You are not the crew lead and you are not the GM. You sequence the board, lock facts while they are still true, and hand production a scope that does not invent work under pressure.
Dispatchers fill the phone. Techs pull water. You decide which address gets a real estimate today — and which facts leave the site with you.
First 4 hours — Triage, safety, and the scene that still exists
Decision point: Which properties get scoped first.
Do not run first-caller-wins. Sequence by active water still moving, authorized commercial doors you already serve, occupied residential where dry-in and extraction can start without a mystery decision-maker, then vacant or access-blocked files that wait for daylight and a key. Decline work that needs a crew class you lack, a hazard you cannot clear, or an authorization path that leaves materials unpaid.
On every inbound before you drive: loss type, water active or stopped, power on or off, approximate affected area, building type, who can authorize, carrier or TPA already on file. Put it in the shared log. If it is not in the log, it did not happen.
Decision point: Enter or hold at the curb.
Safety and access come before the sketch. Confirm the road is open. Note downed lines, structural movement, gas odor, and standing water at grade. Do not enter a building you cannot exit safely. Vacant sites need a key or written property-manager authorization. Occupied sites need a walk with the contact and a note of what they will not release.
Capture the scene before mitigation changes it. Photograph approach, elevations, openings, water or debris lines, point of entry, affected rooms, and contents in place. Take moisture readings with location, material, instrument, and time. Identify the source in notes — wind-created opening, overland intrusion, backup — before anyone moves finishes. A wet ceiling without the opening above it is half a story.
Do not open walls on the first visit unless the mitigation lead has a documented reason and you have already photographed and metered the assembly. The first four hours belong to facts that disappear once extraction and demo start.
Hours 4–24 — Scope discipline under surge volume
Decision point: Write what you measured, or wait.
Surge tempts phone-photo scopes. Resist that. Price rooms, slopes, openings, and wet assemblies you stood in front of. Split wind-path notes from water-path notes. Do not fold a roof, a pack-out, or a category call into a line item from a doorbell video.
Write Xactimate line-item justification notes while the facts are fresh. Each contested line needs location, quantity basis, condition observed, and why the action is remove/replace or clean/dry — not adjectives from memory later. F9 notes on site beat a clever email next week.
Say what is in today’s estimate and what is flagged for later. List known unknowns: cavities not opened, finishes not lifted, attic or crawl not accessed, roof not walked in daylight. Flag what must move now for mitigation. Document what production will confirm after dry-in and monitoring.
Decision point: Communicate now, or the file orphans.
Cadence in the first day:
- GM / owner: tickets opened, deferred, or declined — and any job that burns cash or mutual-aid capacity if accepted.
- Mitigation lead: source, category/class rationale as written, moisture map status, what must not be demolished until photographed, what already changed after your walk.
- Adjuster: cause narrative, dry-in proof if any, category/class with rationale, moisture map, photo set. Offer a phone window only after missing docs are in the thread. Storm desks are drowning; the easy file gets attention.
- Property owner / insured: arrival window kept or missed, what was documented, what is wet, dry-in status, next on-site time. One voice when you can. Three people bouncing the customer burns trust fast.
Handoff to production is not “they’ll figure it out.” Leave a named file owner, authorization status, open questions, and the photo/moisture package where the crew can find them.
Hours 24–72 — Desk-review file and honest supplements
Decision point: Supplement now versus document for later.
Mitigation has moved the scene. Revisit with a purpose: confirm readings, photograph post-extraction conditions, close known-unknowns, or write a supplement while the change is still visible. Do not rewrite the sketch from memory because the drywall is gone.
Flag now: active leaks still admitting weather, category changes supported by new facts, additional wet rooms after contents moved, structural or safety items that stop drying. Document for later: matching, code items under debate, full roof pending test squares and daylight slopes, contents without inventory, rebuild assemblies still drying.
Documentation that survives desk review is boring on purpose: date/time of loss vs discovery vs arrival; source and peril split; before/during photos; moisture map with unaffected references; equipment tied to readings when you speak to drying days; authorization and who walked the site. Build the file so an adjuster who never walked the site can reconstruct cause and sequence without a phone call.
Handoff by hour 72: mitigation authorized and running; estimate version labeled; supplement log started; open questions owned by a name; photo and moisture package complete enough that a new tech does not reinvent the loss.
On the spot vs escalate
Decide on the spot when you have eyes on the loss and a clear authorization path: preliminary category/class with written rationale, rooms in today’s mitigation scope, site safe to enter, what to photograph before demo, and which known unknowns stay off the first estimate.
Escalate to the GM / owner when intake would break staffing, cash, or a key account promise; when mutual aid or a specialty trade is the only safe path; or when the customer demands a coverage promise you cannot make. Escalate to the mitigation lead before demo that destroys uncaptured evidence. Escalate to the adjuster — docs first — when scope is blocked.
You can write the sketch. You cannot spend the company.
Common failure modes
These cost money or lose the account:
- Scoping after mitigation. Estimate from post-demo rooms with no as-found photo set.
- Thin photo sets. Wet floors without the opening, water line, or elevation that explains entry.
- Notes from memory days later. Line-item justifications invented after the board moved on. Fresh F9 notes are part of the inspection, not homework.
- One blended storm file. Wind and water mixed so neither peril has a clean cause path.
- Phone-photo pricing under surge. Full roofs, pack-outs, and category calls from a text thread. Measure or wait.
- Silent handoff. Production arrives without the moisture map, authorization status, or known-unknowns list.
Questions
What does the estimator own in the first 24–72 hours that the mitigation lead does not? Triage order, the as-found photo and moisture record, preliminary scope with justification notes, and the communication pulse to the GM, adjuster, and owner. Mitigation runs water and dry-in. You run the file that explains why that work exists.
Which losses should be scoped first in a surge? Active intrusion with authorization and safe access; commercial doors you already serve; occupied residential where extraction can start. Vacant, blocked, or mystery-approver files wait. First caller is not triage.
What must be captured before mitigation changes the scene? Elevations and openings, point of entry, water or debris lines, contents in place, room-by-room moisture readings, and a written source identification. Demo without that package is how supplements die.
How do you keep Xactimate notes defensible under volume? Write line-item justification on site: location, quantity basis, observed condition, action. Flag known unknowns instead of guessing. Do not rebuild the narrative from memory after demo.
What do you tell the adjuster on day one? Cause narrative, peril split, dry-in proof if any, category/class with rationale, moisture map, and the photo set. Short and complete. Phone call after the docs are in the thread — not instead of them.
When do you escalate instead of deciding on the spot? When the next yes spends cash or mutual aid the GM owns, when demo would destroy uncaptured evidence, when the customer wants a coverage call, or when safety says stay outside. Write what you saw. Escalate what can break the company.