%20(1920%20x%201080%20px).png)
Episode Description:
If BAS sales takeoffs feel inconsistent, the issue usually is not the tools. It is the process.
Episode 545 breaks down how to create accurate BAS takeoffs that protect margin, reduce missed scope, and improve project handoffs. You’ll learn how experienced sales engineers and account executives review specs, drawings, sequences, integrations, labor, and risk before a proposal ever goes out the door.
This episode walks through the patterns top performers use to avoid expensive surprises later in execution.
Topics Covered
• How to identify BAS scope before pricing mistakes happen
• The project documents that matter most during takeoff review
• Common integration and specification issues that create hidden costs
• How labor, commissioning, and warranty requirements impact profitability
• Why better handoffs between sales and operations improve project outcomes
If you are responsible for estimating, sales engineering, or project delivery, this episode will help you build a more repeatable and profitable process.
Click here to download or listen to this episode now.Podcast Video
How to Perform BAS Sales Takeoffs Without Missing Scope
Building automation projects rarely fail because of programming logic or hardware limitations. Most problems begin much earlier during the takeoff and estimating phase.
Missed integrations, unclear scope, forgotten labor, vague specifications, and poor handoffs create expensive problems that show up during execution. A strong BAS sales takeoff process reduces those risks before the project even starts.
Episode 545 of the Smart Buildings Academy Podcast breaks down a practical framework for performing BAS sales takeoffs that improve accuracy, profitability, and project delivery.
What a BAS Sales Takeoff Actually Is
A BAS sales takeoff is the process of reviewing project documents to determine:
- What systems are included in the BAS scope
- What points are required
- What controllers and hardware are needed
- What integrations are required
- What labor and subcontractors must be included
- What assumptions, exclusions, and risks exist
Many estimators focus only on counting controllers or referencing equipment schedules. That approach may work on simple commercial jobs, but larger projects require a more detailed review process.
Hospitals, data centers, universities, and regulated environments often contain hidden scope that can destroy project margins if missed during estimating.
Why BAS Projects Go Sideways
According to Phil Zito, most BAS projects fail in two places:
- The takeoff
- The closeout
The takeoff phase creates the foundation for everything that follows. If the scope is missed during estimating, operations teams inherit the problem later during execution.
Common issues include:
- Missed integration requirements
- Unclear installation responsibilities
- Missing commissioning requirements
- Underestimated labor
- Incomplete sequences
- Vague specifications
- Incorrect assumptions about factory controls
These mistakes often lead to change orders, lost margin, delayed schedules, and disputes between contractors.
The Documents You Must Review
A complete BAS sales takeoff requires more than reviewing mechanical schedules.
1. Controls Specifications
The controls specification typically includes:
- Approved manufacturers
- Communication protocols
- Graphics requirements
- Trending requirements
- Alarm requirements
- Warranty requirements
- Training requirements
- Commissioning requirements
- Integration requirements
This section often contains scope that never appears on the drawings.
It also determines whether alternate manufacturers can be submitted.
2. Mechanical Drawings and Schedules
Mechanical drawings identify:
- Air handlers
- Rooftop units
- VAV boxes
- Boilers
- Chillers
- Pumps
- Cooling towers
The estimator must determine:
- Whether the equipment is fully controlled or integrated
- Who provides the controls
- Who installs the controls
- Whether field devices are included
- Whether VFDs, dampers, valves, or actuators are included
This is where many scope gaps begin.
3. Sequence of Operations
Sequences help identify:
- Operating modes
- Control strategies
- Setpoints
- Sensor requirements
- Alarms
- Special sequences
- Required integrations
Sequences also reveal when integrated equipment may require additional field devices because factory integration points are limited.
4. Electrical Drawings
Electrical drawings identify:
- VFD responsibilities
- Motor starters
- Disconnects
- Lighting controls
- Power requirements
- BAS panel responsibilities
Ignoring electrical drawings can result in missing hardware, wiring, or installation scope.
5. General Conditions and T&Cs
General conditions often contain hidden labor requirements, such as:
- Meetings
- Functional testing
- Documentation
- Closeout requirements
- Scheduling restrictions
- Liquidated damages
- Time of day restrictions
These items directly impact labor estimates and project risk.
Building the Equipment Matrix
A structured equipment matrix improves consistency during takeoffs.
A simple matrix should include:
- Equipment type
- Quantity
- Location
- BAS scope status
- Control type
- Integration type
- Notes
Example entries might include:
- Full BAS control
- BACnet integration only
- Monitoring only
- Start/stop/status control
This creates visibility into scope before estimating begins.
Understanding Points and Controller Requirements
Once systems are identified, the next step is determining point requirements.
This includes:
- Inputs
- Outputs
- Setpoints
- Alarms
- Trending points
- Network points
- Integration points
At this stage, estimators should verify whether factory integration cards expose all required points.
Many projects require additional sensors or field devices because integrated equipment does not expose every required value through BACnet or Modbus.
Controller Architecture Matters
Controller selection affects both hardware cost and system performance.
Estimators should determine:
- Supervisory controller requirements
- BACnet routing requirements
- IO expansion requirements
- Licensing impacts
- Power supply requirements
- Panel enclosure requirements
Larger systems may require advanced application controllers with distributed IO modules.
Environmental conditions also matter. Rooftop installations may require different enclosure types than indoor installations.
Common BAS Takeoff Mistakes
Counting Equipment Instead of Scope
Two air handlers may look similar on a schedule but require completely different control strategies.
One may require:
- Economizer control
- VFD control
- Heat recovery
- Enthalpy control
- Additional sensors
The other may require simple start/stop/status control.
Estimators who count equipment without understanding functionality often miss scope.
Ignoring Specification Details
Specifications frequently include requirements not shown on drawings, including:
- Naming standards
- Graphics requirements
- Training requirements
- Warranty requirements
- Commissioning requirements
- Integration standards
Sequence discrepancies between drawings and specifications are common.
Missing Responsibility Notes
Several phrases should immediately trigger clarification requests:
- Provided by BAS contractor
- Installed by BAS contractor
- Integrated by BAS contractor
- Controlled by BAS
- Monitored by BAS
- Coordinate with controls contractor
These statements often hide labor and material responsibilities.
Assuming Integrations Are Simple
BACnet integrations are easier than they were years ago, but problems still occur regularly.
Common issues include:
- Missing writable points
- Missing priority arrays
- Incorrect object types
- Gateway requirements
- Startup dependencies
- Point exposure limitations
Modbus integrations require even more verification because register mapping varies widely between manufacturers.
Structuring Labor Correctly
Labor should never be lumped together into one estimate category.
Breaking labor into categories improves visibility and performance tracking.
Recommended labor categories include:
- Field installation
- Engineering
- Programming
- Graphics
- Project management
- Commissioning and closeout
This structure allows companies to measure performance accurately across projects and teams.
Assumptions Versus Exclusions
Assumptions and exclusions are not the same thing.
Examples of assumptions include:
- Assume electrical contractor provides 120V power
- Assume normal working hours
- Assume factory controllers are provided with equipment
- Assume integration point lists are available before programming
Anything unclear should be clarified through RFIs or RFCs before submitting proposals.
A Practical BAS Takeoff Workflow
A repeatable BAS takeoff workflow should include:
- Build the equipment matrix
- Review all project documents
- Mark up drawings and sequences
- Build point lists
- Verify controller architecture
- Create RFIs and RFCs
- Finalize scope narrative
- Build estimate buckets
- Review risks and assumptions
- Conduct sales-to-operations handoff
The final handoff should include:
- Scope documents
- Assumptions
- Exclusions
- RFIs
- Marked drawings
- Point lists
- Vendor quotes
- Labor assumptions
- Risk notes
This ensures operations teams start with complete project visibility.
Final Thoughts
Strong BAS takeoffs are built on process, not guesswork.
Experienced estimators recognize patterns, validate scope carefully, and document assumptions clearly. The goal is not just winning projects. The goal is winning profitable projects that operations teams can execute successfully.
A structured takeoff process improves estimating accuracy, protects margin, reduces project risk, and creates better outcomes for both sales and operations teams.
For BAS professionals involved in estimating, sales engineering, or project delivery, mastering takeoffs is one of the highest-leverage skills in the industry.
For a deeper discussion and insights from the field, listen to this episode on the Smart Buildings Academy podcast.
%20(1920%20x%201080%20px)%20(10).png)
