The Exclusion That Was in the Quote and Still Cost the Job
Why this matters
Every shop that has been burned once writes exclusions. Almost none of them check whether the exclusion is doing the job it was written for, because the test looks like it passes: the words are in the document, the customer signed the document, and if it ever went to a lawyer the shop would probably be fine. That is the wrong test. An exclusion is not defeated by argument, it is defeated by surprise, and the surprise happens weeks before anybody reads the document. This is a reconstruction of one job where the exclusion was correct, present, and signed, and the shop lost the customer anyway.
The outcome we are working backwards from
A 26.0-hour job, finished on time and technically clean. On day two the crew found a condition that fell squarely inside an exclusion in the quote. The extra work ran 7.5 hours, which is 29% of the original job. The customer said it should have been included, the shop pointed at the exclusion, and the two of them split it. The account, which had produced four jobs over three years, has not called since.
Nobody did anything wrong on the day. That is what makes it worth reconstructing.
The file, in order
Six documents, and the order is the finding.
- Site survey note, written by the estimator on the day of the visit. Four lines about access and equipment. Nothing about the condition that later came up.
- The quote, issued nine days later. Three pages. Page one, scope. Page two, price and the signature block. Page three, a block of eleven standard exclusions. The disputed item is exclusion seven.
- The customer's acceptance, an email reply two days after the quote: "Looks good, when can you start."
- A photo from day two, taken by the lead tech, showing the condition. Timestamped mid-morning.
- A message thread the same afternoon between the tech and the office, then the office and the customer.
- The final invoice, with the extra 7.5 hours split.
Reading the sequence for the moment the expectation formed
The instinct is to start at the dispute and work back through the paperwork. Start instead at the earliest point where the customer could have formed a belief about what they were buying, because that is the moment an exclusion has to beat, and it is almost never the moment the document is read.
That moment is document one, the site survey, nine days before the quote existed. The estimator walked the property with the customer for about twenty minutes. The customer pointed at the area, described what they wanted, and the estimator said the work could be done. Everything the customer believed about the scope of this job was set in those twenty minutes.
The quote arrived nine days later into a belief that was already fully formed. Read in that light, the acceptance email is not a careless customer skipping the fine print. "Looks good" is a person confirming that the document matches what they already understood. It is what agreement looks like when the document is a formality.
Where the exclusion was, and what it said
Exclusion seven, on page three, read roughly: work arising from pre-existing conditions not visible at the time of survey is not included.
Three properties of that sentence, each of which is a separate defect.
It sat after the signature block. The customer signed on page two. Whether terms appearing after a signature are incorporated into an agreement is a contract question that varies by state and by how the document is structured, and it belongs with your attorney rather than being assumed either way. What is not in doubt is the behavioural fact: a reader who has signed has stopped reading.
It was written in the negative and never contradicted anything. "Not included" only registers with a reader who already thought it was included. This customer never formed a thought about pre-existing conditions at all, so the sentence passed over an empty space in their head and left nothing behind. An exclusion has to collide with a belief to do any work.
It was generic, so it did not map to the thing they pictured. "Pre-existing conditions not visible at the time of survey" is a category. What the customer pictured was a specific area of their property being made right. When the condition appeared, the customer did not experience it as an instance of a category. They experienced it as part of the thing they had been shown and priced.
What the record cannot settle, and why that is part of the answer
The file cannot tell us what was said during those twenty minutes. There is no survey note beyond four lines about access, no photograph of the area under discussion, and no record of any question asked or answered. So we cannot know whether the estimator mentioned the possibility of hidden conditions.
Treat that gap as the finding rather than as an inconvenience. Two things follow from it.
If the estimator did mention it, the shop cannot prove it and gets no benefit from it, which is the same practical position as not having mentioned it. If the estimator did not, then the only moment in the entire transaction when the customer's expectation could have been shaped was allowed to pass without anyone shaping it.
Either way the fix is in the same place, which is a good sign that we have found the real one. When a gap in a record makes two opposite explanations lead to the same corrective action, the corrective action is almost certainly right.
The second gap is smaller and worth logging: nobody photographed the area at survey. A survey photograph of the area as it appeared, attached to the quote, would have established what was and was not visible on the day, which is the exact question exclusion seven turns on. The shop had no way to show what the survey could see.
The mechanism, stated so it transfers
An exclusion has two jobs and shops only ever check the first.
Its legal job is to define, if it ever comes to that, what the agreement covered. Most exclusion blocks do this adequately.
Its expectation job is to prevent the customer from believing something that is not true, at the moment they are forming the belief. This is the job that determines whether you keep the account, and it is done at the survey, in conversation, not in a document delivered nine days later.
An exclusion that only does the first job produces exactly this outcome: you are right, you are paid, and the customer does not come back. From their side nothing was fair about it. From yours the paperwork worked. Both readings are accurate, which is why arguing about it never resolves anything.
One boundary on all of this: an exclusion governs who pays. It never governs whether you disclose. Where the condition found on day two is a hazard rather than a cost, the exclusion is irrelevant to the disclosure duty and the finding is stated plainly and in writing regardless of who is paying for the correction. See related: What You Owe When You Find Something Dangerous.
The change that would have worked
Three changes, all cheap, and the first one carries most of the weight.
Name the risk out loud at the survey, in the customer's own terms, and write down that you did. Not "we exclude pre-existing conditions." Something like: "Behind that section, I can't see what condition it is in until we open it. Most of the time it is fine. Occasionally it adds work, and if that happens I will call you before we do anything." Then one line in the survey note: raised concealed-condition risk with the customer at the area, plus a photograph. That line converts an unprovable conversation into a record and takes about fifteen seconds.
Move up to three exclusions above the signature, in plain language, and leave the rest where they are. Not all eleven, because eleven above a signature reads as boilerplate and gets skipped exactly like page three did. Three, chosen as the ones a customer would plausibly assume were included on this specific job. On this job, exclusion seven was one of them.
Attach a survey photograph of the area to the quote. It establishes what was visible on the day, which is the fact that every concealed-condition dispute turns on.
None of these would have prevented the condition. What they change is the customer's experience of it: an event they were warned about and expected a call on, rather than a surprise defended with a document. That is the difference between 7.5 hours discussed and 7.5 hours disputed, and it is the difference between four jobs in three years continuing and stopping.
Testing your own exclusions for surprise
Take your current exclusion block and run each line through three questions.
- Does it contradict something a customer would otherwise believe? If it does not collide with a belief, it will not be remembered, and it is doing legal work only.
- Is it stated anywhere before the signature, and out loud before the quote? If both answers are no, the customer will meet this exclusion for the first time on the day it costs them something, which is the worst possible introduction.
- Would it map to something the customer can picture on their own property? Categories do not survive contact. Locations do.
Then one test on the block as a whole: count the exclusions a customer sees before signing. If that number is above three, you have a block, and blocks get skipped. Pick the ones that actually apply to this job and let the standard list live where standard lists live.
Whether a given exclusion is enforceable, and how it interacts with any consumer-contract requirements in your state, is a question for your own attorney, and it varies by state and by whether your customer is a consumer or a business. The surprise problem is separate from that and is entirely yours to fix.
References
- See related: The Conditions Clause: Protect the Quote; Scoping the Hidden Conditions Risk; What a Partial Fix Obliges You to Say; What You Owe When You Find Something Dangerous
- Trade-standard practice for site survey documentation and pre-quote condition photography
- Confirm contract formation, incorporation of terms, and any residential contract content requirements with your own attorney; these vary by state and by customer type