Every civil engineer in active construction administration knows the submittal stack. When a contractor wants to install a product, they submit the documentation: cut sheets, certifications, test reports, manufacturer data. Before that material goes in the ground, the engineer of record confirms it matches what the contract documents require.
That sounds like a quick comparison. In practice it isn’t, because the controlling requirements for a single material aren’t all in one place. They come from the project specification (the CSI section for that trade), from notes on the construction plans, and from agency or utility standards for the jurisdiction, sometimes all three at once. A storm drain submittal might need to satisfy the project spec, a note on the civil grading sheets, and the city’s standard specifications simultaneously. The most stringent governs.
I run Calichi, a civil engineering firm with offices in Oakland, Portland, Hood River, and Haiku. Construction administration runs on most of our projects, which means this review process lands on every active project, often several submittals deep at the same time. After enough time watching engineers spend two hours per submittal on a workflow with an identical pattern every time, I built an agent to handle the production part. Here’s what that workflow actually involves, what it used to take us, and what it takes now.
What a material submittal review actually involves
The review has two distinct jobs, and they’re different in kind.
The first is a factual determination for each controlling requirement: does the submitted product meet it, or doesn’t it? This is a checklist, not a judgment call. Pipe stiffness: required SDR-35 by the project specification; submitted SDR-26. That’s a factual comparison. You state the requirement, its source, the submitted value, and the verdict. You do this for every controlling requirement on every item. A normal reviewer spot-checks. A thorough review covers all of them and cites every source.
The second job is harder. When a submitted product exceeds the specified requirement, that isn’t automatically a clean approval. SDR-26 pipe where SDR-35 is specified is a thicker wall and a stiffer pipe. The question isn’t whether it’s stronger. The question is what follows from it. Did the contractor elect a better product at no cost change (benign over-delivery)? Or did they substitute a different product with cost and warranty implications (unauthorized substitution)? Does the heavier product create a fitting conflict with the specified joints (fit or interface conflict)? Does it affect a downstream submittal or system (downstream impact)? Each of those is a different engineering judgment. Only one is an uncomplicated approval.
A thorough review documents that judgment, quantified, for every item that exceeds the specification. Most reviews don’t.
Then you write the response letter to the contractor, stamp it with the overall determination, and file it in the project CA folder.
What it used to take us
At Calichi, a single submittal review, including loading the project specs and plan notes, pulling the applicable agency standards, cross-referencing each item against the controlling requirements, and drafting the response letter, ran about two hours of an engineer’s time. That’s our own measured number.
Two hours per submittal sounds manageable until you count the submittals. A mid-size site development project might generate fifteen to thirty of them across the construction phase: concrete, aggregate base, pipe, valves, fittings, manhole frames and covers, detectable warning surfaces, and more. They don’t arrive on a schedule. They arrive when the contractor orders material, which is when the contractor needs the approval. Construction administration is already the most interrupt-driven phase of a project, and a steady stream of submittals, each requiring a full spec review and a carefully worded response, is exactly the kind of work that pulls a senior engineer off the tasks that actually require their judgment.
The pattern was the same every time. Pull the spec sections. Pull the plan notes. Check the agency standards for this jurisdiction. Read the cut sheets. Compare each item against each requirement. Write up the determination. Draft the response. The reasoning varied; the sequence never did.
How the agent does it now
The engineer sends the submittal to the agent the way they’d forward it to a junior with a note: "Review submittal 35, storm drain, Osgood South." From there:
- It resolves the project folder, locates the project specifications by CSI section, the most recent construction plan set, and the submittal file from the project’s CA folder.
- It loads the controlling requirements in three tiers: project spec sections first, then construction plan notes and schedules, then the applicable agency and utility standards for the jurisdiction, fetched from the governing authority’s published online specifications. City standard over county, county over state, state over federal. More stringent always governs.
- Where Civil 3D is available, it cross-references submitted pipe materials against what the utility plans show, flagging any discrepancy in material, size, or class.
- Before reviewing the cut sheet content, it searches for the manufacturer’s current data sheet and checks whether the submitted product has been superseded or replaced since the cut sheet was printed.
- It runs the two-layer conformance analysis. The first layer is the per-item determination matrix: every controlling requirement checked, the requirement and its source cited, the submitted value stated, and the verdict given. Meets or Does Not Meet, one determination per requirement, no adjectives. A deficiency line states exactly what is required, what was submitted, and what corrective action is needed.
- The second layer is the Engineer’s Note: a consolidated narrative written as client-letter prose, discussing every item that exceeds the specified requirement. For each exceeding item, it states the controlling requirement and source, the submitted value, the quantified margin as actual numbers, and the engineering judgment: benign over-delivery, unauthorized substitution, fit or interface conflict, or downstream impact. One outcome per item, not a hedge.
- Each line item carries one of five canonical status designations: Approved (meets), Approved (exceeds), Not Approved (revise and resubmit), Rejected with Comment, or Not Reviewed. The overall stamp is driven only by deficiencies. An item that exceeds a requirement is still approved at the overall level.
- Confidence is scored on every determination. Confirmed by two or more sources: HIGH. Single authoritative source: MEDIUM. Inferred from general practice: LOW, flagged explicitly for contractor verification.
- Input is validated before the review starts. The output is verified before delivery.
At Calichi, that two-hour task comes back in five minutes. That’s our own production-measured result.
The QC gate
The agent does not hand its output to the engineer without a validation pass first.
The validation checks structural completeness: review table present with at least one line item, approval stamp present and matching one of the five canonical values, no unfilled placeholders, CDG brand header intact. A non-canonical stamp string silently defaults to "Not Reviewed" in the delivery template and does not fire the correct checkbox. The validator catches that before the engineer sees the package.
For multi-submittal runs, the validator confirms that each response is filed in its own per-material subfolder rather than loose in the output folder. It also checks that the delivery note includes a placement map, one line per response naming the destination folder, so the CA bundle can be filed correctly without hunting.
The audit trail is a mandatory contract artifact and is checked independently. Every external source relied on during the review, including spec sections, plan notes, agency standards, ASTM or AWWA references, and manufacturer data sheets, must appear as a logged entry with the source, the governing value, and a real working link. No placeholder entries. No reconstructed log after the fact. The audit is client-facing.
The validation must print [QC PASSED] before the package is delivered. A failing run gets up to three fix attempts before escalation. The agent does not ship a failing package.
What stays human
The determination matrix and the Engineer’s Note are the agent’s production work. What stays with the licensed engineer:
The judgment calls the determination matrix can’t own. When an item exceeds a specification, the agent documents the engineering outcome and lands on one of the four categories. The engineer reads that judgment and decides whether to accept it. If the agent flags an unauthorized substitution, the engineer decides whether to approve or reject it and carries that decision into the project record. The agent makes the determination; the engineer owns the conclusion.
When no spec section exists for a given trade, the agent works from plan notes and agency standards and states that explicitly. Any determination based on inference rather than a cited source is tagged LOW confidence and flagged for contractor verification. The engineer decides whether that confidence level is sufficient before the response letter goes out.
The response goes out under the engineer’s stamp. The engineer takes the contractor call when a determination is contested. Every submittal response is PE-reviewed before it leaves the office.
The agent produces the draft. The engineer owns the decision.
Where it applies
Material submittal review is construction administration, which means it runs on every project that reaches the field. Volume tracks the project size and complexity. A simple utility extension might generate five submittals. A full site development with utilities, paving, structures, and landscaping can generate forty or more, arriving sporadically across the life of the project.
The agent handles site civil submittals: pipe (storm, sewer, water, dry utilities), aggregate base, concrete, valves, fittings, access frames and covers, detectable warning surfaces, and similar items. It resolves the controlling jurisdiction from the project address and fetches the current published standards for that agency or utility provider. That search step, locating the governing edition of the city or utility’s standard specifications and reading the applicable material sections, was consistently the most time-consuming part of any submittal in a jurisdiction we hadn’t worked in recently.
Multi-submittal runs produce a per-material filing structure. Each response lands in its own subfolder, and the delivery note carries a placement map so the CA file stays organized as the submittal stack arrives.
We run it on every active construction project.
What this means for your firm
I’m not going to tell you the Calichi numbers translate directly to your practice. Two hours to five minutes is our measurement, on our projects, with our spec standards and our CA workflow. Your number depends on how your engineers work today, how complex your typical submittal packages are, and how many concurrent construction projects you carry.
What I can describe is the pattern shift. Before: the engineer in charge loads the specs, finds the applicable requirements, cross- references the cut sheet line by line, handles the "exceeds" items with whatever judgment the day allows, and writes a carefully worded response for each determination. The reasoning differs each time. The sequence never does. After: the engineer reviews a completed analysis, owns the judgment calls, and stamps the response.
The agent does the production pattern-work. The engineer does the engineering.
If that shift sounds worth measuring in your practice, the first step is the AI Readiness Audit. It identifies where the highest-value automation opportunities sit across your actual workflows, so the numbers come from your own projects rather than from a case study that may not reflect how your firm operates.