How to Document a Water Damage Inspection and Export an ESX File for Xactimate®

Restoration

5 min read

A water damage inspection creates a lot of information.

Which rooms were affected? Where did the water come from? Did it reach the adjacent bedroom? What did the bathroom look like before mitigation? And does the estimator have enough information to build the scope without calling the technician?

The easiest way to answer those questions isn't to sketch first and document later. It's to do both while walking the property.

By building the floor plan as you inspect each room and attaching the relevant photos and videos along the way, you leave the site with a water damage documentation record that shows not only what happened, but where it happened.

1. Document the Entire Property, Not Just the Damage

When you arrive at a water loss, it's tempting to head straight for the wet room.

But unaffected areas matter too.

In the example inspection, the technician starts with the kitchen, then documents the connected living and dining area to determine whether the floor was affected. The hallway and bedrooms are also inspected, even when no obvious damage is found.

That creates a baseline for the loss.

Instead of a job file that only says, "Here's the damage", you have a floor plan showing where the crew looked, what was affected, and what appeared unaffected during the inspection.

That context can become important later when questions arise about the extent of the original loss.

2. Build the Floor Plan as You Inspect

The floor plan shouldn't be another task waiting for the technician after the walkthrough.

Build it while you're already moving through the property.

Scan each room as you inspect it, including smaller spaces such as closets and utility areas. In the transcript, the technician works through the kitchen, living and dining area, hallway, bathroom, bedrooms, closet, and laundry room before saving the completed scan.

That gives the office spatial context that a folder of photos can't provide.

Instead of asking which bathroom a photo came from or whether the laundry room shared a wall with another affected area, the project itself provides the answer.

3. Identify the Source and Extent of the Water Damage

Once you reach the affected area, document what the technician can actually observe.

In the bathroom example, the water is identified as coming from the toilet, with visible mold growth near the tub. The inspection then continues into adjoining rooms to determine whether they were also affected.

Later, the laundry room shows another visible area of water damage associated with the washing machine.

This is where combining the sketch with the inspection becomes valuable.

You're not just recording individual damage photos. You're placing the observed conditions inside the property's actual layout.

4. Attach Visual Evidence to the Rooms Where It Belongs

Photos are much easier to understand when they have context.

During the walkthrough, photos are captured when damage is identified, including additional images of the visible mold growth near the tub. Once the property scan is complete, the project retains the photos and videos captured throughout the rooms.

That reduces one of the biggest headaches in restoration documentation: figuring out what a photo shows after everyone has left the property.

The technician already knows. The job record should preserve that knowledge for the estimator, project manager, reconstruction team, or anyone else who touches the project next.

5. Add Context Before the Details Get Forgotten

A photo can show damage without explaining why it matters.

Annotations help close that gap.

After the walkthrough, relevant details can be marked directly in the visual documentation. The transcript demonstrates indicating the water-affected area while also blurring information that shouldn't appear in the shared documentation.

This is a small step with a big payoff.

Instead of expecting someone in the office to interpret every image, the technician can point out the important condition while the inspection is still fresh.

And if a label or other sensitive information appears in the documentation, it can be redacted before the file moves further through the workflow.

6. Create One Field Record for the Estimator

The purpose of good restoration documentation isn't simply to prove that technicians took photos.

It's to give the next person enough information to move the job forward.

When the floor plan, room conditions, photos, videos, annotations, and affected areas are captured during the same inspection, the estimator receives a much clearer starting point.

That means fewer questions like:

"Which wall was that?"
"Was the bedroom affected?"
"Where was the washing machine relative to the damage?"

The field crew already answered those questions while standing inside the property. The documentation makes sure those answers don't disappear when they leave.

7. Carry the Field Sketch Into the Estimating Workflow

Once the property has been scanned and documented, that information shouldn't have to be recreated from scratch.

In the demonstrated workflow, the completed sketch can be exported to Xactimate® (as an ESX file) after the field documentation is finished.

That's an important distinction.

The field documentation isn't trying to replace the estimating workflow. It's giving that workflow a better starting point.

The technician captures the property once. The estimator gets a sketch and visual context built from what the crew actually saw. And the company reduces the amount of information that has to be manually reconstructed between the field and office.

Capture the Loss Once and Keep It Moving

The best water damage documentation workflow doesn't ask technicians to document the same job three different ways.

Inspect the property. Build the floor plan as you move. Record affected and unaffected rooms. Photograph the damage where you find it. Add the context the office will need. Then carry that field record into the next stage of the job.

The result isn't just a better sketch or a better photo report.

It's a clearer record of the loss, built by the people who actually saw it, while the evidence was still in front of them.

Sketch it once. Document it at the source. Give the rest of the team something they can actually work from.

READ MORE: Before You Choose a Sketching Solution, Ask Yourself This