First-pass submittal review

The job

The project manager at a US general contractor doing about $5–10M a year — often the owner wearing a PM hat, or one person who also writes RFIs, walks pay apps, and answers the superintendent at 6 p.m. There is no project engineer whose only job is the submittal log. Packages arrive as PDFs in email. If the first pass is slow, the package sits, the sub buys the wrong thing, or the architect gets an unread catalog dump with a rubber stamp.

This job is use an agent, not build a model. The PM already has a desk: email, the spec PDF, the submittal PDF, and a spreadsheet log (Excel, or whatever log they already keep). The agent sits in the compare-and-draft step only. It does not stamp. It does not send.

Without an agent the work is still the same: open the spec section, open the package, check that the product matches what was specified, write comments, stamp, log, forward.

What a submittal is. Official AIA Contract Documents guidance on A201–2017: the term “submittal” is used throughout A201 but is not separately defined. Section 3.12 covers the three types the GC actually sees:

• Shop Drawings — drawings, diagrams, schedules, and other data specially prepared for the Work to illustrate some portion of it.
• Product Data — illustrations, standard schedules, performance charts, instructions, brochures, diagrams, and other manufacturer information furnished to illustrate materials or equipment. Usually a catalog cut the contractor marks up (model, options, finishes).
• Samples — physical examples that illustrate materials, equipment, or workmanship and set the standard by which the Work will be judged.

AIA is explicit: Shop Drawings, Product Data, Samples, and similar submittals are not Contract Documents. Their purpose is to show how the contractor proposes to conform to the information given and the design concept in the Contract Documents. A submittal is not a change order. Official CSI practice (O’Beirne on CSI’s blog, quoting A201 § 3.12.4) says the same: an approved shop drawing that “improves” the spec does not rewrite the contract unless a modification is issued.

This job is the contractor’s review, not the architect’s. A201 § 3.12.6 (AIA, Mike Koger, AIA, Esq.): by submitting, the Contractor represents to the Owner and Architect that it has (1) reviewed and approved the package, (2) determined and verified materials, field measurements, and field construction criteria, or will do so, and (3) checked and coordinated the information with the Work and the Contract Documents. AIA’s counsel is blunt: a contractor who merely receives and stamps a sub’s package without that independent evaluation has not complied. The contractor’s review happens immediately before the architect’s. Rubber-stamping is the failure mode this job exists to catch.

The architect’s review is a different seat. Official AIA pairing of B101 and A201: the architect reviews shop drawings, product data, and samples for design intent, not means and methods. A201 § 4.2.7 / B101 § 3.6.4.2: limited purpose of checking conformance with information given and the design concept; not dimensions, quantities, or installation, which remain the contractor’s. AIA’s republished CCA primer (“According to Hoyle”) quotes A201 § 3.12.5: submittals not marked as reviewed and approved by the Contractor may be returned by the Architect without action. A201 § 3.12.7: no portion of the Work that requires a submittal proceeds until the Architect has approved it. A201 § 3.12.8: Architect approval does not relieve the Contractor of deviations from the Contract Documents.

Where the spec lives. CSI MasterFormat is the North American numbering for project manuals. Division 01 is general requirements (procedures). Technical work sits in later divisions. CSI SectionFormat puts each technical section in three parts; Part 1 – General is where that section lists required submittals. CSI’s published practice (O’Beirne) names Section 01 33 00 – Submittal Procedures as the project-wide rules (numbering, transmittals, review cycles). AIA’s Hoyle primer: MASTERSPEC tracks A201 and splits action submittals (architect must act) from informational submittals (for the record). CSI SectionFormat’s four types: action, informational, closeout, and maintenance materials. This job’s first pass is almost always an action package — product data, shop drawings, samples — before buy-out.

Stamps. Typical action dispositions in CSI practice, written to match AIA A201 / B101’s verb “approve”:

• Approved — appears consistent with the Contract Documents; procurement may proceed.
• Approved as Noted — approval is conditioned on complying fully with the written comments; failure to comply typically nullifies it.
• Revise and Resubmit — not an approval; needs detailed written comments naming the non-compliance.
• Rejected — not close; incomplete packages often land here too.

AIA’s Hoyle primer lists the architect’s options as approved, approved as noted, revise and resubmit, no action taken, or submittal not required. CSI warns against hybrid “Approved as Noted / Resubmit” as vague. The GC PM’s first-pass stamp is the contractor stamp under § 3.12.6 — often “return to sub” — before the package ever goes downtown.

Why a $5–10M GC still does this. Sending the package is a representation. Work that needs a submittal cannot start until the architect acts. A late or wrong first pass is a buy-out problem, a resubmittal cycle, or a product in the wall that is not what was specified. A $5–10M shop does not have a PE reading every catalog. They have one PM and a PDF. That is why the draft comparison is the job.

Use

This is a use workflow. You do not train a model. You do not ask it to invent a spec paragraph, a UL listing, or a field dimension. You give it the section and the package, you get a draft, you stamp.

