The Water-Damage Dispatch Playbook: From First Ring to Field Handoff

The call comes in at 6:52 on a Tuesday morning. The woman on the line says her sump pump quit overnight and there’s water in the finished basement. Whoever answers scribbles the address on the back of a supply invoice, hangs up, and yells across the shop for somebody to head that way. By 9:00 the crew is standing in the basement, and nobody can answer three basic questions: when did it start, is the water still moving, and did anyone tell the caller’s husband — who mentioned something about the panel — that the breaker was off. Every one of those answers existed at 6:53 a.m. The record didn’t.

That gap is what this article fixes. Not with software and not with slogans, but with a short written procedure your office person, your spouse, or your answering service can run the same way every single time.

What this playbook is

A dispatch playbook is a written, repeatable procedure for taking a water-damage call, recording it in a standard format, flagging anything the caller reports about safety, and handing it to the field with one named person accountable for the next step. It has four moving parts: a minimum record, a flag list, an ownership rule, and a response commitment. Everything else — your forms, your software, your after-hours coverage — hangs off those four.

One thing it is not: a diagnostic protocol. Professional water-damage restoration is a defined field with a recognized standard, and it depends on trained people making judgments on site. ANSI/IICRC S500 exists precisely because that field judgment matters. Your dispatch procedure exists to move information from the phone to the people qualified to act on it — not to replace the site visit.

The minimum record

Every water-damage inquiry gets one record. Not a sticky note, not a text thread, not “I’ll remember.” One record, in one place, with the same fields every time. If your record is missing any of these, you will eat the cost eventually in drive time, callbacks, or a job you can’t reconstruct a week later.

Copy this list into your intake form or build it directly with the Water Loss Intake Builder. Thirteen required fields, three optional:

• Date and time of call — actual timestamp, not “this morning.”
• Caller name and direct callback number — a number that rings a person, not a main line.
• Property address — confirmed read-back to the caller.
• Caller’s relationship to the property — owner, tenant, property manager, family member, other.
• What happened, in the caller’s words — verbatim or near-verbatim, in quotes.
• When the event started or when it was noticed — as the caller states it.
• Is water still active — running, leaking, or stopped, per the caller.
• Areas the caller names as affected — room by room.
• Safety flags reported — see the flag list below; record them even if they seem minor.
• Utilities status as the caller describes it — what they say is on, off, or unknown.
• Access notes — occupancy, pets, gate codes, lockboxes, who will be present.
• Insurance status the caller reports — claim opened, not opened, or unknown.
• Referral source — so you know which marketing line actually produced the call.
• Dispatcher name — whoever took the record.
• Handoff time and recipient — when it moved to the field and to whom.
• Disposition — scheduled, declined, referred out, or still open.

If a caller can’t or won’t answer a field, the entry is unknown, never blank. A blank field and an unknown field look identical on a form but mean different things to the crew. “Unknown” tells the technician what to ask at the door. The water-damage lead intake checklist covers the caller-side questions line by line if you want a second list for the phone itself.

Record versus diagnose

This is the line that keeps a dispatch process clean, and it deserves its own section. Two sentences that sound similar are worlds apart on a record:

• Recording: “Caller reports water coming from upstairs bathroom.”
• Diagnosing: “Source is a failed toilet supply line, category 2, affected drywall to 24 inches.”

The first sentence is true no matter who says it, because it attributes the statement to the person who made it. The second is a conclusion that only a qualified person on site can reach. When the dispatcher writes conclusions instead of statements, the crew inherits assumptions dressed up as findings — and they stop checking, because the record sounds authoritative.

So the rule for the office is simple: every condition described on the phone is written as caller reports X. Every condition confirmed in the field is written by the person who confirmed it, on the field record, with whatever documentation their training calls for. The dispatch record and the field record stay separate documents that link to each other. Nothing gets edited in the dispatch record after the fact to match what the crew found — the difference between the two is itself useful information, and it protects everyone if a job is ever questioned.

