Commissioning gets the attention it deserves. It is structured, it is witnessed, it produces evidence, and our guide to data center commissioning and acceptance testing covers the levels and the test procedures in detail.
Handover gets almost none. It is treated as an administrative event at the end, a date rather than a deliverable, and the consequences surface months later when somebody needs a drawing that does not exist or a setting that nobody recorded.
The distinction is worth stating plainly. Commissioning demonstrates that the facility works. Handover transfers the means to keep it working. A building can satisfy the first completely and fail the second, and the failure is invisible on the day because everything is running.
As-built drawings, and why design drawings are not a substitute
Design drawings record what was intended. As-builts record what was installed, including every deviation agreed on site when something did not fit, a route changed, or an item was substituted.
Those deviations are the entire value. A facility whose documentation shows the design rather than the installation is a facility where every future change starts with an investigation, because nobody can trust the drawing in front of them. Our guide to change management in a live facility describes how alterations are supposed to be planned, and that process assumes you know what is currently there.
The drawings worth insisting on are the electrical distribution schematics down to final circuits, with circuit identification matching the labels physically on the equipment; mechanical layouts including pipework and ductwork routes with valve and damper identification; containment and pathway routes, which matter the moment anyone needs to add a cable; the grounding and bonding arrangement, which our guide to grounding and bonding systems covers and which is nearly impossible to verify by inspection afterward; and the fire detection and suppression layout with device addresses.
Two practical requirements make the difference between a usable set and an archive. Insist on native editable files as well as PDFs, because the next alteration has to be drawn on top of them. And insist on a revision scheme, so that there is an unambiguous way to tell which version is current once changes begin.
The operation and maintenance package
What usually arrives is a collection of manufacturer brochures. What is needed is a structured set covering each installed system.
Per system, that means the manufacturer's operating and maintenance instructions for the model actually installed rather than the product range; the maintenance tasks with their intervals and the competence required to perform them; a parts list with identifying numbers, which is what makes ordering a replacement possible at short notice; the commissioning and test records for that system; and warranty documentation with the start date and the route for making a claim.
Two items are routinely missing and routinely painful. The first is the set of configured settings: protective relay settings, control setpoints, alarm thresholds, BMS configuration and network addressing. These are decisions made during commissioning that are not recoverable by inspection, and reconstructing them after a controller failure is a genuinely difficult exercise. The second is an index. A folder of several hundred unsorted PDFs is technically a handover package and practically unusable at two in the morning.
Spares, keys and access
The physical side of handover is smaller and easier to verify, which is why it is worth doing properly.
Attic stock is the material left on site for the operator: filters, lamps, fuses, belts and the specific items a manufacturer designates as consumable. It should be listed and located rather than stacked somewhere and forgotten, because stock nobody can find is not stock.
Specialist tools matter more than their cost suggests. Some equipment cannot be opened, racked or serviced without a proprietary tool or key, and if the only one left with the contractor, the first maintenance task becomes a procurement exercise.
Keys, access credentials and administrative passwords for every system with a controller need a documented transfer. Commissioning engineers invariably hold administrative access to BMS, power monitoring and fire panels, and that access must be enumerated and changed rather than assumed to have lapsed.
Note that this is a different subject from fleet hardware spares. Our guide to warranty, RMA and spare parts strategy covers the IT equipment side, which runs on manufacturer warranties and RMA processes rather than on a construction contract.
Training is a deliverable, not a walk-around
Operator training is frequently satisfied by a demonstration given to whoever happened to be available on the day, and treated as complete.
What makes it useful is modest and specific. It should be delivered to the people who will actually operate the facility, which requires that they have been recruited, so the staffing plan has to lead the handover date rather than follow it; our guide to staffing and shift models covers that side. It should be recorded, so that the next hire can be trained from the material rather than from somebody's recollection. It should cover failure modes and responses, not only normal operation, because normal operation is the part that is self-evident. And it should be delivered by the people who commissioned the systems, while they still remember the decisions they made.
The warranty period is an operational period
A construction warranty, or defects liability period, is a window during which the contractor remains responsible for rectifying defects. It is an instrument that is routinely wasted.
It is wasted in two ways. The first is a failure to log: faults are fixed informally, nothing is recorded, and when a pattern emerges there is no evidence that it was a pattern. The second is a failure to inspect before expiry. Defects that are latent rather than obvious, which is most of them, are found by looking, and a deliberate inspection before the period closes is the last opportunity to have them rectified at the contractor's cost.
Both are solved by treating the period as something actively managed: log every fault against the system and the responsible party from day one, and schedule a formal inspection in advance of expiry rather than discovering the date after it has passed.
It is also worth confirming when each warranty actually starts, since equipment energized early during commissioning may have begun its warranty before the building was handed over, and the operator can inherit less coverage than the contract implies.
Tie the package to payment
The structural reason handover packages are thin is leverage. Documentation is the last deliverable, and by the time it is due the contractor has been paid nearly in full and has moved their team to the next project. Chasing it is then a favor rather than an obligation.
The remedy is to move it earlier. Require a draft package before the final commissioning stage, make acceptance of the documentation a condition of a payment milestone, and review it properly rather than confirming receipt of a hard drive. A review means opening the files, checking that drawings reflect what you can see in the room, and confirming the settings records are populated rather than templated.
A short verification visit with the documentation in hand finds most of what is missing, and it finds it while somebody still has a commercial reason to supply it.
For a tenant rather than an owner
Colocation customers do not receive a handover package, but the same information shapes what the operator can do for them: how quickly a circuit can be traced, whether capacity figures are reliable, how an alteration gets planned. Those are reasonable questions to ask during a due-diligence visit, and the answers say a good deal about how the facility is run.
If you would rather the documentation burden sat with the facility operator, talk to our team about colocation and hosting at Rax.
Frequently Asked Questions
What is the difference between commissioning and handover?
Commissioning is the testing process that demonstrates the installed systems perform as designed. Handover is the transfer of the facility and everything needed to operate it: as-built drawings, operation and maintenance manuals, test records, settings, spares, keys and access, and training for the people who will run it. A building can be fully commissioned and still be hard to operate if the handover package is thin.
What should an O&M manual actually contain?
For each installed system: the manufacturer's operating and maintenance instructions, the recommended maintenance tasks and their intervals, a parts list with identifying numbers, commissioning and test records, warranty documentation with its start date and contact route, and the contact details of the installing contractor. Generic manufacturer brochures are not an O&M manual, and a folder of PDFs without an index is close to unusable during an incident.
Why do as-built drawings matter so much?
Because every future change depends on them. Design drawings record intent; as-builts record what was actually installed, including the deviations made on site. Without them, each alteration begins with an investigation to establish what is there, which is slow, and any assumption that turns out to be wrong is a safety matter rather than an inconvenience.
When should the handover package be required?
Progressively, with the package tied to payment milestones rather than requested after practical completion. Leverage falls sharply once the final payment is made and the contractor has demobilized, and documentation is the deliverable most often outstanding at that point. Requiring a draft package before the final commissioning stage is a common and effective arrangement.
A Real Energisation Date, Not a Brochure
Rax operates where transmission investment has run ahead of load, and we are direct about staged capacity and real dates. Talk to our team about sizing a deployment against a timeline.
Contact Rax Data & Energy