Construction closeout data: as-builts, O&M manuals, and new asset records

Reference article · 6 min read

Every capital project ends with two handovers. One is physical: the building, the pump station, the radio site, the interchange. The other is informational, and it is the one that tends to go badly. The punch list closes, final payment goes out, and the agency discovers months later that nobody can say what model the rooftop units are, which panel schedule is current, who holds the controls passwords, or whether the lift station pumps are still under warranty. A technician stands in front of an untagged piece of equipment with no record in the work order system and no path to the manufacturer.

That is usually a specification failure rather than a contractor failure. Closeout language in many public specifications was written for a paper world: submit record drawings and three binders of cut sheets. If the agency instead defines closeout as a structured data handover, with named fields, named formats, and an acceptance test, it gets records it can load into the systems that actually run the facility. Tying a payment milestone to acceptance of that data is what makes it happen on schedule rather than a year late.

Name the deliverable: an asset record, not a binder

Write the asset list into the specification as a tabular deliverable with defined columns, and state that the agency, not the contractor, defines the schema. At minimum, require one row per maintainable asset with:

• Identity. Asset tag or barcode as physically applied, asset type or class from the agency's own taxonomy, and parent system.
• Nameplate data. Manufacturer, model number, serial number, capacity or rating, voltage, and year of manufacture.
• Location. Building, floor, room or space number, and where applicable a coordinate or station reference that matches the agency's GIS.
• Commercial data. Supplier, installing subcontractor, substantial completion date, warranty start and end dates, warranty terms, and the contact for warranty claims.
• Service data. Manufacturer-recommended maintenance tasks and intervals, filter and belt sizes, lubricant types, and recommended spare parts.

Require that the tags on the equipment match the tags in the file. Mismatched or missing physical tags are the single most common reason a clean spreadsheet still fails to become a usable asset register. Specify who applies tags, what material and format they use, and that tagging is verified during the walkthrough.

Controls, keys, and credentials

Building automation, SCADA, access control, and lighting systems carry a second layer of records that rarely appears in closeout specifications and is expensive to reconstruct later.

• Point lists and programming. Require the full controller point list with object names, units, and network addressing, plus exported programming, graphics files, and database backups in a form the agency can restore without the original integrator.
• Protocol documentation. Where open protocols such as BACnet or Modbus are specified, require the device profiles and the integration documentation that show what is actually exposed.
• Credentials. Require administrator accounts to be delivered to the agency, factory and vendor default credentials to be changed, and a written record of accounts, roles, and licensing.
• Keying and access. Require the keying schedule, key bitting, core and cylinder records, and the credential and cardholder configuration for electronic access control, delivered to the agency's security or facilities lead rather than left with the installer.

Drawings and manuals in formats you can actually use

Specify format and structure, not just submission. Ask for record drawings in the native authoring format as well as PDF, with layers and sheet naming intact, and state whether a model is required and at what level of development. If the agency uses a model-based handover, an open data-exchange format such as COBie is commonly specified for equipment and space data; the useful part is the discipline of defining required fields, not the file extension.

For O&M manuals, require a searchable, text-based PDF organized by specification section and asset tag, with an index that maps each manual to the asset rows it covers. Commissioning reports, test and balance reports, functional performance test results, training records, and remaining deficiency logs belong in the same package, indexed the same way.

Where the data lands

Closeout data is worth what the receiving systems make of it. Decide before bid where each field goes and who loads it: the enterprise asset management or work order system, the BAS front end, the GIS, the space and facilities inventory, and the IT asset inventory for anything networked. Assign an owner for the load, budget the time, and plan a reconciliation pass that compares what was submitted against what exists.

Networked devices deserve a separate look. Controllers, cameras, meters, and gateways arriving at the end of a construction project are new endpoints on an agency network, and they should reach the IT and security inventory with the same rigor as any other device, including firmware versions and network configuration.

Make data acceptance a payment milestone

Documentation submitted after final payment rarely arrives complete. The reliable lever is to define a closeout data milestone, withhold a portion of retainage or a defined final payment against it, and state the acceptance test in the specification: the agency loads a sample of rows into the target system, spot checks tags in the field, restores a controls backup, and confirms the manuals open and match. Prompt payment and retainage rules are set by state statute and local ordinance and vary considerably, so confirm with procurement and counsel that the structure you want is permitted and that the acceptance criteria are objective enough to survive a dispute.

How to start

1. Write the agency's field schema once and reuse it across projects rather than negotiating it per job.
2. Require a sample submission early, at roughly the first major equipment delivery, so format problems surface before the end of the job.
3. Put a named agency reviewer on the acceptance step and give that person authority to reject.
4. Include the training, warranty tracking, and system load in the project budget instead of the operating budget.

HQT works with state and local agencies on asset data structure, system integration, and technology requirements in capital project specifications.

Frequently asked questions