Walk into a restoration company on a busy week and you will hear two different words for the same person. To the crew in the truck, the customer is whoever is standing in the flooded house — the one who called, the one whose kitchen is ruined, the one you are trying to make whole. To the office, the customer is a claim number. Both are right, and the gap between them is where nearly everything strange about this business lives.
Because the person standing in the house is your customer, but the money almost never comes from them. It comes from their insurance carrier, out of a claim, measured against a scope of repair that someone other than your customer wrote. You are running a service business whose payer is not its client. Once you see the job that way, the receivables, the scope arguments, the program requirements, and the estimating platforms all stop being separate headaches and start being one shape.
Two people are in the room; only one signs the check
On a typical loss there are at least three parties, not two. There is the property owner, who hired you and whose property you are restoring. There is the adjuster on the loss, working for the property owner’s insurance carrier, who decides what the claim will pay for. And there is you, standing between them, doing the work the first one wants and getting paid by the second one.
That is not a dysfunction to be fixed. It is the design of insurer-funded work. The property owner suffered a covered loss, the insurer is funding the repair, and you are the contractor performing it. But it means your customer and your payer have different interests, different timelines, and different definitions of “done” — and you answer to both at once. Every other strange thing about the trade is downstream of that.
You are working inside a claim you did not file
The claim already exists before you arrive. The property owner reported the loss, the insurer opened a file, and by the time your crew is on site there is a claim number, an adjuster, and a process running that you did not start and do not control.
You are a participant in someone else’s proceeding. That has real consequences for how you work: what you can do is bounded by what the claim will fund, the timeline is partly the claim’s timeline, and the documentation you produce is not just your record — it is evidence inside a file that someone else owns. An owner who treats a restoration job like a normal remodel, where the client decides and the client pays, keeps running into walls that only make sense once you accept that you are working inside a claim rather than a contract with the person in the house.
The scope you are paid on is written by someone else
Here is the part that surprises new operators most. The scope of repair — the itemized statement of what work the loss requires — is written by or agreed with the insurer, not by your customer and often not by you.
The property owner’s insurance carrier sets the scope you are paid on. You can build your own estimate, you can disagree with the insurer’s, you can document why a wall has to come out or why the drying will take longer than the scope assumes, and a good operator does exactly that. But at the end, the money is measured against the agreed scope, and the agreed scope is the insurer’s instrument. This is why scope disputes are not a sign of a broken job. They are a routine, expected feature of a business where the person paying is not the person you are serving, and where “what this loss requires” is itself the thing being negotiated.
Program and TPA relationships, and the file they open
Most restoration companies do not wait by the phone for the property owner to find them. Work flows through relationships — program and TPA relationships — that route assignments from insurers to contractors.
A program is an arrangement in which an insurer or a network sends restoration assignments to approved contractors on agreed terms. A third-party administrator, or TPA, is a company an insurer hires to run parts of the claims process, often including handing out and managing that work. From the contractor’s chair the two feel similar: they are pipelines of assignments, and in exchange for the flow they set terms. Those terms are not suggestions. They govern how fast you respond, how you document, which estimating platform you write on, and what your certificate of insurance has to show. Signing into a program is signing into a way of working, and the agreement is worth reading as the terms of your business rather than as onboarding paperwork.
The estimating platform the insurer accepts
One of those terms deserves its own paragraph, because owners underestimate it: the estimate is written on the platform the insurer accepts, not the one you prefer.
The estimating platform the insurer accepts is how scope, line items, and pricing get compared consistently across every contractor in a program. Which means the platform is not neutral plumbing — it is where your work turns into something the claim can pay. If a program requires a particular platform and you do not use it fluently, the gap does not show up as a technology problem. It shows up as work you performed that the claim will not clearly pay for, because it was never entered in the form the settlement runs on. Fluency in the platform the insurer accepts is, in a real sense, part of getting paid.
Paid out of a claim, which is why the receivables behave that way
Now the cash flow. A restoration company can be fully booked, running crews around the clock, and still be short on cash — and owners who do not understand the split find that maddening.
Real-World Scenario: A company runs a large water loss over several weeks. Labor goes out every day, equipment sits on site the whole time, and subcontractors expect to be paid on their own terms. The work is documented carefully and the job is done well. But the money does not arrive when the job ends. It arrives when the claim resolves — after the scope is agreed with the adjuster on the loss, after the documentation clears the program’s requirements, after the file moves through steps the contractor does not control. The gap between when the cost went out and when the payment came back is not a billing error. It is the whole business model showing its shape.
You are paid out of someone else’s claim, which is why your receivables behave the way they do. The costs run on your schedule; the payment runs on the claim’s schedule; and the space between the two is a financing problem every restoration owner is solving whether they have named it or not. Recognizing that the receivable is tied to a claim rather than an invoice is the first step to planning around it instead of being ambushed by it every busy season.
The certificate a program checks before the first day
Before any of this pipeline turns on, a program or TPA usually checks one thing: your certificate of insurance. And it checks it against the agreement, not against your good intentions.
The check is straightforward in purpose. The program is attaching its name to the assignments it sends you, so it wants evidence that your own coverage is in force before your crew touches a job. In practice that check lands hardest on the lines that describe how a restoration crew actually creates risk. Your general liability answers for damage your work does to other people’s property, and your commercial auto answers for the fleet that drives to every loss — so those are usually central to what a program verifies, at the limits the agreement names, current, and listed the way the contract specifies. A certificate that has lapsed or does not match can stall assignments even when the crews are excellent, because the program cannot let work flow to a contractor it cannot verify.
<rect x="24" y="58" width="180" height="96" rx="9" fill="#F1E5D6" stroke="#DCC9B0"/>
<text x="114" y="86" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="13" font-weight="600" fill="#12703F">The property owner</text>
<text x="114" y="110" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="11" fill="#5A5048">Your customer — the one</text>
<text x="114" y="126" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="11" fill="#5A5048">who called and whose</text>
<text x="114" y="142" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="11" fill="#5A5048">property is being restored</text>
<rect x="260" y="58" width="180" height="96" rx="9" fill="#ffffff" stroke="#12703F"/>
<text x="350" y="86" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="13" font-weight="600" fill="#12703F">You, the contractor</text>
<text x="350" y="110" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="11" fill="#5A5048">Serving the one on the</text>
<text x="350" y="126" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="11" fill="#5A5048">left, paid by the one</text>
<text x="350" y="142" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="11" fill="#5A5048">on the right</text>
<rect x="496" y="58" width="180" height="96" rx="9" fill="#F1E5D6" stroke="#DCC9B0"/>
<text x="586" y="86" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="13" font-weight="600" fill="#12703F">The insurance carrier</text>
<text x="586" y="110" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="11" fill="#5A5048">Your payer — writes the</text>
<text x="586" y="126" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="11" fill="#5A5048">scope and funds the</text>
<text x="586" y="142" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="11" fill="#5A5048">claim you work inside</text>
<path d="M 258 106 L 206 106" fill="none" stroke="#12703F" stroke-width="2" marker-end="url(#funded-arrow)"/>
<path d="M 442 106 L 494 106" fill="none" stroke="#12703F" stroke-width="2" marker-end="url(#funded-arrow)"/>
<rect x="30" y="176" width="640" height="72" rx="10" fill="#C7683F" stroke="#12703F"/>
<text x="350" y="206" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="15" font-weight="600" fill="#1A1A1A">You are paid out of a claim you did not file</text>
<text x="350" y="230" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="12" fill="#1A1A1A">The customer wants the work; the payer decides what it funds</text>
<path d="M 350 250 L 350 268" fill="none" stroke="#12703F" stroke-width="2" marker-end="url(#funded-arrow)"/>
<text x="350" y="288" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="13" font-weight="600" fill="#12703F">Which is why the rest of the business behaves the way it does</text>
<rect x="24" y="304" width="208" height="104" rx="9" fill="#ffffff" stroke="#DCC9B0"/>
<text x="128" y="332" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="12" font-weight="600" fill="#12703F">Scope you did not write</text>
<text x="128" y="356" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="11" fill="#5A5048">Measured against the</text>
<text x="128" y="372" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="11" fill="#5A5048">insurer’s scope, so</text>
<text x="128" y="388" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="11" fill="#5A5048">disputes are routine</text>
<rect x="246" y="304" width="208" height="104" rx="9" fill="#ffffff" stroke="#DCC9B0"/>
<text x="350" y="332" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="12" font-weight="600" fill="#12703F">Receivables that lag</text>
<text x="350" y="356" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="11" fill="#5A5048">Costs run on your</text>
<text x="350" y="372" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="11" fill="#5A5048">schedule; payment runs</text>
<text x="350" y="388" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="11" fill="#5A5048">on the claim’s</text>
<rect x="468" y="304" width="208" height="104" rx="9" fill="#ffffff" stroke="#DCC9B0"/>
<text x="572" y="332" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="12" font-weight="600" fill="#12703F">A program file kept current</text>
<text x="572" y="356" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="11" fill="#5A5048">The platform, the</text>
<text x="572" y="372" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="11" fill="#5A5048">documents, and the</text>
<text x="572" y="388" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="11" fill="#5A5048">certificate the program checks</text>Before you sign the next program agreement
None of this is a complaint about the claims economy. It is the market restoration lives in, and for most operators it is a good market — steady assignments, real volume, a reason the phone rings after every storm. The point is only to see it clearly.
Your customer is the person in the house. Your payer is their insurance carrier. The scope, the platform, the documentation, and the timing all follow from that split, and the program and TPA agreements are where the terms of it get written down. Read those agreements as the terms of your business, build the insurance file a program will check before it needs to see it, and treat the receivable as tied to a claim rather than an invoice. If you want the restoration program underneath your operation built to match the way the claims economy actually pays you, ask us for a quote.