What belongs in technology handover documentation

Every building technology system is eventually inherited by someone who was not there when it was installed. What that person receives determines whether a future change is an hour of work or a week of investigation. Undocumented systems are not broken — they are simply expensive to touch, and that cost is paid repeatedly for the life of the building.

• As-built drawings. Device positions, containment routes, riser diagrams and equipment room layouts reflecting what was actually installed, not what was drawn at tender.
• Cabling schedules. Every permanent link identified, with outlet, panel, port and route, matching the physical labels.
• Labelling convention. A short written explanation of the naming logic so future work extends it rather than inventing a second scheme.
• Test results. Field test reports for cabling and evidence of functional testing for each system.
• Configuration records. Addressing, network segmentation, device naming, backup files and where those backups are stored.
• Equipment register. What was installed, where, with model and serial details, plus supplier documentation and handover records.
• Operating information. How the system is used day to day, in language the operator can follow, plus the training that was given and to whom.

Administrative access should transfer to the owner in a controlled way at handover, with any default credentials changed and a record of which accounts exist and what they can do. This is a governance question as much as a technical one; the owner should know who can reach their systems and be able to revoke that access.

• Consultants: make the documentation set an explicit deliverable at design stage, not a closeout request.
• Main contractors: align the technology closeout format with the wider handover pack so it is not the outstanding item at completion.
• Facility and IT teams: ask for configuration records and credentials handling, which are the items most often missing.
• Owners: check that the pack would make sense to a contractor other than the one who installed the system.

Ask one question at handover: could a competent engineer who has never visited this building make a safe, correct change tomorrow using only this pack? If the answer is no, the pack is not finished — and the gap is far cheaper to close before the project team disperses.