What to Do When You Open a Wall and Find Something Unexpected

Demolition day. The tile comes off the shower wall, and the substrate behind it crumbles. Or the ceiling opens and the wiring is not what anyone expected. Or the deck ledger comes free and the rim joist behind it is soft.

Nobody priced this. Nobody could have. The price was based on what could be seen, and this could not be seen.

What happens in the next hour often determines whether the discovery becomes a documented decision or a final-invoice argument. The repair itself is usually the easy part. The dispute, when it comes, is about money, authority, and memory: who approved what, for how much, and when.

Here is a field process for that hour.

The best time to handle a concealed condition is before demolition

A concealed-condition dispute usually starts weeks earlier, in the scope of work.

If the agreement says nothing about hidden conditions, the customer can reasonably believe the price covers whatever the job turns out to require. A scope that states its basis prevents that assumption:

The price is based on visible conditions. Concealed rot, mold, structural damage, code deficiencies, or other hidden conditions are not included unless specifically identified. The contractor will notify the owner and document any proposed additional work before proceeding.

Where the risk is predictable, a base amount with a process is even better:

Price includes replacement of up to 32 square feet of damaged subfloor discovered beneath the existing bathroom flooring. Additional replacement requires customer approval through a change order.

A concealed-condition clause is not permission to charge whatever appears later. It is a promise about process: when something unexpected shows up, work pauses, the discovery gets documented, and the customer decides with complete information.

If your current agreement has no such language, that is worth fixing before the next job, not during this one.

Step 1: Stop at the discovery, not after it

When the unexpected appears, stop the affected work.

Stopping does not mean the whole job halts. Crews can usually continue in other areas. It means no one keeps cutting, demolishing, repairing, or covering in the affected area until the discovery is documented and a decision exists.

Two moments deserve particular discipline:

• Do not expand the opening beyond what is needed to understand the problem without telling the customer. "We opened one wall and found rot" is a discovery. "We opened four walls looking for more" is a scope decision the customer did not make.
• Do not cover anything up. Closing a wall over an undocumented condition, or ahead of a required inspection, converts a manageable discovery into a serious problem. If an inspection is required for the work, the condition gets resolved and inspected before drywall.

Step 2: Photograph it like a stranger will judge it

Take photographs before anything is moved, cleaned, or repaired. Then take more as the condition is exposed.

Useful discovery photos share a few habits:

• Wide shots that show the room and location, not just a close-up of damage that could be anywhere.
• Close-ups with something for scale: a tape measure beats a thumb.
• A caption for every photo: date, location, and what the photo is intended to show.

October 14, second-floor hall bathroom, north wall behind removed tub surround. Deteriorated substrate and staining on lower 24 inches of wall cavity, extending approximately 40 inches from the corner.

A captioned photo can later be referenced in the change order and attached to the agreement. An uncaptioned photo is just a picture of a wet board in an unknown house on an unknown date.

Step 3: Tell the customer promptly and plainly

Notify the customer before proceeding, and before the discovery gets stale. Same day is the standard worth holding.

Plain language works better than alarm or jargon:

While removing the tub surround today, we found deteriorated subfloor and lower wall framing along the north wall. I have photos. I want to show you what we found, what I recommend, and what it would cost before we go any further. Nothing in that area moves forward until you have the full picture.

Notice what that message does. It states the discovery, promises documentation, and confirms that the customer decides. It does not quote a price from the top of a ladder, and it does not minimize the finding to avoid an awkward conversation.

Step 4: Define the proposed repair, including its limits

Describe the repair the same way a good scope describes any work: what will be removed, what will be furnished and installed, where, with what materials, and what is excluded.

Be honest about what remains unknown:

Replace up to 40 square feet of damaged subfloor and sister the two affected joists as shown in the attached photos. If additional damage is found beyond the area now visible, the contractor will stop, document the added area, and obtain approval before continuing.

