A chiller fails in month fourteen. The operations manager asks whether it is under warranty. Nobody knows. The warranty schedule was attached to an email from a mechanical subcontractor who left the business, the O&M manual on the shared drive is the draft version, and the commissioning engineer who set the sequence has moved to another project.

The repair costs £40,000 and the owner pays it. It was almost certainly covered.

This is the ordinary outcome of a handover done badly, and handovers are done badly more often than not. The construction team is measured on reaching completion. The operations team is measured on everything that happens afterwards. The fortnight where those two responsibilities overlap is where most of the next decade's operating cost gets decided, and it is usually the least planned part of the whole project.

Key takeaways

• Handover is a process with a defined aftercare period, not a single day when keys change hands.

• Practical completion, the defects liability period, and the contractual warranty are three different things with three different end dates.

• The asset register is the most valuable thing you receive, and it is almost never handed over in usable form.

• Warranties fail through lost paperwork far more often than through expired terms.

• Most of what you need has to be agreed before completion. After completion you have no leverage.

This guide is written for the receiving side of the project: property owners, facilities teams, operations managers, and property managers taking responsibility for a completed or refurbished building. It assumes you were not involved in every construction decision but are now responsible for operating what was delivered.

In this guide

• What is a building handover?

• Why handover determines the next ten years

• The handover document set: what to demand

• Practical completion, defects liability, and warranty are not the same thing

• Patent and latent defects

• Building the asset register

• Where warranties go to die

• The handover sequence, week by week

• What to agree before practical completion

• How to tell whether a handover worked

• Frequently asked questions

What is a building handover?

Short answer: A building handover is the transfer of a completed or refurbished building from the construction team to the party that will operate it. It covers the physical asset, the documentation needed to run it, the data needed to maintain it, and the obligations that survive completion. Done well it is a phased process with a defined aftercare period rather than a single date, because a building that has never been through a full heating and cooling season has not yet demonstrated that it works.

Terminology varies by market, and the same concept carries different names depending on which contract you are working under. The terms below are close counterparts rather than exact legal equivalents, and their precise effect depends on the contract form.

The differences matter when a project team and an operations team are working from different vocabularies. Agree the terms at the first handover meeting. Contract terminology and legal obligations also vary significantly by jurisdiction and by contract form, so treat the general positions described below as orientation rather than as advice on your specific project, and refer to the governing contract and local requirements.

Why handover determines the next ten years

Three things are set at handover and are expensive to fix later.

Your maintenance cost baseline. Preventive maintenance schedules are built from the asset register and the manufacturers' service requirements. If the register is incomplete, the schedule is incomplete, and the gap shows up as reactive failures two or three years in.

Your warranty position. A warranty you cannot evidence is a warranty you do not have. Every claim depends on knowing what was installed, when, by whom, and under what terms.

Your building's actual performance. Systems are commissioned in whatever season the project happened to finish in. A building completed in March has never had its cooling proved under load. Without a mechanism to bring the commissioning team back, that discovery happens in July, with tenants in occupation.

The BSRIA Soft Landings framework addresses this directly. Its 2018 edition sets out six phases running from inception and briefing through design, construction, pre-handover, initial aftercare, and extended aftercare with post-occupancy evaluation. BS 8536-1 defines the approach as a graduated handover with a defined period of aftercare by the design and construction team, planned from the outset of the project rather than bolted on at the end.

The practical translation for an operations team: initial aftercare, where the delivery team remains readily available to the building whether on site or on call, typically runs four to eight weeks after handover. Extended aftercare, covering fine-tuning and performance review, can run up to three years. If your project has no aftercare provision at all, that is worth raising before completion, not after.

The handover document set: what to demand

Two items on that list are worth extra attention because they are quietly the most damaging when missing: BMS administrator credentials and the warranty schedule. A building management system you cannot log into as an administrator is a building you do not control. And a warranty you cannot evidence costs real money the first time a major plant item fails.

Practical completion, defects liability, and warranty are not the same thing

This is the most misunderstood area in handover, and the confusion is expensive.

Construction law commentary puts the typical defects liability period at 12 months from practical completion, though it varies: shorter for some residential contracts, and up to 24 or 36 months on complex or infrastructure work. Some contracts restart the clock on any individual item that is repaired, so that item carries a fresh period from the date of the remedial work.

The point most owners get wrong is what happens when that period ends. Legal analysis of AIA-form contracts makes the distinction plainly: the one-year correction period obliges the contractor to come back and fix defective work, but its expiry does not extinguish the contractor's warranty. The contractor may no longer be required to perform the repair itself, while the owner can still pursue a claim for breach of warranty afterwards, subject to the applicable statute of limitations or repose.

Operationally, that means the end of month twelve is not the end of your rights. It is the end of the easy remedy. Treat it as a deadline for identifying and reporting defects, not as the moment your position expires. Confirm the specific position under your own contract and jurisdiction with your legal adviser, since the forms and statutory periods differ significantly by market.

