Construct IQ

Construction Handover Documentation: Building a Package Operations Can Use

By Kush Agarwal, President and CEO, YelloSKYE. Published 2026-10-28.

Executive Summary

• The Question: What should a construction handover package contain so that the people running the building can actually use it, years after the contractor has gone?
• The Answer: Build it from the operator's questions backwards. Capture services, structure and buried work before they are hidden, organise every record by location, system and asset rather than by contract package, deliver it in open formats, and give someone on the owner's side the job of keeping it current.
• The YelloSKYE Angle: Construct IQ records the building with drones, 360° cameras and fixed cameras as it goes up, and the DEX platform hands the whole dated history to the operator with role-based access.

Construction handover documentation is the set of records a contractor passes to the owner at completion so the building can be operated, maintained, repaired and altered safely. A good package lets a maintenance planner find a valve, a cable route or a roof outlet from a desk; a poor one is a stack of manuals and drawings sorted by which subcontractor supplied them.

The difference is decided long before completion. Many of the records an operator values most can only be made while the work is still exposed, and the structure of the package has to be agreed early enough for every trade to follow it. This guide sets out what to capture during construction, how to organise and format the package, and how to stop it going stale once the building is occupied. It draws on how Construct IQ, our construction monitoring solution, records a building through the build. For the full list of project records phase by phase, see our construction documentation checklist; this guide concentrates on the subset that operations inherit.

Start from the questions operations will ask

During construction, records answer delivery questions: is the work done, was it built to drawing, can we pay for it? After handover the questions change completely. A facilities team is trying to fix a leak, plan a shutdown, price a refurbishment or avoid hitting a cable with an excavator.

The quickest way to design a useful package is to list those future questions first and work out which record will answer each one.

Run this exercise with the people who will operate the building. A hospital estates manager and a warehouse tenant will each add questions the project team never thought of.

Why handover packages fail in operation

Most handover packages are complete on paper and still fail the first time someone needs them. The causes are predictable.

• Organised by supplier, not by place. Folders named after trade packages mean an engineer looking at one riser must search the mechanical, electrical, fire and controls folders separately.
• Visual records stay with the builder. Site photos and walkthroughs live in the contractor's account or on personal phones, so the owner receives the manuals but not the evidence of what is behind them.
• Static files with no owner. The package is a snapshot on handover day. Six months later a tenant fit-out moves walls and services, nobody updates anything, and trust in the record quietly collapses.
• Formats nobody can open. Native files tied to a specific software version, or links to a portal the contractor stops paying for, lock the owner out of its own information.
• Captured too late. A walkthrough recorded at completion shows finishes. It cannot show the ductwork above a ceiling that was closed four months earlier.

Each of these is cheaper to prevent at mobilisation than to repair at completion.

What to capture while it is still visible

The defining feature of handover documentation is that much of it has a deadline. Once the next layer goes on, the chance to record what is underneath has gone, and the only alternative is opening up finished work.

Below ground

Record drainage, ducts, cable routes, chambers, foundations and any abandoned services in open excavations, with enough survey control that positions can be located later. A drone map of each open trench section, flown before backfill, gives a measurable plan view at low cost. Our guide to utility as-built mapping covers the method in detail.

Slabs, walls and embedded items

Capture reinforcement, cast-in conduits, sleeves, fixings and post-tensioning before each pour, and services inside walls before boarding. The detailed sequence for these hold points is in our guides to pre-pour inspection and pre-drywall inspection. For handover, the point is simply that every one of those captures should be filed against its room and element so an operator can find it later.

Ceiling voids, risers and plant rooms

These are the spaces operators visit most and see least. Walk every ceiling void with a 360° camera before the grid is closed, record every riser floor by floor, and capture plant rooms twice: once with services exposed and once fully commissioned and labelled. Where equipment will one day be replaced, a laser scan of the room and its access route turns a future question about clearances into a measurement.

Roof and envelope

Record membranes, upstands, flashings, penetrations, outlets and facade brackets as each area is finished. When a leak appears in year three, comparing the current condition with the as-installed record is often the fastest way to tell a workmanship defect from damage or wear.

Commissioning state

Photograph labels, settings and equipment nameplates once systems are commissioned, and link each image to the asset register entry. This is the record a maintenance technician uses most often, and it costs very little if it is done while the commissioning team is still on site.

