Facility As-Built Documentation: Digital Handover Standards

By Corin Hale on October 1, 2026

facility-as-built-documentation-digital-handover

A building is handed over, the ribbon is cut, and the facilities team inherits a pile of binders, a USB drive of unnamed files and drawings that do not match what is on the ceiling. Within months, technicians are tracing pipes by hand and chasing manufacturers for manuals. The cost of that gap lands on maintenance for the whole life of the asset. Setting digital handover requirements early, and loading the results into a maintenance system built for asset records, closes that gap before it opens.

Construction to Operations

Facility As-Built Documentation: Digital Handover Standards

What drawings, O&M manuals, warranties and asset data every project must deliver, and how to accept them.

As-built drawings and models
Structured asset data (COBie)
O&M manuals and parts lists
Warranties and certificates
Commissioning and test records

Where Handover Information Gets Lost

Information is rarely missing because nobody created it. It is lost because nobody defined who delivers it, in what format, and by when.

Design
Equipment is specified, but no data requirements are written into the brief.
Construction
Substitutions and field changes are made without updating drawings.
Commissioning
Test results sit with the contractor, not the owner.
Handover
Files arrive late, unsorted and in mixed formats.
Operations
FM re-surveys the building to build an asset register from scratch.

What the Gap Costs Operations

  • Technicians spend site visits locating valves, panels and isolation points.
  • Warranty claims fail because install dates and serial numbers were never recorded.
  • PM schedules cannot be generated until someone creates the asset list.
  • Renovations proceed on drawings that no longer reflect the building.
  • Insurers and auditors ask for records that cannot be produced quickly.

The Standards Behind Digital Handover

You do not need to invent a handover specification. Several established standards cover most of what an owner should ask for.

Standard or methodWhat it coversHow an FM team uses it
COBieStructured spreadsheet or data format for facility, space, type and component informationSource for the asset register and PM planning
ISO 19650 seriesInformation management across the project and asset lifecycleFrames owner requirements and delivery responsibilities
IFC (ISO 16739)Open model exchange formatKeeps model data readable without proprietary software
Owner information requirementsOwner-defined questions the data must answerWritten into the contract before design starts
Local codes and permitsFire, life safety and inspection recordsEvidence for authorities and insurers

Use these as a base, then tailor them to your portfolio. A short, enforceable requirement beats a long one nobody checks.

What a Complete Handover Package Contains

Group deliverables so reviewers can confirm each one against a checklist rather than reading everything.

Drawings and models
  • Architectural, structural, mechanical, electrical and plumbing as-builts
  • Riser and single-line diagrams
  • Model in an open format where one was produced
Asset data
  • Manufacturer, model and serial number
  • Install date and location
  • System membership and parent relationships
O&M documentation
  • Operation and maintenance manuals by equipment
  • Recommended PM tasks and intervals
  • Spare parts and consumables lists
Warranties
  • Warranty start and end dates
  • Provider contact and claim procedure
  • Exclusions and conditions
Commissioning records
  • Test and balance reports
  • Functional test results
  • Open issues and agreed close-out dates
Compliance
  • Fire and life safety certificates
  • Inspection and permit sign-offs
  • Training attendance records

How COBie Data Maps to Your Asset Register

COBie organizes handover data into related sheets. Knowing how each one lands in your CMMS makes the import predictable.

COBie sheetTypical contentCMMS destination
Facility, Floor, SpaceBuilding, level and room hierarchyLocation hierarchy
TypeEquipment model, manufacturer, warranty termsAsset class and model template
ComponentIndividual installed items with serial and locationAsset records
SystemGroupings such as a chilled water loopParent and child asset links
Job and ResourceMaintenance tasks and skillsPM templates and labor assignments
SpareRecommended partsInventory and parts-to-asset links
DocumentManuals, drawings, certificatesAttachments on asset or type

Insist on a sample COBie file early in construction. Errors found at the first sample are cheap to fix. Errors found at handover are not.

Acceptance Gate: Do Not Sign Until These Pass

Treat data like any other deliverable. Link final payment or practical completion to documented acceptance.