That last sentence matters. Concealed conditions sometimes reveal more concealed conditions. Building the pause into the repair scope keeps the process honest through the second discovery, not just the first.

Step 5: Price it, place it in the contract, and state the schedule effect

The customer needs three numbers and a date:

• The price of the repair, or a defined basis if quantities are still uncertain.
• The new running contract total, calculated from the original contract plus and minus every prior approved change. Do not price change order three against the original contract and quietly forget the first two.
• When the added amount is due.
• The schedule effect, even if the honest answer is "none expected."

If the repair changes the completion date, say so now, in the same document. A discovery that adds work usually adds time, and the schedule conversation goes better attached to the discovery than raised for the first time when the original deadline passes.

That running total is one of the eight things a change order should document.

Step 6: Get approval before the wall closes

Put the discovery, photos, repair scope, price, payment timing, and schedule effect in one organized record and obtain the approval the job and agreement require, before the changed work proceeds and before anything is covered. This is the same discipline as getting approval before the changed work begins on any change.

Wisconsin's home-improvement rules reinforce the writing habit. Under Wis. Admin. Code section ATCP 110.05, certain home-improvement contracts and all changes to their terms and conditions must be in writing. ATCP 110 is not universal contractor law. Its definition of "home improvement" excludes construction of a new residence and major renovation of an existing structure, so contractors should confirm which requirements apply to the particular project. But the practical habit is the same either way: a discovery that changes the work, the price, or the schedule deserves a written, approved record. Wisconsin law also recognizes that an electronic record can satisfy a writing requirement, which means a well-organized electronic change order can do this job.

When the discovery is a safety or code issue

Some discoveries are not optional repairs. Compromised structure, hazardous wiring, active leaks, suspected hazardous materials, and code deficiencies in work being altered can carry obligations that a customer's preference does not override.

If the customer says "just cover it up," slow down. Document the condition, explain the concern in writing, and get qualified guidance before proceeding. Depending on the situation, that may mean the local building inspector, a licensed specialist in the affected trade, or your attorney. A contractor's licensing, permit, and code obligations are not waived by a homeowner's request, and a written record that you identified and raised the condition is far better than a memory that you mentioned it.

Suspected hazardous materials such as asbestos or lead paint deserve particular caution. Testing and abatement are specialized, regulated work. If your scope excluded them, the exclusion plus the discovery documentation is exactly why that language existed.

What if the customer declines the repair?

Sometimes a customer declines work that is optional. Where the declined work is genuinely optional, document the decision with the same care as an approval:

The owner has elected not to proceed with replacement of the stained but structurally sound sheathing shown in photos 4 through 6, dated October 14. The contract price and scope are unchanged. The contractor makes no warranty regarding the declined condition.

Whether a particular condition can responsibly be left in place, and how to document that, is judgment territory. When in doubt, ask your attorney how to handle declined-repair records under your contract.

The one-hour standard

A concealed condition handled well looks like this: work in the area stops, photos with captions exist, the customer hears about it the same day, a written repair proposal with a price and schedule effect follows, and nothing gets covered until the decision is documented and any required inspection is complete.

None of that requires an office, a laptop, or a lawyer on site. It requires a repeatable habit and about an hour of discipline at the moment the job changes.

Where ScopeAccord fits

ScopeAccord is built for exactly this moment: the job changed in the field, and the paperwork needs to catch up before the work does.

Describe what you found by voice or text, the way you would explain it to the homeowner. The interaction is conversationally AI-native, helping organize the discovery, the repair scope, and the pricing into a reviewable change order. The legal document structure stays deliberately deterministic, using counsel-reviewed Wisconsin templates and verified running-total calculations, and photos can be attached so the record shows what you saw.

You confirm every detail before anything becomes final. ScopeAccord does not replace your judgment, licensing obligations, permit responsibilities, or attorney. It makes the organized record faster to create while the dust is still in the air.

Try ScopeAccord →

Learn more about ScopeAccord.