What should an office handover checklist actually contain?

Handover is treated, too often, as a single event — the day keys change hands and everyone moves in. In practice it's a checklist, and an incomplete one is what turns small post-occupancy issues into problems nobody can resolve quickly, because the documentation or the accountable contact needed to fix them was never actually handed over in the first place.

Documentation

As-built drawings — reflecting what was actually constructed, not the original design intent where the two diverged during construction — are the single most important document set, since every future change, repair or expansion will be planned against them. Alongside these: operations and maintenance manuals for every installed system, warranty documents with clear start dates and durations, and test certificates for fire safety systems, electrical installations and any other statutory testing carried out during the project.

The physical walkthrough and punch list

A joint walkthrough with the contractor, room by room, produces a punch list — the formal record of every open item still to be resolved, each with a named owner and a committed date. This is different from a casual "a few things still need finishing" conversation. A proper punch list is written down, tracked to closure, and referenced when the final payment is reconciled, so nothing gets quietly forgotten once the contractor's team has moved to the next project.

Compliance sign-offs

Depending on the city and the building, this typically includes a fire department no-objection certificate, electrical safety certification, and any building-specific occupancy sign-off required before the space can legally be occupied. These should be handed over as completed documents, not as "in process," before final possession.

Furniture and asset inventory

A simple, dated inventory of what furniture and fixed assets were supplied, matched against the original specification, protects both sides if a dispute arises later about what was actually delivered versus what was quoted. This is a small amount of paperwork at handover and a genuinely useful record if anything needs replacing or matching in the future.

Vendor and AMC records

Every system with an ongoing annual maintenance contract — HVAC, fire safety, access control, lifts if applicable — should hand over with a clear record of which vendor holds that contract, what it covers, and when it renews. This is also where a decision about ongoing operations belongs: some clients bring this in-house, and some prefer the same team that built the space to keep running it, so nothing gets lost in a handoff to a facilities team encountering the building for the first time.

Training and orientation for your team

A handover that includes documents but skips training leaves a facilities team holding manuals for systems nobody on site knows how to operate. Building management system controls, HVAC zoning and scheduling, access control administration and any smart-lighting or occupancy-sensor systems should come with a proper walkthrough for whoever will actually run them day to day, not just a manual left in a folder. This is a small addition to a handover schedule and one of the more commonly skipped ones, usually because it's not written into the original contract as an explicit deliverable.

A realistic handover timeline

Handover works better as a scheduled process than a single end-of-project event. Documentation review, the punch list walkthrough and compliance sign-offs are usually easier to complete properly if they start one to two weeks before the planned move-in date, rather than being compressed into the final two or three days once the pressure to occupy the space is at its highest. Building this buffer into the project schedule from the start, rather than treating handover as whatever's left once construction finishes, is what makes the difference between a handover that's genuinely complete and one that's rushed through to hit a move-in date.

Final account reconciliation

The last payment should be reconciled against the original scope, any approved change orders along the way, and the punch list — not released simply because the move-in date has arrived. Holding a reasonable, pre-agreed retention against outstanding punch list items is standard practice and gives both sides a real incentive to close them promptly.

This final reconciliation is exactly where the budget discipline set up before the project started either pays off or falls apart — a scope and change log that were tracked properly throughout make this a formality; a project without one turns it into a negotiation.

Who should own handover on the client side

Handover works best with a single named owner on the client side, rather than being split informally across facilities, IT and finance with nobody responsible for confirming the whole list is actually complete. That person doesn't need deep technical expertise in every system — their job is to make sure each item on the checklist below has genuinely been received and verified, not simply promised, before the final payment is released and the contractor's team moves on to their next project.

A simple handover checklist

• As-built drawings, matched to what was actually constructed
• Operations and maintenance manuals for every system
• Warranty documents with start dates and durations recorded
• Statutory test certificates and compliance sign-offs
• A signed, dated punch list with owners and closure dates
• Furniture and fixed asset inventory
• Vendor and AMC contact list and coverage summary
• Final account reconciled against scope, change orders and punch list

The gaps that surface months later, not on day one

Some handover gaps are obvious immediately — a missing warranty document is easy to notice when you go looking for it. Others surface only when something actually breaks, which is precisely the wrong time to discover they were never handed over. A common example: an HVAC or fire system installed by a specialist subcontractor, where the main contractor hands over a generic manual but not the subcontractor's own direct contact details or the specific AMC terms that subcontractor offered. When that system needs servicing eight months later, the facilities team is left trying to trace a vendor relationship the main contractor never formally passed on. Asking explicitly, at handover, for direct vendor contacts and AMC terms for every specialist system — not just a general manual — closes this gap before it becomes a problem.

Common questions

What happens if the contractor doesn't provide as-built drawings?

Ask for them as an explicit deliverable in the original contract, not as an afterthought at handover — by the time handover arrives, there's little practical leverage left to insist on documentation that wasn't scoped from the start.

How long should a punch list take to close?

Most genuine punch list items are minor and should close within two to four weeks of handover. Anything open significantly longer than that is worth escalating rather than letting it drift.

What's the difference between a warranty period and a defects liability period?

The terms are often used loosely, but a defects liability period is typically a defined window, commonly six to twelve months after handover, during which the contractor is contractually obligated to fix defects at no cost. Manufacturer warranties on specific products or systems run on their own separate timelines, which is exactly why keeping warranty documents with clear start dates matters — without them, it's difficult to know which period actually applies when something needs fixing.

Should snagging happen before or separately from handover?

A proper snagging inspection typically happens just before formal handover, and feeds directly into the punch list — we've covered how to run one properly in a separate article.

If you're approaching handover on a current project and want a second opinion on whether the documentation is genuinely complete, get in touch and we'll talk through it.