Guides
Water restoration service standards: the eight documents a crew will actually use
A working set of eight one-page water restoration service standards, the four questions each answers, version control rules, and when to review a procedure.
What to take away
- Write standards a wet technician can read on a phone at midnight. Anything longer than a page per procedure will not be read at all.
- Each standard needs four thingswho does it, what triggers it, what good looks like, and what record it leaves.
- Version and date every document. Two conflicting copies of a drying procedure is worse than none.
- Write the standard from what your best crew already does, then fix what is wrong. Standards imported from a manual describe someone else's company.
- Review a standard when it is broken, not on an annual calendar. The breach is the useful signal.
Written procedures do not replace technical judgment or qualified specialists. Conditions in a specific building govern, and this page is about how to write and maintain the documents.
The document set worth having
Most small restoration companies need eight documents and no more.
The Eight Documents
- Emergency call intakecompleted intake sheet
- First visitsigned authorization, condition photographs
- Assessment and drying planmoisture map
- Monitoring visitreading log entry
- Change of scopesigned change authorization
- Completioncompletion record, final readings
- Referral outwritten note of referral
- Complaint intakecomplaint log entry
| Document | Triggered by | Record it leaves |
|---|---|---|
| Emergency call intake | Any inbound loss call | Completed intake sheet |
| First visit and authorization | Arrival on site | Signed authorization, condition photographs |
| Assessment and drying plan | After extraction | Inspection sheet, moisture map, dry standard |
| Monitoring visit | Each day equipment is placed | Reading log entry with adjustments |
| Change of scope | Any change in scope, category or price | Signed change authorization |
| Completion | Dry standard met | Completion record with final readings |
| Referral out | Conditions beyond crew competence | Written note of what was referred and to whom |
| Complaint intake | Any customer complaint | Complaint log entry |
Eight documents, each one page. If a ninth appears, ask which of the eight it should have been part of.
The four questions each standard answers
Write every procedure to answer the same four questions in the same order, so a technician knows where to look.
- Who does it?
- What triggers it?
- What does good look like?
- What record does it leave?
Four Questions Every Standard Answers
- Who does this, and who decides when they cannot
- What starts it, in observable terms
- What good looks like, so two people agree
- What record it leaves, named exactly as the form
That structure is what makes a standard usable while a crew is standing in water. Prose about commitment to excellence is not a standard; it is a poster.
The monitoring visit is the easiest one to try first. A one-page procedure, in outline:
- Who does it
- the technician assigned to that loss.
- What triggers it
- arrival on site on each day equipment is placed.
- What does good look like
- readings at the same marked points, inside the dry standard, with any adjustment made before the technician leaves.
- What record it leaves
- a dated reading log entry with points, values and equipment changes.
That is the whole procedure. One page, read once on site.
Writing from the work, not from a manual
Start by watching your best crew do the job and writing down what they actually do. You will find steps nobody knew were happening and steps everyone assumed were happening.
Then correct it against the technical requirements, not a template. For contamination, the U.S. Environmental Protection Agency: Flood Cleanup to Protect Indoor Air and Your Health guidance describes hazards a procedure must control.
It also gives conditions when the correct step is to stop and refer out. A procedure with no stopping condition is not finished.
Then give it to a technician who was not involved and ask them to follow it literally. Every ambiguity surfaces in ten minutes.
Version control that a small company can actually run
Three rules are enough.
Put a version number and effective date at the top of every document. Keep exactly one current copy in one place, and tell everyone where it is.
When you issue a new version, remove superseded copies from vehicles, folders, and phones. A technician using last year's monitoring procedure follows a rule you already rejected.
Add a fourth if you can: record what changed and why. One line is enough: 04 Mar 2026, monitoring visit v3, added a second reading point at the stair landing after a missed wet wall. Six months later, that line saves an argument about whether a step was dropped deliberately.
Making standards stick
Standards fail for predictable reasons, but one does the most damage: following them takes time the pricing never allowed for.
That point is the important one. If a monitoring procedure takes forty minutes and the schedule assumes twenty, the procedure loses every time. Check the standard against the job schedule and the quality assurance checks before publishing it, and against the water restoration service measures afterwards to see whether it changed anything.
Train against the document rather than around it. New technicians should be assessed on the company's own written standard, which is what the training ladder for new technicians should be built from, rather than on a general course alone.
Standards for the customer-facing side too
Two of the eight documents face outward, and both carry rules beyond your own preferences.
Follow-up contact, including any request for a review, is regulated. The U.S. Federal Trade Commission: Soliciting and Paying for Online Reviews: A Guide for Marketers guidance sets out the line.
Permitted: asking every customer the same way, and asking for a review with no conditions attached. Prohibited: offering a discount or gift for a positive review, filtering out customers likely to leave a bad one, and asking staff or relatives to post reviews themselves.
Record retention underlies everything else. Write down how long you keep a job file, and in what form, per Internal Revenue Service: What kind of records should I keep? guidance and any longer period your state or insurer expects.
Reviewing when it breaks
Annual reviews of documents nobody has read are theatre. Review a standard when something goes wrong: a callback, a complaint, a scope reduction at review, a near miss, or a technician saying the procedure does not fit the work.
Each of those is evidence that either the standard or the operation is wrong. The equipment and setup guide, and the staffing side in the restoration business hiring piece, cover both halves.
The failure sets the review date, not the calendar.
Common questions
How long should a procedure be?
One page. If it needs two, it is probably two procedures, and splitting it usually reveals that the second half belongs to a different role.
Should standards be on paper or on a phone?
Both. Phones fail, get wet and lose signal in crawlspaces, and a laminated card in the vehicle costs almost nothing.
Who owns the documents in a small company?
One named person, usually the owner or the most senior technician. Shared ownership produces multiple current versions, which is the failure mode these documents exist to prevent.
What if a crew consistently ignores a standard?
Assume first that the standard is wrong or the schedule does not allow it, and go and watch the work. Discipline applied to a procedure that cannot be followed in the time available fixes nothing.
