A data centre can look physically complete and still be unready to carry load. Power failover may be untested, cooling response unclear, BMS and DCIM alarms incomplete, and fire interfaces unvalidated. None of those gaps show up in a walkthrough. They show up in testing, or they show up later as an outage.
A structured data centre commissioning checklist closes that gap by tying every activity, task, and document to a specific stage of the process. It gives owners an evidence trail and gives construction and operations teams a shared definition of done at each level.
This article walks through the levels most commissioning programs follow and the verification points an owner should expect to see at each one.
What a Data Centre Commissioning Checklist Is For
A commissioning checklist is a monitoring and delivery tool. It tracks the activities, tasks, and documentation required to complete an efficient and effective commissioning process. Used properly, it is not a formality signed at the end of construction. It is worked continuously as equipment arrives, systems start, and tests are witnessed.
The checklist sits underneath the commissioning plan itself. A Cx plan brings together agreements, technical definitions, and clear responsibilities. The plan says who does what and to what standard. The checklist records what was actually verified, by whom, and with what result.
Owners should expect the checklist to be organized by level, so readiness can be judged stage by stage rather than all at once.
The Levels of Data Centre Commissioning
Most published frameworks describe five levels of commissioning, and many projects number additional checkpoints below or above that core set. The named levels in common checklists run from Level 0 at design through Level 4 at functional performance testing, with integrated systems testing as the final proof stage before handover.
The table is a map, not the detail. Each level carries its own verification points, and the owner's checklist should be specific to the equipment and topology in the facility.
Level 0: Design, Planning, and Governance
The early work decides how smooth the rest becomes. A typical commissioning sequence begins with setting up the commissioning team, preparing project requirements, drafting a Basis of Design (BOD) paper, setting the budget, and drafting the commissioning program. Each of those produces an artifact an owner can review long before construction is far along.
Readiness checklists used before testing often start with commissioning governance and vendor readiness. Governance covers who holds authority, how results are reviewed, and how deviations are closed. Vendor readiness covers whether suppliers have submitted the documentation needed for the stages ahead.
Facilities staff belong in this stage. Their involvement in design development and design reviews is one of the clearest predictors of whether the operations team can actually run what gets built.
Level 1: Factory Testing
Factory testing happens before equipment reaches the site, which is exactly what makes it valuable. Problems found on the factory floor are cheaper and faster to correct than problems found after a unit is set on a pad and connected.
On the checklist side, owners should look for confirmation that factory tests were witnessed, that results were recorded against the equipment tag, and that any exceptions were resolved or formally accepted before shipment. When units arrive without that record, the site team inherits unresolved risk.
Level 2: Delivery, Installation, and Pre-Startup
This level covers general equipment and system installation checks. In practice that means wiring, ductwork, piping, and the supporting installation details that determine whether a system can be started safely.
Pre-functional verifications sit here as well. Common items include power verification, rotation checks, pressure hold testing, and leak testing. These are the checks that catch reversed rotation, incorrect terminations, and pressure boundaries that will not hold, all before a system is asked to operate.
If any of these verifications are incomplete, start-up stops being verification and becomes debugging.
Level 3: Systems Start-Up
At start-up, individual systems are energized and run for the first time as installed systems. The owner's interest is in whether each system behaves as designed and whether the controls layer reports what is actually happening in the space.
Alarm and monitoring completeness belongs in this level. BMS and DCIM alarms that are incomplete at start-up tend to stay incomplete, and an operator who cannot see a condition cannot respond to it.
Start-up records should be traceable. Each system should carry a clear status: started, tested, exception open, or accepted.
Level 4: Functional Performance Testing
Functional performance testing (FPT) proves each system meets its specified performance under controlled conditions. At this level the checklist functions as a test register. Each system has defined tests, defined acceptance criteria, and a documented result.
FPTs also feed the final stage. Verification that all FPTs are completed is one of the standard gates that must be cleared before integrated systems testing begins. An FPT still open at that point becomes an untested assumption buried inside a system-level test.
Before Integrated Systems Testing: The Pre-IST Gate
Integrated systems testing (IST) is where the facility is tested as a whole rather than as a collection of individual systems. The pre-IST checklist exists to make sure that test is meaningful.
Items that must be in place prior to IST include verification of generator fuel level and verification of all FPTs completed, along with the remaining readiness items on the approved checklist. The purpose of the gate is straightforward. An IST run on an unready facility produces noise instead of evidence.
Owners should treat the pre-IST gate as a formal hold point with sign-off, not a verbal confirmation exchanged on site the morning of testing.
Integrated Systems Testing: Failure Scenarios and Recovery
IST asks whether the facility can operate under load, fail safely, recover predictably, alert correctly, and be handed over to operations with evidence. Those five outcomes are the clearest way to judge whether a test program was adequate.
Failure scenarios are central to it. Load banks are commonly used to place the facility under realistic electrical load while those scenarios are run. Power failover is tested. Cooling response under changing load is tested. Fire interfaces are validated against the systems they are meant to trigger.
IST also produces the moments that commissioning exists to find. The value is not in confirming that everything works. It is in finding the interactions that no single-system test could have caught.
Documentation and Handover Readiness
Commissioning ends with a handover package , and the checklist should be able to produce it. Every verified item should point to a record: a test result, a witnessed signature, a marked-up drawing, a closed exception.
For existing facilities, the work looks different. It typically begins with a search of existing documentation, followed by site walks, investigations, and analysis before any improvement work is implemented. Owners planning a retrofit should budget time for that discovery phase, because existing records may not reflect the facility as it stands today.
How Owners Should Use the Checklist
- Assign an owner for every checklist section, so no item drifts between contractors.
- Treat each level as a hold point with documented acceptance before the next begins.
- Require evidence with each completed item, not just a checkmark.
- Track exceptions in the same register as the tests, with named owners and closure dates.
- Keep operations staff in the review loop from design onward, not only at handover.
An independent commissioning provider can verify the checklist against the facility itself rather than against the construction schedule. Whatever delivery model is used, the checklist is only as strong as the evidence behind each line.
Questions we get on this topic
How many levels of commissioning does a data centre usually have?
Most programs describe five levels, running from Level 0 design and planning through functional performance testing, with integrated systems testing as the final stage. Some projects add checkpoints below Level 0 or extend the numbering beyond five, which is common when an owner wants more hold points. The right number depends on facility complexity and risk tolerance.
What must be complete before integrated systems testing begins?
The pre-IST gate confirms the facility is ready to be tested as a whole. Standard items include verification of generator fuel level and verification of all functional performance tests completed, plus the remaining readiness items on the approved checklist. Anything still open at that point should be formally accepted as a known exception before testing proceeds.
What is the difference between functional performance testing and integrated systems testing?
Functional performance testing verifies one system at a time against its specified performance criteria. Integrated systems testing verifies how systems behave together under load and under failure, including power failover, cooling response, alarms, and fire interfaces. A system can pass FPT and still contribute to an IST failure, which is why both stages are needed.
Can a data centre be physically complete but not ready for handover?
Yes. A facility can look finished and still be unready if power failover is untested, cooling response is unclear, BMS and DCIM alarms are incomplete, or fire interfaces have not been validated. Physical completion is not the same as verified performance. Handover should follow documented test evidence rather than a construction completion date.
What does commissioning look like in an existing data centre?
Existing building commissioning starts with a search of available documentation, then site walks, investigations, and analysis to establish how the facility actually operates. Findings drive the improvement work, which is implemented and then verified. The discovery phase often takes longer than owners expect, because existing records and the operating facility do not always match.
Quality briefs, straight to your inbox
Field-tested guidance on inspection, audits and project quality systems — one issue on the first Tuesday of each month, written for people who have to make them work.
See past issues →- QA/QC in Data Center Construction Projects: A Practical GuideA practitioner's framework for QA/QC across data center construction — from ITPs and factory witness testing through Levels 1–5 commissioning to turnover packages that survive tenant acceptance.
- How the Checklist Differs from an ITP and Project Quality PlanA checklist, an ITP and a Project Quality Plan are connected — but they are not interchangeable. See how each document fits into the project quality-management system.
- Construction Quality Control Checklist: 30 Inspection PointsThirty field inspection points across earthworks, concrete, structural steel, piping, electrical and turnover — and a clear explanation of how a checklist differs from an ITP and a Project Quality Plan.
Need independent quality assurance on your project?
Talk to our team about inspection, auditing and QMS support.