Field Documentation

Field Documentation Habits That Speed Up Billing

In brief

Most billing delays start in the field: missing photos, gaps in readings, no equipment removal date, an unsigned completion form. These are the documentation habits crews can build so a job file is ready to invoice the day the work ends.

Ask an office manager why a job has not been invoiced and the answer is rarely "we have not gotten to it." It is usually "we are waiting on something from the field." Final readings are missing. Nobody recorded when the dehumidifiers came out. The photos of the kitchen are there, but nobody can tell which wall they show. The completion form never got signed.

Every one of those gaps is small. Together, they can keep a finished job sitting for weeks while the office chases details from crews who have moved on to five other losses. This guide covers the field habits that close those gaps, so a job file is ready to bill when the work ends.

Why billing stalls

Billing delays usually come from one of three places:

  • Missing information. Something that should have been captured on site was not.
  • Unclear information. It was captured, but nobody can interpret it later: unlabeled photos, readings without locations, notes that say "same as yesterday."
  • Missing approvals. Work was done, but the signature, change order or written approval is not in the file.

The fix in every case is a habit in the field, backed by a simple check before the file leaves the PM's hands. Documentation is about accuracy and completeness. It should show what was found, what was done and why, nothing more and nothing less.

The billing-ready job file

Start by defining what "complete" means. If crews do not know what a finished file looks like, they cannot produce one. Here is a checklist many water mitigation jobs can start from; adjust it for your job types.

  • Signed work authorization
  • Customer, property and carrier or TPA details confirmed
  • Cause of loss described in plain terms
  • Initial photo set: context, damage and source
  • Initial moisture readings with locations
  • Equipment set log: type, unit, location, date
  • Daily monitoring readings with locations, for every visit
  • Equipment changes logged when they happen
  • Notes on any change in scope, with photos and approvals
  • Final readings showing drying goals were reached
  • Equipment removal dates for every unit
  • After photos of every affected area
  • Signed completion or certificate of satisfaction where your process uses one
  • Time entries for every crew member who worked the job

Print it, put it in the mobile app as a job checklist, or both. What matters is that it is the same list every time.

Five field habits that close the gaps

Photo habits that hold up

Photos are the backbone of the file, and they are where most of the confusion lives.

  • Shoot in sequence: wide, medium, close. A wide shot shows the room. A medium shot shows the wall or area. A close shot shows the damage. Without the wide shot, a close-up of wet drywall could be anywhere.
  • Photograph the source. The failed supply line, the roof opening, the overflowing fixture.
  • Capture before, during and after for each area. Including demo, equipment placement and the finished condition.
  • Include a reference. A meter reading in frame, a tape measure, a room label on painter's tape.
  • Label or caption by room. "Kitchen, north wall, behind sink" is useful a month later. "IMG_4471" is not.
  • Upload the same day. Photos that live on a technician's phone for a week are photos that get lost.

Readings that tell a clear story

Moisture readings support the drying timeline. They only help if they are consistent.

  • Use the same points every visit. Mark or describe the reading locations on day one and return to them.
  • Record the location with every reading. Room, wall and approximate position.
  • Note the material. Drywall, subfloor, framing, concrete.
  • Record a dry reference for comparison where your process calls for it.
  • Log environmental readings consistently if your process uses them.
  • Never skip a visit's readings. A gap in the log invites questions about what happened that day.

Follow the current industry standard for drying documentation and your own written procedures. The habit to build is consistency: same points, same order, same level of detail, every visit.

Equipment dates, set and removed

Equipment is one of the most common sources of billing questions, and almost always for the same reason: missing dates.

  • Log each unit when it is set: type, unit number, room, date.
  • Log changes when they happen: moved, added, removed.
  • Log removal on the day it happens, by unit.
  • Do a final count at pickup and compare it to the log.

Signatures and approvals at the right moment

Signatures are easy to get on site and hard to chase later.

  • Work authorization before work starts, signed by someone with authority to approve it.
  • Change approvals when scope changes, before the added work begins.
  • Completion signature at the final walkthrough, while the customer is standing in the finished space.

Electronic signatures on a phone or tablet make this much easier. The habit to build is asking at the moment, not promising to send something later.

Daily notes that someone else can read

A good job journal lets a PM, a billing coordinator or an adjuster understand the job without calling the crew. Each daily note should answer:

  • Who was on site and for how long
  • What was done, by area
  • What was found, especially anything new or unexpected
  • What changed: equipment, scope, schedule
  • What the customer was told
  • What is planned for the next visit

Write in plain language. Avoid "same as yesterday." If nothing changed, say what was checked and that conditions were consistent.

Who documents what, and when

Clear ownership prevents the "I thought you did it" problem.

