When should handover planning start?

At project initiation in principle, and in detail by the 50% point. Documentation discipline, operator engagement, and training schedules all need to mature with the project. Leaving handover until the last quarter guarantees a poor result.

What is the difference between practical completion and handover?

Practical completion is a contractual milestone certifying the work is substantially done. Handover is the operational process of transferring care, custody and control. They often coincide on the calendar but are not the same thing — one is legal, the other is human.

How long should the handover phase be?

Rule of thumb: 5–10% of the project duration. A two-year construction project deserves 6–10 weeks of planned handover; a complex hospital or refinery may need 12–16. IT migrations typically need 4–6 weeks of shadow-then-lead transition.

Who owns the snag list?

The contractor owns closing snags; the operator owns deciding which snags block acceptance. A jointly maintained snag register with owners, target dates, and weekly review is non-negotiable.

Should the operator have veto power at handover?

Yes, on safety- and operability-critical items; no on cosmetic items inside the defect-liability period. Distinguish 'cannot operate without this' from 'will be fixed in the next quarter' and document the distinction up front.

How do we handle handover of partial works?

Sectional completion, with the same rigour. Each section gets its own readiness index, documentation pack, training and acceptance gate. Sectional handover is harder than total handover, not easier.

What's the most common handover failure?

Documentation written in a rush in the final month. By that point the people who knew the answers have moved to other projects. Discipline is to write the manuals as the systems are built, not after.

How does handover apply to agile / iterative IT delivery?

Every release is a small handover. The discipline scales down: runbooks updated per release, training delivered incrementally, the operations team embedded in the agile team. Done well, the 'big' handover at programme end is a non-event because it has happened weekly all along.

Which calculators on PMMilestone.org apply to Handover Management?

For Handover Management, the most relevant tools on the flagship platform are the EVM, SPI and CPI calculators on PMMilestone.org. They reproduce the formulas referenced in this entry against your own project data.

What is a common misconception about Handover Management?

That the topic is well-defined across all references. In practice, definitions vary between PMBOK, PRINCE2, AACE and ISO 21500 — this entry uses the definition most aligned with field practice on capital projects, and flags where the standards diverge.

Which related encyclopedia entries should I read alongside Handover Management?

Read Earned Value Management, Critical Path Method and the DCMA 14-point assessment next. The full A–Z is available in the PMMilestone Encyclopedia, and quick one-line definitions live in the PM Glossary on the flagship platform.

How does Dr. Hassan Eliwa's research treat Handover Management?

Dr. Hassan Eliwa's research focuses on owner-side project controls, schedule integrity and forensic delay analysis on capital construction and power programmes. Handover Management is treated through that lens — what a planning or controls engineer is expected to do with it on a live project, not its textbook definition alone. See the full research library at PMMilestone Research Articles.

How is Handover Management defined on PMMilestone Research & Insights?

The structured process of transferring a completed project, phase, or deliverable from the delivery team to the receiving operator, with all documentation, training, and warranties intact. For the full treatment, see the definition, principles, applications and related entries above — every encyclopedia entry follows the same research-grade structure.

When should handover planning start?

At project initiation in principle, and in detail by the 50% point. Documentation discipline, operator engagement, and training schedules all need to mature with the project. Leaving handover until the last quarter guarantees a poor result.

What is the difference between practical completion and handover?

Practical completion is a contractual milestone certifying the work is substantially done. Handover is the operational process of transferring care, custody and control. They often coincide on the calendar but are not the same thing — one is legal, the other is human.

How long should the handover phase be?

Rule of thumb: 5–10% of the project duration. A two-year construction project deserves 6–10 weeks of planned handover; a complex hospital or refinery may need 12–16. IT migrations typically need 4–6 weeks of shadow-then-lead transition.

Who owns the snag list?

The contractor owns closing snags; the operator owns deciding which snags block acceptance. A jointly maintained snag register with owners, target dates, and weekly review is non-negotiable.

Should the operator have veto power at handover?

Yes, on safety- and operability-critical items; no on cosmetic items inside the defect-liability period. Distinguish 'cannot operate without this' from 'will be fixed in the next quarter' and document the distinction up front.

How do we handle handover of partial works?

Sectional completion, with the same rigour. Each section gets its own readiness index, documentation pack, training and acceptance gate. Sectional handover is harder than total handover, not easier.

What's the most common handover failure?

Documentation written in a rush in the final month. By that point the people who knew the answers have moved to other projects. Discipline is to write the manuals as the systems are built, not after.

How does handover apply to agile / iterative IT delivery?

