# Or-Equal or Deviation? Flag It So the Approval Actually Covers It

An approved stamp doesn't approve a deviation you never named. Flag it in writing and on the page, and ask for an answer that changes the contract.

An approved submittal doesn't approve a deviation you never named. Under the standard general conditions, the work still has to meet the contract documents unless you told the engineer about the difference in writing when you submitted, and they accepted it in a form that changes the contract. So name every deviation in two places, separate notice and a mark on the page itself, and ask for the answer you actually need.

Picture a fictional pressure transmitter package. Section 40 73 13 asks for a local LCD and ±0.065% accuracy. Your vendor quoted the same manufacturer's next model down: no display, ±0.075%, eight weeks sooner and a little cheaper. Close enough, you figure, and the datasheet goes in on page 40 with the model number highlighted.

The good ending is the engineer finds it. **Revise and Resubmit**, one comment: "Furnished model does not meet 2.03.B and 2.04.A." You lose a review cycle.

The bad ending is the engineer doesn't find it. The package comes back **Approved**, the transmitters go in, and at startup the owner's I&C tech asks why there's no display on any of them. You point at the stamp. They point at the general conditions, which say the stamp never covered a deviation you didn't name. Now you're buying twelve transmitters twice.

## Or-equal, substitution or deviation

Three different questions get filed under "close enough," and each one has its own door.

- **Or-equal or substitution.** You're supplying a manufacturer or product the spec doesn't name. That's a procedure in Division 01, often a separate request with its own deadline, and it's covered in [substitution requests and the or-equal clause](/learn/substitution-requests-and-or-equal).
- **Deviation.** Any departure from a requirement of the contract documents, whoever made the product. The named manufacturer's other model is a deviation. So is the right model with the wrong enclosure, output or liner.
- **Conflict in the documents.** The spec and drawings disagree, so nobody can tell what the requirement is. That's an RFI before it's a submittal: see [spec and drawing disagree](/learn/spec-and-drawing-conflict-rfi).

An or-equal can carry deviations too. Proposing an unnamed transmitter doesn't flag the fact that it also lacks the display. Each difference needs its own line.

## What the stamp covers, and what it doesn't

Read your own general conditions. On most jobs they're one of two families, and both say the same thing in different words.

**AIA A201-2017.** Section 3.12.8 says the work follows approved submittals, except the contractor isn't relieved of responsibility for deviations from the contract documents by the architect's approval unless the contractor specifically notified the architect of the deviation at the time of submittal, and then either the architect approved it in writing as a minor change in the work or a Change Order or Construction Change Directive authorized it. Section 4.2.7 says the architect reviews submittals "for the limited purpose of checking for conformance with information given" in the contract documents. Review is a check, not a guarantee that they caught everything you left out.

