The pre-submission audit restoration owners are missing
Most restoration claim files leave the office with gaps nobody sees until the carrier reduces the payment. Photos are mislabeled, moisture readings don't line up, line items don't match evidence, and carrier-specific requirements get missed in the rush to submit. On a single file it looks like "a tough adjuster." Across 1–20 locations, it's a quiet, compounding leak in receivables, and exactly what NanoForce's pre-submission audit is built to catch.
By Mark Kurywczak, Founder & CEO, NanoForce Technologies ·
- Most claim files leave the office with documentation gaps the carrier's bill review finds first, before anyone on your team sees them.
- A real pre-submission audit checks the file against known carrier patterns, not a generic completeness checklist.
- The gap usually isn't missing work. It's work that was done but never made it into the file in a form the carrier will accept.
- Catching a documentation gap before submission is materially cheaper than disputing a reduction after the fact.
A true pre-submission audit is not "double-checking the estimate." It's a system that verifies every evidence field, every scope line, and every carrier requirement before the file ever hits the carrier's queue. Most owners don't have that, and the result is predictable: underpaid claims, longer payment cycles, and soft write-offs that never show up as a line item called "leakage."
How does this leak show up in the real world?
- A large water loss file goes in with 300+ photos, but only a fraction are clearly labeled to match the affected rooms and materials.
- Moisture logs are attached, but readings don't match the dry standard or the dates of equipment on site.
- Xactimate line items have weak or missing notes, leaving the carrier room to question scope instead of evidence.
- Carrier-specific documentation (like mold protocols, asbestos clearances, or specialty forms) are partially completed or missing on first submission.
The adjuster doesn't write "your pre-submission audit is weak." They just shave 10–20% off the payment or ask for "clarification" that drags the timeline. Your team calls it a difficult file. Your controller calls it "another reduction." Aggregate this across your locations, and the pattern is clear: too many files going out with evidence and documentation that aren't bulletproof.
What a weak file actually looks like
Take a large water loss with dozens of photos and a full moisture log. Every reading was taken correctly, and every photo was shot at the right moment. The gap isn't the fieldwork, it's the file: the photos got uploaded in whatever order the phone synced them, several are labeled "IMG_4471" instead of "master bath, north wall, day 2," and the moisture log lists dates that don't quite line up with the equipment run log because two different techs entered them into two different places.
None of that is a lie about the loss. It's just a file that makes the adjuster do extra work to connect evidence to scope, and an adjuster who has to do extra work has an easy, defensible reason to knock the payment down instead. The work was real. The file just never proved it in a form the carrier's bill review was looking for.
Xactimate and Encircle weren't built to be full audit engines
Xactimate is great at building estimates, but weak at ensuring every line item is backed by specific, properly labeled evidence. It assumes the user is the auditor. Encircle and similar field tools are strong for capturing photos and readings, but they don't enforce carrier-specific checklists or confirm every required document is in place before submission. NanoForce has profiled documentation requirements and reduction patterns across 215+ carriers, and almost none of that checklist logic lives in Xactimate or Encircle by default. Shared drives and email may hold your documentation, but there's no automated pass that says, "For Carrier A, for Water Loss B, all mandatory evidence is present and matched to scope."
So your tools report "complete file." The carrier sees "incomplete case." That gap is the leak. None of your standard stack is designed to cross-check carrier requirements, evidence, and estimates line by line before the file goes out. Which is why reductions feel random even though they follow predictable patterns.
What to actually check
Pull the last 20 reduced files
Pull the last 20 reduced claim files across all locations, focusing on water and fire losses above $15,000. Bigger files have more room for documentation gaps to hide.
List the evidence gaps
For each file, note photo labeling quality, completeness of moisture logs, and whether carrier-specific documentation was present. Do this before you look at the reduction amount, so the review isn't biased by already knowing the outcome.
Compare against outcomes
Compare that list against the paid amount versus original estimate, and the carrier's stated reason for reduction or delay. The correlation between weak files and reductions is usually obvious within the first ten.
You'll quickly see that reductions correlate with weak evidence and documentation integrity, not just "tough adjusters." Once that's obvious, the next step is to systematize the audit: a consistent checklist, enforced per carrier and per loss type, before submission. That's not a one-time training. It's a daily system, run on every file, before it leaves the building.
Questions owners actually ask
Isn't our estimator already doing a pre-submission review?
Most estimators review scope, not the entire evidence and documentation package. A true audit treats the file as a full case, not just an estimate, and checks against carrier-specific requirements every time.
Do carriers really follow patterns in reductions?
Yes. Carriers and TPAs have standard playbooks that target weak documentation, vague notes, and missing evidence. If your files match those weaknesses, reductions are repeatable, not random.
Can this be fixed with more training instead of systems?
Training helps, but people revert under pressure. Systems that enforce a checklist and automated verification catch what training alone misses, especially across 1–20 locations.
NanoForce's Claims-to-Cash system is built as that missing pre-submission claim file audit: every photo labeled, every moisture reading verified, every line item matched to evidence, and every carrier requirement confirmed before the file leaves your office. See how it works on the Claims-to-Cash page →
Send us one file, one question, or one number that looks off.
Mark reads these personally. No sequence, no sales follow-up you didn't ask for.
Bring one recent reduced claim file to a Margin Leakage Consult.
Ideally a loss that should have paid more. We'll walk through the evidence and documentation gaps that drove the reduction. And what that same pattern looks like across every location you own.