Handover is part of the project
A project ends when the sponsor accepts it and can run it without the project team. Plan acceptance, records, contracts and training from the start.
- Project management
- 3 min read
- Published
On many projects, handover is treated as a formality at the end. The builders leave, the keys change hands, and a folder of documents follows some weeks later. The sponsor then spends months finding out how things work, who installed what and which warranty covers which fault.
A project is not finished when the work stops. It is finished when the sponsor has accepted it and can run what was delivered without the people who delivered it. That takes planning, and the planning starts at the beginning of the project, not in its last week.
Agree what acceptance means at the start
The scope should say how each part of the project will be accepted. Who inspects it, against what standard, and how long they have to respond. Handover then follows a known path instead of turning into a negotiation.
Acceptance is rarely a single moment. A fit-out might be accepted area by area as each is finished. A system might be accepted once it has run for an agreed period with real users. Defects found at acceptance go on a written list, each with an owner and a date for putting it right. Accepting a project with minor defects listed is normal. Accepting it with defects unlisted is how small problems become permanent ones.
Collect the records as the work happens
The records a sponsor needs after handover include drawings that show what was actually built, specifications and product data, test and commissioning results, operation and maintenance manuals, warranties, and any certificates or approvals the project required.
These are far easier to collect while the work is under way than afterwards. Make delivering them a condition of each contractor's completion, list them in the programme, and check them as they arrive. A contractor who has left site and been paid has little reason to search for a missing manual.
Hand over the contracts and the contacts
After handover, the sponsor needs to know who to call. Give the sponsor a single list of every supplier and contractor involved, what each provided, the warranty and maintenance terms that apply, and how to reach each one.
Where the project set up ongoing contracts, such as maintenance, support or supply agreements, make sure they are in the sponsor's name or can be transferred to it. Check the start dates. A maintenance contract that begins months after handover leaves a gap that nobody notices until something breaks.
Train the people who will run it
The people who will use and look after what the project delivered need to know how it works. Plan the training in the programme, with the right contractor or supplier delivering it, and record who attended. Keep the training materials with the handover records so that people who join later can learn from them.
Training is often cut when a project runs late, because it falls at the end. Protect it. A building or a system that its users do not understand will be used badly, and the sponsor will pay for that in faults and complaints for years.
Close the project properly
Once the sponsor has accepted the work, close the project in writing. Confirm the final account with each contractor. Release or retain any money held back against defects, according to the contracts. Record the defects still open, who will fix them and by when. Hand over the complete set of records in an organised form that the sponsor can use.
Then hold a short review with the sponsor. What went well, what did not, and what the sponsor would want done differently next time. The answers are useful for the sponsor's next project, whoever runs it.
A good handover is quiet. Nothing is missing, nobody is chasing anyone, and the sponsor simply starts using what was built. That quiet is the result of work planned from the first day.