A Practical Commissioning Guide for School Districts (K–12)
Commissioning (“Cx”) is a quality-assurance process that verifies your buildings perform as intended—comfort, indoor air quality (IAQ), safety, and energy use—from planning through occupancy and ongoing operations. For districts, good Cx reduces callbacks, stabilizes classrooms (temperature/ventilation), and makes it easier for staff to operate and maintain systems long-term.
Table of Contents
1) What commissioning is (and isn’t)
2) Choose the right type of commissioning
- A) New construction / major renovation (most common)
- B) Retro-commissioning (existing buildings)
- C) Re-commissioning (existing building that was commissioned before)
- D) Monitoring-based commissioning (MBCx)
3) Set district goals up front (the “OPR”)
4) Build the team and define roles
5) Budgeting rules of thumb (district-friendly)
6) Commissioning process by phase (what to do, when)
- Phase 1 — Planning (pre-design)
- Phase 2 — Design
- Phase 3 — Construction
- Phase 4 — Acceptance & functional testing (end of project)
- Phase 5 — Warranty & seasonal testing (months after turnover)
- Phase 6 — Ongoing performance (district portfolio)
7) Define the scope: what systems to commission in schools
8) Turnover package: what you should require (practical checklist)
9) How to procure commissioning (district-friendly RFP tips)
10) Common pitfalls in school commissioning (and how to avoid them)
1) What commissioning is (and isn’t)
Commissioning is a structured process to:
- Define what the district needs (performance, IAQ, maintainability, controls simplicity)
- Verify design aligns to those needs
- Verify construction matches design
- Functionally test systems in real operating modes
- Train staff and hand over usable documentation
- Resolve issues during the warranty period and improve ongoing performance
Commissioning is not:
- Just “TAB” (testing & balancing)
- Just “startup” by vendors
- A punch list substitute
- “One day of functional testing” at the end
2) Choose the right type of commissioning
Use the project type to decide the Cx approach:
A) New construction / major renovation (most common)
Best for new schools, additions, full HVAC replacements, and major controls work.
B) Retro-commissioning (existing buildings)
For schools with comfort complaints, high utility bills, or inconsistent controls. Focus is finding/fixing operational issues.
C) Re-commissioning (existing building that was commissioned before)
Periodic checkup (often every 3–5 years) or after big staffing/control changes.
D) Monitoring-based commissioning (MBCx)
Uses trend data/alarms to maintain performance continuously (great for districts with limited staff across many buildings).
3) Set district goals up front (the “OPR”)
Before design begins, write an Owner’s Project Requirements (OPR)—a short, plain-English document that becomes the project’s “north star.”
Typical school-district OPR goals:
- Thermal comfort: stable classroom temps during occupied hours
- IAQ: ventilation meets requirements, CO₂ controlled where applicable, filtration targets
- Humidity control: prevent mold/condensation (especially in humid climates)
- Noise: classroom acoustics (avoid loud RTUs/VAV boxes)
- Energy: reasonable EUI ((Energy Use Intensity) targets and controls sequences that actually save energy
- Maintainability: standard parts, consistent sequences across campuses
- Operational simplicity: schedules, overrides, alarming, dashboards that staff will use
- Safety: smoke control interfaces, emergency modes, secure access to controls
- Training & documentation: “usable on day 1,” not binder-on-a-shelf
Pro tip: Add “district standards” here (preferred control vendor, naming conventions, graphics expectations, point lists, valve/actuator brands, filter MERV targets, etc.).
4) Build the team and define roles
District-side roles
- Owner/Facilities lead: decision-maker, standards, acceptance
- Maintenance & controls staff: critical reviewers of sequences, graphics, trending, training
- School administrators: occupant needs, schedules, comfort priorities
- IT: network/security requirements for BAS, remote access, OT segmentation
- Risk management / safety: emergency response and compliance needs
Project roles (typical)
- Commissioning Authority (CxA): independent or third-party lead for the Cx process
- A/E (Engineer/Architect): design and responses to Cx issues
- GC/CM: coordination, schedules, trades accountability
- Controls contractor: sequences, programming, point-to-point, trending, graphics
- TAB: airflow/waterflow balancing (coordinate tightly with CxA)
- Vendors: RTUs, boilers, chillers, DOAS, lighting controls, etc.
Independence matters: For larger projects, districts often use a CxA that is independent of the design and construction teams to reduce conflicts of interest.
5) Budgeting rules of thumb (district-friendly)
Costs vary by complexity, but a practical way to budget:
- New construction/major renovation: often ~0.5%–2% of MEP cost (more complex systems = higher)
- Retro-Cx: often priced by building size and system complexity, plus a repair allowance
- MBCx: includes setup + ongoing analytics/service; plan for an annual operating line item
Where districts get the most value
- Controls verification (sequences and trends)
- Ventilation/IAQ verification (especially after COVID-era changes)
- Training + usable turnover deliverables
- Fixing “death-by-a-thousand-cuts” issues across many buildings
6) Commissioning process by phase (what to do, when)
Phase 1 — Planning (pre-design)
Deliverables
- OPR (district goals)
- Preliminary Cx scope (which systems will be commissioned)
- District BAS/controls standards (naming, graphics, trend expectations)
- Commissioning plan outline + schedule integration
Key district actions
- Decide which buildings/systems are in scope
- Identify who will maintain the systems (and their preferences/constraints)
- Include IT/network requirements early (remote access, cybersecurity)
Phase 2 — Design
CxA tasks
- Review design documents at key milestones (SD/DD/CD)
- Confirm sequences of operation are testable and match the OPR
- Confirm access for maintenance and filter changes
- Confirm metering/trending points exist for verification
Design-phase “must-haves” for schools
- Clear ventilation strategy (DOAS vs mixed air, VAV minimums, economizer logic)
- Humidity control approach (especially with high outdoor air)
- Setpoint and schedule strategy (school-day vs after-hours events)
- CO₂ sensors strategy (where, how used, calibration expectations)
- Safe, simple overrides (custodial and events)
- Alarming strategy (what alarms matter, who receives them, escalation)
Deliverables
- Updated Cx plan
- Design review comments + resolution log
- Draft test procedures outline (so testability is ensured)
Phase 3 — Construction
CxA tasks
- Submittal reviews focused on performance and maintainability
- Site observations (not continuous inspection, but targeted)
- Construction checklists (installation verification)
- Issues log (track problems, owners, due dates)
District must-do
- Require contractor participation in Cx meetings
- Enforce documentation quality (as-builts, O&M manuals, controls exports)
Common school-specific construction issues
- Outdoor air dampers wired backwards or stuck
- VAV minimums set too low/high
- Unit heaters/RTUs not integrated into schedules
- CO₂ sensors in bad locations (direct supply air, near doors)
- Controls points mislabeled or missing
- Economizers disabled “temporarily” and never re-enabled
Phase 4 — Acceptance & functional testing (end of project)
This is where systems are tested in real modes, not just “it turns on.”
Functional Performance Testing (FPT) typically includes
- Occupied/unoccupied schedule transitions
- Warm-up/cool-down
- Ventilation modes (minimum OA, demand control, economizer)
- Heating/cooling changeover
- Humidity control modes (if applicable)
- Alarms and safeties
- Power loss/restart behavior
- Interface to fire alarm/smoke control where relevant
Critical dependencies
- TAB must be complete (or at least staged appropriately)
- Controls programming substantially complete
- Trending enabled before testing so you can prove stability
Acceptance deliverables
- Completed test forms with pass/fail and notes
- Issues log closed or with agreed plan
- Controls deliverables (see “turnover package” below)
- Training sessions + recordings/materials
Phase 5 — Warranty & seasonal testing (months after turnover)
Schools operate differently across seasons. Plan follow-up tests:
- Heating season tests (morning warm-up, ventilation with cold OA)
- Cooling season tests (dehumidification, economizer lockouts, hot days)
- Shoulder season tests (mixed modes and changeover)
District action
- Keep the issues log alive through warranty
- Require timely fixes while coverage is in effect
Phase 6 — Ongoing performance (district portfolio)
This is where districts win long-term:
- Standardize sequences across campuses
- Trend and review top problem buildings monthly
- Maintain sensor calibration plans
- Use “recommissioning” every few years, or after staff/vendor changes
7) Define the scope: what systems to commission in schools
Typical Cx scope for K–12
- HVAC: boilers/chillers, RTUs, VAVs, DOAS, exhaust, unit heaters, pumps, heat recovery
- BAS/controls: sequences, graphics, trends, alarming, schedules, point naming
- TAB coordination and verification
- Ventilation/IAQ: outdoor air measurement strategy, CO₂ control, filtration
- Domestic hot water (as needed)
- Lighting controls / daylighting (often worth including)
- Specialty: kitchens, labs, pools, gyms, performing arts (high-impact spaces)
8) Turnover package: what you should require (practical checklist)
Ask for deliverables you’ll actually use:
Controls/BAS deliverables
- Point list with names, units, ranges, and descriptions
- Sequences of operation as implemented (not just design intent)
- Trending setup (what’s trended, at what interval, and where it’s stored)
- Graphics standards + graphics for all equipment
- User roles/security settings (aligned to IT policy)
- Backup/export of the control database/programs
- Alarm list with priorities and recipients
O&M deliverables
- Equipment O&M manuals and warranty info
- As-builts (MEP + controls)
- TAB report
- Recommended preventive maintenance plan
- Spare parts list (filters, belts, critical sensors)
Training deliverables
- Operations training for facilities staff (hands-on, not slides-only)
- “Day-in-the-life” training: schedules, overrides, alarms, troubleshooting
- Quick-reference guides (1–2 pages per system type)
9) How to procure commissioning (district-friendly RFP tips)
When issuing an RFP for a CxA, include:
- Project list and system types
- Expectations for design reviews, site visits, functional testing, warranty support
- Required deliverables (Cx plan, issues log, test scripts, final report)
- Coordination requirements with TAB and controls contractor
- Experience with schools and occupied-campus constraints
- Staff qualifications and availability during peak testing windows
- A clear schedule with milestone dates and seasonal testing expectations
Selection criteria (beyond low price)
- Demonstrated K–12 experience (comfort/IAQ/controls challenges)
- Strong controls expertise
- Clear, sample deliverables (test forms, reports, issues log quality)
- Ability to communicate with both engineers and district operators
10) Common pitfalls in school commissioning (and how to avoid them)
- Cx starts too late → Hire CxA in planning or early design
- Unclear OPR → Write simple goals and “district standards” up front
- Controls treated as a black box → Require point naming, trends, and sequences as implemented
- No time for seasonal testing → Put it in the contract and schedule
- Training is performative → Require hands-on sessions + quick guides + recordings
- Issues log gets ignored → Make it a standing agenda item; assign owners and due dates
- IT/security left out → Involve IT early; define network and remote access requirements
11) A simple commissioning timeline (example)
- Pre-design: OPR + CxA selection + Cx plan outline
- Design (SD/DD/CD): design reviews + testability + sequences finalized
- Construction: checklists + submittal reviews + issues log + periodic site visits
- Pre-occupancy: TAB + controls completion + FPT + training
- 0–12 months: seasonal testing + warranty fixes + final Cx report
- Ongoing: MBCx or periodic recommissioning
Learn More About Bluerithm
Learn more about how Bluerithm supports commissioning for school districts
See how Bluerithm supports commissioning for educational buildings including elementary schools, high schools, K-12 schools, and school districts
How San Diego Unified School District Doubled Project Capacity with Bluerithm's Cloud-Based Commissioning Software
LEED Certification Commissioning Projects
Learn how Green Star Engineering conducted a major commissioning project with a school district in Houston to systematically replace all HVAC control systems for more than 70 locations.
