%20(1920%20x%201080%20px).png)
Episode Description:
Owner-direct BAS projects can be some of the highest-margin opportunities you'll encounter. They can also become some of the riskiest.
The difference often comes down to what happens before a proposal is ever written.
If you're treating an owner-direct job walk the same way you treat a plan-and-spec walkthrough, you may be missing critical information that impacts scope, labor, risk, and profitability.
In this episode, you'll learn how to approach site walks as structured discovery sessions, uncover hidden project risks, identify the real drivers behind upgrade requests, and build scopes that align with owner expectations.
Topics Covered
• Why owner-direct job walks require a different approach than traditional bid projects
• The questions that uncover the real reason a customer is pursuing an upgrade
• What to inspect before, during, and after a site walk
• Common hidden scope items that can destroy project margins
• How to turn site findings into a clear scope, estimate, and proposal
A better site walk leads to better projects, fewer surprises, and stronger customer outcomes. Listen to discover the framework.
Click here to download or listen to this episode now.Podcast Video
How to Perform an Owner-Direct BAS Job Site Walk That Leads to Better Projects
Owner-direct building automation projects present a unique opportunity for controls contractors, integrators, project managers, and facility teams. Unlike traditional plan-and-spec projects, owner-direct work often carries higher margins, greater flexibility, and more direct access to decision makers.
It also carries more risk.
Many BAS retrofit projects that go over budget, experience delays, or fail to meet expectations can be traced back to one common issue: an incomplete job site walk.
A successful owner-direct project begins long before a proposal is written. It starts with understanding the owner's objectives, assessing the true condition of the building systems, and uncovering hidden risks that may not appear in drawings or conversations.
Why Owner Direct Job Walks Are Different
In a traditional construction project, contractors typically receive plans, specifications, sequences, and documentation that define the project scope.
Owner-direct projects rarely offer that luxury.
Facility drawings may be outdated. Sequences may be missing. Controllers may have been replaced over the years without documentation. Existing operators may not fully understand how the system was originally intended to function.
This means the job walk becomes more than a site visit. It becomes a discovery process.
The goal is not simply to count devices and inspect equipment. The goal is to understand the current state of the building and determine whether the proposed project will solve the owner's actual problem.
Start by Understanding the Owner's Desired Outcome
Before opening a control panel or inspecting a mechanical room, take time to understand why the project exists.
Some of the most valuable questions include:
- What prompted this project?
- What is not working today?
- Which areas generate the most complaints?
- Is the issue comfort, reliability, energy performance, or something else?
- What does success look like after the project is complete?
- Is funding already approved?
- Are there deadlines or operational constraints?
Many owners begin with a proposed solution in mind. Your job is to understand the problem they are trying to solve.
Sometimes the answer is a BAS upgrade. Sometimes it is training, operational changes, or correcting maintenance practices.
Without understanding the desired outcome, it is impossible to build an accurate scope.
Gather Information Before You Arrive
A productive job walk starts before you step on site.
Request as much information as possible, including:
- Mechanical drawings
- Control drawings
- Points lists
- Sequences of operation
- Network architecture diagrams
- Service histories
- Trend logs
- Alarm histories
- Utility data
- Capital improvement plans
Even if the documentation is incomplete, reviewing it beforehand helps identify areas that require further investigation during the walk.
Review the BAS Front End First
Many site walks begin in the mechanical room.
A more effective approach is to start with the BAS front end.
The front end often reveals critical information about how the facility actually uses its control system.
Look for:
- User activity
- Alarm management practices
- Trending configurations
- Scheduling strategies
- Offline devices
- Communication failures
- Graphic quality
- Backup availability
A system that is actively used tells a different story than a server nobody has logged into for years.
Understanding how operators interact with the BAS can provide valuable insight into the project's true drivers.
Inspect Mechanical and Control Infrastructure
After reviewing the front end, move into the field.
Document the condition of:
BAS Panels
Open every panel possible.
Inspect:
- Controllers
- Relays
- Transformers
- Terminal strips
- Communication wiring
- Labeling quality
- General workmanship
Take photographs and record model numbers whenever possible.
Central Utility Plants
The central plant often offers the greatest opportunity for operational improvement.
Review:
- Chillers
- Boilers
- Pumps
- Cooling towers
- Associated control strategies
Document how equipment is controlled and identify any obvious deficiencies.
Air Handling Equipment
Inspect:
- Air handlers
- Rooftop units
- DOAS units
- Make-up air units
Pay attention to:
- Valve operation
- Damper operation
- Actuator condition
- Filter condition
- Coil condition
- Accessibility
Terminal Units
Terminal devices frequently create hidden labor costs.
Verify:
- Unit counts
- Accessibility
- Ceiling conditions
- Security restrictions
- Existing controls
Poor access can significantly impact project labor estimates.
Identify Hidden Scope Items
One of the most important objectives of a job walk is uncovering work that may not appear in the initial request.
Common hidden scope items include:
Wiring Problems
Watch for:
- Abandoned wiring
- Improper splices
- Mixed voltage conditions
- Damaged conduit
- Shared transformers
- Poor communication wiring practices
Obsolete Controllers
Determine:
- Whether replacements are available
- Whether programs can be extracted
- Whether integration options exist
Controller obsolescence often drives project scope expansion.
Failed Field Devices
Graphics can be misleading.
Verify actual field operation of:
- Sensors
- Actuators
- Valves
- Switches
- Flow devices
- Pressure devices
Do not assume the displayed data is accurate.
Mechanical Issues Masquerading as Controls Problems
This is one of the most expensive mistakes estimators make.
A failed valve, stuck damper, dirty coil, broken belt, or worn VFD may appear to be a controls problem.
If these issues are not identified during the walk, they often become unexpected project costs later.
Understand Access and Operational Constraints
Project success depends heavily on understanding the environment where work will occur.
Ask questions about:
- Occupied spaces
- Shutdown windows
- School schedules
- Healthcare restrictions
- Security requirements
- Escort requirements
- Lift requirements
- Noise limitations
- Tool restrictions
These factors can dramatically affect labor estimates and project schedules.
Document Everything
A structured documentation process improves both estimating accuracy and project execution.
Create a report that includes:
- Project overview
- Owner objectives
- Existing BAS summary
- Equipment inventory
- Network architecture notes
- Identified deficiencies
- Risk items
- Scope opportunities
- Assumptions
- Clarifications
- Recommended next steps
Support your findings with photos, screenshots, equipment lists, and field notes.
The more information captured during the walk, the fewer surprises will appear later.
Building the Project Scope
Once the walk is complete, organize the project into three categories.
Base Scope
The minimum work required to solve the owner's problem.
Examples include:
- Front-end upgrades
- Supervisory controller replacement
- Major controller replacements
- Graphics rebuilds
Recommended Scope
Items that improve project success but are not strictly required.
Examples include:
- Sensor replacement
- Actuator replacement
- Additional trending
- System cleanup
Alternate Scope
Optional enhancements that provide additional value.
Examples include:
- Guideline 36 implementation
- Terminal unit upgrades
- Standardization efforts
- Operator training packages
Clearly identify exclusions and owner responsibilities to avoid misunderstandings.
Common Job Walk Mistakes
Several mistakes consistently create project problems:
- Failing to qualify the opportunity before visiting
- Moving through the site too quickly
- Speaking only with leadership
- Ignoring operators and maintenance personnel
- Failing to open panels
- Assuming existing devices work properly
- Overlooking access restrictions
- Failing to document assumptions
- Treating mechanical failures as controls scope
Avoiding these mistakes can dramatically improve project outcomes.
A Better Job Walk Creates Better Projects
The purpose of an owner-direct BAS job walk is not simply to gather equipment counts.
It is to understand the owner's goals, evaluate the true condition of the facility, identify hidden risks, and develop a realistic project scope.
The most successful retrofit projects begin with a structured discovery process that combines technical evaluation with operational understanding.
When performed correctly, a job walk reduces risk, improves estimating accuracy, strengthens customer trust, and creates a clear path from discovery to project execution.
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(2).png)
