Water Damage Restoration Management
A Water Damage Job Workflow from First Call to Final Invoice
In brief
A water job passes through a dozen hand-offs between the first call and the final invoice. This walk-through lays out each stage, who owns it, what must be captured and where jobs most often stall.
Most water jobs do not go wrong because the drying was done badly. They go wrong in the hand-offs: a call that is not logged, an authorization that is not signed, a reading that is not recorded, a job that is dry but never invoiced.
This post lays out a water damage job workflow as a sequence of stages. For each stage it names who usually owns it, what must be captured before moving on, and where jobs tend to stall. Adjust the names to your shop, but keep the structure. It is the structure that keeps jobs moving.
Why a written workflow matters
When the owner runs every job, the workflow lives in their head. Once there are two or three crews and a PM, people fill gaps differently, and the gaps show up as callbacks, return trips and slow payment.
A written workflow does three things:
- It sets a definition of done for each stage, so a job cannot quietly skip a step.
- It makes ownership visible, so "I thought you had it" stops being an answer.
- It gives new hires a map, which shortens how long it takes them to be useful.
The technical side of drying should follow the current IICRC standard for water damage work and your local requirements. This post is about the operational path around that work.
The stages at a glance
| Stage | Typical owner | Done when |
|---|---|---|
| 1. First call / intake | Office or on-call | Job record created with contact, address, loss details, carrier info |
| 2. Dispatch | Office or dispatcher | Crew assigned, customer told arrival window |
| 3. Arrival and inspection | Crew lead | Initial photos, readings, affected areas noted |
| 4. Authorization | Crew lead | Work authorization signed, scope explained |
| 5. Mitigation setup | Crew lead | Extraction, removals and equipment placement recorded |
| 6. Monitoring | Crew lead or tech | Daily readings, photos and journal entries logged |
| 7. Demobilization | Crew lead | Dry goals met and documented, equipment pulled and counted |
| 8. File review | Project manager | Photos, readings, notes, signatures and timesheets complete |
| 9. Invoicing | Office or accounting | Invoice sent with supporting documentation |
| 10. Hand-off or close | Project manager | Reconstruction handed off or job closed, customer follow-up done |
Stages 1 and 2: first call and dispatch
The first call sets the quality of the entire file. Use the same intake script every time, including after hours.
Capture at intake:
- Caller name, relationship to property, best phone and email
- Property address, access instructions, pets, parking
- Source and time of loss, whether water is still active
- Rooms or areas affected, number of floors
- Whether the caller has contacted their carrier, carrier name and claim number if known
- Whether this came through a TPA or program, and its assignment details
- Any safety concerns the caller mentions, such as power near water or ceiling sagging
Dispatch turns the record into a scheduled visit. Assign the crew, confirm the arrival window with the customer, and make sure the crew lead can see the intake notes on their phone before they leave the shop.
Stages 3 and 4: arrival, inspection and authorization
On arrival, the crew lead documents conditions before touching anything. That record protects the customer, the company and everyone who reviews the file later.
Before work begins:
- Walk the affected areas with the customer.
- Take wide photos of each room, then detail photos of damage and the source.
- Take initial moisture readings and record locations consistently, for example by room and wall.
- Note anything unusual: pre-existing damage, materials of concern, contents at risk.
- Explain the plan in plain words, including what will be removed and why.
- Get the work authorization signed before work starts.
Signing on a phone or tablet beats paper here, because the signed document lands in the job file immediately and nobody has to scan it later.
Stages 5 and 6: mitigation setup and daily monitoring
Mitigation setup
This is where most of the visible work happens, and where documentation most often lags behind the work.
Record, as you go:
- Water extracted and from where
- Materials removed, with photos before and after removal
- Equipment placed, by type and room, with counts
- Any containment or protection set up
- Contents moved, protected or packed out
Daily monitoring
Monitoring visits are short and repetitive, which is exactly why they get skipped or rushed.
A consistent monitoring visit includes:
- Readings at the same locations as the initial set
- Equipment check and any moves or removals recorded
- Photos of progress where it is visible
- A short journal note: what changed, what the plan is for tomorrow
- A quick customer touchpoint, even a two-line update
If the readings are not moving as expected, that note should reach the PM the same day, not at file review.
When readings stall
A lagging area is normal on some jobs. What is not acceptable is finding out about it on day five. Set a simple rule: if an area shows little change between two visits, the tech flags it in the job journal and messages the PM before leaving the site. The PM then decides whether to add or move equipment, open up more material, or look for a hidden source such as a second leak or wet insulation behind a finished wall.
The same rule applies to anything that changes the scope. If the crew finds damage beyond what was authorized, the customer and, where applicable, the carrier or TPA need to hear about it before the extra work is done, not after. Record who was told, when and what they said.
Stages 7 to 10: demobilization, file review, invoicing and close
Demobilization
Pull equipment when the drying goals for the job are met and documented, not when the schedule says it has been three days.
At demo:
- Take and record a final set of readings at the established locations.
- Photograph each room after equipment is removed.
- Count equipment as it is loaded and note anything left on site.
- Have the customer sign a completion or acknowledgment form if your process uses one.
- Tell the customer what comes next, especially if reconstruction is a separate phase.
File review, invoicing and close
This is the stretch where finished jobs sit for days or weeks. A short, owned checklist fixes most of it.
File review checklist:
- Intake details complete, including carrier and claim information
- Signed work authorization attached
- Initial, daily and final readings present and consistent
- Before, during and after photos for every affected area
- Equipment placement and removal recorded
- Journal entries for each visit
- Crew time recorded against the job
- Completion signature, if used
Once the file passes review, invoicing should happen within a set window your shop agrees on, such as two business days. Then either hand off to reconstruction with the full file, or close the job and follow up with the customer.
The close-out call is worth doing even on small jobs. Ask whether everything was left the way the customer expected, remind them what happens next with their carrier if anything, and note any concerns in the file. A two-minute call often heads off the complaint that would otherwise arrive with the invoice.
Keeping the carrier and TPA side in step
Carrier and program communication runs alongside every stage, and it is easy to let it drift. A few habits keep it accurate:
- Log each conversation with an adjuster or program contact in the job journal: date, who, what was discussed, what was agreed.
- Send documentation in the format and on the schedule the carrier or program asks for, rather than in one large batch at the end.
- When a reviewer asks a question, answer from the file, not from memory. If the file cannot answer it, that is a gap to fix in your process.
- Keep the customer informed of what you have sent and when, so they are not caught off guard by a call from their adjuster.
The goal is an accurate, complete record of what was found and what was done. Nothing more, nothing less.
A hypothetical walk-through: a kitchen supply line on a Friday night
Say a homeowner calls at 9:40 on a Friday night. A dishwasher supply line has leaked under the cabinets into the kitchen and the finished basement below.
- Friday 9:45 pm: The on-call tech uses the intake script, creates the job on the mobile app, notes the carrier name and that the water is shut off. The customer is told a crew will arrive within the hour.
- Friday 10:50 pm: The crew lead arrives, photographs the kitchen and basement, takes initial readings, explains the plan and gets the authorization signed on a tablet.
- Friday to Saturday: Extraction, toe-kick removal and drywall cuts in the basement are photographed. Equipment placement is recorded by room.
- Saturday to Tuesday: Daily visits log readings, photos and a one-line plan for the next day. On Monday the PM sees one basement wall lagging and adjusts equipment.
- Wednesday: Final readings are recorded, equipment is pulled and counted, the customer signs the completion form.
- Thursday: The PM runs the file review checklist and finds a missing after-photo for one room. A tech grabs it on the way to another job.
- Friday: The invoice goes out with the documentation attached, and the job is handed to the reconstruction PM with the full history.
Nothing heroic happens. The job just never sits waiting for someone to notice a gap.
Common mistakes in water job workflows
- No single owner. Every job needs one named person accountable for the file.
- Documenting at the end. Photos and readings reconstructed from memory are weaker and slower.
- Inconsistent reading locations. If the locations change daily, the drying story is hard to follow.
- Treating demo as done. The job is done when the file is complete and invoiced.
- Losing the link to reconstruction. If the rebuild crew cannot see the mitigation file, they start from zero.
How RestoreUnited supports this workflow
RestoreUnited's Job Management and Work Orders let you set up stages like the ones above, and Scheduling & Dispatch connects crews to each job. On site, the mobile app handles Photos & Journals and Electronic Signatures, and Time Tracking records labor against the job. When the file is complete, the QuickBooks Integration helps move it toward invoicing. Mitigation Tracking is coming soon.
What to do this week
- Write your stages on one page, with an owner and a "done when" for each.
- Turn your intake questions into a script and give it to everyone who takes after-hours calls.
- Pick three recently closed water jobs and run the file review checklist on them to see where gaps cluster.
- Agree on an invoicing window after file review and put it on the office calendar.
- Name one person to own every open water job by the end of the week.
See it in RestoreUnited: Job Management
RestoreUnited product videoFrequently asked questions
What is the most common place a water job stalls?
In many shops it is the stretch between demobilization and invoicing. The equipment is out and the crew has moved on, but the file is missing a final reading set, a signature or photos, so nobody sends the invoice. A short close-out checklist owned by one person fixes most of it.
Who should own a water job from start to finish?
Name one project owner per job, usually a project manager or senior crew lead, even though many people touch it. That person is responsible for the file being complete and for the next step happening, not for doing every task themselves.
Should mitigation and reconstruction be one job or two?
Many companies track them as linked but separate jobs, because the scope, approvals, crews and billing often differ. What matters most is that the two records point to each other and share the same customer, claim and document history.