Handling Inspector-Required Extras and Who Pays
Why this matters
An inspector requires something beyond your quote, and the first fight is not with the inspector, it is over the bill. The customer believes the number they signed was complete; you believe the extra was never in it. Handle this badly and you either eat unpaid work on every inspection or you look like you are padding the job with "surprise" charges. Handle it well and both of you know, before the tools come out, who owns an inspector-required extra and why. The deciding question is almost always the same one: was it knowable when you quoted.
The core question: was it knowable at quote time
Sort every inspector-required extra by whether a competent contractor should have priced it in when the quote was written. That single test resolves most of these fairly:
- Knowable and code-required at quote time: it was your obligation to include. You own it. Missing it is a quoting error, not a change.
- Not reasonably knowable at quote time: a hidden condition, a code interpretation you could not have predicted, a requirement that surfaced only when work was opened up. That is legitimately new, and it belongs in a change order.
The honest contractor applies this test the same way whether it helps them or not. That consistency is what keeps customers trusting your change orders when they are real.
Categories of inspector-required extras, and who typically owns each
| Category | Example shape | Who typically owns it |
|---|---|---|
| Code item you should have quoted | A required safety device or clearance the code plainly mandates for your work | You |
| Field-hidden condition | A defect found only once a wall, floor, or trench was opened | Customer, as a change |
| Scope of another trade | An item the inspector flags that belongs to a different permit or discipline | Customer or the other trade |
| Pre-existing / grandfathered pulled into current code | A legal old condition the open permit now forces up to code | Customer, as new scope |
| Inspector interpretation stricter than the text | A judgment call the code does not clearly require | Negotiated; depends on how it resolves |
| Code edition changed since the estimate | A requirement that took effect between quote and permit | Usually customer, if genuinely new |
The pattern: what you could and should have known is yours; what genuinely emerged after the quote is a change the customer authorizes.
Build the answer into the contract before it comes up
The cheapest place to settle who pays is the contract, long before the inspector arrives. Three clauses do most of the work:
- A code-compliance clause stating that the quoted scope covers the code in effect and known conditions as of the quote date, and that requirements arising from hidden conditions, code changes, or authority interpretation are handled as changes.
- Clear exclusions naming what is not in the price (other trades, correction of pre-existing conditions, upgrades the customer has not authorized).
- An allowance or contingency for jobs where you know inspection may surface unknowns, so there is already a mechanism instead of a surprise.
A contract that anticipates this turns a tailgate argument into a paragraph you both already read.
Present the extra as a change order, not a surprise
When a genuine extra lands, the presentation decides how it is received:
- Name the item and the authority for it. "The inspector requires this, here is the code section," not "the inspector wants more money."
- Show it against the contract. Point to the exclusion or the code-compliance clause that puts it outside the base price.
- Price it plainly and separately as a change order, authorized in writing before you do the work.
- Distinguish it from your own miss. If part of what the inspector wants was something you should have quoted, say so and own that part. Splitting the honest line builds more trust than defending all of it.
Protect yourself at quote time
Most who-pays disputes are prevented before the job, not argued after it:
- Quote the actual code that applies, not the cheapest thing that might slip through.
- Note the code edition and quote date on the estimate, so a later change is visibly later.
- Exclude what you are not pricing, in writing, instead of leaving it ambiguous.
- Flag likely inspection unknowns to the customer up front, so a change order later confirms a warning instead of contradicting a promise.
The judgment to bank: you do not get to bill for what you should have known, and you should not eat what you could not have known. Decide which one it is honestly, put it in writing, and the money question mostly answers itself.
References
- International Code Council (ICC) model codes on contractor code-compliance obligations
- Trade-standard practice on change orders, allowances, and scope exclusions
- U.S. Small Business Administration (SBA) guidance on service contracts and estimates
- See related: An Inspector Wants a Change Beyond the Original Scope (decision tree); The Permit Was Pulled But the Scope Changed (decision tree)