Back to Field Guides

How to Build a Restoration Report for an Insurance Carrier

Field Guide

A restoration report should let a carrier or adjuster answer four questions: what happened, what your crew observed, what work was completed, and where the supporting record is.

If the reviewer has to call to ask which room a photo came from, when a reading was taken, or why an item appears in the estimate, the report is missing context. Make each statement easy to trace back to the relevant photo, note, reading, measurement, form, or work record.

Submission requirements vary by claim and program. Follow the recipient’s instructions and the standards, contracts, and company procedures that control the job. The structure below is a practical starting point, not a universal carrier template.

Before you start

Confirm what the recipient wants before building the report

Check the submission instructions before anyone starts arranging photos. This keeps the team from completing the wrong report type, combining documents that should be separate, or sending the package through the wrong channel.

Confirm:

  • Claim or assignment number
  • Insured name and loss address
  • Assigned adjuster or program contact
  • Required portal, email address, or file format
  • File-naming, file-size, and document-separation rules
  • Forms or supporting documents requested for the claim
  • Whether the recipient wants an initial, progress, final, or supplemental report

The report type changes what the reviewer needs to see first:

Report type and what to lead with
Report typeLead with
InitialArrival condition, affected areas, initial evidence, work completed, and open questions
ProgressChanges since the prior report, new records, work or equipment changes, and current status
FinalCompleted visit timeline, final recorded condition, closeout actions, outstanding items, and completion documents
SupplementThe new fact, scope change, or requested item; the earlier submission it affects; and the record supporting the update

If the recipient requests another claim form or document, flag it and follow the instructions for that item. Do not assume the contractor’s report replaces it.

Opening summary

Put the job identity and current status on the first page

Use the first page to identify the file, define the period the report covers, and show what remains open. This gives the reviewer a map before the supporting detail begins.

Include:

  • Restoration company and report author
  • Insured name, loss address, claim number, and adjuster
  • Date of loss, inspection dates, and report date
  • Report type, status, and version
  • Short loss description
  • Affected areas
  • Work period covered by the report
  • Current job status and open items
  • The review, decision, or next action requested from the recipient

Separate reported information from direct observations. Write “the occupant reported” when the statement came from the customer. Write “the technician observed” when the crew saw or measured it. If the cause has not been established, do not turn an assumption into a finding.

A compact opening summary could read:

Hypothetical example: The occupant reported a supply-line release in the kitchen on July 18. During the initial visit, the technician documented visible water impact at the kitchen base cabinets and the adjacent hallway. This report covers the initial work and the monitoring visits listed in the timeline. The file remains open pending the final visit and completion documents.

The summary gives the reviewer a map of the file. The sections that follow provide the evidence.

Area blocks

Build one evidence block for each affected area

Organize the report body by room or clearly named area. Use the same area name in the floor plan, photo captions, readings, work notes, estimate, and attachments.

Each area block should answer:

  1. What condition did the crew observe?
  2. Where exactly was it located?
  3. Which records support the entry?
  4. What work did the crew complete?
  5. What changed or remains open?

Here is one hypothetical area block:

Hypothetical kitchen area block
FieldKitchen entry
AreaKitchen, sink wall
Observed conditionVisible water impact at the cabinet toe-kick and adjacent lower wall area
Supporting recordPhotos K-01 through K-06, kitchen sketch, and initial-visit readings
Work recordedInitial work log records extraction in the kitchen at 10:40 a.m. by Technician A; photos K-07 through K-09 show the area after the visit
Follow-upJuly 19 entry records the next observations at the same locations, current status, and planned next check

This format keeps the condition, evidence, work, and follow-up tied to one place. It also exposes gaps before submission. If the estimate includes an affected hallway but the report has no hallway block, the mismatch is easy to see.

Traceability

Connect every statement to a specific record

Link each statement in the report to the record that supports it. A large photo appendix or an unlabeled table of readings makes that harder than it needs to be.

Give each selected photo:

  • A stable photo ID
  • Room or area name
  • Capture date or visit
  • A caption stating what the image shows
  • A reference from the relevant area block or work entry

Label readings and measurements with the same care. Include the location, material or surface when relevant, visit date, and the instrument or record associated with the entry. Keep the label consistent anywhere that reading appears.

Use captions to explain the purpose of the record, not to claim more than it shows. “K-04: visible staining at the cabinet toe-kick before extraction” is specific. “K-04: proof of covered water damage” makes a coverage conclusion the photo cannot establish.

Timeline

Show the job in visit order

Use a timeline when the report covers more than one visit. Each entry should show what the crew found, what they did, which record supports the entry, and what changed next.

For each visit, record:

  • Actual date and time
  • Areas checked
  • Condition found
  • Work or equipment change
  • Supporting photo, reading, note, or form
  • Reason for the change, when it was documented
  • Current status and next action

Do not add a reason from memory during report assembly. If the record shows that equipment moved but does not explain why, state what is known and flag the missing explanation.

The timeline matters most when the estimate or invoice depends on duration, repeat visits, equipment records, or a change in scope. Consistent visit entries let the reviewer follow the sequence without rebuilding it from photo timestamps.

Package assembly

Keep the report, estimate, and attachments synchronized

Use the same room names, dates, measurements, work descriptions, and version numbers across the entire package. The report explains the field record; the estimate or invoice prices the scope. Consistent labels let the reader move between them without translating one document into another.

For an estimate item that may prompt a question, point directly to the relevant report section and record IDs. Attach the applicable floor plan, measurement, log, signed authorization, change order, invoice, or other supporting document.

Keep the report body focused on the loss, affected areas, evidence, work, and current status. Put supporting records behind it in a stable order:

  1. Cover page and job summary
  2. Area index, floor plan, or sketch
  3. Room-by-room evidence blocks
  4. Visit and work timeline
  5. Current status or closeout section
  6. Photo appendix
  7. Readings, drying, or equipment logs
  8. Authorizations, forms, and change records
  9. Estimate, invoice, or supplement
  10. Requested third-party reports

If a portal requires separate uploads, preserve the same job number, area names, document names, and version labels across the files. The parts should still read as one record after they are separated.

Final check

Run the reviewer reconstruction test before sending

Give the completed report to someone who was not on the job. Ask them to reconstruct the file using only what you plan to submit.

Every guess points to a missing label, reference, or explanation. Fix those gaps before export. Page count and visual polish cannot make up for a report the reviewer has to decode.

  • Can they identify the property, claim, report type, work period, and version?
  • Can they explain the recorded condition without guessing at cause or coverage?
  • Can they find the supporting record for each affected area?
  • Can they see what changed between visits?
  • Can they trace a questioned estimate item to a photo, note, measurement, log, form, or authorization?
  • Can they tell what is complete, what remains open, and what the recipient is being asked to review?

Build the report without rebuilding the job

If the office has to pull photos, notes, readings, and signed forms from separate places, it has to reconstruct the job before it can finish the report. Brighthammer Reports builds the PDF from the same job file as those field records.

Restoration Report FAQs