Retention is the other lever. Many contracts release part of the retention at practical completion, commonly half, and hold the balance until the defects period closes and outstanding remedial work is complete. That remaining balance is your practical enforcement mechanism during the defects period. Know how much is held and when it is due to be released.

Patent and latent defects

The distinction determines what you can reasonably expect the contractor to accept.

Patent defects are visible or discoverable at the time of inspection: a door that binds, a damaged finish, a missing seal. These are recorded on the snagging or punch list at completion and remedied within an agreed timeframe. If they were visible at handover and you did not record them, arguing about them later is difficult.

Latent defects are hidden and emerge in use: a failed waterproofing detail, an undersized system, a structural issue. They are not knowable at handover, which is why the completion inspection cannot be the end of your protection and why statutory limitation periods extend far beyond the defects period.

The practical consequence is that your completion inspection should be genuinely thorough, because everything visible is your responsibility to catch. Bring the people who will operate the building, not just the project team. A maintenance engineer walking a plant room finds things a project manager does not.

Building the asset register

If you take one thing seriously from this article, take this one. In our experience the asset register is the most valuable output of a handover, and it is the one most often delivered in unusable form or not at all.

An asset register is a structured record of every maintainable item in the building. It is what the preventive maintenance schedule is generated from, what the capital replacement plan is built on, and what every future work order attaches to.

Two rules make the difference between a register that works and a spreadsheet nobody opens.

Specify the format before completion. If you ask for the asset register at handover, you get whatever the contractor has. If you specify the fields, the naming convention, and the file structure in the contract, you get something you can import. This costs nothing to ask for early and is nearly impossible to obtain later.

Match it to your operating hierarchy from day one. Locations should use the naming convention your team will actually use, not the one the drawings used. That mapping is exactly what property and community setup exists to define, and doing it during handover rather than six months afterwards saves a full re-keying exercise.

Once the register exists, the preventive schedule and the reactive workflow both hang off it. RIOO guide to managing maintenance requests covers what happens downstream.

Where warranties go to die

Warranties rarely fail because they expired. They fail because nobody could produce them.

The common failure modes:

• The schedule was never consolidated, so terms sit in individual subcontractor documents

• Manufacturer warranties run from commissioning, not from completion, and the commissioning dates were never recorded per item

• Registration was required within a set window and nobody registered

• The warranty required documented servicing at specified intervals, and the servicing was done but not evidenced

• The failed component was replaced under warranty, restarting its own period, and that was never logged

The fix is unglamorous. Every warranty becomes a dated record attached to its asset, with the start date, expiry, conditions, and claim contact. Set a review at month nine or ten of the defects period, before the correction window closes, and walk every major system looking for anything that should be raised while the easy remedy is still available.

The handover sequence, week by week

Handover starts well before completion. If your first involvement is on handover day, the important decisions have already been made without you.

Twelve weeks before completion. Operations team joins project meetings. If you want the wider development context that leads to this point, RIOO's overview of multifamily development from site study to lease-up covers the construction sequence. Confirm the documentation schedule, asset register format, training plan, and aftercare provision. Identify who from the operating team attends each system's training.

Eight weeks before. Review draft O&M content and the asset register template. Reject anything not in the agreed format now, while it is still cheap to fix.

Four weeks before. Witness commissioning where practical, particularly for the systems your team will maintain. Confirm which systems have been proved under load and which have not.

Two weeks before. Systems training, with attendance recorded. Take BMS administrator credentials and confirm access works before the trainer leaves. Reconcile the spare parts and key schedules against what is physically on site.

Completion week. Joint inspection with operating staff present. Record every patent defect with photographs and location references. Confirm the statutory certificate set is complete. Confirm insurance transfer and effective date.

Weeks one to eight after. Initial aftercare. Delivery team available for questions and fine-tuning. Log every fault against its asset from day one, since this data becomes your baseline. Track defect closure against the snagging list weekly.

Months three to twelve. Extended aftercare. Seasonal commissioning for any system that has not yet run through a full load cycle. Review energy performance against design intent. Conduct the pre-expiry defect sweep before the correction period closes.

What to agree before practical completion

You have leverage before completion. You have very little afterwards. Six things worth writing into the contract or agreeing in the handover plan:

1. The asset register format, field by field, with the naming convention specified.

2. Documentation acceptance criteria, so incomplete O&M manuals do not satisfy the requirement.

3. Training scope and attendance, naming which roles must be trained on which systems.

4. Aftercare provision, including how long the delivery team remains available and what response is expected.

5. Seasonal commissioning, where completion falls outside the season a system needs to prove itself.

6. A consolidated warranty schedule, delivered as one structured document rather than as subcontractor attachments.