Every release is a small handover. The discipline scales down: runbooks updated per release, training delivered incrementally, the operations team embedded in the agile team. Done well, the 'big' handover at programme end is a non-event because it has happened weekly all along.

Which calculators on PMMilestone.org apply to Handover Management?

For Handover Management, the most relevant tools on the flagship platform are the EVM, SPI and CPI calculators on PMMilestone.org. They reproduce the formulas referenced in this entry against your own project data.

What is a common misconception about Handover Management?

That the topic is well-defined across all references. In practice, definitions vary between PMBOK, PRINCE2, AACE and ISO 21500 — this entry uses the definition most aligned with field practice on capital projects, and flags where the standards diverge.

Which related encyclopedia entries should I read alongside Handover Management?

Read Earned Value Management, Critical Path Method and the DCMA 14-point assessment next. The full A–Z is available in the PMMilestone Encyclopedia, and quick one-line definitions live in the PM Glossary on the flagship platform.

How does Dr. Hassan Eliwa's research treat Handover Management?

Dr. Hassan Eliwa's research focuses on owner-side project controls, schedule integrity and forensic delay analysis on capital construction and power programmes. Handover Management is treated through that lens — what a planning or controls engineer is expected to do with it on a live project, not its textbook definition alone. See the full research library at PMMilestone Research Articles.

How is Handover Management defined on PMMilestone Research & Insights?

The structured process of transferring a completed project, phase, or deliverable from the delivery team to the receiving operator, with all documentation, training, and warranties intact. For the full treatment, see the definition, principles, applications and related entries above — every encyclopedia entry follows the same research-grade structure.

Closeout · Letter H

Handover Management

The structured process of transferring a completed project, phase, or deliverable from the delivery team to the receiving operator, with all documentation, training, and warranties intact.

By Dr. Hassan Eliwa, PhD · Founder of PMMilestone.org and PMMilestone.com · Updated 2026-06-23

Definition

Handover management is the discipline of transferring a completed asset, system, or deliverable from the team that built it to the team that will operate, maintain, or use it. It covers physical hand-over, documentation, training, defect-liability arrangements, warranties, spares, and the formal acceptance gate. A project that is technically complete but badly handed over is, from the operator's point of view, not complete at all.

Why It's the Most Underrated Project Phase

Handover is where ten months of good work can be undone in ten days. Operations teams remember projects by their handover quality, not by how clever the design was. I have seen award-winning buildings go into operation with no commissioning data, no asset register, and a confused FM team — and I have seen modest projects shine because the handover pack was complete, indexed, and walked through with the operator over two patient weeks. The latter wins every benchmarking study I have ever read.

Real-World Construction Example

On a 180-bed hospital project, handover was planned as a structured 12-week ramp: O&M manuals delivered in week 1, training program through weeks 2–6, dry commissioning of clinical systems weeks 4–8, wet commissioning 6–10, parallel-running 8–11, formal acceptance week 12. The trust took ownership of a building they understood. Compare with a sister project where the contractor handed over a stack of binders on the practical-completion date — six months later the FM team was still finding undocumented systems and the snag list was growing instead of shrinking.

Real-World IT / Agile Example

The IT equivalent is the transition from a build team to a sustaining team — a SRE squad, a managed-service provider, or the client's internal IT. On a digital-banking platform migration, we ran handover as a six-week overlap: weeks 1–2 sustaining team shadowed the build team, weeks 3–4 sustaining team led with build team support, weeks 5–6 build team observed only. Incidents during the first 90 days post go-live were 60% lower than the previous migration, where the build team had simply emailed runbooks and disbanded.

Standard Handover Components

Asset register / CMDB: every item or system, with location, ID, and key data.
O&M manuals: indexed, searchable, version-controlled.
As-built drawings / architecture diagrams: reflecting what was actually delivered, not designed.
Commissioning records: proof systems perform to specification.
Training: delivered, attended, evidenced.
Warranties and defect-liability schedule: who fixes what, for how long, contact path.
Spares and consumables: first-fit spares delivered, supplier list with lead times.
Outstanding works ("snag list"): with owner, target date, and status.
Acceptance certificate: signed by the receiving party.

Project Controls Perspective

Controls teams should baseline handover as a real phase, not a milestone day. We track handover readiness on a weighted index (documentation %, training %, commissioning %, snags closed %) and report it weekly from 90 days out. Projects that hit readiness scores of 95%+ at the planned handover date have a smooth transition; those below 80% almost always slip and damage the client relationship even when they don't slip.

Common Mistakes

