What does producing a handover pack cost a firm?
A handover pack is the record a client or an incoming team relies on once your people have gone. At the end of a facilities contract it lists the assets, the planned maintenance history, the open reactive jobs and the supplier contacts. At the end of an IT service transition it holds the network diagrams, the credentials register, the runbooks and the tickets still open. For an advisory engagement or a closed matter it summarises what was decided, what was delivered and what the client now owns.
Almost all of that information existed long before the handover date. Yet the pack is usually compiled in the last two or three weeks, by the account lead or project manager, pulling from shared drives, inboxes, ticketing systems and memory. It competes with the final stretch of delivery and with mobilising the next piece of work.
To cost it for your own firm, take the hours spent producing one pack and multiply by the number of handovers you complete in a year, then by the charge-out rate of the people who compile them. Add the time spent afterwards answering questions the pack should have answered. The unbillable hours calculator works the same sum on a weekly basis, and the audit places it beside the other places your hours go.
Why does handover documentation get written twice?
The work was recorded once as it happened: in a job log, a change record, a file note or a visit report. Then it is written again at the end, in a different shape. The handover template asks for things in an order that no working system keeps them in, so somebody reads back through months of records, retypes what matters and decides what to leave out.
That second writing is also where things go missing. A warranty expiry mentioned in an email, a workaround agreed with the client's IT team on a call, a lease break noted in a file note: if the person compiling the pack does not remember it, the incoming team finds out the hard way. The rewrite costs hours and still leaves gaps, because it runs on recall rather than on the record.
What does a rebuilt handover process look like?
The rebuilt version treats the pack as something that fills while the engagement runs. We start from your handover template and trace each section back to where its content is first created.
| Section of the pack | Where it is first recorded | How it reaches the pack |
|---|---|---|
| Asset or service register | CAFM system, CMDB or asset spreadsheet | Read directly, with the date each entry was last updated |
| Decisions and variations | Meeting notes, emails, change records | Drafted into a dated decisions log, each line linked to its source |
| Open items and known issues | Ticketing or job management system | Pulled at the point of handover and grouped by priority |
| Contacts and responsibilities | CRM and contract schedules | Checked so nobody is listed who has since left |
| Warranties, renewals and key dates | Contract files and supplier correspondence | Extracted into a dates schedule naming the source document |
As the handover date approaches, the account lead opens a draft pack that is already mostly complete. The process flags what is missing, such as an asset with no service history or a decision with no recorded outcome, so gaps are chased while the people who know the answer are still around. A named person reviews every section and signs the pack off before it leaves the firm.
How does handover change for the people doing it?
The account lead moves from writing the pack to checking it. Instead of a fortnight of evenings piecing the engagement back together, their time goes on the parts that need judgement: the summary narrative, the risks worth warning the incoming team about, and the closing conversation with the client.
Handovers also stop depending on who happens to run them. A pack produced by a manager in their first year follows the same structure, and draws on the same records, as one produced by someone who has been with the firm for a decade. When a key person leaves mid-contract, which is when handover knowledge is most exposed, the record is already in shape. When knowledge leaves looks at that risk more closely.
Which firms get the most from this?
Firms whose work ends in a formal transfer. Facilities management companies hand over at contract exit and receive packs at mobilisation, often under exit clauses that spell out what must be provided. Managed service providers hand over at service transition and offboarding. Property and asset managers hand over when a building or portfolio changes manager. Advisory firms such as engineering consultancies and environmental consultancies close out engagements with a bundle of reports, data and recommendations.
Where the pack leans on formal reports, technical report writing is often the natural next rebuild.
What happens during the 30 days?
In the first week we take one recent handover pack and trace every section back to its source, with the people who compiled it, noting which parts took longest and which were nearly missed. In weeks two and three the process is built against your template and your systems, then run on an engagement that is genuinely due to hand over, so the draft pack is judged against real work. In week four the account leads are trained and the new process replaces the end-of-contract scramble. Thirty days of support follow go-live. How we work describes each stage.