The Spec vs Field Reality Decision Tree

Why this matters

The plan said one thing. The wall, the slab, or the existing system says another. This gap is one of the most common ways a clean job turns into a fight: you build exactly what the spec told you and it turns out the spec was wrong, or you "fix" it on your own judgment and the engineer, the GC, or the inspector says you deviated. Both ends of that lose. The skill is knowing when you may adjust on your own, when you must stop and get a ruling, and how to document either way so the gap never lands on you.

Start here: is anyone in immediate danger or is something about to be hidden

Before you weigh paperwork, check two things.

• If the spec as drawn would create a hazard (an unsafe clearance, an undersized service, a venting or structural problem), stop. Do not build a hazard because a drawing told you to. Flag it to whoever owns the design before you proceed, in writing.
• If the conflict is about to be permanently covered (poured, closed in, tiled over), stop before the cover-up. A discrepancy you build into a closed wall is one you will be tearing back open. Resolve it while it is still visible.

Everything below assumes no hazard and no imminent cover-up. Now you can think.

Step 1: name what kind of gap this is

Sort the discrepancy into one of three buckets. They get different moves.

• A dimensional or field-condition gap: the spec assumed a measurement, a clearance, or an existing condition that the real building does not match. Common and usually solvable.
• A code or safety gap: the spec, built as drawn, would violate code or be unsafe. This is never yours to silently override, but it is also never yours to silently build.
• A scope or intent gap: the spec is buildable, but doing it as drawn clearly is not what the customer or designer actually wanted. This is a communication problem, not a technical one.

Name the bucket out loud before you decide. Most bad calls come from treating a code gap like a dimensional one.

Step 2: decide who owns the answer

The question that settles most of it: does changing this change cost, code compliance, or another trade's work?

• If it changes none of those - a minor field adjustment, a fitting routed the obvious way, a fastener pattern the situation dictates - you generally adjust to field conditions using standard practice and note what you did and why. This is the day-to-day judgment you are paid for.
• If it changes any one of those - the price goes up, the code answer is unclear, or it forces another trade to move - it is not yours to decide alone. Stop and get a ruling from whoever owns that piece: the designer or engineer for code and intent, the GC or owner for cost and scope, the inspector for an ambiguous code call.

The trap is the middle ground: a change that "seems small" but quietly adds cost or moves someone else's work. Treat those as decisions to escalate, not adjustments to make.

Step 3: get the ruling the right way

When you escalate, do not just raise a problem. Bring a recommendation.

• State the conflict in one sentence: what the spec says, what the field shows, why they cannot both be true.
• Offer the buildable option you would recommend and what it affects (cost, timeline, other trades).
• Ask for the decision in writing. Email, a marked-up plan, a signed change order, an inspector's note. A verbal "yeah, just do it" from a GC is not protection when the owner asks later who authorized it.

A tech who shows up with the problem and the fix already framed gets a fast yes. A tech who shows up with only the problem gets a delay and a reputation for being hard to schedule.

Step 4: if you genuinely cannot reach anyone

Sometimes the slab truck is here and the engineer is not answering. Do not guess on anything that changes code, cost, or another trade.

• If you can keep working without committing the disputed piece, do that and leave the conflict point reversible.
• If the disputed piece is the only thing blocking progress, the right answer is usually to hold that portion rather than build something you may have to undo. A short delay is cheaper than a redo plus a fight over who authorized it.
• Document the attempt: who you tried to reach, when, and what you did in the meantime.

Recap: the order to follow

1. Hazard or imminent cover-up? Stop and flag before proceeding.
2. Name the gap: dimensional, code/safety, or scope/intent.
3. Does it change cost, code, or another trade's work? If no, adjust and document. If yes, escalate.
4. Escalate with a recommendation and get the answer in writing.
5. Cannot reach anyone? Keep the disputed piece reversible and document the attempt.

The judgment to bank: you are paid to adjust to field reality, not to silently overrule the people who own cost, code, and scope. Decide what is yours, escalate what is not, and put the answer in writing every time. Then the gap between the spec and the building is never the thing that becomes your liability.

References

• Trade-standard practice on field adjustments versus design changes
• Authority Having Jurisdiction (AHJ) for ambiguous code interpretations
• Applicable building, electrical, mechanical, and plumbing codes for the work
• See related: The Code Official Gray Area (decision tree); The Multi-Stakeholder Job: Who Decides (decision tree)