HVAC Liability for Architects: Why You Should Hire an Engineer, Not a Contractor

Architects carry professional liability for the projects they stamp, and HVAC liability is one of the areas architects underestimate most. When HVAC design gets handed off to a mechanical contractor instead of a licensed mechanical engineer, that liability doesn't go away — it just moves into murkier territory. A contractor's job is to build the system, not necessarily to optimize it for the owner's long-term interests. When something goes wrong, the question of who designed it — and whether it met the standard of care — comes back to you.

This post covers the practical steps architects can take to limit HVAC liability exposure: what to look for in subcontracts, how to use your insurance carrier as a resource, and why a structured owner discovery process is one of the most effective tools you have.

Key Takeaways

• A licensed mechanical engineer owes a duty to the owner's best interests; a mechanical contractor owes a duty to build what's profitable.

• Subcontracts that lack explicit "standard of care" language leave design responsibility undefined — and that ambiguity lands on the architect.

• Your professional liability carrier will often review subcontract language at no extra charge; most firms never ask.

• A structured owner discovery process — documenting how the owner expects systems to operate — is the single most effective way to prevent scope gaps that become litigation.

• Environmental requirements, control sequences, and occupant comfort criteria must be captured in writing and shared with the engineer before design begins.

• HVAC litigation typically traces back to a failed alignment between what the owner expected and what was designed; discovery closes that gap.

• A mechanical engineering scope that runs 1.5%–2% of MEP construction cost is cheap insurance against an E&O claim that can reach six figures in defense costs alone.

The Difference Between a Contractor Designing Your HVAC and an Engineer Designing It

A licensed Professional Engineer working under an engineer-of-record model is legally and ethically obligated to place the owner's interests ahead of cost and constructability convenience. That obligation is built into the professional code of conduct and enforced by the state licensing board. The standard of care — what a competent engineer would do under the same circumstances — is the benchmark courts use when things go wrong.

A mechanical contractor operates under a different set of incentives. Their job is to price, procure, and install equipment. Design-build contracts sometimes ask contractors to perform both roles, but it's worth understanding what that means: the contractor is optimizing for margin and schedule, not necessarily for the owner's 15-year operating cost, indoor air quality, or resiliency. That's not an indictment — it's just a different role.

The problem for architects is that when HVAC performance fails and the owner asks who was responsible for the design intent, the answer matters. If a licensed mechanical engineer signed and sealed the drawings, there's a clear responsible party and a clear professional standard against which the work is judged. If a contractor produced the design under a loosely worded design-assist arrangement, the liability picture gets complicated fast — and architects are often drawn into it.

What Your Subcontracts Need to Say — and What Your Insurance Carrier Can Tell You

Subcontracts are where most HVAC liability gaps live. A subcontract that assigns design responsibility to a mechanical contractor but doesn't define the standard of care leaves a vacuum. In litigation, that vacuum gets filled by whoever makes the better argument. You don't want to be on the wrong side of that argument.

At a minimum, subcontracts for any HVAC design-build or design-assist work should include:

• Standard of care language. The contractor's design work must meet the standard of care applicable to licensed professional engineers performing the same scope. Vague terms like "industry standard" or "good workmanship" don't cut it.

• Scope definition. What is the contractor designing, and what is the engineer of record reviewing and approving? Blurry lines between these roles are where disputes begin.

• Submittal and approval requirements. All contractor-generated design documents should be reviewed and approved by the engineer of record before construction. This step is often skipped to save time and almost always regretted.

• Insurance and indemnity alignment. The contractor's professional liability coverage should cover the design scope. General liability alone doesn't cover design errors.

The good news: most professional liability carriers will review subcontract language as part of their risk management services, usually at no additional cost. This is an underused resource. A 30-minute conversation with your carrier's risk management team before you sign can identify problem language that would cost hundreds of thousands of dollars to litigate later. Make the call before you execute the contract, not after the project is in dispute.

The Owner Discovery Process: Understanding Success Criteria Before Design Begins

Most HVAC disputes don't start with a design error. They start with a misunderstanding about what the owner expected. The owner expected the conference room to stay at 70°F during a full occupancy meeting in July. The engineer designed to the thermal comfort criteria in ASHRAE Standard 55-2023 for typical occupancy, with ventilation to ASHRAE Standard 62.1-2022. Both can be technically correct — and the result is still a lawsuit.

A structured owner discovery process closes that gap before design begins. This isn't a one-page questionnaire. It's a working session with the project owner to document the following:

• How the owner expects the systems to operate. Not just heating and cooling setpoints — mode transitions, after-hours operation, occupancy scheduling, response times. If the owner expects the building to go from 55°F to 70°F in 20 minutes on a Monday morning, the engineer needs to know that.

