division 22 23 submittal process explained

If you've managed the mechanical scope on a mid-size commercial project, you know the submittal stack. A 100,000 SF office building might have 120 Division 22 and Division 23 submittal items. A hospital fit-out can run 400. Between product data, shop drawings, O&M manuals, test reports, and engineer review letters, getting through the division 22 23 submittal process explained in most project manuals is one of the most time-intensive workflows in the trade — and one of the least automated.

This post walks through exactly how the Division 22 and 23 submittal process works, where it consistently breaks down on real projects, and where mechanical contractors are using AI tooling to take back hours every week.

what the division 22 23 submittal process actually means

CSI MasterFormat divides mechanical work cleanly. Division 22 is plumbing — domestic water, sanitary drainage, vent systems, storm drainage, gas piping, and specialty plumbing equipment. Division 23 is HVAC — air handling, duct distribution, refrigeration, terminal equipment, and building automation interfaces. Each has its own submittal requirements, and those requirements are specified in detail in the project manual.

Division 22 (Plumbing) submittals typically include:

• Product data for all fixtures: faucets, flush valves, floor drains, water closets, urinals
• Product data and shop drawings for water heaters, storage tanks, and heat exchangers
• Shop drawings for prefabricated plumbing assemblies and modular skids
• Certification and test documentation for backflow preventers, pressure-regulating valves, and check valves
• Commissioning and startup records for equipment with controls
• O&M manuals for everything with moving parts

Division 23 (HVAC) submittals typically include:

• Shop drawings for ductwork fabrication — usually produced by a sheet metal subcontractor
• Product data for air handling units, fan coil units, VAV boxes, diffusers, grilles, and registers
• Equipment submittals for chillers, boilers, cooling towers, and pumps — including performance curves and rated capacities
• Control sequences and BAS point lists
• Test and balance reports at project closeout
• Commissioning records per the owner's commissioning requirements

On a typical commercial project, Division 22 and 23 together generate more submittal volume than any other mechanical scope. The submittal log is the backbone of procurement coordination — nothing moves until something gets approved.

the specific problems with the division 22 23 submittal process on real projects

The division 22 23 submittal process explained in a specification reads like a straightforward compliance checklist. On a live project, five problems turn it into the highest-friction part of the job.

1. spec interpretation gaps that generate revise-and-resubmit cycles

Division 22 and 23 specs are written by MEP engineers who design for a range of acceptable products. The language — "equal or better performance," "approved manufacturer," "submit for engineer's review and acceptance" — is deliberately flexible, which means the line between an acceptable product and an unacceptable one often isn't clear until after you submit.

A boiler submittal that doesn't include the right combustion controls documentation. An AHU submittal where the published performance curve doesn't match the specified leaving air temperature at design conditions. A VAV box submittal where the controls interface doesn't align with the spec'd BAS protocol. Each of those generates a revise-and-resubmit. Each round is 10–14 calendar days of engineer review time — time your procurement schedule doesn't have to spare.

2. transmittal tracking at scale

A mechanical PM managing 150 submittal items across two active projects is doing a meaningful amount of administrative work just keeping track of what's been submitted, what's under review, what came back with comments, and what's still outstanding. When items fall through the cracks — submittals sitting with the GC waiting for a transmittal forward, engineer review deadlines that passed without follow-up — the schedule impact is real. Missing a two-week review window on a long-lead AHU can cascade into a delivery delay that compression scheduling can't fix.

3. procurement integration timing

Mechanical submittals aren't just a compliance exercise — they're on the critical path for equipment purchasing. You can't issue a purchase order for a $90,000 custom air handling unit without an approved submittal. The submittal has to go in early enough to allow engineer review (10–14 days minimum, often longer), leave time for a revise-and-resubmit round if needed, and still put the approved PO in the manufacturer's hands before the fabrication lead time expires.

Get that timing wrong and you're choosing between two bad options: order before approval and take the substitution risk, or wait for approval and compress the delivery window.

4. subcontractor coordination in Division 23

Ductwork fabrication is frequently subcontracted to a sheet metal contractor working under the mechanical sub's contract. That sub's shop drawings need to go through the same review process — but they also need to be coordinated with Division 22 plumbing penetrations, structural penetrations, electrical clearance requirements, and the overall architectural reflected ceiling plan. Managing those dependencies manually across three or four parties requires sustained attention that a PM running multiple active projects doesn't always have.

5. closeout documentation that accumulates invisibly

The Division 22 and 23 closeout package — O&M manuals, test and balance reports, commissioning records, as-built documentation — is substantial, and it's typically the last thing holding up final payment. Projects where closeout documentation isn't tracked from day one end up in a scramble at substantial completion, chasing manufacturers for updated O&M manuals and pulling test records from a technician who hasn't touched the job in six months. On more than a few projects, mechanical subs have carried outstanding retainage for months past substantial completion because of missing closeout submittals.

how AI is changing division 22 23 submittal management

The mechanical contracting industry has been slow to automate submittal workflows. Part of that is legitimate complexity — the work requires real domain knowledge. Part of it is that the tools available until recently required more IT infrastructure than most mechanical shops have. That's changed. Here's where AI-driven submittal tools are making a concrete difference:

spec parsing and log generation

Instead of reading a 45-page Division 23 spec to build a submittal log by hand, AI tools parse the specification document and extract every submittal requirement — section number, description, required document type, submission timing, and responsible party. A task that used to take 6–10 hours per project takes minutes. More practically: it catches requirements that human readers miss, especially the ones buried in paragraph 1.4 of Section 23 73 00 that most PMs skim past the first time.

package assembly from vendor documentation

