The Conditions Clause: Protect the Quote
Why this matters
Most arguments over a final bill are not about the work you did. They are about the work nobody agreed was part of the job. A conditions clause is the short paragraph on your quote that says what you assumed, what you did not include, and what changes the price. It is the difference between a clean change order and a fight that costs you the customer and the review.
What a conditions clause is
A conditions clause (sometimes called assumptions, exclusions, or a qualifications note) is plain language on the estimate that fences the quoted price. It tells the customer three things in writing:
- What you assumed to be true when you priced it ("walls are standard framing", "existing wiring is to code", "ground is diggable by hand").
- What is not included ("does not include drywall repair", "permit fees billed at cost", "haul-away of old unit excluded").
- What triggers a new price ("hidden damage found behind the wall is quoted separately before work continues").
It is not fine print meant to trick anyone. It is the honest boundary of the number you gave.
Why a verbal "it depends" is not enough
You probably already say these things at the kitchen table. The problem is memory. Three weeks later, when you open a wall and find rot, the customer remembers a price and a handshake, not your caveat. Written conditions move the conversation from "you said" to "here is what we both signed." That protects you, and it protects the customer from feeling ambushed.
A clause also forces you to think the job through before you quote. If you cannot write down your assumptions, you do not actually know the scope yet.
What to assume, and how to write it
Keep each line short and specific. Vague conditions ("subject to site conditions") protect nothing because they mean nothing. Tie each assumption to a real risk you can see on the job.
| Risk you see | Weak clause | Strong clause |
|---|---|---|
| Old building | "may need extra work" | "Assumes existing structure is sound; concealed damage quoted separately" |
| Access unknown | "access permitting" | "Assumes clear access to work area; furniture moving by customer" |
| Buried unknowns | "if needed" | "Assumes no buried lines or obstructions in dig path" |
| Code surprises | "code compliance extra" | "Assumes existing system meets current code; corrections quoted before proceeding" |
Write what you would actually point at if you had to defend it.
The hidden-condition trigger
The single most valuable line is the one that covers what you cannot see until you start. Behind walls, under floors, inside panels, below grade. The standard, fair practice is: when you find something the quote did not cover, you stop, document it, and present a separate price before continuing. The customer can approve it, decline it, or get a second opinion. Nobody gets surprised at the invoice.
State the trigger and state the pause. "If concealed conditions are found, work pauses and the additional scope is quoted for approval before continuing." That sentence has saved more relationships than any discount ever has.
What does not belong in a conditions clause
A conditions clause is a boundary, not a loophole. Do not use it to:
- Hide a price you should have included. If a job clearly needs haul-away, quote the haul-away.
- Excuse sloppy scoping. Conditions cover the genuinely unknown, not the things you should have measured.
- Pile on so many exclusions the customer cannot tell what they are actually buying. Three to seven tight lines beat a wall of text.
Used right, the clause makes you look thorough. Used as a dodge, it makes you look like you are setting a trap, and customers smell that.
Make it standard, not custom every time
Build a base set of conditions for your common job types and keep them ready to drop onto a quote. Add the one or two job-specific lines that this particular site demands. A reusable block means you never forget the assumption that bites you most often, and the customer sees the same professional boundary on every quote you send.
When the job is approved, the conditions ride along with it into the file. If a dispute ever comes, you reach for one document, not a memory.
References
- Trade-standard practice for written estimates and scope of work
- See related: The Photo and Note Scope Record
- See related: The Second Look Before You Commit the Price
- SBA guidance on clear contracts and customer agreements for small businesses