Home/Resources/HVAC Design-Build/Sequences of operation, points lists, and BAS scope explained
Guide · 10 min read

Sequences of operation, points lists, and BAS scope explained

A sequence of operations is the written logic that tells your HVAC system how to behave; a points list is the inventory of every sensor, output, and value the controls system reads and writes. Together they are the heart of an HVAC controls scope — and writing them vendor-neutral is what keeps a building owner from being locked to a single controls contractor for the life of the building.

Section 01

What a sequence of operations actually is

A sequence of operations (SOO) is plain-language and logic-diagram documentation of how each piece of equipment should run: when it starts and stops, what setpoints it holds, how it stages, how it responds to occupancy and outdoor conditions, and what it does on a fault.

It is the difference between equipment that is merely energized and a system that actually controls the building. A good SOO is specific enough that two different controls contractors would program the same behavior from it.

Section 02

What a points list is and why it matters

A points list enumerates every input and output the building automation system touches — temperature and pressure sensors, valve and damper positions, fan and pump commands, status feedbacks, setpoints, and alarms. Each point is typed as analog or binary, input or output.

The points list drives controller sizing, wiring, and cost. It is also where scope disputes get settled: if a point is not on the list, it is not in the bid, and the owner discovers the gap during commissioning. A thorough points list at design time prevents that.

Section 03

ASHRAE Guideline 36 and high-performance sequences

ASHRAE Guideline 36 publishes standardized, high-performance control sequences for common HVAC systems — VAV boxes, air handlers, and more. Specifying to Guideline 36 gives you vetted logic that controls contractors can implement consistently, instead of every job reinventing the sequence.

For an owner, referencing Guideline 36 in the controls scope is a quality floor: it raises the baseline of how well the building runs and makes competing bids more comparable.

Section 04

Why vendor-neutral controls protect the owner

Many controls contractors will happily write a sequence around their proprietary platform. The result is a building that can only be serviced, expanded, or re-programmed by that one vendor — and the owner pays monopoly prices for every future change.

A vendor-neutral scope specifies open protocols (such as BACnet) and behavior rather than a brand. It keeps future service competitive and lets the owner change controls contractors without ripping out the system. This is one of the most valuable things a design-assist partner does on the owner's behalf.

Section 05

DDC vs. legacy controls

Modern commercial buildings use direct digital control (DDC): microprocessor-based controllers that read sensors, run the sequence, and command equipment, all networked to a front end. DDC is what makes trending, alarming, and remote access possible.

Older buildings may still run pneumatic or simple electromechanical controls. A controls retrofit to DDC is often the highest-return HVAC upgrade an existing building can make, because it unlocks both efficiency and visibility — frequently without touching the mechanical equipment.

Section 06

Where controls fit in design-build and commissioning

In design-build, the controls scope is written alongside the equipment design, so the sequence reflects the system that is actually being installed — not a generic template. The points list is coordinated with the electrical and equipment design before anything is ordered.

At commissioning, the sequence becomes the test script. Functional performance testing verifies the system behaves exactly as the SOO specifies, point by point. A building is not commissioned until its sequences have been proven, not just its equipment turned on.

Operator FAQ

Quick answers

What is the difference between a sequence of operations and a points list?

A sequence of operations is the written logic for how equipment should behave — start/stop, setpoints, staging, fault response. A points list is the inventory of every sensor, output, command, and value the controls system reads or writes. The sequence is the behavior; the points list is the hardware and data that make it possible.

What is ASHRAE Guideline 36?

ASHRAE Guideline 36 is a published set of standardized, high-performance control sequences for common HVAC systems. Specifying to it gives owners vetted control logic and makes controls bids more consistent and comparable.

Why should HVAC controls be vendor-neutral?

Vendor-neutral controls specified on open protocols like BACnet keep a building serviceable and expandable by more than one contractor. Proprietary controls lock the owner to a single vendor for all future service and changes, usually at premium prices.

Is a controls upgrade worth it for an older building?

Often it is the highest-return HVAC investment an existing building can make. Retrofitting to direct digital control unlocks efficiency, trending, alarming, and remote access — frequently without replacing the mechanical equipment.

Get help

Planning a commercial HVAC project in Tampa Bay?

Suncoast Cold Systems delivers commercial HVAC design-build across Tampa, St. Petersburg, Clearwater, Brandon, Riverview, Temple Terrace, and Wesley Chapel — load calcs, equipment selection, layouts, controls, install, and commissioning under one contract. Licensed Class A A/C Contractor (FL #CAC1824642), with a Florida PE of record on sealed work.

HVAC design-build Start a conversation
More

Keep reading

Compliance8 min

What a Florida Class A contractor can legally design

The 471.003(2)(h) thresholds and the PE-seal boundary.

Read the note
Guide9 min

Design-build vs design-bid-build for commercial HVAC

Schedule, cost certainty, and accountability compared.

Read the note
For engineersLanding

A design-assist partner for mechanical engineers

Controls scope, constructability, and field follow-through.

Read the note