PassAsset count in data matches a sample walk-down of installed equipment.
PassSerial numbers and locations match nameplates on critical equipment.
PassEvery manual is present, readable and attached to the correct type.
PassWarranty dates and contacts are populated for each warranted item.
PassAs-built drawings reflect field changes and carry a revision date.
PassOpen commissioning issues are listed with owners and dates.
PassOperators have been trained and attendance is recorded.
Load Handover Data Once, Maintain It for Years
Oxmaint turns delivered asset data, manuals and warranties into live records with PM schedules and work order history attached.

Paper Handover vs Digital Handover

Binders and drives
  • Searched manually, often by one long-serving person
  • Out of date after the first modification
  • Warranty details buried in contract appendices
  • PM plans written from scratch after opening
  • No link between document and asset
Structured digital handover
  • Searchable by asset, location or system
  • Updated through work orders and change records
  • Warranty dates trigger reminders
  • PM templates generated from asset type
  • Every document attached to the item it describes

Writing the Requirement into the Contract

Handover quality is decided long before the building is finished. The contract is where you set expectations.

Clauses Worth Including

  • A named data template and file format for all asset information.
  • A staged delivery schedule with data drops at design freeze, mid-construction and pre-handover.
  • Naming and tagging rules that match your existing asset register.
  • Responsibility for updating drawings after field changes.
  • A retention or completion condition linked to accepted data.
  • A defects period during which data corrections remain the contractor's duty.

Staged Delivery Timeline

Stage 1
Requirements issued
Owner information requirements and data template agreed with the design team.
Stage 2
Sample submission
One system delivered in full to prove the format loads cleanly.
Stage 3
Progress audits
Data checked against installed equipment during construction.
Stage 4
Pre-handover review
Acceptance gate run before practical completion.
Stage 5
Post-occupancy correction
Gaps found during the first season of operation are fixed.

Warranty Records That Actually Get Used

A warranty is only valuable if someone notices it is about to expire. Capture the details as data, not as a clause inside a PDF.

  • Start date, end date and what triggers the start, such as substantial completion.
  • Provider, contact and the claim method.
  • Maintenance conditions that keep the warranty valid.
  • Reminder dates ahead of expiry so defects are logged in time.

Linking warranty status to the asset record means a technician sees it the moment a work order is opened.

Measuring Handover Quality

Data accuracy on audit
Share of sampled assets whose record matches the field.
Time to first PM
Days from occupancy until PM schedules are live.
Manual coverage
Share of equipment types with a usable O&M manual attached.
Warranty recovery
Defects claimed within warranty versus total early defects.
Re-survey effort
Hours FM spends rebuilding data after handover.

How Oxmaint Fits After Handover

Oxmaint gives the delivered data an operating home, so the handover investment keeps paying off.

  • Asset management with location and system hierarchies that mirror delivered data.
  • Preventive maintenance schedules built from asset types and manufacturer recommendations.
  • Work orders that carry history, documents and warranty status.
  • Mobile inspections to verify delivered data during the first months.
  • Inventory links between assets and recommended spares.
  • Reports that show how complete and current the asset record is.

To see how a delivered COBie file loads into a working register, request a short demo.

Frequently Asked Questions

What is the difference between as-built drawings and record drawings?
Terms vary by region, but both describe drawings updated to show what was actually installed. Specify the term and the revision rule in your contract.
Do we need a BIM model to use COBie?
No. COBie data can be produced and checked without a full model, though models make extraction easier.
When should handover requirements be written?
Before design begins. Late requests cost more and rarely cover every system. Set up your asset structure first so the requirements match it.
How do we verify contractor-supplied asset data?
Sample installed equipment against the data, prioritizing critical systems. Failed samples trigger a full resubmission.
Can older buildings benefit from the same standard?
Yes. Use the same fields to survey existing assets. Talk to the team about a retrofit data plan.
Receive a Building You Can Actually Maintain
Bring handover drawings, asset data, manuals and warranties into one maintenance system from the first day of occupancy.

Share This Story, Choose Your Platform!