On YelloSKYE projects, routine drone and 360° captures through the build already cover much of this. In our warehouse operator handover use case, drones and 360° cameras recorded every zone during construction, including MEP installations before they were enclosed behind panels, so the handover record existed long before completion.

How to structure the package

A handover package works when any record can be reached from where the problem is. That means one location hierarchy, used by every trade, every capture and every document.

One location hierarchy

Agree a breakdown at mobilisation, for example site, building, level, zone, room, and publish the codes. Every drawing, test sheet, photo and walkthrough is tagged with the lowest level it applies to. A 360° image of a corridor ceiling is filed against that corridor; a riser scan is filed against the riser on each level it covers.

Systems and assets on top

Within each location, records are also linked to the system (for example chilled water or fire alarm) and, where relevant, to an individual asset tag. The asset register becomes the index: open an asset and you see its manual, warranty, test results, location and every image in which it appears.

A naming convention people can read

The exact scheme matters less than the discipline of using it everywhere. If your organisation already uses a structured asset data format for handover, such as COBie, align the codes with it rather than inventing a second set.

What goes into each section

Formats that will still open in twenty years

Buildings outlive software. A package that relies on one vendor's viewer or a contractor's portal is a package with an expiry date. Ask for open or widely supported formats as the master copy, with native files supplied alongside where they are useful.

On DEX, captures can be exported in standard formats: drawings to DWG and DXF, point clouds as RCP, LAS and LAZ, drone maps as GeoTIFF, and 3D models as OBJ and FBX. That means the owner can keep using the platform for day-to-day access while also holding an independent copy of its own data.

Handing over the visual record

The visual record is usually the part of the package that operators value most and receive least. There are two ways to hand it over, and many owners use both:

• As files. The full set of maps, walkthroughs and scans, exported and indexed, so the owner has a permanent copy.
• As access. Role-based access to the platform where the record already sits, so the operator can scroll through the build by date and location from a browser.

That second route is what the warehouse developer chose: the operator was invited into DEX with its own access rights and could browse every capture of the build, sorted by phase and section. Physical pre-delivery inspection time dropped by 70%, and no documentation disputes followed handover. Our interior fit-out use case shows the same kind of navigable 360° record being used to close snags before handover.

For the walkthrough itself as a handover tool, including how to plan tours for owners and remote stakeholders, see our guide to virtual construction walkthroughs.

Keeping the record alive after handover

A handover package starts to decay the day the first tenant moves a partition. Without a plan for updates, operators learn that the record is sometimes wrong and stop relying on it.

Name an owner

Give one role on the operations side responsibility for the record: accepting it at handover, controlling who can see and change it, and checking that later works update it.

Make updates part of every later project

Write into every future works contract that the contractor must supply revised drawings and fresh captures for the areas it changes, filed under the same location codes. Treat it as a condition of final payment, as you would for manuals and certificates.

Close work orders with evidence

When maintenance work opens up a ceiling or replaces a unit, attach before and after images to the work order and file them against the location. Over time this keeps the most-visited spaces current without a separate capture programme. Our guide to facility management reality capture covers how operations teams use these records day to day.

Refresh, do not overwrite

Repeat site-wide captures on a set interval, for example yearly or after major works, and keep every earlier capture as history. The construction-stage images of hidden services remain the most valuable layer, because they can never be taken again.

Measure existing buildings properly before major change

Where the record has drifted too far, or an older building never had one, a laser scan converted to an as-built model resets the baseline. Our scan to BIM for renovation use case shows an existing building turned into a design-ready model before redesign.

Handover documentation checklist

At mobilisation

1. List the questions operations will ask and the record that answers each one.
2. Issue the location hierarchy, system codes and naming convention to every trade.
3. Agree formats, delivery method and who on the operations side accepts the package.

During construction 4. Capture buried services before backfill, embedded items before each pour and services before each wall or ceiling is closed. 5. Record roof and envelope details as each area is finished. 6. File every capture against its location, system and asset as it is taken, not at the end.

At commissioning and completion 7. Photograph labels, settings and nameplates and link them to the asset register. 8. Compile record drawings, model, manuals, test results, warranties and certificates in the agreed structure. 9. Hand over the visual record both as an indexed export and as role-based access.

After occupation 10. Name the owner of the record and write update duties into every future works contract. 11. Attach evidence to work orders and refresh site-wide captures on a set interval, keeping all earlier captures as history.

Explore Construct IQ