I don't read a submittal stamp as a paperwork status. I read it as a procurement instruction. A stamp on a transmittal may look like a simple disposition box, but on the ground it decides whether your subs can order steel, fabricate ductwork, or release a long-lead pump. Misread one and you ship procurement decisions on authority that never existed.
That misread is what turns a single stamp into a schedule problem. Repeated revision cycles on critical path items disrupt procurement and sequencing, and the damage compounds every time a team treats the stamp as paperwork instead of an instruction to act, wait, or stop.
This guide breaks down the standard approval stamp categories, what each one obligates the contractor to do next, where AIA and USACE conventions diverge, and why the gap between "Approved as Noted" and "Revise and Resubmit" is the line that costs you money.
Where the submittal stamp lives in the review cycle
A submittal stamp gates contractual work. Under AIA A201-2017 § 3.12.7, the contractor "shall perform no portion of the Work for which the Contract Documents require submittal and review of Shop Drawings, Product Data, Samples, or similar submittals, until the respective submittal has been approved by the Architect." Architect approval, typically indicated by the stamp, is what clears that work to begin.
Two stamps, two different authors
Two distinct stamps appear in the cycle, and mixing them up creates costly mistakes.
The first is the contractor's own approval stamp, applied before submission. AIA A201 § 3.12.5 requires the GC to review, approve, and stamp every submittal before transmitting to the architect, representing that it has verified materials, field measurements, and coordination with the Contract Documents (§ 3.12.6).
The second is the architect's review stamp, applied after review. This is the disposition that drives downstream action and it is the one procurement should be watching for.
The limited scope of review
The architect's review carries narrow legal weight, and that scope matters as much as the stamp itself. Per § 4.2.7 in the AIA A201 contract, the architect reviews "only for the limited purpose of checking for conformance with information given and the design concept expressed in the Contract Documents."
Everything else, including dimensions, quantities, installation methods, and equipment performance, stays with the contractor. Section 3.12.8 closes the loop, stating that the contractor "shall not be relieved of responsibility for deviations from the requirements of the Contract Documents by the Architect's approval." In other words, the stamp clears the work to begin, but it does not transfer responsibility for what the submittal actually contains.
The contractor still owns every deviation from the Contract Documents, approved or not.
Reading the submittal stamp categories correctly
Each stamp category triggers a specific contractor action, and the difference between them is the difference between proceeding and stopping. The same decision shows up under different names depending on the firm, so do not read the wording in isolation. Read each disposition by the work it authorizes next.
Approved / no exceptions taken / furnish as submitted
This is the cleanest disposition in the set. When the reviewer marks the submittal "Approved," "No Exceptions Taken," or "Furnish as Submitted," the contractor may move directly to procurement and fabrication. The design professional has found the submittal consistent with the contract documents and design intent, and no further review is needed. The California State University (CSU) specification states it plainly for its Action 1 equivalent: "Fabrication, manufacture, or construction may proceed providing submittal complies with Contract Documents."
Contractor action: proceed with procurement and fabrication. No resubmission.
Approved as noted / make corrections noted
The contractor may proceed only if it incorporates every written comment. Do not treat it as a clean approval or proceed without folding in the reviewer's corrections. In the same spec doc for CSU, their conditional-approval language states that fabrication may proceed only when the submittal complies with the architect's notations and the Contract Documents.
Contractor action: incorporate all noted changes before fabrication. No resubmission required.
Revise and resubmit
A "Revise and Resubmit" stamp withholds approval. The design professional has determined the submittal requires revisions and a full resubmission, which means a new review cycle starts from scratch. Generally, the contractor cannot move forward on procurement, fabrication, or construction until the revised drawings are resubmitted and come back with an acceptable mark.
Contractor action: correct every flagged issue and resubmit. Procurement, fabrication, and installation must wait.
When a resubmittal is required, Datagrid's Submittal-Builder Agent assembles submittal packages from cover page to final PDF, including corrected product data and drawings for owner or design team review.
Rejected / submit specified item
A rejection signals fundamental non-conformance and generally requires an entirely new submittal rather than a revision.
A common variant, "Submit Specified Item," means the contractor submitted a product that is not what the spec requires, so the package needs a compliant specified item rather than a substitution-style shortcut.
Contractor action: submit a new, complete, compliant submittal for the specified item. No work proceeds.
For record only / for information only
Record-only and information-only submittals go into the project record. No responsive action is expected from the reviewer, though these can still be returned for format non-compliance. The CSU specs document notes record submittals "will not be acted upon, stamped or returned to Contractor."
Contractor action: file for project record.
AIA vs. USACE: same decisions, different language
AIA and USACE conventions describe the same core dispositions, but they use different vocabularies, and crossing between them on a federal project is where teams run into issues.
AIA projects and CSI guidance lean on plain-language phrases like "Approved as Noted" or "Revise and Resubmit." USACE takes a more codified approach, using single-letter action codes entered into the Resident Management System (RMS) and governed by ER 415-1-10 ("Contractor Submittal Procedures").
A quick citation note, because I've seen this one cause issues on federal jobs: the regulation that governs submittal procedures is ER 415-1-10. A similarly numbered regulation, ER 415-1-15, looks like it could apply but actually covers weather-related time extensions. If you are writing a submittal policy or referencing the rule in correspondence, double-check that you are pointing to ER 415-1-10.
The mapping looks like this:
Concept | AIA / CSI | USACE / RMS |
Full approval | "No Exceptions Taken" / "Approved" | Code A , Approved as submitted |
Conditional, no resubmission | "Approved as Noted" | Code B , Approved, except as noted |
Conditional, resubmission required | "Approved as Noted, Resubmit" / hybrid resubmittal condition | Code C , Approved, resubmission required |
Rejection | "Rejected" | Code E , Disapproved |
Non-compliant acknowledgment | "Submit Specified Item" | Code X , Receipt acknowledged, does not comply |
Informational | "No Action" / "Not Required" | Code F , Receipt acknowledged |
Treat Code C as a project-specific hybrid approval-with-resubmission condition. Standard "Revise and Resubmit" remains a non-approval under the project-specific stamp language.
Beyond the side-by-side mapping, two specific divergences between AIA and USACE conventions are worth calling out, because both have a direct impact on how a stamp gets read in the field:
The word "approved" carries different weight. AIA and CSI phrasing qualifies it with terms like "as Noted" or uses labels such as "No Exceptions Taken," while USACE applies "Approved" across Codes A, B, and C, even though B and C still require corrections or a full resubmission.
USACE adds a Government Approval (GA) designation. For critical systems, USACE reserves approval authority for the government itself through the GA designation. There is no AIA equivalent, so teams moving from civilian to federal work can miss that an extra approval layer exists.
The takeaway is the same. Read the disposition by the work it authorizes, not by the word on the stamp. If your team treats a USACE Code B as a clean go because it contains the word "approved," you have just repeated the "Approved as Noted" mistake on a federal job.
The two stamps that quietly cost the most money
Of all the disposition pairs in this guide, "Approved as Noted" and "Revise and Resubmit" are the ones to watch. They sit one step apart on the form and a world apart in what they authorize:
"Approved as Noted" lets you proceed, provided you incorporate the comments.
"Revise and Resubmit" stops you cold.
The Massachusetts standard specification draws the line by stating "Approved as Noted" means work may proceed if it complies with the notations, while "Revise and Resubmit" means no work proceeds, including purchasing and fabrication. That single-step gap is where procurement decisions go wrong, and the consequences show up in two places: timing and reviewer alignment.
Procurement timing turns a misread stamp into a dollar figure
Proceed on a "Revise and Resubmit" and you risk ordering material that does not conform to the eventual approved version. Anything already fabricated becomes your exposure if the revised submittal comes back with further changes. CSU's specification (mentioned previously) states that any work performed before a fully approved submittal is done at the contractor's risk. On critical path items, multiple cycles can turn that exposure into sequence delay, and sequence delay is what reaches the schedule.
Multiple reviewers multiply the risk
The same package often passes through more than one reviewer, and that is where ambiguity compounds. When the architect, structural engineer, and MEP consultant each stamp the same package with different terminology, contractors end up with mixed signals on a single submittal.
Multiple stamps without clarifying language has potential to blur which professional is responsible for which portion of the work. CMAA's Submittal Register guidance describes the same multi-party bottleneck pattern. The architect responds quickly while the mechanical engineer is backed up, and the result is cascading delays on items that were never clearly cleared in the first place. One ambiguous stamp is a hazard; a stack of mismatched stamps on the same package is how those hazards compound.
What changes with agentic AI
Stamp decisions rarely cause the workflow failure I see. The failure usually occurs after the decision lands in the resubmittal workflow. A "Revise and Resubmit" that receives no corrected follow-up package can stall silently. Without named ownership, follow-up can become optional, and package assembly can turn into a second bottleneck after the technical comments are resolved.
Datagrid's agentic AI platform deploys AI agents to automate complex, multi-step workflows. The platform works across project files and connected systems. Package assembly can move from ad hoc effort to guided workflow.
The Submittal-Builder Agent executes the corrected resubmittal as a defined package-assembly workflow. People still make the calls. The agent completes the work between decisions.
How it works
Datagrid's Submittal-Builder Agent builds guided package assembly from cover page to final PDF in three practical ways:
Prepare: Generate cover-page fields and validate required identifying information for owner or design team review
Bundle: Assemble product data, drawings, and attachments into one organized package
Enforce: Enforce a consistent submittal structure across projects, instead of letting each team invent its own package format
Decision authority stays with your project team. The workflow gives the team a structured way to confirm that the corrected package is complete, organized, and ready for review before procurement clocks tick.
Standardize the handoff before procurement absorbs the delay
Picture a Project Executive overseeing a dozen active jobs. On nearly every one, the same blind spot appears. A "Revise and Resubmit" comes back, the technical comments get addressed in pieces, and nobody owns the clean package that has to return to the reviewer. The original stamp was read correctly. What stalled is the corrected package that should have followed.
The operating standard I would enforce is simple: no procurement decision moves on a stamp nobody has interpreted, and no resubmittal sits without a named owner. A structured package-building workflow makes both stick. Stalled resubmittals stop hiding inside scattered files and inboxes because every corrected package has a single, visible owner and a clear cutoff.
That is where the Submittal-Builder Agent closes the loop. Once the stamp is interpreted, the agent assembles the corrected handoff into a complete package before informal follow-up turns into rework, giving the Project Executive a structured way to confirm the resubmittal is moving instead of stalled.
