USACE construction submittals run on a coded system that affects whether work can proceed, how approvals are documented, and how submittal management may appear in later performance documentation.
I see the same failure pattern when commercial teams move into federal work. They assume USACE submittal codes map cleanly to AIA workflows, and they do not.
The USACE submittal codes, from transmittal action codes A through E to the GA/FIO classification system, operate under federal regulations with no exact one-to-one equivalent in common AIA commercial workflows. The code system, ENG Form 4025 field requirements, and AIA workflow mismatches determine whether federal submittals move forward or come back.
Why federal construction runs on a different code system
Federal regulation governs USACE submittal actions on construction contracts. Four structural realities explain why USACE codes operate differently from AIA workflows:
Dual-layer quality structure. FAR Part 46 mandates that the contractor handles QC and the government handles QA on construction contracts. This structure exists because the government is both owner and regulator, so approval points require government oversight.
Agency-specific quality standards. USACE enforces standards through ER 415-1-10 that exceed common private-sector practice.
Distinct roles with defined authority. The contractor must employ a CQM-certified QC manager who reviews and certifies every submittal before transmission. The government side includes the Contracting Officer's Representative (COR) and a QA team with independent review authority.
Direct government enforcement power. Unlike commercial work where the architect often mediates between owner and contractor, on USACE contracts the government may reject installed work and withhold payment for materials lacking required approval. The government's decision recorded in RMS is the documented disposition used in the submittal process.
These four realities are why USACE codes carry contractual weight that AIA workflows do not, and why the specific documents and systems that operationalize them deserve their own look.
The governing documents and systems behind USACE submittals
Four governing references define how USACE submittal codes operate in practice:
ER 415-1-10 governs submittal workflows.
UFGS 01 33 00 defines specification-level requirements and includes the payment enforcement clause, which states, "Payment for materials incorporated in the work will not be made if required approvals have not been obtained."
ENG Form 4025 is the standard transmittal cover sheet that carries the contractor's certification and the government's action code for every submittal line item.
RMS is the government-mandated tracking system used for submittal administration and payment-related workflow documentation.
CPARS evaluations may document submittal management deficiencies, and those evaluations remain visible for six years on construction contracts per FAR 42.1503. Every ENG Form 4025 transmittal also carries a Buy American Act and Trade Agreements Act compliance attestation with no AIA parallel.
USACE transmittal action codes: what A through E mean for your next step
Every government action code is entered in Column i of ENG Form 4025. The letter the reviewer enters there (A, B, C, D, or E) represents the government's formal disposition for that submittal line item and tells the contractor exactly what to do next: proceed, comply with comments, resubmit, wait for correspondence, or start over.
Codes A and B: you can proceed
Code A (Approved as Submitted) is unconditional. Proceed with fabrication, procurement, or installation immediately.
Code B (Approved, Except as Noted, Resubmission Not Required) closes the action but carries a binding obligation. Comply with every annotated comment before implementing the submitted material. Skipping those comments is a contract noncompliance even though the submittal is formally complete.
Code C: the code that burns commercial contractors
Code C (Approved, Except as Noted, Resubmission Required) requires resubmission before work begins. The word "Approved" in the code causes confusion. RMS status reads "Resubmit." The contractor must address all reviewer comments and resubmit with a decimal-extended transmittal number (e.g., 033000-001.1). A subsequent Code A or B is required before any work begins.
In AIA practice, "Make Corrections Noted" is a closed action, the functional equivalent of USACE Code B. Code C has no AIA equivalent. It is simultaneously labeled "approved" and requires resubmission.
Codes D and E: separate return and full disapproval
Code D (Returned by Separate Correspondence) applies to primary contract plans like the Accident Prevention Plan or QC Plan. Await formal government correspondence before acting.
Code E (Disapproved) carries no approval of any kind. The contractor must review comments, select a fully compliant product or method, and prepare a new submittal from scratch.
How GA vs. FIO classification controls payment on USACE submittals
Every submittal on a USACE Design-Bid-Build contract is classified as either Government Approved (GA) or For Information Only (FIO). This classification directly affects whether required approval must be obtained before payment for installed materials.
GA submittals trigger the 30-day review clock
A "G" designation in the specification section means the item requires government approval. GA submittals receive government review within 30 calendar days, with an additional 14 days for proposed variations. UFGS 01 33 00 states explicitly, "Payment for materials incorporated in the work will not be made if required approvals have not been obtained."
FIO still requires contractor QC review
Any submittal item not tagged with a "G" in the SUBMITTALS paragraph of its UFGS specification section defaults to FIO classification.
For FIO submittals, government review is generally limited compared with GA items, while ER 415-1-10 requires the contractor's QC manager to review all FIO submittals for contract compliance. FIO uses a different accountability structure.
ENG Form 4025: the fields that get packages returned
ENG Form 4025-R is the standard USACE transmittal cover sheet. Incomplete forms come back without review. The contractor completes Section I (Fields 1 through 17). The government completes Section II after review.
Errors most often appear in six ENG Form 4025 fields:
Field 2 (Transmittal Number): Format is the specification section number followed by a dash and sequential number (e.g., 033000-001). Resubmittals add a decimal extension (033000-001.1). RMS numbering automatically provides the next transmittal number.
Field 7 (Specification Section Number): One transmittal covers one specification section. ER 415-1-10 prohibits consolidating items from different sections on a single form.
Field 11 (SD Code): The USACE SD-01 through SD-11 taxonomy has no AIA equivalent. Misclassifying SD-06 (Test Reports) as SD-03 (Product Data) can route test results to the wrong reviewer.
Field 12 (Specification Paragraph): References the exact paragraph requiring the submittal. Incorrect references delay review.
Field 14 (Contractor QC Action Code, Column h): The contractor enters G (Government Approval Required), I (Information Only), or V (Variation). Marking "V" obligates you to explain the variation in the Remarks block. Per the CQM Study Guide, if a variation is not identified on ENG Form 4025-R, the government may rescind any inadvertent approval.
Field 17 (Contractor Signature): Unsigned transmittals are returned without review. The signature certifies that submitted items comply with contract drawings and specifications.
Where USACE submittal codes break for commercial teams carrying AIA habits
Commercial contractors entering USACE work carry AIA habits that generate predictable failures.
Form and workflow errors
Three AIA habits get USACE packages bounced before a reviewer ever opens them:
The first is bundling multiple specification sections onto a single transmittal. USACE requires one transmittal per spec section, so a bundled package is returned without review.
The second is leaving Column h (the contractor's QC action code) blank. AIA has no equivalent field, so commercial contractors often skip it, and RMS rejects any transmittal that arrives without it filled in.
The third is using project-wide sequential numbering (001, 002, 003 across the whole job) instead of section-specific numbering (033000-001, 033000-002 within each spec section). It feels like a minor formatting choice up front, but at closeout the project-wide numbers don't line up with how RMS organizes the submittal register, and the linkage between your records and the government's record breaks.
Classification and system-of-record errors
Two AIA habits create the biggest classification and record-keeping failures on USACE work.
The first is misclassifying submittals. Submitting GA items as FIO, often because AIA routes everything through the architect, means work gets installed without the required government approval. That single misclassification can trigger compliance findings, withheld payment, and a negative entry on the performance record that follows the contractor for years.
The second is relying on the wrong system of record. Commercial project-management or document-control platforms are not the governing record on USACE contracts. RMS is. When payment disputes or schedule claims come up, the government looks at what RMS recorded rather than what your commercial platform says, so any transmittal that never made it into RMS effectively did not happen.
Schedule and record consequences
The most common scheduling mistake is building the project schedule around a 14-day review window, which is the AIA norm, when USACE contracts give the government 30 calendar days to act. The Partnering Playbook flags this as a high schedule risk whenever the first submittal also comes back without approval, because the contractor is now two weeks short and facing a resubmission cycle.
The downstream cost is real. A DoD IG audit of four military construction (MILCON) projects originally valued at $248.5 million found schedule delays ranging from 120 to 847 days and $19.6 million in increased contract costs. Much of it was traceable to submittal and review breakdowns. Every returned package adds another full review cycle to the critical path and pushes procurement, fabrication, and installation further to the right.
How Datagrid AI agents shift USACE submittals from assembly to review
I see most USACE submittal delays start long before government review. They start in the manual assembly work: parsing specifications, building the register, populating the form, assembling the package, and verifying it before transmission.
That assembly burden is well documented. The RMS Quick Reference Guide walks through the manual register-building work USACE expects contractors to do inside RMS, and the ABC 2024 AI Technology Report found that contractors using AI to generate submittals directly from specifications recover significant hours per project.
Datagrid's Submittal-Builder Agent takes on that assembly work end-to-end, leaving the contractor to do what only the contractor can: review and certify before signing the ENG Form 4025.
What the agent handles on a USACE package
Assembles the full package from cover page through supporting documents, table of contents, and final PDF
Cross-checks submittal content against the spec to surface compliance gaps and scope misalignment before transmission
Runs a pre-submission review so the contractor signs ENG Form 4025 on a package that has already been validated
Time savings for federal project teams
Jacob Freitas, Project Executive at Level 10 Construction:
"With Datagrid we are able to review 8 submittals in 1 hour. This would have taken a team of 4 people at least 8 hours."
They reported faster submittal execution, catching errors that prevented a full week of project delays. For federal contractors operating under 30-day government review clocks where returned packages reset the clock to zero, that pre-submission accuracy is the difference between maintaining schedule and generating a CPARS deficiency.
Build your next USACE package with AI agents
Federal submittal workflows need standardized repeatable steps that hold up under deadline pressure. Explore Datagrid's construction submittal workflows to assemble USACE-compliant submittal packages and validate against federal spec requirements before your team signs the ENG Form 4025.