That same boundary applies to your language on the phone. When a caller asks “is this mold?” or “is it safe to be down there?”, the dispatcher’s job is to note the concern, route it to a qualified person, and decline to make the call from a kitchen table ten miles away. This is not a dodge. It is the same reason OSHA’s emergency preparedness publications treat recovery work as work with real hazards that requires applicable safety practices: conditions on site, not descriptions over the phone, are what get assessed. The EPA’s mold and moisture resources make the related point that controlling moisture is what governs mold growth — which is a reason to move promptly and document carefully, not a script for the person answering the phone.

Caller-reported safety flags

A safety flag is anything the caller mentions that could change how a crew approaches the property. The dispatcher does not evaluate flags. The dispatcher records them, reads them back, and makes sure a named person sees them before anyone rolls. Here is the standard flag list — keep it visible at the desk:

• Caller reports any electrical concern: outlets under water, panel in the affected area, sparking, breaker behavior.
• Caller reports sewage, a strong waste odor, or water from a drain backup.
• Caller reports a gas smell or any heating/appliance concern.
• Caller reports ceiling sagging, bulging, or structural movement.
• Caller reports water still running and unable to shut it off.
• Caller reports occupants with access or health needs: limited mobility, infants, elderly residents, medical equipment in the home.
• Caller reports a confined space concern: crawlspaces, window wells, anything a person would enter.
• Caller asks a safety question the dispatcher cannot answer.

Every flag gets a one-line record: what was reported, who reported it, who it was routed to, and when. The disposition of a flag — how the crew handles it on site — belongs to the people qualified to make that call. Your job in dispatch is to guarantee the information arrives before the truck, not after.

Who owns each call

Every record carries exactly one owner’s name from the moment it is created until it reaches a disposition. Not “the office” and not “whoever gets to it” — a person. In a two-person shop the owner is the owner; in a five-person shop it’s a dispatcher or office manager with a named backup for sick days and vacations. The ownership rule is what keeps a 6:52 a.m. scribble from becoming a 9:00 a.m. mystery.

Three ownership decisions to make once, in writing:

1. Who takes records during business hours, and who takes them when that person is on another line. A missed call is an uncreated record; decide now whether the second call rolls to a cell, an answering service, or voicemail with a fixed callback window.
2. Who reviews safety flags. One name. The reviewer confirms they saw the flag before the crew departs — a ten-second acknowledgement, noted on the record.
3. Who closes the loop. A record without a disposition is an open liability. The owner of the record either gets it to scheduled, declined, or referred, or hands it to someone who will — and writes the handoff time on the record.

Response commitments you can keep

A response commitment is a time-bound promise attached to the record: how fast you acknowledge, and when you’ll be there or follow up. Set your own numbers based on your staffing and coverage area — there is no universal figure, and promising someone else’s number is how small shops get reputations for no-shows.

A commitment has three parts:

• Acknowledgment: a human callback within a stated window during business hours, or a stated window after hours.
• Arrival or follow-up window: a range you give the caller, wide enough that traffic and a prior job don’t break it.
• Escalation: what happens when the window is at risk — who calls the caller, and how early.

Write the commitment into the record when you make it: “Callback promised by 7:15; arrival window offered 9:00–10:00.” Then your weekly audit can measure promises against reality instead of guessing. If you want to see how your own response times affect your pipeline, the Lead Response Opportunity Calculator lets you run your actual numbers rather than somebody’s industry claim.

A worked handoff example

Here is the Tuesday morning call run the way this article describes. Names and numbers are an illustrative example only — not a benchmark for what your times should look like.

6:52 a.m. — Call answered by the office manager. She opens a record and works the field list. The caller, Ms. Alvarez, reports her sump pump “wasn’t running when I got up” and there is “an inch or so” of water in the finished basement. She says her husband “messed with the breaker before he left for work.” The office manager writes it as caller reports electrical panel interaction; status unknown — that is a safety flag, routed immediately to the owner, who acknowledges it at 6:58.

