Commissioning Readiness Checklist: A Self-Assessment for Data Center Programs
Checklist · March 24, 2026
Who This Assessment Is For
This checklist is for prime contractor project managers and commissioning leads on Tier III/IV data center programs — typically 3 to 6 months before energization.
The readiness criteria below map to the L1-L5 commissioning framework, a five-level verification sequence that structures commissioning from factory testing through integrated system testing. Each level has defined scope, gate criteria, and deliverables.
The goal is straightforward: identify documentation and procedure gaps before they surface during testing — when the schedule impact is highest.
How to Use This Assessment
Review each section below. For each readiness criterion, assess whether your program has it in place. Then use the scoring rubric at the end to evaluate your overall readiness per level.
Items marked Rated-3 only or Rated-4 only in L5 apply based on your facility’s TIA-942 target rating. All other items apply to both.
Pre-Commissioning Readiness
Pre-commissioning work front-loads verification before any physical testing begins. A logic error caught during simulation is a settings change. The same error caught during L5 integrated system testing is a schedule slip.
| # | Readiness Criterion |
|---|---|
| 1 | Power system models (ETAP, SKM, or PSCAD) completed and validated |
| 2 | Protection coordination studies reviewed against design intent |
| 3 | Bench testing plan identified for IED logic and communication protocols |
| 4 | HIL testing scope defined for critical failure modes |
L1: Factory Witness Testing
Factory witness testing catches defects in long-lead items before they reach the job site — and before rework becomes schedule-critical. Components with open L1 punch items should not advance to L2.
| # | Readiness Criterion |
|---|---|
| 1 | FAT/IFAT procedures developed for each long-lead component type |
| 2 | Test standards identified (manufacturer, national, owner requirements) |
| 3 | Witness plan assigns project team representative to each factory test |
| 4 | Deviation/punch list tracking process established |
| 5 | FWT report template ready for each component category |
L2: Receipt and Installation Verification
L2 verifies that what arrived on site matches what left the factory and was installed correctly. This level catches problems that only appear at installation: wrong mounting orientation, missing auxiliary connections, accessibility issues that would block maintenance under live load.
| # | Readiness Criterion |
|---|---|
| 1 | Receipt inspection checklists prepared (match procurement + L1 docs) |
| 2 | Installation verification plan references current drawings and specs |
| 3 | Code compliance requirements identified (local codes, OEM directives) |
| 4 | Accessibility and maintainability criteria defined |
| 5 | Photo documentation protocol established |
| 6 | Discrepancy reporting process defined with resolution tracking |
L3: Functional Component Testing
L3 answers a single question: does each installed component turn on and respond to commands? A component that passes L1 but fails at L3 gets caught here — not during system testing when the commissioning agent is on site.
| # | Readiness Criterion |
|---|---|
| 1 | Startup checklists prepared for each equipment type |
| 2 | Calibration procedures and acceptance ranges documented |
| 3 | Settings documentation matches design intent (relay settings, controller configuration) |
| 4 | Component test report templates ready |
| 5 | L3-to-L4 gate criteria defined (all components operational, checklists signed) |
L4: Functional System Testing
L4 is where individual components become systems. Testing covers five operating modes: normal, emergency, maintenance, failover, and black-start. The L4-to-L5 gate requires all systems to be ready for integration with the FST punch list cleared.
| # | Readiness Criterion |
|---|---|
| 1 | Scenario-based FST procedures cover all five operating modes |
| 2 | NFPA 110 and AHJ acceptance testing scripts prepared |
| 3 | Load testing plan defines acceptance criteria per system |
| 4 | Monitoring and control function verification procedures documented |
| 5 | Punch list process established with severity classification |
| 6 | L4-to-L5 gate criteria defined (all systems integration-ready, FST punch list cleared) |
| 7 | Test execution record templates match documentation requirements |
L5: Integrated System Testing
L5 is the final verification level — and the one the owner’s commissioning agent witnesses. It confirms that all systems work together under load, responding correctly to actions, maintenance activities, and faults per design sequences of operation.
Items 3 through 5 depend on your facility’s TIA-942 target rating. A Rated-4 program checks item 3. A Rated-3 program checks items 4 and 5. All programs check items 1, 2, and 6 through 12.
| # | Readiness Criterion |
|---|---|
| 1 | IST procedures cover cross-system integration under all five operating modes |
| 2 | TIA-942 target rating confirmed (Rated-3 or Rated-4) — determines test scope below |
| 3 | Rated-4 only: Single-failure replication test matrix covers all capacity systems, distribution elements, controllers, and network components, plus FMEA-based scenarios for firmware bugs, cyber-attacks, and human errors |
| 4 | Rated-3 only: Planned-removal test matrix demonstrates each capacity component and distribution path can be removed without impacting the critical environment |
| 5 | Rated-3 only: Maintenance scenario testing plan confirms no disruption from planned work activities |
| 6 | Utility/third-party witness testing scheduled with roles and responsibilities assigned |
| 7 | MOPs developed with documented back-out procedures for each test sequence |
| 8 | PRP/HSR failover and GOOSE latency characterization procedures with acceptance criteria defined |
| 9 | PTP/IRIG time sync verification plan with accuracy thresholds documented |
| 10 | Black-start recovery drill procedures with sequenced bus energization and resynchronization |
| 11 | As-built configuration baseline process defined with documentation standards |
| 12 | Post-IST tuning, defect resolution process, and turnover criteria established |
Gaps in Your Readiness?
Scope a Commissioning Readiness Sprint
A focused engagement closes documentation and procedure gaps before your commissioning window opens.
Readiness Scoring
Use this rubric to assess your program’s readiness at each level. Count how many criteria you have fully in place.
| Level | Green — Ready | Yellow — Gaps Exist | Red — Not Ready |
|---|---|---|---|
| Pre-Commissioning | All 4 items verified | 1–2 items pending | 3+ items missing or not started |
| L1 | All 5 items verified | 1–2 items pending | 3+ items missing |
| L2 | All 6 items verified | 1–2 items pending | 3+ items missing |
| L3 | All 5 items verified | 1–2 items pending | 3+ items missing |
| L4 | All 7 items verified | 1–3 items pending | 4+ items missing |
| L5 | All 12 items verified | 1–4 items pending | 5+ items missing |
If You’re Not Ready
Mostly green with one or two yellows. Your program is in good shape. The gaps are likely procedural details that can be closed with existing team resources. For methodology detail on any level, see the L1-L5 framework deep-dive.
Multiple yellows or any red in Pre-Commissioning through L3. Documentation and procedure gaps at early levels compound through later levels. An incomplete L1 witness plan means L2 receipt checking has no baseline to verify against. These gaps are the easiest to close — but only before site work begins.
Yellow or red in L4 or L5. Scenario-based procedures for system testing and integrated system testing require cross-system coordination across all five operating modes. These are the hardest test procedures to develop without prior Tier III/IV commissioning experience — and the most visible when they’re missing, because L5 is where the owner’s commissioning agent is watching.
For programs with gaps at L4 or L5, a pre-commissioning engagement scopes the procedure development, identifies the operating mode coverage, and builds the test documentation before the commissioning window opens. Book a scoping call to assess the fit.
Learn More
This checklist is a self-assessment tool. For the full methodology behind each level — including gate criteria, deliverable standards, and the verification sequence logic — read the L1-L5 Commissioning Framework.
For how the commissioning framework integrates with our full engineering methodology, see our technical approach. For the full scope of protection and controls services, see our services.
Related Insights
Put This Engineering Depth Behind Your Next Program
Tell us about your data center protection and controls requirements — we'll scope the work and show you how we'd approach it.