HVAC estimating hits the same three bottlenecks at nearly every contractor: manual takeoff time, scope development for proposals, and the endless back and forth of RFIs, addenda, and revisions. Specialized takeoff tools handle the visual counting from drawings. Claude AI does something different. It handles the language, scope, and analysis work that surrounds the takeoff.
What Claude AI Can and Cannot Do for HVAC Estimation
Set expectations up front. Claude is strong at some things and weak at others.
What Claude Does Well
- Writing scope of services and proposal narratives from your equipment list and project details
- Reviewing mechanical specifications for scope gaps, conflicts, or unusual requirements
- Drafting RFIs from ambiguous drawing notes or spec language
- Comparing addenda against original documents and summarizing what changed
- Turning your bulleted takeoff notes into structured proposal language
- Reviewing your bid comparison for missing scope items across bidders
- Generating clarifications and exclusions specific to your scope
- Writing letters, transmittals, and follow up emails to owners and GCs
What Claude Cannot Do
- Count ducts, diffusers, or pipe lengths from a drawing PDF (this is a computer vision problem; use a specialized takeoff tool)
- Measure quantities visually from a plan set
- Access your internal cost database in real time
- Apply your labor rates or crew productivity assumptions unless you tell it
The right way to think about it: Claude is the estimator's writing and analysis assistant. The takeoff software counts what is on the drawings. Claude helps you use those numbers to build a winning bid.
What Claude AI Can and Cannot Do for HVAC Estimation
Set expectations up front. Claude is strong at some things and weak at others.
What Claude Does Well
- Writing scope of services and proposal narratives from your equipment list and project details
- Reviewing mechanical specifications for scope gaps, conflicts, or unusual requirements
- Drafting RFIs from ambiguous drawing notes or spec language
- Comparing addenda against original documents and summarizing what changed
- Turning your bulleted takeoff notes into structured proposal language
- Reviewing your bid comparison for missing scope items across bidders
- Generating clarifications and exclusions specific to your scope
- Writing letters, transmittals, and follow up emails to owners and GCs
What Claude Cannot Do
- Count ducts, diffusers, or pipe lengths from a drawing PDF (this is a computer vision problem; use a specialized takeoff tool)
- Measure quantities visually from a plan set
- Access your internal cost database in real time
- Apply your labor rates or crew productivity assumptions unless you tell it
The right way to think about it: Claude is the estimator's writing and analysis assistant. The takeoff software counts what is on the drawings. Claude helps you use those numbers to build a winning bid.
Three Proven Prompting Patterns for HVAC Estimating
Every effective estimating prompt uses one of three patterns. Pick the one that fits your task.
Approach A: The Full Brain Dump
Best for equipment replacements, straightforward renovations, and scopes where you know everything about the project. Give Claude everything in one message: facility info, existing equipment, every scope item, phasing, controls, and any special considerations.
Example prompt pattern:
Write me an HVAC engineering scope of services for a chiller replacement project.
Facility: 250,000 sq ft office building, 12 floors, occupied during construction.
Existing equipment:
* (2) 400-ton York YCAV chillers, R-134a, 22 years old
* (2) 40 HP inline centrifugal chilled water pumps, constant primary
* (1) 4-cell Marley crossflow cooling tower, 800 tons total
* Existing BAS: Johnson Metasys N2 network
Scope of work:
* Demolish both existing chillers, associated piping, VFDs
* Replace with (2) 400-ton Trane centrifugal chillers, R-1233zd
* Convert constant primary to variable primary flow
* Provide new DP sensor, new SOO, integrate with existing Metasys BAS via BACnet MS/TP
* Phased approach: replace one chiller at a time, keep one online during construction
* Include temporary rental chiller connection points
Disciplines: MEP only, no structural, no architectural
CA: 4 site visits during construction, 2 pre-installation coordination meetings
Fee: $85,000 design plus $22,000 CA
When to use: you know the scope cold and want a complete draft in one pass. This is the fastest path.
Approach B: Reference Format Plus New Scope
Best for repeat clients, similar project types, or when you have a previous proposal you want to replicate exactly.
Attach a prior proposal or scope document and tell Claude to follow that exact format. Claude reads the attached file and matches the structure, tone, section headings, and voice.
Example prompt pattern:
Attached is a scope of services I wrote for a similar chiller replacement last year. Write a new one for a different project using the exact same format and section structure. Ask me the project-specific questions you need to fill out the new scope.
When to use: you have an existing document that represents your firm's format. This works especially well for scopes where the structure is standardized and only the project specifics change.
### Approach C: Interactive Section by Section
Best for complex new projects, first-time project types, or scopes where you want to think through each section and approve as you go.
**Example prompt pattern:**
I need to write a proposal in this format:
A. Executive Summary
B. Project Understanding
C. Scope of Services
D. Deliverables
E. Assumptions and Exclusions
F. Fee
Help me write it for a new project by asking me questions for each section, showing me the draft to approve, then moving to the next section.
When to use: unfamiliar project types (industrial process cooling, healthcare renovation, data center MEP), scope that has evolved from client discussions, or any situation where you want to review before committing to the full document.
The Information Checklist Claude Needs for HVAC Proposals
Whatever approach you use, Claude needs specific information to produce a usable draft. Missing information produces generic output.
| Category | Information | Priority |
|---|---|---|
| Project ID | Project name, project number | Critical |
| Facility | Name, address, building type, approximate square footage | Critical |
| Existing equipment | Tag, manufacturer, model, capacity, age | Critical for replacements |
| System configuration | Loop type, pump arrangement, controls network | Critical |
| Scope | What is being demolished, replaced, installed, retained | Critical |
| Controls | Existing BAS, protocol, new SOO scope | Critical |
| Phasing | Number of phases, temporary measures per phase | If phased |
| Disciplines | M, E, P, FP, S, C, A | Critical |
| CA scope | Site visit count, submittal review, RFI response | Critical |
| Fee | Total, breakdown by phase or discipline | Critical |
| Exclusions | Anything explicitly excluded beyond standard | Helpful |
The rule: everything marked Critical must be in the prompt. Everything marked Helpful improves the draft but Claude will ask for it if missing.
Five HVAC Estimating Workflows That Save the Most Time
These five specific workflows produce the biggest returns for HVAC estimators using Claude.
Workflow 1: Scope Development from Takeoff
You have completed the takeoff (manually or with an AI tool). You have equipment counts, duct footage, and pipe lengths. Now you need to turn that into scope language for a proposal.
Prompt:
I have completed a takeoff for an HVAC scope. Turn this into a scope of services narrative organized by system.
Equipment counts:
* (4) VAV air handlers, 15,000 CFM each
* (85) VAV boxes with hot water reheat
* 12,500 LF supply/return ductwork, spiral and rectangular
* (2) condensing boilers, 2,500 MBH each
* (2) chillers, 200 tons each, air-cooled
* Full DDC controls, BACnet IP
System configuration: variable primary CHW, primary-secondary HHW, VAV overhead distribution with hot water reheat.
Write the scope organized by:
* C.1 Air Handlers and Ductwork
* C.2 Terminal Units
* C.3 Heating Plant
* C.4 Cooling Plant
* C.5 Controls and BAS
* C.6 Piping Systems
Use active voice. Include applicable code references (ASHRAE 90.1, IECC).
Workflow 2: Spec Review for Scope Gaps
Upload the mechanical spec section and ask Claude to review it for gaps, conflicts, or unusual requirements that could affect your bid.
Prompt:
I am attaching Section 23 05 00 (HVAC Common Requirements) and 23 82 39 (Unit Heaters) from a project I am bidding.
Review these sections and identify:
1. Any unusual product requirements or manufacturer-specific language
2. Warranty terms that extend beyond standard 1-year
3. Testing, adjusting, and balancing scope
4. Startup and commissioning requirements
5. Owner training requirements
6. Any spec language that conflicts with typical trade practice
7. Any requirements that might warrant an RFI before bid
Format the response as a checklist with page/section references.
Workflow 3: Addendum Comparison
An addendum drops the day before bid. You need to know what changed fast.
Prompt:
Attached are the original mechanical drawings/specs and Addendum \#2.
Review the addendum and summarize:
1. What sheets/details were changed
2. What was added
3. What was removed
4. What was clarified (no scope change but confirmation)
5. Which changes affect quantities (require takeoff update)
6. Which changes affect scope narrative (require proposal update)
Format as a bullet list under each heading. Reference specific detail callouts and spec paragraphs.
Workflow 4: RFI Drafting
You spot ambiguity in the drawings or specs. Claude drafts the RFI.
Prompt:
Draft an RFI on this issue:
The mechanical drawings show (2) hot water pumps HWP-1 and HWP-2 in parallel configuration on Sheet M-501. The pump schedule on M-601 shows HWP-1 at 350 GPM and HWP-2 at 175 GPM. The specification 23 21 23 paragraph 2.4.B calls for equal pumps in parallel.
The GPM difference suggests either a schedule error or an unusual primary/secondary arrangement not shown on the diagram.
Draft an RFI in professional tone that:
* Cites the specific drawing sheets and spec paragraphs
* States the discrepancy clearly
* Asks the specific question needed to resolve
* Notes the bid impact if unresolved
Format: subject line, background, question, action requested.
Workflow 5: Bid Comparison Analysis
You have three subcontractor bids. Claude compares them for scope alignment.
Prompt:
Attached are three HVAC subcontractor proposals for the same project. Compare them across:
1. Total base bid amount
2. Scope items each includes
3. Scope items each excludes
4. Warranty terms
5. Startup, commissioning, and T\&B inclusion
6. Any unusual assumptions or clarifications
7. Alternates and add/deduct items
Highlight where bidders differ on scope so I can normalize the comparison. Flag any bidder who excludes something the others include.
Common Mistakes to Avoid When Using AI for HVAC Estimates
Vague equipment descriptions: "Replace the old chillers with new ones" produces generic output. "Replace (2) Trane RTHB 150 chillers, 150 tons each, R-134a, 18 years old, with new Trane centrifugal chillers of equivalent capacity, R-1233zd" produces specific, usable scope.
Missing system configuration: Constant primary vs. variable primary is fundamentally different scope. Primary-secondary vs. injection loop is different scope. Tell Claude the loop type or it will guess (and often guess wrong for your project).
No phasing information: Any occupied facility needs a phasing plan. The proposal must describe what maintains service during construction, the transition sequence, and any temporary equipment. Skip this and the scope Claude writes will miss the phasing story that owners actually care about.
Forgetting controls scope: BAS integration is its own scope item, not an afterthought. Always specify the existing BAS manufacturer, protocol (BACnet MS/TP, BACnet IP, Modbus, LON), whether integration is to existing or new controller, and whether a new sequence of operations will be developed.
Not distinguishing OFCI from designed: If the owner is furnishing process equipment, autoclaves, tanks, or generators, state that. The engineering scope changes from "design and specify equipment" to "design infrastructure to support owner-furnished equipment" and the fee changes with it.
Skipping exclusions: If structural, architectural, hazmat, commissioning, or permits are excluded, state them up front. This prevents Claude from including scope you do not intend to cover and protects against scope creep in the final document.
The Minimum Viable Prompt for Fast HVAC Proposal Drafts
If you are short on time and need a first draft fast, the absolute minimum information Claude needs:
- Project type: chiller replacement, AHU renovation, new construction MEP
- Facility: name, address, building type, approximate size
- Existing equipment: tags plus capacities
- Scope actions: demolish, replace, redesign piping, new controls SOO
- Disciplines: MEP only, no structural
- Fee: total or breakdown
Everything beyond these six items improves the first draft but is not strictly required to get started. Claude will ask for the rest.
How to Review AI Generated HVAC Proposals Before Submission
The first draft is rarely the final version. After receiving output, review for these things.
Check for Consistency
Does the title match the scope? Are the disciplines listed in the executive summary consistent with the scope of services and fee table? If a code (ASHRAE 90.1, ASHRAE 62.1, NFPA 90A) appears in the scope, does it also appear in the applicable codes section? Are excluded items in the exclusions section absent from the scope?
Check for Scope Gaps
Is demolition explicitly described or assumed? Are temporary measures during construction addressed? Is test and balance included or excluded? Does the controls scope match the complexity of the project?
Check Fee Alignment
Do the fee line items add up? Does the phase breakdown match the discipline breakdown if both are present? Is the CA fee proportional to the number of inspections and construction duration?
Check Voice and Tone
Does the scope read like an experienced HVAC estimator wrote it, or does it read like AI wrote it? Generic AI language ("comprehensive solutions," "state of the art systems," "innovative approach") is a sign the prompt lacked specificity. Rewrite the prompt with more detail rather than editing the output.
Build a Repeatable AI Estimating System That Scales With Octopus Builds
If you are spending more time writing scope narratives, comparing addenda, and drafting RFIs than you are on actual takeoff and pricing, the bottleneck is not your counting. It is the language work that surrounds it.
At Octopus Builds, we help contractors connect their takeoff data to AI systems that write proposals, review specs, and flag scope gaps without producing generic fluff. We build the prompt libraries, the review interfaces, and the integration logic so your estimators stay in control while the repetitive writing work gets handled automatically.
If you are tired of estimator hours disappearing into proposal formatting, spec reading, and RFI drafting, do this with Octopus Builds. We will show you how to automate the analysis and writing layer so your team can focus on bidding and building.
Build with Octopus Builds
Need help turning the article into an actual system?
We design the operating model, product surface, and delivery plan behind AI systems that need to ship cleanly and keep working in production.