1. Identify the section. Read the transmittal. The number should be a MasterFormat section (for example 08 71 00), not “doors.” If the package has no section, send it back to the sub before you involve an agent.
2. Open the issued spec, not memory. Pull that section from the project manual you actually contracted — including addenda that revised it. Pull Division 01 / 01 33 00 for procedure (how many copies, how to number, substitution rules) only when the fight is procedure, not product.
3. Open the package. Product data with the model circled; shop drawings with a title block; samples as photos plus the cut sheet if that is all you have. Note the revision / cycle (A, B, resubmittal).
4. Feed the agent only those files. Spec section PDF + submittal PDF + your comment template (Word, email, or the log you already keep). Prompt shape: compare this package to this section only; quote paragraph numbers from the uploaded section; list matches, misses, and open questions; suggest a contractor disposition (approved / approved as noted / revise and resubmit / rejected); leave a line blank if the files do not support it; do not cite a paragraph that is not in the upload; do not treat a substitution as an or-equal unless the section says so.
5. Human edit before the sub or the architect sees it. Open the spec and click every cited paragraph. Strike invented article numbers. Check the title block and revision stamp yourself — clouds, deltas, “VOID,” and “supersedes” are easy for a model to skip. Confirm the circled model is the one in Part 2, not a nearby catalog cousin. Write the field-measurement and coordination notes yourself; those are the § 3.12.6 representation.
6. Stamp. Name, date, disposition. The package is not reviewed until a person who owns the job stamps it.
7. Log and send the way you already do. Update the Excel (or existing) log: section, number, cycle, date in, date out, disposition. Email the sub or the architect only the stamped package. Do not stand up a new vendor for this job.

Expected shape of the gain: less time staring at a 40-page catalog next to a spec you have not opened in three weeks. That is not “the model approved the door hardware.” There is no published, independent hours-saved or accuracy number for a $5–10M GC first-pass submittal review that this page will invent. Time a week of your packages (draft + your edit vs reading cold) before you change anything you pay for.

Build

A general-purpose model that can read PDFs can draft a comment sheet from a spec section plus a product-data or shop-drawing package. Precise code listings, stamped revisions, and physical samples need a person. Do not treat the draft as the architect’s review, and do not bid or buy from the raw comments.

A workable v1: a prompt template that returns a comment table — spec paragraph (quoted from the upload), what the package shows, match / miss / unknown, suggested contractor disposition — run per section and per review cycle. Keep the transcript with the submittal file so comments are auditable. Require the model to say “not in the uploaded section” instead of filling a gap.

Do not build a custom classifier this quarter. Do not fine-tune. The issued spec and this package are the only corpus that matters.

Deploy

1. Pick three recently closed packages you already stamped and would still defend — one clean product-data cut, one messy catalog, one resubmittal.
2. Run the agent on the same spec section + package. Time upload, draft, and your edit.
3. Diff the draft against the comments you actually sent. Record invented paragraphs, missed revision stamps, missed circled-model errors, and whether your edit caught them.
4. Decide using a rule set in advance: every cited paragraph must exist in the section; no draft leaves the trailer unstamped; if the model invents a paragraph on the clean package, it is not ready.

Use your project manual, not a vendor demo spec. Keep the workflow only if the stamped comments are still something you would send to the architect.

Manage

What “good” looks like

• A named human stamps every package before it goes to the sub or the architect.
• Comments quote the issued spec section (plus addenda), not a generic MasterSpec memory.
• Raw model text is never emailed to the architect, owner, or sub.
• Substitutions are not approved in the submittal stream; they follow whatever substitution article Division 01 requires.
• Resubmittals include the prior stamped comments, not a fresh compare against a blank section.
• The log (Excel or the app you already pay for) records section, cycle, dates, and disposition. AIA G712 is the architect’s shop-drawing log — receipt, referrals, action, return date — useful as the shape of a chronology, not a form you must buy.
• If you already have a submittal-log app, the agent drafts into that. This page does not sell a new one.

Who owns the seat

The PM / owner-PM owns the contractor review. On a $5–10M GC that is one person and the laptop they already use. The superintendent does not stamp product data. The architect’s B101 review is their record, not a substitute for yours. An agent does not become the “approved by Contractor” signature in § 3.12.6.

When to skip the agent

• Physical samples and mockups. Color, texture, and workmanship are not a PDF problem.
• Delegated design — sealed drawings, calculations, or certifications from the contractor’s licensed design professional. Official AIA: A201 § 3.12.10 requires an appropriately licensed professional to sign and seal that work; the architect’s review is still only design-concept conformance; responsibility stays with the contractor and that professional. Format a transmittal header if you want; do not let a model “check the calcs.”
• Fire-rated assemblies, life-safety listings, and anything you cannot verify without the listed standard in front of you. Open the listing yourself.
• A substitution slipped into a shop drawing. AIA’s Hoyle primer: treat it as nonconforming and point at the substitution procedure; do not approve it as if it were the specified product.
• Means-and-methods or safety plans. CSI practice: those are the contractor’s, and routing them as action submittals muddies who owns them. Do not ask a model to “approve” a lift plan.
• You did not attach the issued spec section. Do not ask a model to remember MasterSpec.
• The log is already a five-minute habit and reading is not the bottleneck. Leave it.

