Integrated automation closeout is reviewed by the commissioning authority, the owner's facilities and energy team, and the mechanical engineer, because the building automation system is what they will operate every day. A package missing as-built sequences or controller backups leaves the owner unable to run or modify the system they paid for.
Every document required in a Division 25 Integrated Automation closeout package, including who provides it and when it applies.
| Document | Applies |
|---|---|
| As-Built Sequences of Operation (Final) | Always |
| BAS Point-to-Point Checkout Reports | Always |
| Functional Performance Test (FPT) Records | Always |
| Control System Commissioning Report | If applicable |
| BAS O&M Manual (System-Specific) | Always |
| Controller & Graphics Program Backups | Always |
| Network Topology & Riser Diagrams (As-Built) | Always |
| BAS Software License Certificates | Always |
| Operator Training Records | Always |
Division 25 is the connective tissue of a modern building. The building automation system ties HVAC, lighting, metering, and often Division 21 and 28 life-safety points into one supervisory network, so its closeout documentation comes almost entirely from a single source: the controls contractor or system integrator. That concentration sounds like it should make collection simple. In practice it does the opposite, because the integrator is usually the last trade to finish, completing programming, graphics, and functional testing after every other system has been energized and balanced.
The documentation gap on this division is rarely about missing binders. It is about version drift. Sequences get tuned during commissioning, set points are adjusted after the TAB contractor balances the air and water systems, and controller code is patched right up to the acceptance test. The as-built record that lands in the closeout package frequently reflects the submittal version, not the logic actually running in the field. Add the items almost no one asks for, namely the controller and graphics database backups, the BACnet or LON device address tables, and the software license certificates, and you have a package that looks complete on a table of contents but cannot actually rebuild the system.
What is at stake here is operational control, not just retainage. When the warranty expires and a future integrator (sometimes a different manufacturer's dealer) is hired to expand the system, they need the program backups and network documentation to touch it without starting from scratch. Owners and their commissioning authorities know this, which is why BAS closeout is gated tightly: many specifications tie the integrator's final payment and the start of the warranty period to an approved commissioning report, accepted record drawings, and delivered training. Hand over an incomplete package and you may find the warranty clock does not start and the administrative access credentials never transfer.
What each document is, why it's required, and what to watch for. Written for the GC PM collecting documents from multiple subs and engineers.
The final sequences must describe the logic as actually programmed and tuned in the controllers at acceptance, including occupied and unoccupied modes, economizer and reset strategies, staging, alarm limits, and safeties. During commissioning, integrators routinely adjust loop tuning, set points, and staging logic, and the original design narrative rarely captures those changes. The owner's facilities staff rely on these sequences daily to diagnose comfort complaints and to understand why the system behaves the way it does.
Require a sequence-by-sequence comparison against the approved submittal. If the integrator hands you the same narrative submitted as a shop drawing, that is the design version, not the as-built.
Point-to-point checkout verifies every physical and virtual point end to end: the field sensor or actuator, the wiring, the I/O termination, and the value displayed at the operator workstation. The report lists each point by controller and object name with its checkout result and any calibration offset. This is the foundational record that the installation is wired, addressed, and calibrated correctly before functional testing begins.
Confirm the point count in the report matches the I/O point list in the approved submittal. A checkout that covers only representative points rather than every point is not complete and is a common shortcut.
Functional performance testing exercises each sequence under simulated and real conditions to confirm the system responds as designed: failure modes, interlocks, staging, setback, and alarm annunciation. On commissioned projects the commissioning authority witnesses these tests and compiles them into a commissioning report with an issues log. Each test record should show the expected result, the observed result, and a pass or fail disposition.
A commissioning report with open issues is not finished. Every line in the issues log should read resolved or formally deferred with written owner acceptance before the report enters the closeout package.
The operations and maintenance manual for the automation system covers the supervisory software, controllers, gateways, and field devices actually installed, with model numbers, configuration settings, and maintenance procedures. It should include the point naming convention, the alarm and trend configuration, and instructions for backing up and restoring the database. Generic manufacturer literature pulled from a website does not satisfy this requirement.
Tie your O&M content to the as-built point list and network diagram. A binder of cut sheets with no system-specific configuration data will be returned.
The closeout package must include the actual program and database files: controller logic, the graphics and screens database, the point database, and any custom programming. These backups are what allow a future technician to restore a failed controller or modify the system without rebuilding it from observation. Many owners discover these files were never delivered only when a controller fails out of warranty.
Ask for the editable program files in the manufacturer's native engineering format on owner-controlled media, not just PDF screenshots of the graphics. Confirm the files actually open in the engineering tool.
As-built network documentation shows the supervisory and field-bus architecture: controller locations, BACnet/IP, MS/TP, and LON segments, device addresses (MAC and instance numbers), gateway locations, IP assignments, and cable routing. This is the map a future integrator needs before touching the system. It must reflect the installed network, including any field changes to addressing or routing made during startup.
Verify device addresses and instance numbers on the diagram against the live device list at the operator workstation. Address tables drift during commissioning when controllers are added, moved, or re-addressed.
Building automation platforms are licensed software protected by tiered passwords. The closeout package must transfer the software license certificates to the owner along with administrator-level credentials, so the owner is not captive to a single service provider. Without the licenses and admin access, the owner holds a system they cannot fully program or expand, and the proprietary engineering tools may revert to the integrator. This item is frequently overlooked because it has no physical deliverable.
Confirm the license is registered to the owner, not the integrator, and that administrator or operator credentials are formally transferred in writing. View-only access is not ownership.
The codes and standards that define what's required in a Division 25 Integrated Automation closeout package. Reference these when an owner or architect pushes back.
Defines the BACnet protocol used by most building automation systems. As-built network documentation should identify device and object instances and the protocol versions in use for interoperability.
Establishes the overall commissioning process and documentation, including functional performance testing and the systems manual that BAS closeout feeds into.
Provides the technical commissioning requirements for HVAC controls, including point-to-point checkout, sequence verification, and functional performance testing.
Mandates direct digital control capabilities, economizer and reset strategies, and controls commissioning that the as-built sequences and FPT records must demonstrate.
International standard series covering BACS hardware, software, functions, and the BACnet data communication protocol, sometimes referenced for BAS functional and documentation requirements.
These are the specific issues that cause owner rejection, AHJ refusal, or retainage holds. Each one is documented with the root cause and how to prevent it.
This is the most common rejection on Division 25. The integrator tunes loops, changes set points, and revises staging during commissioning, then submits the original shop-drawing narrative as the as-built. Reviewers compare the narrative against the commissioning trend data and find set points and modes that do not match what is actually running.
Have the integrator redline the approved sequence narrative with every change made during startup, or export the sequence logic directly from the controller.
Keep a running markup of sequence changes during commissioning rather than reconstructing them from memory at the end.
Specifications require verification of every I/O point, but integrators sometimes document a sample and extrapolate. Owners and commissioning authorities cross-check the report against the I/O point list and reject the package when terminal units, exhaust fans, or metering points are missing.
Compare the checked point count in the report to the submittal point list. Unaddressed controllers and skipped terminal-level points are the usual gaps.
The package includes a polished O&M binder but no editable controller program, graphics database, or point database. Without the source files the owner cannot restore a failed controller or expand the system, so reviewers who know to look for the backups reject the package as unusable for long-term operation.
Require the files in the manufacturer's native engineering format on owner-controlled media, and verify they open. PDF screenshots of the graphics are not a backup.
Many BAS platforms are licensed and protected by tiered passwords. If the license stays in the integrator's name or the owner receives only view-only access, the owner is locked to one service provider and cannot fully operate or modify what they bought.
Confirm the license certificate names the owner and that administrator-level credentials are transferred in writing as a closeout condition, not left in the integrator's control.
BACnet device instances, MS/TP MAC addresses, and IP assignments are frequently changed during startup as controllers are added or re-addressed. An as-built network diagram that reflects the design rather than the field leaves a future integrator unable to find devices on the bus.
Spot-check several device addresses and instance numbers on the diagram against the workstation device list before accepting the network documentation.
The MasterFormat specification sections that govern Division 25 Integrated Automation closeout. Pull these from the project spec to confirm exact requirements for your project.
The broadscope section establishing general requirements, submittals, and closeout deliverables for the automation system.
Governs the O&M manual content, record documents, and maintenance requirements for the BAS.
Covers supervisory controllers, servers, and network hardware; review for what network documentation must be delivered.
The control and monitoring network requirements (BACnet, LON, Modbus); relevant to as-built topology and device addressing.
Field and application-specific controllers; review for point lists and checkout requirements.
The control sequences section; the as-built sequences of operation must conform to and update this content.
Use this checklist when collecting documents from your subs and engineer. Print or save as PDF for your project files.
The things that don't appear in the spec but that experienced GC PMs know from hard experience. These are the insights worth sharing.
The integrator's as-built sequences, FPT records, and trend data only exist after commissioning is finished. If you wait until the general punch list is closed, the integrator has often demobilized and trend logs may be purged from a temporary server. Capture the program backups and trend exports the week functional testing wraps.
A PDF of the graphics looks like documentation but cannot restore a failed controller. The deliverable that matters is the native engineering database (WebCTRL, Metasys, Desigo, Niagara, EcoStruxure, and similar) that lets a future technician re-download logic. Make 'controller and graphics database backup, verified to open' an explicit line item.
BAS platforms are licensed software with tiered passwords. Owners who accept view-only access discover at the first expansion that they are locked to one dealer. Tie transfer of the owner-registered license and administrator credentials to the integrator's final pay application.
The BAS set points should match what the TAB contractor balanced to and what the mechanical sequences require. When duct static, minimum outside air, or differential pressure set points in the as-built sequences disagree with the TAB report, reviewers notice. Coordinate Division 25 and Division 23 closeout so the numbers agree.
Questions GC PMs and subcontractors ask most often about Division 25 Integrated Automation closeout.
Closeout Desk collects, classifies, and organizes all your Division 25 Integrated Automation documentation, plus every other division on the project. We flag what's missing before you submit, so you're not discovering gaps after the owner reviews the package. Fixed-fee pricing. Delivered in 1–10 business days depending on urgency.
Related reading
Closeout Documentation: DIY vs. Hiring a Service (Real Cost Breakdown)
9 min read
Free HVAC Closeout Checklist: Every Document Required for Division 23
7 min read
Division 26 Electrical Closeout: Arc Flash Study, Panel Schedules, and NETA Testing
9 min read
What Is Substantial Completion? Retainage, G704, and What Happens Next
8 min read
Other division guides
Closeout Desk