Mechanical contractors receive product data from multiple vendors per project. AHU submittals from one manufacturer, boiler packages from another, controls documentation from a BAS vendor. AI submittal tools can ingest that vendor documentation — pull out the relevant performance data, equipment schedules, and certifications — and assemble a properly organized submittal package with a cover sheet, transmittal, spec compliance matrix, and supporting documentation. No manual PDF collating. No missing attachments.

status tracking and automated follow-up

Every outstanding submittal item has a status, a due date based on the project schedule, and a follow-up sequence. When a submittal goes past the expected review period without a response, the system flags it. The PM spends their time on exceptions rather than doing status-check rounds across 150 items.

closeout tracking from project kickoff

The same system that tracks procurement submittals tracks closeout requirements from day one. When test and balance reports are due, which O&M manuals are still outstanding, what commissioning records need to be collected before the final walk — all tracked automatically, not reconstructed from a spec review after the fact.

what still requires human judgment in the division 22 23 workflow

Automation handles the administrative load. It doesn't replace the expertise that makes a mechanical contractor competitive.

technical compliance calls. When a submitted product doesn't precisely meet a spec requirement but might be accepted as an approved equal, someone with domain knowledge needs to make that call — and make the case to the engineer. Automation flags the discrepancy. It doesn't negotiate the substitution.

substitution requests. If the specified boiler has a 24-week lead time and the schedule needs it on-site in 18, the mechanical PM needs to propose a substitution that addresses every spec requirement and gets engineer sign-off. That's a document that requires industry knowledge and project context no automated tool provides.

coordination conflicts. Physical space conflicts between mechanical, electrical, and structural don't surface in submittals — they surface in BIM coordination or in the field. Submittal automation doesn't replace mechanical coordination or the judgment calls that come with rough-in.

owner and engineer relationships. The MEP engineer on a repeat-client project has preferences and flexibility that aren't in the spec. The GC's submittal coordinator has a workflow you need to accommodate. Those relationships and that context matter for turnaround time and approval rates. Automation supports the process; it doesn't replace the people running it.

the roi calculation for mechanical submittal automation

For a mechanical PM managing 150 submittal items across a 12-month commercial project, the time math is direct. Typical PM hours spent on submittal administration — logging, assembling packages, tracking status, following up, managing closeout:

• Project kickoff: 8–12 hours building the submittal log from spec
• Active submittal period: 4–8 hours per week tracking, assembling, and following up
• Closeout: 10–20 hours assembling the final package

Over a 12-month project, that's 200–400 hours of PM time on administrative submittal work — at a fully-loaded rate of $90–$120/hour, that's $18,000–$48,000 per project per PM.

A PM running two active projects simultaneously is spending close to half their workweek on submittal paperwork.

Automation typically reduces that burden by 60–75% — handling routine assembly, tracking, and follow-up while the PM focuses on technical decisions and trade coordination. That's a $12,000–$36,000 annual return on administrative labor alone, before accounting for avoided schedule delays from missed submittals or late revise-and-resubmit cycles.

For electrical contractors with similar Division 26 submittal volumes, the same economics apply — and the tooling built for mechanical submittals extends naturally to electrical work.

how kjags advisors approaches division 22 23 submittal management

At kjags advisors, we've built AI submittal tooling specifically for mechanical and electrical contractors working commercial projects in the Baltimore and Washington DC market. Our AI Submittal Employee for mechanical contractors handles the full Division 22 and 23 workflow — spec parsing and log creation, vendor document intake and package assembly, review status tracking, and closeout document management.

This isn't a generic project management platform that treats submittals as a to-do list. It's built for contractors who understand the difference between a Division 22 plumbing scope and a Division 23 HVAC scope, who are managing multiple submittals across multiple active projects, and who need tooling that fits into their existing workflow rather than requiring them to rebuild how they operate.

We also work with general contractors who are managing mechanical subcontractor submittals through Procore or Autodesk Build. If your platform is becoming a graveyard of unreviewed submittals and stalled approvals, we can help with that too.

If you're handling complex Division 22 or 23 scopes — hospital work, laboratory fit-outs, data centers, or large commercial — we'd like to show you what the workflow looks like in practice. Book a call with our team and we'll walk through a live demo with your actual project scope in hand.

what to look for when evaluating submittal management tools

If you're comparing options, these questions separate tools that save time from tools that move the work without reducing it:

Does it understand CSI division structure? A tool that treats all submittals as undifferentiated line items will require manual organization. Look for tools that understand spec section numbers and can sort by division automatically.

Can it ingest vendor documentation directly? If you're manually uploading and organizing PDF submittals from every vendor, you've moved the work from a spreadsheet to a different interface. The right tool accepts documents and extracts the relevant data.

How does it handle revise-and-resubmit cycles? The first submission is rarely the last. The tool needs to track version history, document changes clearly, and show exactly what was revised between rounds.

Does it integrate with your GC's platform? If the GC is running Procore, the question is whether your tool integrates or whether your PM is managing two systems and doing double-entry.

Does it track closeout from day one? The best time to start tracking closeout submittals is at project kickoff. If the tool only handles procurement, you still have a manual closeout problem.

The division 22 23 submittal process explained clearly is useful — but the contractors pulling ahead aren't just the ones who understand the process. They're the ones who've systematized it. Submittal management isn't a task to be completed on each project. It's a workflow to be optimized once and run consistently across every project.

kjags advisors builds AI submittal tooling for mechanical and electrical contractors in the Baltimore–Washington DC region. Our AI Submittal Employee handles the full Division 22 and 23 submittal workflow so your project managers can focus on the work that actually requires their expertise. Start the conversation here.