Site Handover Checklist
A site handover checklist template for taking a building from the people who built it to the people who will run it. Forty-four items across documents, keys and spares, systems and training, because handover is the last moment anyone has any leverage. Everything on the list is harder to obtain the week after the contractor demobilizes, and some of it is never obtained at all.
- Forty-four items across paperwork, physical handover and training
- The asset register with serial numbers, chased while you still can
- Seasonal commissioning arranged for what cannot be proved yet
- Warranty conditions recorded, not just warranty dates
Site Handover Checklist
While you still have leverage
| # | DOCUMENTATION | RECEIVED | FORMAT | REFERENCE |
|---|---|---|---|---|
| 1 | Asset register with make, model, serial and location | |||
| 2 | Operation and maintenance manuals | |||
| 3 | Commissioning records and test certificates |
The document you will get. Download for the full, editable file.
Who this building handover checklist is for
One building changing hands, and three people whose next twelve months depend on what was collected this week.
The incoming facilities lead
All of it, but section 2 first. What you accept here determines whether the building can be operated or merely occupied, and you are the person who finds out which.
Whoever builds the first PM schedule
The asset register and the O&M manuals. With serial numbers you have a maintenance plan in an afternoon; without them somebody walks the building with a clipboard for a fortnight and still misses the roof plant.
Whoever runs the handover meeting
The 44 items, the defect list and the acceptance decision. The job is to turn a date on a schedule into a list of things that are either received or named as outstanding.
The client or project sponsor
Acceptance and retention. Accepting a building with critical defects open transfers the problem and the cost to whoever runs it, which is a decision worth making deliberately.
Where handover decides the next five years
The structure suits any building changing hands. What changes is how much plant there is and how expensive it is to discover something was never handed over. If you run one of these, the sector page goes further than the template does.
- Commercial real estate
New lettings and refurbishments, where the asset register is what the service charge budget will eventually be built from.
Portfolio maintenance software - Corporate facilities
Fit-outs, where the fabric was somebody else's handover and only the fit-out is yours to accept.
Corporate facilities software - Healthcare
Clinical buildings, where witnessed commissioning and validated systems make the evidence pack part of the asset.
Healthcare maintenance software - Education
Campus projects handed over in the summer, which is exactly when heating cannot be proved and seasonal commissioning matters most.
Campus maintenance software - Retail and malls
Unit handovers on a trading deadline, where the pressure to accept and open is at its highest.
Retail maintenance software - FM service providers
Mobilizing on a building somebody else built, inheriting whatever the handover did or did not collect.
FM service provider software
What a project handover checklist should contain
A site handover checklist is the record of a completed building being transferred from the contractor who built it to the team who will operate it. It tracks the documents, keys, spares, training and warranties received, lists outstanding defects by severity, and ends in a decision to accept, accept with conditions or refuse.
A. The sections that carry the weight
| Field | What goes in it | Why it earns its place |
|---|---|---|
| Handover details | The project, the parties, practical completion and the defects liability period | The defects liability period needs its end date written down here, because it is the clock that decides who pays for things that fail in the first year. |
| Documentation | Seventeen documents from as-builts to the spares schedule | The section that determines whether the building can be maintained. A missing health and safety file is a legal problem; a missing asset register is an operational one. |
| Asset register | Make, model, serial number and location for every asset | Singled out because it is the most valuable item on the list and the one most often substituted with a drawing set. Serial numbers are what connect a warranty claim to a specific unit. |
| Physical handover | Twelve items covering keys, access, spares, consumables and site condition | Quantities matter here. Keys tagged and scheduled is a different handover from a box of keys, and the difference surfaces the first time somebody is locked out at night. |
| Systems, commissioning and training | Fifteen items from witnessed testing to recorded operator training | The line worth insisting on is that it was filmed or written down. The staff trained at handover are not the staff who will be running the building in three years. |
| Seasonal commissioning | Arranged for anything that cannot be proved at this time of year | The trap in every summer handover. Heating cannot be demonstrated in June, and the arrangement to prove it later has to be made while somebody is still contractually obliged to turn up. |
| Defects and outstanding items | Location, description, severity, owner and target date | Severity is Critical, Major or Minor, spelled exactly that way. Critical means the building cannot be occupied or operated safely, which is a different conversation from a snag. |
| Warranty register | Item, supplier, start, expiry, and the conditions attached | The conditions column is the one that earns its place. Most long warranties are voided by a missed annual inspection, and nobody discovers that until they try to claim twelve years later. |
| Handover readiness | Items due against items complete, and defects by severity | One number that says how much of the handover actually happened. Forty-four items if you worked every line, and the percentage is what the acceptance conversation should start from. |
| Acceptance | Accept, accept with conditions, or do not accept | The decision the whole document exists to inform. Accepting with critical defects open transfers the problem and the cost to whoever operates the building. |
| Post-handover arrangements | Who manages defects, how they are reported, and when the end of defects inspection is | Booked at handover rather than remembered eleven months later, which is when the inspection is worth the most and the least likely to happen. |
| Signatures | Contractor, client and the facilities team, each signing separately | Three signatures because the facilities team accepting the building is a different act from the client accepting the contract, and conflating them is how operational gaps get signed away. |
Two items on this list are worth more than the rest combined, and both are routinely lost because the people who need them are not in the room when the building changes hands. The first is the asset register with serial numbers. It looks like an administrative deliverable and it is actually the foundation of everything that happens afterwards: the planned maintenance schedule, the warranty claims, the spares holding, the lifecycle plan and eventually the capital budget. Handed over properly it is a spreadsheet, and the first PM schedule can be written from it in an afternoon. Handed over as a set of drawings and an O&M manual, which is what happens when nobody specifically asks, it has to be reconstructed by walking the building with a clipboard, which takes a fortnight, misses the roof plant and produces a register nobody fully trusts for years. The second is seasonal commissioning. A building handed over in June has not had its heating proved, and one handed over in December has not had its cooling proved. There is no way around that, and the only thing that matters is whether somebody arranged, in writing and while the contractor still had an obligation, to come back and prove it. Teams that skip this find out in the first cold week, by which time the contractor has demobilized, the retention has been released and the conversation is about goodwill rather than obligation.
B. What it looks like filled in
One fit-out handed over. Forty-one of forty-four items complete, and the two major defects are why this was accepted with conditions rather than accepted.
| Line | Value |
|---|---|
| Project | Northgate House fit-out |
| Practical completion, handover | 28/05/2027, then 01/06/2027 |
| Items complete | 41 of 44, so 93% readiness |
| Defects | 0 critical, 2 major, 9 minor |
| Outstanding at acceptance | 3 |
| Decision | Accept with conditions |
Ninety-three percent sounds like a successful handover, and the decision was still not a clean acceptance. That is the readiness figure doing its job. Forty-one items of forty-four arrived, which by most standards is a well-run project, but three did not, and two major defects were open on the day. Accepting outright would have meant those three items becoming somebody's problem to chase with no leverage and no obvious deadline. Accepting with conditions names them, attaches dates, and keeps them inside a conversation that still has a retention attached to it. Notice that there were no critical defects. Had there been, the honest answer would have been not to accept at all, because a critical defect means the building cannot be operated safely and accepting it transfers both the risk and the cost to the operating team. Where the date genuinely cannot move, and sometimes it cannot, the decision is still accept with conditions and never a silent acceptance. The difference between the two is whether anybody can point at a document in four months and say what was promised.
Word for the version you work through in the handover meeting, Excel for the one that counts readiness and holds a Handover Register across several projects, and PDF for the signed copy. Free, and yours to rebrand.
How do you run a site handover?
Start it weeks before the handover date, not on it. The list is only useful while somebody is still contractually obliged to respond to it. Six steps.
Issue the list before practical completion
Send it to the contractor early so the documents are being assembled rather than requested. A handover list first seen at the handover meeting is a list of things that will arrive late or not at all.
Chase the asset register with serial numbers
Ask for it specifically and by name, because the default deliverable is a drawing set and an O&M manual. Without serial numbers the first PM schedule gets built by walking the building.
Arrange seasonal commissioning in writing
Anything that cannot be proved at this time of year, heating in summer or cooling in winter, needs a booked return visit agreed while the obligation still exists.
Record warranty conditions, not just dates
Most long warranties are voided by a missed annual inspection. Capture what each one requires alongside when it expires, and who to contact to claim on it.
List the defects by severity and own them
Critical, Major or Minor, spelled exactly that way, each with an owner and a target date. Critical means the building cannot be operated safely, which is a different conversation entirely.
Accept, or accept with conditions, and name them
Work out readiness as items complete against items due, then decide. If the date cannot move and things are outstanding, accept with conditions and write them down. Never accept silently.
Practical completion versus operational handover
Two milestones that often share a date and mean entirely different things. One closes a contract. The other decides whether the building can actually be run.
| Aspect | Practical completion | Operational handover |
|---|---|---|
| What it certifies | The works are substantially complete | The building can be operated |
| Who it matters to | The contractor and the client | The team who will run it |
| What it triggers | Retention, insurance and the defects period | Maintenance, statutory duties and warranties |
| What proves it | A certificate | Forty-four items received and signed for |
| What can be missing | Very little that is contractual | Almost everything operational |
| Who notices a gap | Nobody, for months | Whoever is on call the first night |
A building can reach practical completion with the contractual position perfectly in order and still be impossible to operate. The certificate says the works are substantially complete; it does not say anybody has the asset register, the keys are scheduled, the BMS login exists or that a single member of staff has been trained. Those are operational questions, and they are only asked if somebody from the team who will run the building is in the room with a list. That is the entire case for treating handover as its own event with its own document, and for having the facilities team sign separately from the client. Separately, this checklist does not cover bringing plant back on after a shutdown. That is a pre-startup safety review and it belongs in a plant shutdown checklist, which is written for a system coming down and going back up in a building you already operate. The two get confused because both involve proving that things work, but handover is about what you are receiving and from whom, and a startup review is about whether it is safe to energize something you already own.
When the template starts to feel limiting
The file is built for one handover at a time. Four things start to hurt as soon as that is not the shape of the problem.
The defects liability period counts down unwatched
The end date is recorded and nothing acts on it. The end of defects inspection is remembered late, which is the point at which it is worth the least.
The asset register arrives and then sits still
A handed-over register is a file. Turning it into a maintenance schedule is a separate exercise somebody has to start, and between the two the building runs on nothing.
Warranty conditions are invisible once filed
Each warranty carries conditions and the file records them. Nothing reminds anybody that the annual inspection keeping a twelve year warranty alive is due.
Outstanding items do not accumulate across projects
Items outstanding at acceptance, tracked across handovers, is the number that improves the next contract. On paper it is several spreadsheets nobody totals.
What running this in Facilio looks like
The handover does not change. What changes is that the register becomes a maintenance plan and the dates that matter are watched.
Asset Intelligence
The register becomes the asset list
Make, model, serial and location come in as assets rather than as a spreadsheet, so the handover deliverable and the thing you maintain are the same record.
Work Order Intelligence
Defects become tracked work
Outstanding items and defects carry owners and dates as jobs, so the conditions attached to an acceptance are visible rather than sitting in a file.
Ops Performance Intelligence
The dates that matter are watched
The defects liability end date and each warranty condition carry their own reminder, so the end of defects inspection happens while it is still worth something.
Audit Report Intelligence
Handovers compare with each other
Items outstanding at acceptance across several projects becomes a number, which is the evidence that changes what the next contract asks for.
Hallucination-free by design. Atom AI answers from the records in your tenant rather than generating plausible text, so an empty field reads as empty rather than filled in for you.
Frequently asked questions
What is a site handover checklist?
It is the record of a completed building being transferred from the contractor who built it to the team who will operate it. This one covers 44 items across documentation, physical handover, and systems and training, plus defects, warranties and an acceptance decision.
It exists because handover is the last moment anyone has leverage. Everything on the list is harder to obtain once the contractor has demobilized.
What should a building handover checklist include?
Documents: as-builts, O&M manuals, the health and safety file, commissioning records, statutory approvals, the fire strategy, electrical and gas certificates, lift and water hygiene records, the asbestos position, warranties, supplier contacts, BMS backups and the spares schedule.
Then the physical handover of keys, access, spares and consumables, and the systems side: witnessed testing, BMS handover, cause and effect demonstration, and operator training recorded for the staff who will arrive later.
Why does the asset register matter so much?
Because it is the foundation of the planned maintenance schedule, the warranty claims, the spares holding and eventually the capital plan. With make, model, serial and location you can write the first PM schedule in an afternoon.
Without it, the register has to be reconstructed by walking the building, which takes weeks, misses plant in places nobody thinks to look, and produces something nobody fully trusts for years.
What is seasonal commissioning?
Proving the systems that cannot be demonstrated at the time of year the building is handed over. A building handed over in June has not had its heating proved; one handed over in December has not had its cooling proved.
The only thing that matters is whether a return visit was arranged in writing while the contractor still had an obligation. Discovering the gap in the first cold week means relying on goodwill.
How should defects be classified?
Critical, Major or Minor, spelled exactly that way so the counts underneath mean something. Critical means the building cannot be occupied or operated safely until it is fixed.
That distinction drives the acceptance decision, because a critical defect is a different conversation from a snag and should not be buried in the same list without a severity against it.
Should you accept a building with defects outstanding?
Often you have to, and the answer is to accept with conditions and name them, with owners and dates attached. What you should never do is accept silently, because that transfers the problem and the cost with nothing written down.
With critical defects open the honest answer is usually not to accept at all, since the building cannot be operated safely and somebody is about to become responsible for it.
Why record warranty conditions rather than just dates?
Because most long warranties are conditional, commonly on an annual inspection being carried out and recorded. Miss the inspection and the warranty is void regardless of what the expiry date says.
Nobody discovers this until they try to claim, which with a roof or a structural warranty can be a decade later and expensive.
Does this cover restarting plant after a shutdown?
No. That is a pre-startup safety review and it belongs in a plant shutdown checklist, which is written for a system in a building you already operate coming down and going back up.
Handover is about what you are receiving and from whom. The two get confused because both involve proving things work, but the leverage, the parties and the documents are different.
In one paragraph
A site handover checklist works because it is used before the handover rather than at it. Handover is the last moment anyone has leverage, so issue the list early, chase the asset register with serial numbers by name, and arrange seasonal commissioning in writing while the contractor still has an obligation to return. Record what each warranty requires rather than only when it expires, and if things are outstanding on the day, accept with conditions and name them rather than accepting silently.
The leverage ends the day they demobilize
Get the register with serial numbers, book the seasonal commissioning, write down the warranty conditions and name your conditions of acceptance. Once nothing is watching the defects liability clock, or the register is still a spreadsheet rather than a maintenance plan, the handover has done its part.