MomentWhat gets capturedWho owns it
First visitAuthorization, cause of loss, initial photos and readings, equipment set log, room namesCrew lead
Each monitoring visitReadings at the same points, equipment changes, photos, daily noteTechnician on the visit
Scope changePhotos, readings, description, approvalCrew lead, with PM approval
Final visitFinal readings, after photos, equipment removal by unit, completion signatureCrew lead
Before billingChecklist review, gaps sent back to the fieldPM
DailyTime entries for every person on the jobEach crew member

A hypothetical walk-through: the job that sat for two weeks

Picture a residential water mitigation job that wrapped on a Friday. The crew pulled the equipment, the homeowner was happy and everyone moved on. Two weeks later, the job still has not been invoiced.

When the office manager reviews the file, she finds four gaps. There are no final readings for one bedroom. Equipment removal is recorded as a note that says "picked up all units," with no per-unit dates. The after photos cover the kitchen and hallway but not the bedroom. And the completion signature is missing because the homeowner was not home at pickup.

Each gap takes a phone call, a text thread or a return visit. The technician who did the last visit is on a different job and does not remember the bedroom readings. Someone has to go back out.

Now picture the same job with the habits in this guide. The crew lead opens the job checklist at the final visit. The bedroom readings, after photos and per-unit removal are captured before the truck leaves. The homeowner is not home, so the crew lead schedules a time to collect the completion signature and notes it in the journal. The PM reviews the checklist Monday morning, sees one open item and follows up the same day. The file goes to billing early that week.

Same job, same crew. The difference is a checklist and the habit of finishing the file before leaving the site.

Common documentation mistakes

These show up again and again in files that stall:

  • Photos without context. Dozens of close-ups and no wide shots, so nobody can tell where they were taken.
  • Readings that change location. A reading taken in a different spot each visit makes the drying trend impossible to follow.
  • Notes written for the writer. Abbreviations and shorthand that only the technician who wrote them understands.
  • Batch uploads at the end of the week. By then, details are fuzzy and some photos never make it off the phone.
  • Verbal approvals. "The homeowner said it was fine to take out the vanity" is not an approval in the file.
  • Time entered from memory. Hours reconstructed on Friday for the whole week rarely match what happened.

Each of these is a habit problem, not a skill problem. Crews who know what good looks like and have a quick way to capture it on site will usually do it.

Documentation for the reconstruction handoff

When a job moves from mitigation to rebuild, the reconstruction PM inherits the file. Good mitigation documentation makes that handoff much faster. The rebuild team needs to know exactly what was removed, where, and in what condition the structure was left: how many feet of drywall came out of which walls, which cabinets were detached, what flooring was removed and what remains.

A short handoff note in the journal, with links to the relevant photos and the final readings, saves the reconstruction PM a site visit just to figure out the starting point. It also helps the estimator build an accurate reconstruction scope without guessing.

Make it stick

Habits need reinforcement:

  • Review files in the morning meeting. Pick one recent job and walk through its documentation, good and bad.
  • Send gaps back fast. When a PM finds a gap, the fix should happen within a day, while memory is fresh.
  • Recognize good files. Point out crews whose documentation makes the office's job easy.
  • Keep the checklist current. If the office keeps asking for something not on the list, add it.

Where RestoreUnited fits

Documentation is easier when photos, notes, signatures and time all land in the same job record from the field. RestoreUnited's Photos & Journals give each job a photo stream and job journal, Electronic Signatures capture authorizations and completions on site, Time Tracking ties hours to the job, and the mobile app lets technicians do it all from their phones. Mitigation Tracking is coming soon. Custom Reporting can show which jobs are complete and which are waiting on something from the field.

What to do this week

  1. Write your billing-ready checklist for water mitigation jobs, using the list above as a starting point.
  2. Agree on a room-naming habit and a wide-medium-close photo sequence, and share both with every crew.
  3. Add per-unit equipment set and removal dates to your field routine.
  4. Make it a rule that completion signatures are requested at the final walkthrough.
  5. Have each PM review the checklist on every job before it goes to billing.
  6. Pull your three oldest unbilled jobs and list exactly what each one is waiting on.

See it in RestoreUnited: Photos & Journals

RestoreUnited product video

Frequently asked questions

Who is responsible for making a job file billing-ready?

The crew lead owns the field documentation on site, and the PM confirms the file is complete before it goes to billing. Making that ownership explicit is often the single biggest improvement a shop can make.

How many photos are enough?

Enough to show the condition of every affected area before, during and after the work, including context shots that show where each close-up was taken. Volume matters less than coverage and clear labels.

Does better documentation mean jobs get paid faster?

Complete, accurate documentation removes many of the reasons a file gets sent back with questions, which tends to shorten the back-and-forth. It cannot control how a carrier or customer reviews an invoice, and it is never about inflating a claim.

See RestoreUnited run a restoration company

Book a live walkthrough with our team, or choose a plan and get started.