🏠 GEM Resource Hub Β· πŸ“š Library Β· πŸ“˜ About RocketLevel Β· πŸ“˜ Playbooks Β· πŸ—ΊοΈ What's Your Market Worth? Β· πŸ“… Book a Call

Thin files get pulled for review and paid late. Complete, standards-supported documentation, captured the same way on every loss, gets the file paid on the first pass.

A RocketLevel guide for estimators, field crews, project managers, and whoever chases accounts receivable (AR), backed by decades of experience in the trade. This is the GEM home for documentation that gets a file approved and paid. About an 11-minute read.


πŸ“‚ "The work was right, but the file could not prove it"

You dried the structure, you demoed what had to go, you placed the equipment the job called for. Then the file lands on an adjuster's desk, or inside an automated estimate-review tool, and it stalls. The photos are blurry and unlabeled. The drying log has three readings, not daily ones. Half the line items have no note explaining why they are there. The scope is fine, but the evidence behind it is thin, so the file gets routed to manual review and the payment slides weeks to the right.

It is a common and expensive paperwork problem in restoration, and the breakdown almost never starts in Xactimate. It starts in the field, in the first hour of the response, before anyone opens an estimate. By the time the estimator sits down, the evidence is already incomplete.

Carriers and their review tools are looking for the same thing you should want in your own file: a complete, standards-supported record that shows what happened and why each line is justified. Your job is closing the gaps before you submit.

🚦 Why a clean file moves and a thin file stalls

Carriers screen estimates with automated review tools before a human ever looks. Verisk sells one, XactXpert, a rules engine inside Xactimate that alerts in real time when an estimate departs from an organization's guidelines. Those tools flag the same gaps a careful adjuster would: a line item with no supporting photo or note, a water category that does not match the documented conditions, a drying log that skips days, a room in the scope that never appears in a photo. A flagged file goes to manual review, and manual review is where weeks disappear.

The answer is completeness: every line tied to a reading, a photo, or a standard, and no daylight between the estimate, the photos, and the notes.

πŸ“· The photo set that proves a loss

A thin photo set is a common reason a file gets sent back. The standard is wide, medium, and close on everything that matters, captured on site, in the moment, not reconstructed from memory later. A loss that is fully proven in photos covers seven things:

  1. Source of loss. Two or three shots: a close-up of the failed supply line, the appliance, the roof penetration, plus a wider shot that places it in the room. The cause of loss drives coverage, and without a photo of it the carrier has to guess.
  2. Affected materials. Every affected room photographed from opposing corners so the space reads in context, then close on the wet drywall, the cupped flooring, the saturated insulation. This is what ties square footage and material line items to reality.
  3. Moisture readings. Photograph the meter on the material with the reading visible, on affected and unaffected areas, so a reviewer can check each number in the drying log against a photo.
  4. Equipment placed. Show the air movers and dehumidifiers in position. This supports the equipment and monitoring line items that adjusters most often question.
  5. Daily drying progress. Dated photos across the dry-out, not just day one and the final. Progress photos turn a list of readings into a story a reviewer can follow.
  6. Dry-standard comparison. The final readings on affected materials next to the unaffected dry standard, so the file shows the job ended where the standard says it should.