A water-damage intake checklist is a structured set of questions used to record the caller’s location, source status, timeline, affected areas, access, reported safety concerns, and requested next step. Its job is to improve routing and preparation. It is not a remote inspection, a water-category determination, or a declaration that the property is safe.
The intake sequence
- Confirm the service location and a callback path. Record the property ZIP code first so the call can be routed even if it drops. Confirm the caller’s preferred callback method and whether they are the owner, tenant, manager, insurer representative, or another party.
- Ask what the caller can observe. “What are you seeing or hearing right now?” is more useful than asking the caller to select a technical category. Write down their words instead of silently converting them into a diagnosis.
- Record whether the source is stopped. Use “stopped,” “still active,” “intermittent,” or “unknown.” Ask who stopped it and when. Do not assume that visible flow stopping means the underlying source is corrected.
- Build a simple timeline. Capture when the problem was first noticed, when the source may have started if known, and what actions have already occurred. Label uncertain dates as estimates.
- List affected rooms and materials as reported. Note levels, rooms, visible materials, contents, and whether neighboring units may be involved. Avoid promising a drying plan or scope before evaluation.
- Screen for escalation flags. Ask about water near electrical equipment, possible sewage, sagging materials, restricted access, vulnerable occupants, active fire or gas concerns, and other conditions required by your company’s safety program.
- Clarify access and decision authority. Record who can authorize entry, who will be on site, lockbox or gate requirements, pets, parking limits, and any building-management process.
- Ask what outcome the customer expects. Inspection, emergency stabilization, documentation, an estimate, and full restoration are different requests. Restating the requested outcome prevents a mismatched visit.
- Assign a named next action. Every call should end with an owner, action, and time: “Maria will call by 10:15 to confirm whether a visit can be scheduled.” Avoid vague promises such as “someone will get back to you.”
Build a call sheet from this checklist →
Minimum viable field handoff
A useful handoff should fit on one screen. The field team needs the property location, contact, source status, timeline, reported affected areas, escalation flags, access notes, requested outcome, and the exact promise made by dispatch.
| Field | Good entry | Weak entry |
|---|---|---|
| Source status | Caller says supply valve was closed at 8:20 a.m.; no visible flow now | Leak fixed |
| Affected area | Caller sees water in laundry and hallway; lower drywall looks wet | Whole floor damaged |
| Next action | Sam to call by 9:45 a.m. after service-area check | Call soon |
A ten-minute weekly review
- Read five random intake notes without listening to the calls.
- Can another person identify the next action and owner?
- Are observations attributed to the caller, or rewritten as facts?
- Are the same required fields missed repeatedly?
- Did dispatch make promises the field calendar could not support?
Use the misses to revise the form or coaching. Do not add twenty questions because one unusual job occurred; keep a short core and a documented escalation path.
Standards and sources to keep nearby
This operational checklist does not summarize or replace restoration standards. Build technical procedures from the current standards, regulations, manufacturer instructions, insurance requirements, and competent professional guidance applicable to your work.