Why a Contingency You Do Not Explain Reads as Padding

Why this matters

A customer holding three quotes cannot see risk. They can see numbers. Your contingency and a competitor's optimism look identical on paper: one number is bigger, and nothing on the page explains why. So the bigger number gets read as the thing bigger numbers usually are, which is more margin, and you lose a job you had priced correctly to a shop that priced it wrong.

The contingency is not the problem. The silence around it is. An unexplained risk premium competes only on size, and on size you will lose to whoever understood the job least.

What the customer is actually comparing

Put yourself on their side of the table. Three quotes, similar scope language, one clearly higher. The customer has no way to tell which of these is true:

• The higher shop looked harder and found something the others missed.
• The higher shop is busier and does not want the work badly.
• The higher shop charges more because it can.
• The two lower shops will be back in three weeks asking for more.

Every one of those is consistent with the evidence in front of them. Absent information, people default to the simplest explanation, and the simplest explanation for a higher number is a higher margin. That default is not cynicism, it is the only inference available.

Disclosure does not make your number smaller. It changes what is being compared. Once the contingency is named and attached to a specific unknown, the customer is no longer comparing your number to the low bid. They are asking whether the unknown is real, which is a question about the building rather than about you, and it is a question the low bidder has to answer too.

The three honest postures

There are exactly three defensible ways to carry contingency, and the difference between them is what happens to the money when the unknown does not materialize. Pick one per job, say which, and be consistent.

Folded. Contingency is distributed into the line items and never appears as a line. The register exists internally. If the unknown does not appear, you keep it. This is honest as long as you are not simultaneously telling the customer your price contains no contingency.

Named and retained. The line is on the quote, attached to a stated unknown, and the quote says plainly that it is part of the fixed price whether or not the condition appears. You are being paid to carry a risk, and carrying it is the service. Say so in those words.

Named and returned. The line is on the quote and the quote states the unused portion is not invoiced. You are the customer's agent for that unknown rather than the insurer of it. This wins competitive residential work and it costs you the upside, so it only makes sense when your register is accurate enough that you do not need the good jobs to fund the bad ones.

Whichever you pick, a disclosed line invites one question, and you should have the answer ready because it arrives on most jobs: can you just take it out? The answer is yes, and the sentence that follows it decides whether you keep the job on terms you can live with. "Yes. If we remove that line, the work stops when we find that condition and the additional work is quoted then, at whatever it turns out to be. You would be choosing to carry it instead of us." That is not a threat and it is not a sales line. It is an accurate description of what removing the line does, and plenty of customers who ask leave it in once they hear it. The ones who take it out have made an informed choice, which is a much better position for both of you than a customer who thinks they negotiated away a risk rather than acquiring one.

The dishonest version is not on this list, and it is common: a line labelled in a way that suggests it will come back, retained silently when it does not fire. That is the version that poisons the well for everyone using the instrument properly.

One rule, two jobs, opposite answers

The rule: name the contingency as its own line, attach it to a specific unknown, and state what happens to it if the unknown does not appear.

Job one: residential, three bids, and it works.

A shop quotes work in an older home carrying a contingency of 9 percent of sold hours, all of it attached to one named unknown, the condition of a concealed run that cannot be inspected without opening a finished surface. Their total sits about 12 percent above the low bid.

The quote carries three sentences: what the unknown is, what it would cost in additional hours if it turns out badly, and that any unused portion of the line will not be invoiced. The estimator adds one more thing at the walk-through, which is a photograph of the surface in question and a plain statement that neither they nor anyone else quoting can see behind it.

The customer takes that photograph back to the other two bidders and asks what they carried for it. Neither had considered it. Both come back with a conditional answer, which is the same answer the winning shop gave, only three days later and after being prompted. The job goes to the shop that raised it, at 12 percent above the original low bid.

Nothing about the price changed. What changed is that the customer stopped choosing between three numbers and started choosing between one shop that had examined the building and two that had examined the drawing.

Job two: institutional bid, and the same rule loses.

The same shop bids repair work for a facility that issues a written invitation with a required response format: a single lump sum per line item, and explicit instructions that any qualification, allowance or conditional pricing renders the response non-responsive.

Following the rule here gets the bid thrown out unread. The correct move is the folded posture: the register still exists, sized the same way, and it is distributed across the line items with nothing conditional on the page. If the unknown is too large to fold without pricing the shop out, the answer is not to sneak a qualification in. It is to ask the question during the bid question period, on the record, so the answer goes to every bidder in an addendum. That converts your private unknown into a shared one, which is the only legitimate way to remove it from a lump-sum bid.

Same rule, opposite outcomes, and the deciding variable is not the customer's sophistication. It is whether the buying process has room for a conversation. Where it does, disclosure moves the comparison off price. Where the process forbids conversation, disclosure just disqualifies you, and the instrument that does the work is the bid question, not the contingency line.

Why the low bidder's silence is expensive for them too

Worth understanding, because it is the argument you make to the customer without ever criticising a competitor.

A shop that does not carry contingency is not carrying less risk. It is carrying the same risk uncompensated. Across a year, its jobs that hit the unknown come out of margin, and its jobs that do not are priced fine. So its average job is under-priced by the frequency of the unknown times its impact, which is the same arithmetic your register does openly. The difference is that your version is visible and adjustable and theirs shows up as a bad year with no traceable cause.

You never say this about a competitor. You say it about the job: this condition shows up on roughly one job in three of this type in this housing stock, it costs about a day when it does, and somebody is paying for that whether it is named or not.

The language that works and the language that does not

Does not work: "contingency," "allowance for unforeseen," "miscellaneous," "P and O," any acronym, any line whose label is a category. These read as the fee they are.

Works: the unknown in the customer's own words, followed by the consequence. "The run behind the finished wall in the hall cannot be inspected without opening it. If it is in the condition we expect, this line is not invoiced. If it has to be replaced, it covers up to a day of additional work and we will show you the condition before we do anything."

Three properties make the second version work: it names a place in their house, it commits to a specific behaviour, and it is falsifiable, meaning the customer will find out whether you were straight with them. A line the customer can check is worth more than a line that sounds professional.

What changes the answer

Repeat customers and maintenance agreements. With a customer who sees ten of your jobs a year, the folded posture is usually better. Naming a contingency on every visit trains them to negotiate it, and across ten jobs the portfolio effect that makes a register work is already operating inside your relationship rather than needing to be explained on each quote.

Jobs where the unknown is scary to say out loud. Some conditions cannot be raised gently, particularly anything touching structure, combustion, or water intrusion. There the disclosure is not a pricing conversation at all: the finding gets stated plainly, in writing, on its own, and the commercial discussion happens after the customer has understood what was found. A serious found condition is never a negotiating position.

How to verify your disclosure is doing its job

For a quarter, note on every lost bid whether the customer asked you about your contingency line. If they never ask, your disclosure is invisible: it is buried in terms, written in trade language, or labelled as a category. If they ask and you still lose, that is a genuine price loss and useful information. The failure you are hunting is the third case, where they never asked and never mentioned it, which means the number was on the page doing nothing but making you the high bid.

References

• U.S. Small Business Administration (SBA), guidance on pricing and bidding for small businesses
• Bid protest and responsiveness rules for public solicitations are set by the issuing authority and by state or federal procurement law; read the instructions to bidders in each solicitation rather than generalizing across them
• See related: How to Size a Contingency You Can Defend; The Contingency Line and How to Size It; Padding the Estimate: The Temptation