• Environmental requirements by space. Temperature and humidity tolerances, air quality requirements, pressurization relationships between spaces, noise criteria. A recording studio has different requirements than an open office.

• Controls expectations. Does the owner want a full building automation system with remote monitoring? A simple programmable thermostat per zone? Integration with an existing BAS? Owners who aren't asked often assume the answer is yes to everything — until they see the cost.

• Operational and maintenance constraints. Who maintains the equipment? Does the building have on-site engineering staff? Is the owner prepared for quarterly filter changes, annual coil cleaning, and BAS calibration? If not, the design should reflect that.

• Owner-defined success criteria. Ask directly: how will you know this project was a success? The answers are often specific and concrete — and often different from what the design team assumed.

Document everything. Share the discovery summary with the mechanical engineer before design kickoff and confirm in writing that the design addresses each item. This single step — done consistently — eliminates a significant share of the HVAC liability exposure architects face.

The Owner's Project Requirements (OPR) document, defined in ASHRAE Guideline 0, is a solid framework for this process. It's been used in commissioning work for years and translates directly to design-phase discovery.

HVAC Liability for Architects: FAQs

Can a mechanical contractor legally provide HVAC design on an architect-stamped project?

Yes, in many states and project types — but with conditions. Design-build and design-assist delivery models are common, and mechanical contractors often prepare design documents under these arrangements. The liability question is who is responsible for the design meeting the standard of care. If the contractor is providing design without a licensed engineer reviewing and approving the work, the architect is often left holding that responsibility. Subcontract language and the role of the engineer of record determine who bears that risk.

What does "standard of care" mean for HVAC design, and why does it matter for HVAC liability?

Standard of care in HVAC design means what a competent, licensed mechanical engineer would do under the same project conditions — the same building type, climate zone, owner requirements, and available information. It's not perfection, and it's not necessarily the best possible solution. Courts use expert witnesses to establish what the standard of care required on a specific project, and then compare the actual design to that benchmark. If the design falls short and causes harm, that's the basis for a negligence claim.

What subcontract language should architects require for HVAC design-assist work?

At minimum, require explicit standard of care language holding the contractor's design work to the standard applicable to licensed professional engineers. Define the scope of what the contractor is designing versus what the engineer of record is reviewing. Require contractor-generated design documents to be reviewed and approved by the engineer of record before construction. Verify that the contractor carries professional liability insurance covering the design scope — general liability alone does not. Have your carrier review the language before executing.

How can a professional liability insurance carrier help with subcontract review?

Most professional liability carriers offer risk management services that include contract and subcontract review. This is typically included in your policy at no additional cost. Their reviewers know what language exposes architects to additional liability and what language shifts risk appropriately. Request a review before signing any subcontract that includes a design-assist or design-build component. It takes less time than one deposition.

What should an owner discovery process cover to reduce HVAC liability exposure?

A thorough owner discovery process for HVAC should document system operating expectations, space-by-space environmental requirements (temperature, humidity, noise, pressurization), controls and automation expectations, maintenance capability of the owner's staff, and the owner's specific success criteria for the project. All of this should be shared with the mechanical engineer before design begins and confirmed in writing. The Owner's Project Requirements (OPR) format defined in ASHRAE Guideline 0 provides a structured framework for this documentation.

When to Bring In a Mechanical Engineer

Architects should engage a licensed mechanical engineer — not just a mechanical contractor — when:

• Any project has a design-assist or design-build HVAC component where design responsibility needs to be clearly assigned

• The owner has specific environmental, controls, or operational requirements that go beyond standard comfort conditioning

• The building type carries elevated occupant health or safety expectations (healthcare, schools, food service, laboratory)

• Subcontract language for MEP scope needs to be drafted or reviewed before execution

• An owner discovery process needs to be structured and documented before design begins — see our blog post "What a Good Engineer Asks Before Design Begins: Owner Requirements Discovery for HVAC Systems"

• You're in early project programming and need someone to help translate owner requirements into a design brief

None of this is legal advice — your attorney and your professional liability carrier have the final word on contract language. But the engineering side is straightforward: the fee to get HVAC design right is a fraction of the cost to litigate it later. A mechanical engineering scope that runs 1.5% to 2% of MEP construction cost is cheap insurance against an E&O claim that can easily hit six figures in defense costs alone — before any damages.

Axiom Engineering Group works on projects coast to coast. Learn more about our structural, mechanical, plumbing, technology, and commissioning services: aeg.design

About the author: John Melvin, PE, is the CEO of Axiom Engineering Group, an SMEP engineering, technology, and commissioning firm with offices in Missoula, MT, Salt Lake City, UT, St. George, UT, and San Diego, CA. John is a licensed Professional Engineer with over 20 years of experience designing mechanical, plumbing, and electrical systems for commercial, institutional, hospitality, healthcare, and luxury residential projects.