If you hire for commissioning by job title alone, you will miss the mark. In data centers, Levels 1 to 5 show what a person has actually done - from factory testing to black-building tests. And with pre-committed capacity near 89% and vacancy at record lows, teams do not have much room for weak handoffs or thin field experience.
Here’s the short version:
What this means for you:
The main point: hire to the level, not the title. A person who witnessed FATs is not the same as someone who led IST. And that gap affects risk, schedule, and pay.
Quick comparison
| Level | Main focus | What it proves | Typical roles |
|---|---|---|---|
| 1 | Factory acceptance | Equipment matches design before shipment | Factory reps, junior Cx, QA/QC |
| 2 | Site acceptance | Equipment arrived right and was installed right | Field engineers, startup techs |
| 3 | Startup | Equipment can be energized and checked safely | Startup techs, controls, TAB, Cx |
| 4 | Functional testing | Each system works as intended | Cx engineers, controls leads, TAB |
| 5 | Integrated testing | The full facility stays online during failures | Senior Cx leads, PMs, owner reps |
So if you are screening resumes, planning staffing, or sizing up your next move, I would map each person to level, system, and deliverable first. That gives you a much clearer read on fit than a title ever will.
Data Center Commissioning Levels 1–5: Roles, Deliverables & Hiring Signals
Levels 1 and 2 are the documented checks that happen before energization and before Level 3 startup begins.
Level 1 takes place at the manufacturer's facility before shipment. The point is simple: confirm that the equipment meets the Owner's Project Requirements (OPR) and Basis of Design (BoD) in a controlled setting. This stage often covers UPS systems, generators, switchgear, chillers, CRAH/CRAC units, PDUs, and controls hardware.[5][3][4]
At this point, Cx engineers review vendor submittals and FAT procedures against the OPR and BoD. During witness testing, they check live results against the written requirements. That can include voltage stability, load step performance, cooling capacity, alarm outputs, and control logic behavior.
If something doesn’t line up, it becomes a non-conformance. The team logs the related spec clause, the measured deviation, and the corrective action needed. Vendor test engineers run the test procedures and provide raw test data, calibration certificates, and corrective action records. Controls professionals check point lists, I/O assignments, and sequence-of-operations logic tied to startup and functional testing.[7][2][8]
Level 1 wraps up with:
After the equipment reaches the site, Level 2 checks condition and installation quality before energization. The team confirms the equipment arrived without damage, matches the approved FAT records, and was installed the right way.[5][3][6]
QA/QC staff inspect packaging and nameplates at delivery. After that, field service engineers and startup technicians move through checklists for anchorage, alignment, restraints, terminations, grounding, piping, insulation, valve orientation, and leak tests. Safety reviews also check emergency stops, access clearances, lockout/tagout provisions, and compliance with NEC, NFPA, and local codes.[3][6][2][1]
Superintendents coordinate trade sequencing and push punch-list items toward closure. Cx engineers oversee the process and make sure SAT documents are complete and traceable back to the FAT records.
Level 2 is the hard gate. Each serial number needs a complete SAT checklist before Level 3 pre-functional testing can start.[6][1][9] If any critical items are still open, they stay on the issue log with clear owners and due dates. Any limits that remain should be documented for the startup handoff.
Once Level 2 is closed, the project moves into Level 3 energization, point-to-point checks, and pre-functional testing.
Level 2 shows the site is ready for installation. Level 3 shows it’s ready for startup. Once Level 2 is done, Level 3 proves each subsystem can be energized safely before any systems get tied together. That’s why this stage sits right between site acceptance and system testing.
The work moves in a deliberate order. Before any energization starts, the team confirms LOTO plans, energization permits, and MOP approvals. Trips, relays, and breaker protection also need to be checked before equipment takes load.
At the same time, controls point-to-point verification runs alongside physical startup. Every I/O point between field devices and the BAS/EPMS gets checked. At this stage, common work includes:
All of that work is recorded in pre-functional forms and startup reports. A complete form includes equipment tag numbers and serial numbers, pre-energization safety checklists, measured voltages and currents, rotation direction, alarm outputs, controls point results, and a deficiency log with corrective actions and dates.
These records are the formal gate for moving a subsystem to Level 4. A subsystem should advance only when forms are complete, deficiencies are closed and retested, points are verified, and safety devices pass.
Four roles do most of the heavy lifting in Level 3. Startup technicians and manufacturer representatives handle the physical startup work. That includes energizing switchgear, UPS modules, chillers, CRAHs, pumps, and fans, checking rotation and local safety devices, and filling out OEM startup checklists.
Controls and BAS/EPMS specialists focus on logic, I/O mapping, alarm routing, and trending. Their job is to make sure the monitoring platform shows the actual state of every energized component.
TAB specialists check preliminary airflow and hydronic performance. Cx engineers tie the whole effort together across trades, track deficiency closure, and own the readiness signoff that lets the project move ahead.
Level 3 experience points to safe execution, troubleshooting skill, and strong documentation habits under schedule pressure. The skills that matter most here are solid LOTO discipline, strict MOP adherence, the ability to troubleshoot wiring and configuration issues without slowing the job, and the discipline to produce startup reports that stand up through Level 4 and Level 5 review.
Levels 4 and 5 answer two different questions.
Level 4 asks: Does each started system work the way it should?
Level 5 asks: Can the whole facility stay online when something goes wrong?
That split matters. Level 4 tends to suit engineers who can read control sequences, spot weak logic, and fix system behavior. Level 5 leans more toward people who can handle risk, coordinate operators, and lead final acceptance.
After startup shows equipment can energize safely, Level 4 checks whether each system performs to spec under live operating conditions. A commissioning engineer looks at load transfer, voltage and frequency stability, and event logging - one system at a time - across normal, degraded, and failure modes.
At this stage, everything runs through formal test scripts. Each script lays out preconditions, step-by-step actions, expected results, and pass/fail criteria tied to the Basis of Design and Owner's Project Requirements.
For electrical systems, scripts often cover:
Mechanical scripts check items like chilled water plant lead/lag staging, condenser water pump changeover, CRAC/CRAH fan speed modulation, economizer operation based on outdoor air temperature, and automatic restart after a power interruption. Controls testing focuses on PID loop tuning, interlock behavior, alarm priorities, and trend logging during occupied, unoccupied, and emergency modes.
TAB verifies airflow and temperature, while commissioning engineers review trends and load-bank steps to confirm stable control response before Level 5. If there’s a hotspot, an unstable staging sequence, or a failed failover, it goes into the Level 4 deficiency log and has to be closed before Level 5 starts. Passing Level 4 opens the door to integrated failure testing and owner-readiness checks.
Level 5 is where commissioning moves from system performance to facility survivability. Level 5 Integrated Systems Testing proves the facility can keep critical load online during actual failure scenarios.
The main IST scenario is the black-building test. Utility power is dropped at the point allowed by the test plan, UPS carries the load, generators start within the required window, cooling recovers, and critical load stays online. Other scripted tests cover partial utility loss, ATS failure, generator loss, and UPS module loss, all run with approved steps and a stop plan.
The deliverables at Level 5 are the deepest in the commissioning lifecycle. The IST report records every scenario, participant, result, deviation, and retest. A consolidated deficiency log pulls together open items from Levels 3 through 5 with priority ratings, responsible parties, and resolution dates. The final evidence package - trend logs, test forms, photos, redlined drawings, and sign-off sheets - becomes the formal record for owner turnover, warranty support, and sometimes certification audits.
This is the moment where commissioning proof turns into operational readiness. Senior Cx managers and mission-critical project managers use these artifacts in owner readiness meetings to walk operators through how the facility performed, what risks are still on the table, and what procedures should be used from day one.
For recruiters and candidates, Level 4 and Level 5 often mark the line between systems troubleshooting and crisis leadership. Level 5 work is usually led by senior Cx managers, mission-critical PMs, field managers, and owner reps. It’s also the stage where hiring expectations and pay tend to be highest.
| Feature | Level 4: Functional Performance Testing | Level 5: Integrated Systems Testing |
|---|---|---|
| Primary focus | Individual system performance and sequence validation | Facility resilience and system integration |
| Key scenarios | Failover logic, trend reviews, airflow and temperature performance | Black-building tests, utility loss, UPS ride-through, cooling recovery |
| Load simulation | Load banks at staged increments (25%–100% of design kW) | Load banks on all paths |
| Roles | Cx engineers, controls leads, TAB specialists, Cx managers | Senior Cx managers, mission-critical PMs, field managers, operators, owner reps |
| Deliverable | Functional test scripts, trend reviews, corrective action logs | IST reports, consolidated deficiency logs, final evidence packages |
A candidate’s commissioning level often tells you more than their job title ever will. It shows whether they’ve watched testing happen, done startup work themselves, or led a full system handoff. That makes screening much cleaner: match the role to the commissioning level, not just the title on a resume.
At the early stages, hiring is less about owning a whole system and more about solid verification habits. Levels 1 and 2 are where many people start in commissioning. At this stage, the credentials that matter tend to be hands-on ones: OSHA safety training, NICET certifications, and manufacturer training for equipment like UPSs, chillers, and generators.
Why do those matter? Because they show a candidate can follow test steps closely and spot problems before they turn into costly field issues. Put simply: L1/L2 = acceptance.
By Level 3, you start to see clear specialization. Startup technicians, controls engineers, and TAB specialists are expected to carry out work under schedule pressure, often at night or on weekends. For electrical testing roles, NETA certification can help a candidate stand out. For controls work, vendor-specific BMS or controls training shows deeper skill in controls checkout. L3 = startup readiness.
Once the work shifts from startup into testing, the hiring bar changes too. Now it’s not just about doing the task. It’s about making calls when risk is on the table. Levels 4 and 5 mark the move from technical execution to leadership accountability.
At Level 4, commissioning engineers and discipline leads own test scripts, defect tracking, and system performance validation. The credential mix shifts with that change. Hiring managers at this stage tend to look for BCxP, PE in mechanical or electrical, and working knowledge of NFPA 70 and NFPA 70E. L4 = system performance.
At Level 5, the scope gets broader. These roles involve cross-system coordination, risk control during live failure tests, and owner handoff. That’s the kind of work expected from commissioning managers, mission-critical project managers, and operations transition leads. Here, PMP paired with BCxP or PE is a strong sign that someone is ready. L5 = operational readiness.
| Level | Main Objective | Common Deliverables | Primary Roles | Hiring Signal |
|---|---|---|---|---|
| L1 | Factory acceptance and design verification | FAT reports, equipment data sheets, witness sign-offs | Manufacturer field rep, junior Cx engineer | Familiarity with OEM standards and design conformance |
| L2 | Installation verification and site readiness | SAT checklists, megger test results, installation punch lists | Field engineer, startup technician | Confirms installation quality and early issues |
| L3 | Startup and subsystem readiness | Energized systems, pre-functional forms, point-to-point checklists | Startup technician, controls engineer, TAB specialist | Safe energization, controls checkout, pre-functional discipline |
| L4 | System performance under operating conditions | FPT scripts, issue logs, redlined sequences, corrective action records | Cx engineer, discipline lead, field manager | System-level thinking, test script ownership, defect management |
| L5 | Full-system integration and owner readiness | IST reports, SOP/EOP validation, training records | Cx manager, mission-critical PM, operations lead | Leadership of high-risk IST events and successful handoff to operations |
There’s a clear jump between these tiers. Level 3 roles tend to focus on troubleshooting within a single system. Levels 4 and 5 demand coordination across systems, teams, and test conditions. That gap matters in hiring.
Hiring breaks down when a job description asks for commissioning experience but never says which level it needs.
A startup technician with deep Level 3 experience is not automatically ready to lead Level 5 integrated systems testing. On the flip side, a senior commissioning manager who has spent years working at Levels 4 and 5 may not be the right fit for a role that calls for someone willing to handle point-to-point checks in the field at 2:00 a.m.
iRecruit.co helps employers get specific about the commissioning level a role calls for. On the candidate side, that same clarity helps people present their background around the work they’ve actually led. That distinction - witnessing, executing, or leading - is what experienced commissioning recruiters look for, and it’s often what gets the right people in front of the right roles on mission-critical data center projects.[10][2]
That level-based framing sets up the hiring framework in the conclusion.
When you look at all five levels together, they give hiring teams a practical staffing map. Each one points to a different handoff, a different degree of risk, and a different kind of talent need - from factory and site verification to startup to functional and integrated testing.
The smartest hiring question is simple: which handoff points has this candidate actually led? There’s a big difference between witnessing a FAT and signing off on IST. That gap matters most at the upper levels.
People who have led FPT or IST have dealt with live-load risk, multiple trades, and owner-facing handoff. That kind of experience lines up directly with Cx manager, mission-critical construction manager, and data center startup lead roles.[11][12]
Candidates should show commissioning experience by level, system, and deliverable. That means spelling out readiness, handoff documentation, redundancy validation, and operational resilience. When each role is tied to a specific level - and the systems and deliverables are named clearly - a resume becomes much easier to review than a generic list of duties.
For construction leaders and recruiters, this framework makes it easier to match the right people to each phase, set clear handoffs, and keep commissioning on schedule. Hire to the level, not just the title.
Go beyond job titles. Show what you owned across the commissioning lifecycle.
Employers want to see hands-on work and clear project leadership. They’re not just scanning for a title. They want proof that you did the work, drove it forward, and got it over the line.
Spell out the tasks you handled, such as:
That kind of detail helps hiring teams picture how you work day to day. It also shows where you stepped in, what you led, and how far your scope went.
No. Skipping from Level 3 to Level 5 is not standard practice, and it’s not a good idea.
Commissioning moves through gated phases in order. Each level sets up the next one. If you skip Level 4, you weaken risk control and increase the chance of delays, defects, or operating problems during go-live.
Across data center commissioning levels, the certifications people recognize most are BCxP, CxA, and CBCP.
For more technical, safety-focused work at Levels 3 through 5, OSHA 30 is often required for site safety. That makes sense. Once work moves deeper into live systems, testing, and field coordination, safety stops being a box to check and becomes part of the job itself.
Some specialized roles may also put extra weight on CDCPM, especially when the goal is to show mission-critical project delivery experience. In plain terms, these credentials help show that someone can handle complex system testing, stay on top of documentation, and work through high-stakes project demands without things going off the rails.
