You can price for contingency, write a tight scope of work, and still have a Tuesday where the drywall comes down and there's water damage nobody could see coming. Contingency is the money for this. This post is what to actually do in the two hours after it happens — before the change order gets written, before the contingency line gets touched.
First decision: stop, or keep going?
Not every surprise stops the job. Sort it fast, because the crew is standing around costing you money while you decide.
Keep working around it when the surprise is contained and doesn't affect safety, structure, or code compliance — a subfloor patch needed in one corner of a bathroom while the rest of the room gets tiled, a light fixture that's back-ordered while the electrician finishes rough-in elsewhere. Work the parts of the job that aren't blocked.
Stop the specific task, not the whole job when the surprise sits on the critical path for that trade but other trades can still move — rot found behind a shower wall stops the plumber, but the electrician can still finish the panel upgrade in the garage.
Stop everything when it's a safety issue, a code violation that has to be corrected before work can legally continue, or a failed inspection that blocks the next trade from starting anywhere. A failed rough-in inspection on a whole-house rewire stops drywall, insulation, and everything downstream until it's resolved — there's no partial path around it.
The mistake to avoid in either direction: stopping the whole job out of caution when only one task is actually blocked, or quietly working through a code or safety issue because stopping feels expensive. The first burns days you didn't need to burn. The second turns into a much more expensive problem at the next inspection.
Document it before you touch it
Whatever the surprise is, the sequence is the same and it happens before you call anyone:
- Photos, immediately, before anything gets moved or removed. Wide shot for context, close shot on the actual damage or issue, something in frame for scale (a tape measure, a phone). A rotted joist looks different in a photo taken before cleanup than one taken after — and "different" here means "harder to justify the price on."
- Write down what you found and when, in plain language, timestamped. "Removed shower surround 8/15, 10:40am, found water damage to two floor joists and subfloor, approx. 3'x4' area, likely long-term leak from failed pan liner." This is the sentence that turns into your change order description later, and it's also your protection if the client's memory of the conversation drifts.
- Note what it would take to verify further, if you're not sure of the full extent yet. Sometimes you don't know if it's two joists or four until more material comes out — say that, rather than guessing at a final number before you actually know.
Skipping this step is the single most common reason a legitimate discovered-conditions charge turns into a dispute. A client who sees photos and a timestamped note believes you. A client who gets a verbal "yeah it was bad in there" three days later, after the wall's already closed back up, has no way to independently confirm anything — and no reason not to assume you're padding the number.
Call the client before you price it
The order matters: photos and notes first, then a call, then a price — not a price shoved through email with photos attached as an afterthought.
Keep the call short and factual. What you found, what it means for the schedule, roughly what kind of cost range it's in if you have one in mind, and what needs to happen next. "We opened up the shower wall and found water damage to the subfloor and a couple of joists — looks like the old pan was leaking for a while. I want to get a plumber's eyes on it before I give you a firm number, but you're probably looking at somewhere in the $800–1,400 range depending on how far it extends. I'm going to hold off on framing that wall back up until we've talked it through." That's a five-minute call that leaves the client informed and still in control of the decision, which is the same principle covered in how change orders get communicated — the difference between "here's what happened to your bill" and "here's what I found, here's roughly what it costs, want me to proceed."
What not to do: keep working, close the wall back up, and mention it on the invoice. Even if your price is completely fair, a client who finds out about a $1,100 charge after the fact — with no photos, no conversation, no chance to ask a question before it was too late to matter — will assume the worst about the number regardless of whether it's accurate.
Pricing it without guessing and without stalling
You don't need a perfect number on the first call, but you do need a process that gets to one fast:
- If it's discovered conditions (rot, bad wiring, a pipe that isn't where the plans said), price it the way you'd price a change order for anything else — labor and material for the actual fix, at your normal rates, not inflated because the client is now a captive audience mid-project. If contingency was built into the estimate for exactly this kind of thing, this is what it gets spent on — track it against that line rather than treating it as a separate, unbudgeted hit.
- If it's a material price jump between bid and buy — lumber moved 8% since you quoted the deck, the tile the client picked went up $2/sq ft at the supplier — the fix is transparency, not absorption. Show the client the actual supplier price then and now if you can, and price the difference straight through. This isn't a discovered-conditions issue, so it doesn't belong in contingency; it's a direct pass-through, and being able to point at a real number keeps it from feeling arbitrary.
- If it's a subcontractor no-show, the cost is usually schedule, not dollars, unless you have to bring in a replacement sub at a rush rate to keep the job moving. If that's the case, be straight with the client about why: "my original plumber fell through, I've got someone else who can start Thursday but it's a slightly higher rate to get him in this week" is a legitimate conversation, not a markup to hide.
Protecting the relationship, and the margin
The jobs that survive a bad surprise with the relationship intact all have the same shape: the client heard about the problem before they saw it on a bill, they got a real number quickly instead of a vague one slowly, and the price matched the same rates and logic as the rest of the estimate. The jobs that don't survive it usually have a client who felt the surprise was managed around them rather than communicated to them — even when the underlying cost was completely legitimate.
Margin gets protected the same way it gets protected everywhere else on the job: don't eat legitimate discovered-conditions costs to avoid an uncomfortable conversation, and don't quietly pad them to make up for a tight bid elsewhere. Price it straight, document it well, and let the contingency and change-order process you already built into the estimate do the job it's there for.
JobPencil's change orders share the same line-item format as the original estimate, so a discovered-conditions charge shows up looking like a professional add, not a hastily scrawled number on an invoice. Build and manage your estimates free, no account required until you save.