Skip to main content

Is That Review Comment in the Spec? Trace It Before You Rework

Before you swap a part or add I/O for a review comment, find the paragraph behind it. Where requirements hide, and what to do when none exists.

Before you rework anything for a review comment, find the paragraph or drawing that requires it. Search the section, its addenda, the related sections, Division 01, the drawing notes and the referenced standards. Then sort each comment into one of three bins: the spec says so, the spec is silent, or the spec says otherwise. Only the first bin gets reworked on the spot.

Here's how it usually goes. A fictional instrumentation package comes back Revise and Resubmit. Comment 4: "Transmitters shall be the owner's standard manufacturer." Comment 7: "Provide 20 percent spare I/O, wired to terminals." Nobody argues with a red pen two weeks before the panel is due, so you swap eleven transmitters, add an I/O card and a row of terminals, and resubmit. Rev 1 comes back approved.

A month later someone actually reads Part 2. Your transmitter manufacturer was listed by name, with "or equal." The PLC section asks for 10 percent spare, not 20. The engineer didn't change the contract. You did, with your own money, because nobody asked which paragraph.

A comment is a requirement only if a paragraph is behind it

Submittal review checks your package against the contract. It doesn't write new contract. Under AIA A201-2017, submittals are not contract documents (3.12.4), and the architect reviews them "only for the limited purpose of checking for conformance with information given and the design concept" (4.2.7). A July 2026 post from Adams Leclair puts it plainly: reviewers are "generally not authorized to use the submittal review process to modify or add to those requirements." Your project's own conditions decide, so read them, but most follow the same idea.

The flip side hurts just as much. Plenty of comments have a paragraph behind them that you never read. Dispute one of those and you've burned a review cycle and told the engineer you skipped part of the book. So the job isn't to push back. The job is to look before you do anything.

Number every comment, then add one column

Transcribe every comment on the return as a numbered row, the way answering review comments lays out. Then add one column before anyone touches the panel: Paragraph. For each row, write the section and paragraph (or the sheet and note) that requires what the comment asks, with the words quoted. A number without the quote is a guess you haven't checked.

A blank in that column is the most useful thing on the sheet. It tells you which comments to hold.

Where the paragraph hides

Reviewers rarely cite the paragraph they're thinking of, and it's often not in the section you submitted against. Look in this order:

  • The whole section, all three parts. Spare parts, testing and warranty demands often sit in Part 1 Quality Assurance or Part 3 Execution, not Part 2. See how to read a spec section.
  • Addenda. The paragraph you priced may have been rewritten. Read every addendum that touches the section, or the conformed copy if there is one.
  • Related sections. Part 1 lists them. Spare I/O percentages usually live in the PLC hardware section, not the panel section. Instrument manufacturers can live in a separate instrument section.
  • Division 01. Product requirements, owner standards, spare parts, warranty and training. An owner's standard products list here can quietly govern every section in the book.
  • The drawings. General notes, legends and schedules. "All pressure transmitters shall be..." on an instrument legend sheet counts as much as a spec paragraph.
  • Referenced standards. A standard the section incorporates is part of the requirement, to the extent the section adopts it.
  • Answered RFIs and modifications. An RFI answer or change order on the job may already have settled the question.

Search the spec PDF for the reviewer's own words ("spare", "standard", the manufacturer's name) and for the equipment tag. That one search finds most of the paragraphs a page-by-page read misses.

Three bins, three responses

Every comment lands in one bin, and the bin decides what you write back.

  • The spec says so. Comply, and cite it: "Complied per 40 61 13 3.03.B; wire numbers added at both ends, see E-04." The reviewer checks it in ten seconds and the row closes.
  • The spec is silent. Don't rework yet. Say where you looked: "No requirement found in 40 61 13, 40 63 43, Division 01 or sheets I-001 to I-004. Please cite the paragraph or direct the change." If the comment changes cost or time, use the project's RFI or notice path. When a review comment changes the work covers notice and pricing.
  • The spec says otherwise. The comment contradicts a paragraph. Quote both and ask for direction: "40 72 13 2.01.A lists the submitted manufacturer by name, or equal. Comment 4 requests a different manufacturer. Please confirm whether this is a change." If the book has two answers of its own, that's a spec and drawing conflict, not a review comment.

The middle bin is where the money is. A silent comment answered with a question costs a paragraph. A silent comment answered with rework costs the part, the labor, the drawing revision and the margin on the job.

Rework only what you can cite

Once the column is filled, the rule for the shop is short: touch what has a paragraph, hold what doesn't. Rework the cited comments now. Leave the held items in the package as submitted and mark their rows pending, with the RFI or notice number, so the reviewer sees the question is in their court.

Rev 1 then goes out with a response letter where every row carries a citation or a question. That letter is also your record. If a held item becomes a change, the comment, the paragraph you searched and the date you asked are all on one page.

Swapping only the sheets that changed is in revise and resubmit without rebuilding.

How Submittal Kit handles this

Finding the paragraph is still yours. Submittal Kit doesn't decide whether a comment is a requirement. What it does is keep the answer from getting lost once you've found it. Each returned comment is a row in the submittal's Comment Response Log, and the citation you type in the response prints in the resubmittal: item number, their comment, your response, status. Before you mark the resubmittal submitted, a checklist lists every comment that still has No response yet, so a held row can't slip out unanswered.

When you're checking whether a paragraph changed, open the section under Specifications. A section an addendum touched opens with Changed by and the addendum's name, showing each requirement it added, removed or changed with the old and new wording. See Upload specifications. A silent comment becomes an RFI with its spec and drawing references on the page, and its number goes in the response row.

Disclosure: I build Submittal Kit. The Paragraph column works in a spreadsheet too.

Where this lives in Submittal Kit

Want to see your BOM become a reviewable package?

Bring a CSV or Excel BOM, or use a demo project. You'll see the proposed matches before anything changes and review the compiled PDF before issue.

Book a walkthrough