How to stand it up this quarter

Use the model you already have access to. Drop in last week’s Section 09 91 00 (or whatever you actually closed) plus the product-data PDF plus your comment headings. Edit, click every citation, stamp. Repeat on a live package. Keep the workflow only if the stamped comments are still something you would send. Do not buy a submittal-management product to complete this job.

Source notes

Tools are citations, not new brand pages. Do not invent vendor homepages. This page does not create a Procore, Submittal Exchange, PlanGrid, or any other submittal-log vendor listing.

• AIA A201–2017 — keystone general conditions for the Conventional (A201) family. Shop drawings / product data / samples live in § 3.12; architect action in § 4.2.7. Official summary also notes § 3.12.10.2 (contractor’s design professional must certify delegated-design work).
• AIA § 3.12.6 contractor review — submitting is a representation that the contractor reviewed, approved, and coordinated. Rubber stamp is non-compliance.
• AIA types of submittals — shop drawings, product data, samples; not Contract Documents; architect review is design concept (B101 § 3.6.4.2). Pairing: B101 + A201 during construction. Delegated design: A201 § 3.12.10.
• AIA G712–1972 — architect’s log of receipt, consultant referral, action, and return. Chronology, not the GC daily tool.
• CSI MasterFormat — shared section numbers. SectionFormat: three-part section, Part 1 lists submittals. CSI practice: definition and purpose; four types; review stamps (Approved / Approved as Noted / Revise and Resubmit / Rejected). Procedure section commonly specified as 01 33 00 – Submittal Procedures.
• Excel, email, PDF — log, receive, read. If they already have a submittal-log app, the agent drafts into that. No new vendor page on this site.

Process primer (AIA CCA, republished 2025): According to Hoyle: The Submittal Process — contractor prepares, reviews, stamps, then the architect acts; unreviewed packages may be returned without action.

Watch-outs

• Invented spec paragraphs. Models write fluent “Section 2.3.B requires…” citations that are not in the PDF you uploaded. That is the same failure mode as legal citation hallucination: Dahl, Magesh, Suzgun & Ho, Large Legal Fictions, 16 J. Legal Analysis 64 (2024) (arXiv:2401.01301, doi:10.1093/jla/laae003) — public LLMs, asked verifiable questions about federal cases, hallucinated between 58% (GPT-4) and 88% (Llama 2) of the time, and often could not tell. Those percentages are legal-case questions, not submittal comments; do not import them as a construction accuracy rate. Do import the habit: every paragraph number in the draft is unverified until you open the section. Require quotes from the upload. Blank is honest; a confident fake article is not.
• Missed stamped revisions. Models read running text more reliably than a small revision stamp, a cloud, a delta, a “VOID” overlay, or a title-block cycle. A resubmittal that still shows the old sheet 3, or a spec addendum that superseded Part 2, is easy to miss. Check the revision block yourself. Feed the current issued section and the prior stamped comments, not only the first-cycle PDF.
• Unsigned AI to the architect or the sub. Fluent, late, and wrong is worse than a short stamped note. A201 § 3.12.6 is a representation by the Contractor. An agent-drafted email is not that representation. Do not let the model send.
• Wrong seat. This is the GC’s first pass. It is not B101 § 3.6.4.2. Do not write architect-voice comments (“no exceptions taken to design intent”) on a contractor review, and do not tell the sub the package is “approved by the architect.”
• Substitution theater. A shop drawing that swaps the specified product is not an or-equal unless the section says so. Hoyle: reject as nonconforming and run the substitution procedure. A model that “approves as noted — use Manufacturer B” has just rewritten the Contract Documents.
• Delegated design and listings. Sealed calcs and UL/FM fire assemblies are not catalog-cut comparisons. Skip the agent or use it only to format the transmittal.
• Samples. A photo of a chip is not a sample. AIA’s definition is a physical example. Do not stamp color from a screen.
• Do not replace the PM. The agent drafts the comparison. The PM still owns coordination, field measurements, the stamp, and the representation in § 3.12.6.

Verdict

Yes — a $5–10M US GC should run this job this quarter if submittals already arrive as PDFs, the bottleneck is reading the spec against the package, and a person will still stamp every comment. Use an agent to compare the package to the issued spec section and draft comments; the PM approves or rejects. Skip this quarter if you expected the model to review samples, sealed delegated design, or fire listings; if you were about to email raw draft comments to the architect; or if you were about to buy a submittal-log product you do not already have. Do not publish this page as a vendor listing.