None of these are unreasonable requests. All of them are much harder to obtain once final payment has been made.

How to tell whether a handover worked

Frequently asked questions

1. What is a building handover?
The transfer of a completed or refurbished building from the construction team to the party that will operate it, covering the physical asset, the operating documentation, the maintenance data, and the obligations that survive completion. Done properly it is a phased process with a defined aftercare period rather than a single date.

2. What documents should be provided at handover?
As-built drawings, O&M manuals, the asset register, commissioning records, a consolidated warranty schedule, statutory certificates, test and inspection results, BMS documentation and credentials, training records, key and access schedules, spare parts inventory, and a contact list by system.

3. Who is responsible for a building handover?
Responsibility is shared. The contractor delivers the completed building, the required documentation, commissioning records, and any agreed training. The owner or operations team reviews what is provided, verifies the document set is complete, records defects at inspection, and prepares the building for ongoing operation. The precise split depends on the contract form and jurisdiction.

4. What is the difference between practical completion and substantial completion?
They describe broadly the same milestone in different markets. Practical completion is used in the UK, Australia, and much of the Middle East. Substantial completion is the common equivalent in US contracts. Both mark the point where the building can be used for its intended purpose and risk typically transfers to the owner, though the precise definition sits in the contract.

5. What is a defects liability period?
A defined period after practical completion during which the contractor must return and remedy defects in its work at its own cost. It is commonly 12 months, though it varies by contract and project type, and it is called the rectification period under JCT forms and the defects notification period under FIDIC.

6. How long is a defects liability period?
Typically 12 months from practical completion. Some residential contracts use shorter periods, and complex or infrastructure projects may run to 24 or 36 months. Some contracts restart the period for any individual item that is repaired.

7. Does the contractor's liability end when the defects period expires?
Not necessarily. Under US AIA-form contracts, the expiry of the one-year correction period ends the contractor's obligation to perform the repair itself, but does not extinguish the underlying contractual warranty, and an owner may still bring a claim within the applicable statute of limitations or repose. Positions differ by contract and jurisdiction, so confirm yours with legal advice.

8. What is the difference between a punch list and a snagging list?
They serve the same purpose in different markets. Punch list is the US term, snagging list the UK and Commonwealth term. Both record outstanding or defective items identified at completion that the contractor must remedy, though their contractual weight depends on the form in use.

9. What is the difference between patent and latent defects?
Patent defects are visible or discoverable at inspection and should be recorded on the completion list. Latent defects are hidden and emerge later in use. Because patent defects are your responsibility to identify at handover, the completion inspection should involve the people who will operate the building.

10. What is an O&M manual?
The operations and maintenance manual: the compiled record of how each system works, how it should be operated, what servicing it requires and at what intervals, what parts it uses, and who supplied it. It is the reference document the operating team works from for the life of the asset.

11. What is an asset register and why does it matter?
A structured record of every maintainable item in the building, with identifiers, locations, serial numbers, installation dates, warranty terms, and service requirements. It is what the preventive maintenance programme and the capital replacement plan are generated from. Without it, maintenance is reactive by default.

12. What is soft landings in construction?
An approach to graduated handover in which the design and construction team remains involved for a defined aftercare period after completion, planned from the outset of the project. The BSRIA framework sets out six phases from inception through extended aftercare and post-occupancy evaluation.

13. How long should aftercare last after handover?
Initial aftercare, with the delivery team readily available to the building, typically runs four to eight weeks. Extended aftercare covering fine-tuning, seasonal commissioning, and performance review can run up to three years, depending on what was agreed at the outset.

14. What is seasonal commissioning?
Proving and tuning systems under conditions they have not yet experienced. A building completed in winter has not run its cooling under summer load. Seasonal commissioning brings the team back to verify performance in the missing season rather than discovering the problem with tenants in occupation.

15. Why do warranty claims fail after handover?
Usually through lost or incomplete records rather than expiry. Common causes include an unconsolidated warranty schedule, unrecorded commissioning dates where the warranty runs from commissioning, missed registration deadlines, and servicing that was performed but never evidenced.

16. When should the operations team get involved in a project?
As early as possible, and no later than around twelve weeks before completion. The asset register format, documentation standards, training plan, and aftercare provision all need to be agreed while the contractor still has an incentive to agree to them.

17. What should be agreed before practical completion?
The asset register format, documentation acceptance criteria, training scope and attendance requirements, aftercare duration and availability, seasonal commissioning where relevant, and delivery of a single consolidated warranty schedule.

A building is handed over once. Everything that was not captured in that window has to be reconstructed later, at higher cost and with less cooperation, or absorbed as an operating expense nobody budgeted for.

The construction team's job ends at completion. The operations team's job starts there. The handover is the only point where both are in the room, and it is worth treating as the most important fortnight in the building's life, because for the next ten years it will be.