Why HVAC Contractors Get Resubmittals — The Compliance Documentation Gap

Most HVAC resubmittals aren't caused by bad work. The equipment is installed correctly, the system runs well, and the crew knows their trade. The problem is the paperwork — spec documents that miss a local amendment, load calc forms that reference the wrong code cycle, or submittals that don't match what's actually on the job site.

Understanding why this happens — and how to stop it — starts with the documentation process, not the installation.

---

At a Glance

• 50% of contractors report missing key specification updates during active projects
• 800 RFIs are generated on a typical construction project, costing an average of $860,000 to process
• Errors and omissions in contract documents are the leading cause of construction disputes in North America
• The IMC has been adopted by 46 states — but every state and municipality layers on local amendments
• Jurisdiction-specific amendments to codes like the IPC, IMC, and NFPA 90A are the most common source of first-time submittal rejections
• Generating spec documents manually from templates increases copy-paste error risk significantly

---

The Code Maze Every HVAC Contractor Faces

A compliant HVAC or plumbing submittal isn't just about the International Mechanical Code (IMC) or the International Plumbing Code (IPC). It's about getting all of these to agree simultaneously:

Code	What It Governs
IMC (International Mechanical Code)	HVAC design, ductwork, ventilation, efficiency
IPC (International Plumbing Code)	Condensate disposal, water connections, pipe sizing
NFPA 90A	Fire safety for AC/ventilation systems in commercial buildings
ASHRAE 90.1	Energy performance standards with required compliance forms
Local amendments	Everything the jurisdiction changed from the base code

The IMC is adopted by 46 states — but "adopted" doesn't mean "used as-is." Every jurisdiction that adopts the IMC can amend it. California's Title 24 overlaps with ASHRAE 90.1 in ways that conflict with default IMC requirements. New York City adds dozens of local amendments. Texas delegates enforcement differently by county.

A spec document that's perfectly compliant with base IMC may still fail because it doesn't account for the local amendment that changed the make-up air calculation requirement — as the 2024 IMC update explicitly did, requiring conditioned make-up air in kitchen hood applications where unconditioned air was previously allowed.

The result: even contractors who know the codes well can produce non-compliant documents simply by using last year's template.

---

Where Documentation Errors Actually Come From

The research is consistent: the paperwork problem is process-driven, not knowledge-driven.

Copy-paste from outdated templates is the most common failure mode. Contractors build spec templates from past jobs and reuse them. If a local amendment changed between projects — and they often do on a 3-year code cycle — that template is now wrong.

Missing jurisdiction lookups are the second. The IPC, IMC, and local amendments don't live in one place. A contractor writing a submittal for a multi-family HVAC job in Phoenix needs to check the base IMC, Arizona state amendments, and City of Phoenix supplements. That's three separate document sets to cross-reference before writing a single line of specs.

RFI volume as a proxy for documentation quality tells the full story: 800 RFIs per project at $860,000 in processing cost means a large share of project cost is consumed correcting what should have been specified correctly upfront. Nearly 40% of contractors report that they frequently miss key specification updates mid-project.

These aren't isolated failures — they're predictable outcomes of a manual process operating against a moving code target.

---

What Plan Reviewers Actually Flag

Based on common inspection deficiency patterns across jurisdictions, the documentation issues that trigger resubmittals fall into three categories:

1. Load calc mismatches
The submitted equipment schedule doesn't match the load calculations. Either the calcs used an older weather data set, or the equipment was substituted during procurement without updating the design documents.

2. Code cycle mismatch
The submittal references a superseded code edition. Many jurisdictions have staggered adoption timelines — a contractor working across county lines may be submitting to one AHJ still on the 2018 IMC while submitting to another on the 2021 edition.

3. Missing jurisdiction-specific forms
ASHRAE 90.1 compliance requires a Certificate of Compliance form. Some states have their own version of this form with additional fields. Submitting the generic ASHRAE form when the state form is required is an automatic resubmittal trigger.

---

Building a Documentation Process That Holds Up

The contractors who consistently pass first-time inspections treat documentation as a system, not a task. Here's what that looks like in practice:

• Jurisdiction-first lookup before writing: Before pulling any template, identify the exact code cycle in force for the project AHJ. This changes the template you start from, not just what you modify.
• Equipment schedule locked before submittal: Spec documents should only be finalized after the equipment selection is locked. Changes after submittal without a formal change order are one of the top resubmittal triggers.
• Version-controlled templates by code cycle: Maintain separate spec templates for each code cycle version you regularly work under. Mixing content between cycles creates subtle inconsistencies that reviewers catch.
• Checklist verification against the specific AHJ's requirements: Generic checklists miss local amendments. An AHJ-specific checklist, even a simple one, catches jurisdiction-specific form requirements before submittal.

None of this is complicated — but done manually on every job, it adds hours of lookup, cross-referencing, and review that most crews don't have time for before a deadline.

---

Frequently Asked Questions

---

The Cost of Getting It Right vs. Getting It Fast

A resubmittal doesn't just cost a reinspection fee. It delays a certificate of occupancy, triggers contract penalties, and damages the relationship with a GC or building owner who expected a clean permit pull.

The compliance documentation problem is solvable. The contractors who solve it treat spec generation as a process with clear inputs (AHJ, code cycle, equipment data) and a predictable output (a document that matches what the inspector will check against). Manual or not, the process needs to be repeatable.

ForgeSpec AI automates that process. Upload your job inputs — photos, notes, basic specs — and get a jurisdiction-specific, code-compliant document output aligned to the IPC, IMC, NFPA, and local amendments for your project location. No manual lookups. No template versioning errors. No resubmittals from paperwork that doesn't match the install.

Generate your first spec free →