Treating handover as a date, not a phase. Two weeks of pack-up doesn't substitute for a planned transition.
Documentation written at the end. Manuals collated in the last month are universally poor; they must be written in parallel with construction.
Training as a tick-box. A two-hour briefing for a complex BMS or platform doesn't transfer competence.
No operator involvement during build. Operators surprised on handover day push back; involved early, they own the result.
Snag-list amnesia. Open items at handover that nobody owns will still be open a year later.
No defect-liability discipline. Warranties exist but no one knows the contact path; operators give up and pay for repairs themselves.

Expert Tips

Start handover planning at 50% complete. By 80% it is too late to recover documentation discipline.
Embed an operator representative in the project team. Their early sign-offs save months later.
Use a readiness index, not a single milestone. The number forces honest conversations earlier.
Walk the handover pack page by page with the operator. If they can't navigate it in front of you, it isn't ready.
Keep the build team accessible for 90 days post handover. A WhatsApp group or shared channel costs nothing and saves the relationship.

Key Takeaways

Handover is a phase, not a day; plan it with the same rigour as design or construction.
Operations remembers projects by their handover, not by their design awards.
Documentation, training, and snag closure must mature in parallel — not at the end.
A readiness index reported weekly from 90 days out drives the right behaviours.
Build-team accessibility for 90 days post handover is the cheapest insurance in the business.

Related Encyclopedia Entries

Quality Management — companion entry on a directly related concept.
Lessons Learned — companion entry on a directly related concept.
Scope Management — companion entry on a directly related concept.
Stakeholder Engagement — companion entry on a directly related concept.
Issue Management — companion entry on a directly related concept.
Integrated Master Schedule — companion entry on a directly related concept.

Frequently Asked Questions

When should handover planning start?
At project initiation in principle, and in detail by the 50% point. Documentation discipline, operator engagement, and training schedules all need to mature with the project. Leaving handover until the last quarter guarantees a poor result.
What is the difference between practical completion and handover?
Practical completion is a contractual milestone certifying the work is substantially done. Handover is the operational process of transferring care, custody and control. They often coincide on the calendar but are not the same thing — one is legal, the other is human.
How long should the handover phase be?
Rule of thumb: 5–10% of the project duration. A two-year construction project deserves 6–10 weeks of planned handover; a complex hospital or refinery may need 12–16. IT migrations typically need 4–6 weeks of shadow-then-lead transition.
Who owns the snag list?
The contractor owns closing snags; the operator owns deciding which snags block acceptance. A jointly maintained snag register with owners, target dates, and weekly review is non-negotiable.
Should the operator have veto power at handover?
Yes, on safety- and operability-critical items; no on cosmetic items inside the defect-liability period. Distinguish 'cannot operate without this' from 'will be fixed in the next quarter' and document the distinction up front.
How do we handle handover of partial works?
Sectional completion, with the same rigour. Each section gets its own readiness index, documentation pack, training and acceptance gate. Sectional handover is harder than total handover, not easier.
What's the most common handover failure?
Documentation written in a rush in the final month. By that point the people who knew the answers have moved to other projects. Discipline is to write the manuals as the systems are built, not after.
How does handover apply to agile / iterative IT delivery?
Every release is a small handover. The discipline scales down: runbooks updated per release, training delivered incrementally, the operations team embedded in the agile team. Done well, the 'big' handover at programme end is a non-event because it has happened weekly all along.
Which calculators on PMMilestone.org apply to Handover Management?
For Handover Management, the most relevant tools on the flagship platform are the EVM, SPI and CPI calculators on PMMilestone.org. They reproduce the formulas referenced in this entry against your own project data.
What is a common misconception about Handover Management?
That the topic is well-defined across all references. In practice, definitions vary between PMBOK, PRINCE2, AACE and ISO 21500 — this entry uses the definition most aligned with field practice on capital projects, and flags where the standards diverge.
Which related encyclopedia entries should I read alongside Handover Management?
Read Earned Value Management, Critical Path Method and the DCMA 14-point assessment next. The full A–Z is available in the PMMilestone Encyclopedia, and quick one-line definitions live in the PM Glossary on the flagship platform.
How does Dr. Hassan Eliwa's research treat Handover Management?
Dr. Hassan Eliwa's research focuses on owner-side project controls, schedule integrity and forensic delay analysis on capital construction and power programmes. Handover Management is treated through that lens — what a planning or controls engineer is expected to do with it on a live project, not its textbook definition alone. See the full research library at PMMilestone Research Articles.
How is Handover Management defined on PMMilestone Research & Insights?
The structured process of transferring a completed project, phase, or deliverable from the delivery team to the receiving operator, with all documentation, training, and warranties intact. For the full treatment, see the definition, principles, applications and related entries above — every encyclopedia entry follows the same research-grade structure.

View the full FAQ page for Handover Management →