Independent work sample, built for one real business
Chicago Water & Fire Restoration: a signed estimate before work starts, and a record for every disputed line
Public complaint records and a published appellate ruling involving this company describe the same recurring pattern: a cost estimate or invoice that lands far above what the customer or insurer expected, with no clear written scope agreed before work begins. This example shows a small tool that closes that gap for a restoration business specifically: an itemized, IICRC-style estimate generated before a crew is dispatched, a timestamped customer sign-off on the scope and estimated range, and a documentation packet that ties every billed line to real evidence, so a disputed invoice can be resolved by pulling a record.
Power Dry of Chicago, Inc., d/b/a Chicago Water and Fire RestorationElmhurst, IL HQ · second location Houston, TXFire/water damage restoration & reconstruction, since 1988
Independent work sample, not affiliated with or endorsed by Chicago Water & Fire Restoration or Power Dry of Chicago, Inc. All customer names, jobs, and dollar amounts inside the tool below are fictional and clearly for illustration only. The business description, location, and case reference are drawn from the company's own published site and from public court records.
An Illinois appellate court found that Power Dry of Chicago, Inc., d/b/a Chicago Water and Fire Restoration, acted as an unlicensed public adjuster by applying loss circumstances to a homeowner's insurance policy language on the customer's behalf, voiding the contract and leaving the company with no enforceable claim for the disputed invoice.
Power Dry of Chicago, Inc. v. Bean, 2022 IL App (2d) 210043.
The company's BBB profile separately shows a pattern of billing and documentation complaints over the past three years, including deductible-handling disputes, a mechanics-lien and invoice discrepancy, and allegations of pricing above industry standard on flood-mitigation jobs. Two of the disputed amounts named in these public records: a mitigation invoice submitted at $12,764.39 that an insurance adjuster reduced to $4,389.64, and a fire-restoration bill of $89,367.27 with more than $11,000 in line items the customer disputed. The company's own public site shows a general contact form and a payment portal, but no customer-facing itemized-estimate or e-signature step before work begins, which is consistent with the pattern above. None of this is presented as proof of intent; it is the documented pattern the tool below is built to prevent going forward, by making the scope, the price, and the supporting record visible before a dollar is billed.
Build the itemized estimate
Job record & documentation packet
Staff message guardrail check
Paste a draft customer message or call note. This checks it against phrasing patterns that read as promising insurance coverage, offering to negotiate with a customer's insurer directly, or skipping a written estimate, the same fact pattern the Bean appellate opinion above turned on. It is a simple keyword check for illustration, not legal advice or a substitute for compliance review.
How this gets built for real
The estimate categories are illustrative. A real build maps to whatever pricing structure the company already uses internally, whether that's Xactimate-style line items or its own price book.
"Signed" here is a typed name and a timestamp. A real build can use an actual e-signature provider for a stronger legal record; this demo shows the workflow.
The guardrail check is a keyword list, not legal review. It catches obvious phrasing patterns as a first line of defense; it does not replace training or counsel's sign-off on communication templates, and does not resolve the underlying licensing question the Bean opinion raises.