7:04 a.m. — Callback made, arrival window offered: 8:30–9:30. Handoff written on the record: 7:04, dispatched to lead tech R. Osei. Crew rolls at 7:35.

The table below shows the same call as it moves from phone to field. Note that the two columns never merge:

Notice what the dispatch record did not contain: a water category, a source conclusion, a drywall measurement, or an opinion on the panel. The caller’s inch of water and the technician’s findings are both true records of different moments, and the difference between them is exactly the information a trained professional uses on site.

The completeness check

Every record gets scored at handoff with a completeness check. The formula in words: divide the number of required fields you filled by the total number of required fields, then multiply by 100. With thirteen required fields, a fully completed record scores 100.

In the example above, the record at 7:04 had twelve of thirteen required fields complete. Utilities status was unknown, which counts as a recorded answer; insurance status was blank because nobody had asked. So: 12 ÷ 13 = 0.923, and 0.923 × 100 = 92.3%. Those are example numbers, not a target. What matters is that the missing item was visible before the crew arrived, the insurance question got asked on the callback, and the score at final disposition was 13 of 13. The check exists to catch holes while you can still fix them by phone.

The weekly record audit

Once a week, same day, twenty minutes. Pull every water-damage record from the prior week — including the ones that turned into nothing — and run this checklist:

• Count the records. Does the count match every water-damage inquiry anyone remembers? If a call lived only in someone’s memory, find out where the process dropped it.
• Score each record for completeness: required fields filled ÷ required fields total × 100. Log the number per record.
• Check every safety flag has four lines: what was reported, who reported it, who it was routed to, and a reviewer acknowledgement before departure.
• Check every record has a handoff timestamp and one named owner.
• Check every record reached a disposition: scheduled, declined, or referred.
• Compare promised windows to actual times. Where did you miss, and was it a staffing problem or a promise problem?
• Spot-check one record against the call or note that created it. Read-back accuracy is the whole system.
• Write one line per miss and one proposed fix. Two misses three weeks running is a process change, not a coincidence.

Feed the patterns into your measurements, not your memory. The small-shop restoration KPI guide explains how to track a handful of numbers like these without building a dashboard you’ll abandon by March.

Questions owners ask

My spouse answers the phone between jobs. Is this realistic for a two-person shop?

It is actually easiest at that size. One person takes the record, the other is the field owner, and the flag review happens on the porch before entry. Print the field list and the flag list and tape them inside the cabinet where the phone lives.

What if the caller insists on a diagnosis over the phone?

“I can’t tell you what’s happening from here, but I can tell you when someone will be there.” Record their description, give them your acknowledgment window, and move on. Callers mostly want to know a competent person is coming; the ones who want a phone diagnosis are the ones a site visit will serve anyway.

Do I need software to run this?

No. You need one place records live and one format they live in. A shared document with the sixteen fields above beats a stack of sticky notes and a team chat. Software helps when volume grows, but the discipline comes first or the software just makes your mess faster.

How do I handle after-hours calls?

Decide once: either an answering service takes the record on your form, or voicemail states the callback window your team can honor. Whatever you choose, the record still gets created with a timestamp and an owner before the truck moves. Speed does not rescue an incomplete handoff.

Sources and operating boundaries

Primary sources referenced in this article:

• ANSI/IICRC S500 overview — used only to establish that professional water-damage restoration has a recognized standard and requires trained field judgment.
• OSHA emergency preparedness and response publications — used for the broad principle that emergency and recovery work can involve worker hazards and should follow applicable safety practices.
• U.S. EPA mold and moisture resources — used only for the general relationship between moisture control and mold. This article does not provide a mold-remediation procedure.

What this article does not replace: it is not a technical restoration protocol, a safety clearance procedure, an insurance or accounting policy, or legal advice. Technical determinations, hazard assessments, and clearance decisions belong to trained professionals working on site under applicable standards and regulations. WaterProStack is an operations resource for contractors; it is not a restoration company, an insurer, or an emergency service. If a caller describes an immediate danger, direct them to the appropriate emergency services for your area.