Guides
Water restoration software requirements and the KPIs to track
Eight requirements for water restoration software, nine KPIs with formulas and triggers, field capture, data security, recordkeeping and a step by step rollout.
What to take away
- The system of record in this trade is the job filephotographs, moisture readings, equipment placement and the completion record. Choose software that protects that first.
- Field capture matters more than reporting. A tool that makes a technician record readings on site beats a tool with better dashboards.
- Pick a small set of numbers that change a decision, and produce them the same way every month.
- You are holding customers' addresses, photographs of their homes and claim details. That makes data security part of the job, not an information technology hobby.
- Export your data before you need to. A system you cannot leave is a system that owns your history.
Product choices depend on your size, service mix and payer. No product is named or recommended here, and security and tax questions belong with qualified advisers.
What the software has to do
Strip the feature lists away and a restoration company needs eight things.
Eight software requirements
- Capture readings, photos, notes in the field
- Complete job file per loss, retrievable
- Schedule monitoring visits separately
- Track equipment placement and dates
- Produce payer-accepted estimates
- Track receivables by payer age
- Record job cost against the job
- Export readable without the vendor
- Capture in the field: readings, photographs and notes, entered on site by the person who took them.
- Hold a complete job file per loss, retrievable years later by address or claim.
- Schedule monitoring visits, which is a different problem from scheduling new jobs.
- Track equipmentwhat is placed where, on which job, from which date.
- Produce an estimate or scope in the format your payers accept.
- Track receivables by payer, with the age of each invoice visible.
- Record job costlabor hours, equipment days, materials and disposal, against the job.
- Export everything in a form you can read without the vendor.
A tool that does six of these well and forces a spreadsheet for the other two is usually better than one that does all eight badly. Decide which two you can live with before you look at anything.
Field capture is the whole game
The most common failure with restoration software is not the software. It is a technician standing in a basement with a phone, a meter and wet hands, who writes readings on a scrap of paper and enters them from memory that evening.
Memory produces round numbers, plausible trends and no anomalies. That is the exact opposite of what a moisture log is for.
So test any candidate the way it will actually be used: on a phone, with gloves on, in poor light, with no signal. If it cannot capture a reading offline and sync later, it does not work in a crawlspace.
The numbers worth producing
Keep the set small. Each of these changes a decision.
Nine restoration KPIs
Measure
- Calls answered live
- Answering arrangements
- Call to arrival time
- Dispatch and staffing
- Open jobs per technician
- Hiring or narrower area
- Average days to dry
- Training and equipment
- Complete reading logs
- Supervision and process
- Equipment days per job
- Placement discipline
- Scope reduction at review
- Documentation training
- Days to collect by payer
- Invoicing and follow-up
Trigger
- Calls answered live
- Call to arrival time
- Open jobs per technician
- Average days to dry
- Complete reading logs
- Equipment days per job
- Scope reduction at review
- Days to collect by payer
| Measure | How it is calculated | What it tells you | What it should trigger |
|---|---|---|---|
| Calls answered live | Inbound calls answered by a person, divided by inbound calls | Whether you are losing work before it starts | Answering arrangements |
| Call to arrival time | Median hours from the call to a technician starting work | Whether you keep the promise you sell | Dispatch and staffing |
| Open jobs per technician | Drying jobs with equipment placed, divided by field technicians | Whether monitoring visits are being squeezed | Hiring, or narrowing the service area |
| Average days to dry, by job type | Days from equipment placement to the dry standard being met | Whether drying plans are working | Training and equipment |
| Complete reading logs, as a proportion | Jobs where every marked point was read on every day equipment was placed, divided by jobs | Whether the file will survive review | Supervision and process |
| Equipment days per job | Unit days consumed per completed job, by type | Whether capacity is tied up unnecessarily | Placement discipline |
| Scope reduction at review | Value invoiced against value approved, on insurance work | Whether documentation is holding | Documentation training |
| Days to collect, by payer | Median days from invoice to money received, split by payer type | Whether cash will arrive in time | Invoicing and follow-up |
| Callback rate with causes | Jobs requiring a return for a drying-related reason, with the cause recorded | Whether the work is actually finished | Reinspection and retraining |
Nine numbers. Produce them monthly, define each formula once, and compare against your own previous quarter rather than any published figure.
All nine come out of the job file, the phone log and the accounts.
Each measure should name the action it triggers. If it names none, it does not belong on the list.
Definitions drift, and drift is what makes a small company stop trusting its own numbers. Write the formula and the source once and leave them alone for the year. Where a number is unavailable, leave the space blank rather than estimating: a blank is honest, and an estimate becomes a fact by the third month.
Two of the nine carry more weight than the rest combined: open jobs per technician and days to collect by payer. Every open job takes a monitoring visit each day, so the first caps capacity long before revenue does. The second decides whether payroll is comfortable.
Compare like with like. A sewage job and an appliance leak are not the same measurement. On callbacks, the recorded cause matters more than the rate.
Equipment days per job rising without a change in job mix means placement plans are not being adjusted.
Security, because of what you hold
A restoration company holds addresses, photographs of the inside of people's homes, claim references and sometimes payment details. That is a meaningful amount of personal information for a small business.
Security minimum for restoration
- Individual accounts, not shared login
- Multi-factor authentication on email
- MFA on the job system
- Access removed the day someone leaves
- Backups you have restored from once
- Rule for what may be photographed
- Rule for where photos live
The National Institute of Standards and Technology: NIST Small Business Quick-Start Guides set out what a small organization should have in place without assuming a technical department. The Cybersecurity and Infrastructure Security Agency: Cyber Guidance for Small Businesses material covers the same ground from the operational side.
The practical minimum for this trade is individual accounts rather than a shared login, multi-factor authentication on email and the job system, and access removed the day someone leaves.
Backups you restored from once, and a rule for what may be photographed and where those photos live.
Technician phones are the weak point, since they carry the job photographs.
Recordkeeping underneath the software
Software is a convenience laid over an obligation. What has to exist is a record of income and expenses supported by documents, which is the expectation described in the Internal Revenue Service: What kind of records should I keep? guidance.
Recordkeeping obligations
- Record income and expenses with documents
- Job cost recorded against the job
- Decide retention deliberately
- Record what was found and handled
- Keep file readable for retention period
Two consequences. Job cost has to be recorded against the job, not merely in a bank feed, or you will never know which service line earns. And retention has to be decided deliberately, since a job file may matter years after completion when a property is sold or a growth complaint appears.
The technical side of that file has its own requirements. The U.S. Environmental Protection Agency: Flood Cleanup to Protect Indoor Air and Your Health guidance describes the conditions and hazards a job may involve.
A file that does not record what was found and how it was handled is thin exactly where it may later be tested.
Choosing without being sold to
Write your eight requirements first, then look at products. Score each against your own list rather than against the demonstration. Run a trial on real jobs with real technicians, not on sample data, and include a night call.
Vendor questions before buying
What does the export contain?
proceed to trial
vague answer is the answer
Ask three questions of every vendor: what does the export contain, who can see our data, and what happens to the job files if we leave. Vague answers to any of the three are the answer.
Connecting the numbers to the business
Measures matter only when acted on: days to dry depend on equipment sizing and crew competency, while scope reduction depends on documentation and service quality.
Call answer rate depends on presence and availability, which no advertising fixes; days to collect depend on billing terms and cash. What you may record and retain falls under compliance duties and privacy obligations.
Assign each measure to one person and review them together once a month, in the same order, in half an hour. Hold that review on the same day each month. Consistency beats sophistication.
Rolling a system out without losing a month
Most failed software rollouts in small companies fail the same way: everything changes at once, in a busy month, with no fallback, and within three weeks half the crew is back on paper.
Run it in four steps instead.
Start with one crew and one job type, usually residential clean-water losses, and keep the old method running alongside for those jobs only. Duplication for a fortnight is cheap; a month of unreliable records is not.
Then fix what that crew reports before widening it. The complaints will be specific and mostly about field capture: too many taps to record a reading, a photograph that will not attach, a form that requires signal. Those are the things that decide adoption, and they are worth resolving before anyone else sees the system.
Then widen by job type rather than by crew, so the awkward cases arrive with people who already know the tool. Contaminated jobs, commercial jobs and contents work each surface a different gap.
Finally, decide what happens to history. Either migrate it deliberately or keep the old system readable for the retention period, and write down which. The worst outcome is a job file that exists in neither place because everybody assumed the other one had it.
Budget training hours honestly, and train against your own written procedures rather than the vendor's demonstration. The tool should follow how you already document a job, not replace the decision about how to document one.
Common questions
Do we need dedicated restoration software, or will general tools do?
A small company can run on general tools plus a disciplined file structure for a while. The point at which dedicated software pays is usually when monitoring visits and equipment tracking stop fitting in a spreadsheet, which is a job-count question rather than a revenue one.
How many measures should a small company track?
Fewer than ten, and the same ten every month. A dashboard nobody reads is worse than three numbers somebody acts on.
What is the most common data mistake in this trade?
Job photographs living only on technicians' personal phones. They are the most valuable evidence the company holds and the least controlled.
Should we let a vendor host everything?
Usually yes, and on the condition that you can export it. Test the export in the first month rather than assuming it works.