**EJCDC C-700 (2018).** The general conditions you'll see on a lot of water and wastewater work put it bluntly in Paragraph 7.16: with each shop drawing or sample, the contractor gives the engineer "specific written notice of any variations" from the contract documents, in a written communication separate from the submittal, and on a shop drawing, a specific notation on the drawing itself. C-700 also says submittals, approved or not, are not contract documents. EJCDC's own [article on deviations](https://ejcdc.org/shop-drawings-and-submittals-part-5-deviations-from-contract-requirements-by-kevin-obeirne-pe/) walks through how that plays out when a deviation is approved without notice.

Two details are worth reading in your own project's documents:

- **Which submittals the clause covers.** C-700's notice paragraph names shop drawings and samples. A transmitter datasheet is product data. Many 01 33 00 sections extend the deviation rule to every submittal; check yours, and flag product data anyway, because nobody wins an argument about a deviation by pointing out it was on a cut sheet.
- **How the notice has to be given.** Some sections want a separate letter, some a deviation box on the transmittal, some both. [Reading 01 33 00](/learn/reading-01-33-00) covers where it lives.

The practical rule falls out of both families: a deviation is only approved if you said it out loud and they said yes to that specific thing.

## Flag it in two places

C-700's two-place notice is a good habit under any contract, because each place catches a different reader.

**1. Separate notice, up front.** Check the deviation box on the transmittal, and put a numbered deviations list right behind it, before any product data. One line per deviation:

```
DEVIATIONS FROM CONTRACT DOCUMENTS
Submittal 40 73 13-001, Rev 0

D1  PIT-101 to PIT-112 (12 ea)
    Spec 40 73 13, 2.03.B: local LCD indicator required
    Furnished: no local display; indication at HMI only
    Reason: 14-week lead time on the display model
    Effect on other work: none
    Requested action: accept as a minor change (no cost or time change)

D2  PIT-101 to PIT-112 (12 ea)
    Spec 40 73 13, 2.04.A: accuracy ±0.065% of span
    Furnished: ±0.075% of span (datasheet p. 3, highlighted)
    Reason: same model as D1
    Effect on other work: none
    Requested action: accept as a minor change (no cost or time change)
```

When there are none, write "Deviations from contract documents: none." A blank box reads as "didn't check."

**2. On the page itself.** Cloud the value on the datasheet and tag it with the deviation number, "D2," so the engineer reading page 40 is sent back to the list, and the engineer reading the list can find the evidence in one flip. How to mark the rest of the sheet is in [how to mark up cut sheets](/learn/mark-up-cut-sheets).

The list does a second job: it makes you decide. Writing "Reason" next to a deviation you were hoping nobody would notice is a quick way to find out you should swap the product instead.

## Ask for an answer that sticks

A stamp on a submittal isn't a contract change. Under A201 the approval has to come as the architect's written approval of the deviation as a minor change, or a Change Order or Construction Change Directive. EJCDC's guidance is that an accepted deviation with no change in price or time is often documented with a Field Order, and one that changes price or time needs a Change Order.

So the last line of each deviation says what you're asking for:

- **No cost, no time, no effect on other work.** Ask for acceptance as a minor change or Field Order. Many engineers will note it on the return. If the return just says Approved with no mention of D1, send one line asking them to confirm D1 and D2 were accepted, before the transmitters ship.
- **It changes price or time.** Price it, and ask for a Change Order. If the product is cheaper, expect the owner to want a credit, and offer it before they ask.
- **It touches someone else's work.** A smaller panel, a different power draw, a signal another trade now has to land. Name the trade and the drawing in "Effect on other work," and expect a modification, not just a stamp. [When a review comment changes the work](/learn/when-a-review-comment-is-a-change-order) covers pricing the whole ripple.

File the answer with the revision it approved. Two years from now "why don't these transmitters have displays" should take thirty seconds to answer.

## On the resubmittal, flag what they didn't ask for

A201 Section 3.12.9 adds one more: on a resubmittal, you call specific attention to any revision other than the ones the architect asked for. Fixing comment 3 and quietly swapping the transmitter model in the same revision is the same buried deviation with a new revision number. Add it to the list, numbered, like everything else.

## How Submittal Kit handles this

The deviation you can't flag is the one you never noticed, and page 40 of a vendor datasheet is where those live. In Submittal Kit, link the submittal to its spec section and the [Spec Check](/help/spec-check) on the **Checks** tab reads every datasheet against that section, one row per requirement. A missing display comes back **Does not meet**, with the next action "Swap the product, or ask the engineer to accept the deviation," and a product named "or equal" that yours isn't comes back **Look at this**, so both show up before the package goes out instead of after.

Mark a row yourself with a note, such as "D1, see deviations list," and the mark survives re-runs. Add a **Spec Check Results** section in [Configure sections](/help/configure-sections) and the compiled package prints every requirement with your marks in place. The transmittal carries the **Deviations** boxes, **None** and **As listed**, and a Notes block for your statement. The deviations list itself is yours to write: add a custom upload section titled "Deviations," drag it right behind the transmittal, and drop your list in.

*Disclosure: I build [Submittal Kit](/). Your general conditions and Division 01 decide how a deviation has to be flagged and approved, and the list above works on letterhead.*

---
Submittal Kit · Field Guides · Updated 2026-11-09
Canonical: https://submittalkit.com/learn/flag-a-submittal-deviation
