Every contractor writes exclusions. They go at the bottom of the bid, below the price, usually in smaller type. They are the last thing written on bid day and the first thing challenged after contract award.

Most exclusions read like this: “Testing and inspection excluded.” Or “Coordination items excluded.” Or “Mock-ups not included.” The estimator who wrote them knew what they meant. They had just finished reading the spec section where the requirement appeared. The exclusion felt specific enough in the moment because the context was fresh.

Six months later, the owner’s project manager pulls the bid letter out of a file and reads “coordination items excluded” with no memory of what the estimator was looking at when they wrote it. The PM asks a simple question: which coordination items? The contractor points at the spec. The PM points at the contract. The exclusion does not name a section, does not name a requirement, and does not name a scope item. It is a general statement that could mean anything — and in a dispute, a general statement means nothing.

What Happens When an Exclusion Has No Citation

A contract dispute over excluded scope comes down to what the documents say. The contractor’s bid, the owner’s acceptance, and the contract documents form the agreement. When the contractor’s bid includes an exclusion, that exclusion becomes part of the contract — but only if it is specific enough to be enforceable.

An exclusion that says “firestopping excluded” without naming the spec section is ambiguous. The owner argues the contractor should have known that firestopping was part of their scope because Division 07 84 00 assigns it to the trade that creates the penetration. The contractor argues they excluded it in writing. The arbitrator reads both positions and asks the contractor to show where in the bid the specific requirement was identified and rejected. The contractor cannot point to a section number. The exclusion fails — not because firestopping was in their scope, but because the exclusion was not specific enough to prove they identified it and priced around it.

An exclusion that says “firestopping of mechanical penetrations excluded per Section 07 84 00, paragraph 1.3, which assigns penetration firestopping to the trade creating the penetration — mechanical penetrations are created by Division 23 and firestopping of those penetrations is not included in our Division 23 scope” tells a different story. It names the section. It names the paragraph. It names the scope assignment. It names the trade. An arbitrator reading that exclusion knows exactly what the contractor identified, exactly why they excluded it, and exactly where in the spec the requirement lives. That exclusion holds because it proves the contractor read the document and made a deliberate decision.

The Mirror Image Rule

Contract law has a principle that works in the contractor’s favor when exclusions are properly written. When a contractor submits a bid with specific exclusions, and the owner accepts that bid, the exclusions become part of the contract. The acceptance mirrors the offer — including the limitations the offer contained. This is the Mirror Image Rule, and it is the legal mechanism that makes a cited exclusion binding.

But the rule only works when the exclusion is clear enough that the owner can be said to have accepted it knowingly. A vague exclusion — “testing excluded” — does not give the owner enough information to understand what they are accepting. A specific exclusion — “third-party air barrier testing per Section 07 27 00, paragraph 3.5 excluded; testing to be performed and paid for by owner per Section 01 45 00, paragraph 1.3” — gives the owner a clear statement that they either accept or reject before signing.

The specificity protects both sides. The contractor knows what they are not carrying. The owner knows what they need to assign elsewhere. When both sides can point to the same section number and the same paragraph, the exclusion does its job. When neither side can point to anything specific, the exclusion becomes a negotiation rather than a contract term.

What a Defensible Exclusion Looks Like

Every exclusion that will survive a challenge has three elements.

The section number. Not the division, not the general topic — the six-digit CSI section number where the requirement appears. Section 07 84 00, not “firestopping.” Section 01 45 00, not “testing.” Section 09 06 00, not “mock-ups.” The section number proves the contractor found the requirement in the document.

The specific requirement. What does that section say? “Penetration firestopping at all fire-rated assemblies” is the requirement. “Testing of installed air barrier by independent third party” is the requirement. “Full-size mock-up panel reviewed and approved prior to material ordering” is the requirement. Naming the requirement proves the contractor understood what they were excluding.

The reason it is excluded. Why is this not in your scope? Because the spec assigns it to another trade. Because the spec is silent on who pays for it. Because the requirement conflicts with another section. The reason does not need to be elaborate. It needs to exist. “Excluded per scope assignment in Section 23 03 00 which assigns firestopping to the trade creating the penetration” is a reason. “Excluded” is not.

The Five Minutes That Save Five Figures

Writing a defensible exclusion takes five minutes longer than writing a generic one. The estimator has the spec open. The section number is on the screen. The requirement is in the paragraph they just read. The only additional work is writing down what they are already looking at — the section, the requirement, and the reason.

Generic exclusions feel like they save time on bid day. They cost time during construction when the scope dispute arrives and the contractor has no documentation to support their position. The five minutes spent writing the section number into the exclusion on bid day replaces the five weeks spent arguing about scope after the contract is signed.

The spec says what it says. The exclusion that cites the section says what the contractor decided to do about it. The exclusion that does not cite anything says nothing at all.