What a Good Handover Pack Contains

Handover is two separate jobs. There is the physical walk — racks, containment, labels, tidiness — which we cover in a sister piece, what we check before handover. This article is about the other half: the documents. The pack is what survives after the crew has left, the PM has moved on and the fit-out is three tenants old. Five things belong in it, and each has a failure mode with a price tag.

As-built drawings at final revision

Good looks like drawings that show what was actually installed — every route, every containment change, every deviation from design — issued at the final revision and clearly marked as such.

Bad looks like construction-issue drawings with pen marks, or a set stuck at revision A while the site finished at revision F. The cost surfaces years later: an engineer tracing a cable through a ceiling because the drawing shows a route that was value-engineered out before it was ever installed. Every hour of that tracing is an hour the as-built should have saved.

Test results per link, named to the labelling

Good looks like one result per installed link, exported from calibrated kit, with the result name matching the label on the physical port. Anyone should be able to pick a port, find its result and see that it passed on a stated date.

Bad looks like a zip of files named TRACE001 to TRACE900 with no key. Those results are technically present and practically useless. When a link fails in service, you cannot prove it passed at handover — which means you cannot separate an install defect from later damage, and warranty conversations get expensive precisely when you need them to be simple.

A labelling schedule that matches physical reality

Good looks like a schedule where every entry corresponds to a label you can walk up and read, both ends, no exceptions.

Bad looks like a schedule written from the design rather than from the install. The gap between the two turns every future fault into detective work: an engineer pulling patch cords at random because panel 4 port 12 on paper is panel 5 port 3 in the rack. Multiply that by the life of the installation.

A labelling schedule that lies is worse than no schedule at all.

Snags closed with dates

Good looks like a snag list where every item carries a closure date and evidence. Bad looks like snag list to follow, or items marked closed with nothing behind them. Open snags do not disappear at handover — they convert into faults that someone else pays to diagnose from scratch, without the context the install team had for free.

Warranty in plain English

Good looks like a warranty statement that says what is covered, for how long, and what conditions keep it valid — written so an ops manager can read it, not just a lawyer.

Bad looks like a 25-year system warranty that quietly depends on conditions nobody checked. Before you sign, confirm the ones that void headline warranties most often:

• Installer certification held by the firm that did the work
• Products registered with the manufacturer, on time
• Test results submitted in the format the warranty demands
• Ongoing conditions — approved parts, approved changes — spelled out

A handover pack is not admin. It is the difference between a network you operate and a network you excavate. If the packs you receive arrive thin, start asking why — and if you want to see what a complete one looks like, ask us. Ask us for a sample handover pack