How to write a project handover document that protects your business

The day you hand over a finished project is a strange one. Nine months of effort, ten thousand decisions, one final walkthrough, and then a handshake and an envelope of certificates. For most builders, the handover is the final task — the project is done.

For your business, the handover is the most important moment. It's when the client decides whether to recommend you. It's the document they'll dig out in three years when they're selling the house. It's the only artefact that proves what you delivered against what was originally agreed.

Most handover documents in UK construction are bad — and this applies just as much to a £15k bathroom refresh as it does to a £400k extension. Not because builders don't care — they do — but because the document is left to the end, assembled in a panic, and produced under time pressure.

Here's what a proper handover document looks like.

What a handover document is for

It has three audiences:

1. The client today — they need a record of what they paid for, what's where, and what they need to know about their newly-finished home.
2. The client in three years — when they're selling the house, an estate agent or surveyor will ask "do you have any documentation on the works?" A polished handover document is a value-additive selling document.
3. You, in case of dispute — six months after handover, when the client claims the underfloor heating wasn't part of the original scope, you point at the variations log inside the handover document. Discussion over.

A document that serves only one of these audiences is incomplete. A good handover serves all three.

What to include

A handover document — for any client-facing project, big or small — should have, at minimum, these sections (scale the depth to the project):

1. Project header

Project name, address, postcode, original start date, actual completion date, original quote, final contracted value, list of variations, name of client, name of project manager, and your company information including Companies House number and VAT number.

2. Quote vs final summary

Single-page summary showing original quote, variations to date (signed), final contracted value, total invoiced, total paid. Both parties should agree on these numbers before handover — and the document is the artefact of that agreement.

3. Timeline with stages

The original 8-stage plan with actual start and end dates. Optionally: a brief commentary per stage if anything notable happened. This shows the client (and a future surveyor) that the project was managed methodically.

4. Every variation in detail

One section per variation: number, title, description, cost delta, programme delta, date signed, name of person who signed. Yes, every single one. This is the section that wins disputes.

5. Every decision recorded

List of decisions you raised with the client and what was chosen. "Splashback tile: Calacatta marble (£950). Pendant lights: bronze cone trio (£840)." Etc. Same principle: provable record.

6. Project updates chronologically

If you've been posting weekly updates with photos throughout the project, include them. Not as filler — as proof that you communicated. Future surveyors love progress photos because they show concealed work (steel beams, MEP first-fix, waterproofing) before it was covered.

7. Invoices summary

One line per invoice: number, title, amount, issued date, paid date, payment reference. Often clients have lost their copies; the handover document is the canonical record.

8. Certificates and as-built drawings

Building Regulations completion certificate. Electrical EICR. Gas safety certificate. Energy performance certificate. As-built drawings where applicable. Manufacturer warranties for major installations (boiler, MVHR, underfloor heating, roof).

9. Aftercare and snagging

Your snagging policy (typical: snag within 14 days of handover, fix within 28 days). Defects liability period (typically 12 months for residential). Out-of-hours emergency contact. Recommended maintenance schedule (when to service the MVHR, when to re-grout the bathroom, etc.).

10. Builder details for future reference

Bank account in case the client wants to bank-transfer a tip or future works. Your company registration. Your VAT number. Your contact email. Make it easy for the client to come back to you in three years.

What most builders get wrong

They wait until the end. If you start assembling the handover at handover, you'll spend two days finding things. Assemble it incrementally — every signed variation, every decision, every paid invoice — and at the end it generates itself.

They use a Word template. Word templates rot. Tables go misaligned. The client's name is missing from page 7 because someone forgot to find-and-replace it. The Companies House number is out of date. Use software that generates the document from your live project data — there is no manual step that can fail.

They include only the positive bits. A handover document that hides the variations log is suspicious. Include everything, including variations that increased the price. Transparency builds trust; opacity invites scrutiny.

They make it too long. A 60-page handover for a £200k extension is unreadable. The client will skim. Aim for 8-15 pages: punchy, structured, with the summary on page 1 and the detail in the appendices.

They forget to brand it. The handover is one of the few documents the client will keep in a drawer forever. Your logo. Your colours. Your company information on every page. Cheap polish pays for itself.

The role of software

You don't strictly need software to produce a good handover document — but it makes the difference between "I will do this properly" and "I will actually do this properly."

The argument for using a portal like Builders Ready isn't that it produces the document at the end. It's that the document is being produced continuously throughout the project: every decision is logged the moment it's made, every variation is signed the moment it's agreed, every invoice is recorded the moment it's paid. At handover, the document is already there. You generate it in one click.

That removes the most common failure mode — the handover that never quite got finished — and it shifts the question from "do I have the energy to write this up?" to "do I want to send it now or after the snagging walkthrough?"

The bottom line

The handover document is the most professional artefact your business produces. It's the difference between being remembered as the builder who delivered the kitchen and being remembered as the builder who delivered the project. Spend the same care on it that you spent on the build itself.