Per-MW pricing, regional variance, and cost drivers for owners scoping hyperscale & AI builds.
Salary benchmarks across the 14 mission-critical disciplines.
I screen owner-side data center PMs for decisions they owned - not years alone. I ask for redacted records showing what they reviewed, challenged, recommended, or approved. One U.S. posting requires 5+ years and prefers 7–10, but that is one employer’s benchmark, not a universal rule.
My review covers five areas:
The distinction I keep in view: GC PMs manage delivery; owner-side PMs check that delivery meets the owner’s requirements. <u>Installed does not mean ready for acceptance.</u>
Quick Comparison
Look for owner-side PM experience preparing RFPs, comparing GC bids, checking bid exclusions, and setting reporting requirements before award - not just managing subcontracted scope. Candidates should explain how they assessed equipment coordination responsibilities and schedule assumptions, not just price.
Once work starts, the PM moves from bid review to oversight. They review payment applications, RFIs, submittals, quality records, and corrective actions to verify compliance and closure. The GC manages field execution. Ask candidates how they identified deficiencies, assigned responsibility, and confirmed that each issue was resolved.
Design experience should include keeping the Owner’s Project Requirements (OPR) aligned with drawings and specifications. The PM brings together operations, IT, security, engineers, and commissioning stakeholders to check capacity, redundancy, maintenance access, and utility interfaces.
For master-schedule review, look for evidence that candidates tested dependencies across design releases, permits, equipment deliveries, utility work, construction, and commissioning. Progress percentages alone aren’t enough. The PM should check them against factory updates, inspections, and open design issues. The GC sets the sequence; the PM checks whether it supports the planned go-live date.
Independent change assessment starts with scope and contract responsibility, not price. Candidates should trace requests to contract scope, drawings, RFIs, and supporting documents before recommending approval, rejection, or revision within delegated authority. They should separate owner-directed changes from contractor coordination errors and assess the effects on redundancy, commissioning, and future phases. Apply that same independent review standard to capital-budget control and portfolio reporting.
Use GC experience to test ownership of execution, not just coordination support. A GC PM should have owned subcontractor performance, procurement, sequencing, document control, technical coordination, and change management - not simply routed documents. For data center construction, look for subcontractor buyout, scope-gap reviews, labor loading, and recovery schedules across electrical, mechanical, controls, and structural packages. This experience helps an owner-side PM check whether recovery plans hold up against field constraints.
Ask candidates to walk through a procurement log for switchgear, generators, or chillers. They should explain vendor submittals, release dates, factory testing, delivery, storage, and installation readiness - and connect each dependency to the construction schedule. The explanation shouldn’t end with issuing a purchase order. Give owner-furnished equipment interfaces the same attention.[4]
For trade coordination, ask for records that show who resolved a constructability issue, which cross-trade conflicts were caught in submittals and shop drawings before design review, and how the team verified closure. BIM clash logs should show assigned responsibility and verified closure, not just familiarity with the software. An RFI response does not automatically authorize added cost or time.[2][3][5]
GC candidates should also explain their role in installation sequencing, temporary power, equipment setting, and shutdown planning. Look for ownership of trade execution from buyout through installation. In an owner-side role, that knowledge helps a PM question execution risks - not direct the contractor’s means and methods. Ask candidates to identify their authority, required approvals, and documented outcomes in buyout, schedule recovery, and turnover. Those details separate hands-on responsibility from administrative support.
Use that execution record to guide the next screen: who forecasted cost impacts, who owned changes, and who kept reports accurate.
Execution experience matters, but owner-side PMs must also show they can control budgets and report to decision-makers.
Owner-side experience should demonstrate responsibility for the approved total project capital budget, not just construction spending. Verify portfolio responsibility separately.[11] Candidates should reconcile construction contracts with owner-held costs, including design, permitting, commissioning, owner-furnished equipment, allowances, and contingency. Make sure costs already in the GC contract aren’t counted twice.
Budget ownership comes into focus when a change request affects contingency, funding, or executive approval.
Ask for a redacted change assessment and written recommendation that addresses entitlement, cost impact, schedule impact, and funding source.[6] Identify who prepared, reviewed, recommended, and approved the change. Contingency analysis does not prove funding authority.[9][10]
A useful forecast includes the original budget, approved changes, commitments, actuals, accruals, pending exposure, cost to complete, forecast at completion, remaining contingency, and cash-flow needs.[7] Ask what caused the variance and what action followed - not just whether the report balanced. Pending changes should stay visible as exposure while awaiting approval.
These controls should carry through from project-level reports to portfolio reporting.
For roles spanning buildings, campuses, phases, or markets, request a redacted monthly or quarterly executive dashboard. It should use consistent definitions and link utility energization, long-lead equipment, commissioning readiness, and planned vs. installed MW to budget, schedule, risk, cash flow, and capacity decisions.[8] This helps show whether the candidate can turn project data into executive action.
Ask which funding or sequencing decision the report supported. Protect confidentiality by removing customer names, locations, proprietary rates, and sensitive values. Keep the reporting structure, approval levels, and the candidate’s contribution visible. A single-building report does not prove portfolio experience.
Data Center Commissioning: Testing to Owner Acceptance
After budget control and reporting, the final check is whether the project is ready for acceptance and turnover. GCs execute turnover; owner-side PMs verify acceptance evidence and recommend approval within delegated authority. For data center construction roles, look for proof that the candidate coordinated acceptance criteria with the GC, commissioning provider, designers, vendors, and operations team.[12][13]
This division of responsibility matters most during commissioning, when testing shows whether the project is ready for acceptance.
Commissioning follows several stages: factory acceptance testing (FAT) before shipment; site acceptance testing (SAT) after delivery and installation; pre-functional checks; functional performance testing; and integrated systems testing (IST).[12][13][14] Functional testing checks individual systems. IST checks how systems work together across power, cooling, controls, and other critical systems under normal and failure conditions.
Ask for approved test scripts, FAT and SAT reports, pre-functional and functional checklists, startup records, and a test register listing criteria, witnesses, results, exceptions, and retests.
The owner-side PM coordinates the review schedule, confirms responsibilities, and aligns testing with contractual acceptance criteria. They also ensure operations personnel witness relevant demonstrations and escalate unresolved issues. Commissioning providers plan, witness, evaluate, and document testing; the owner retains approval authority.[13][1]
Substantial completion, final completion, owner use, and operations acceptance are separate milestones. Their definitions, sequence, and effects depend on the prime contract, specifications, lender requirements, insurance provisions, permits, and applicable regulations. Occupancy or use does not automatically mean final acceptance.
Request milestone checklists, certificates or notices of substantial completion, open-item and exception logs, and permit status. Written acceptance recommendations should identify unresolved conditions and the authorized approver for each milestone.
Critical deficiencies affecting safety, reliability, code compliance, capacity, or the Owner’s Project Requirements should normally block the relevant milestone unless the owner formally approves an exception. Each issue should include an identifier, location or system reference, description, severity, responsible party, target date, corrective action, retest requirement, and closure evidence. Assign a different identifier to each issue so it can be tracked without confusion.
The owner-side PM verifies closure and recommends action; formal approval rests with the authority named in the contract. Building officials control jurisdictional approvals, licensed professionals provide required design certifications, and commissioning authorities or qualified specialists perform or validate technical testing within their scope.[1][13][14]
Request a turnover matrix tied to acceptance requirements. It should cover record drawings, operation and maintenance manuals, equipment schedules, sequences of operation, controls documentation, test and balance reports, commissioning and IST reports, warranties, spare-parts lists, permit and inspection records, training records, emergency procedures, preventive-maintenance requirements, and signed handover approvals.
The matrix should also identify missing or rejected submissions, revision status, reviewers, witness signatures, and outstanding actions.
Owner-side PMs verify system-specific training and usable records before recommending handover. Ask candidates to show the readiness evidence behind their recommendation, along with approval from the designated operations authority - not simply the PM.[12][15]
For owner-side hiring, screen for decision authority, not job title. In data center construction, verify ground-up scope, MW capacity, and the candidate’s responsibilities. Neither background is better; the evidence needs to match the role.
Apply the same standard to oversight, cost control, reporting, and acceptance.
Ask for redacted proof of decisions, not just general project exposure. Review schedules and forecasts for critical-path and float analysis in P6 or comparable schedule controls. Check contract notice requirements and forecast assumptions. Ask candidates to explain N+1 and 2N redundancy, their commissioning decisions, and what they were personally accountable for.
Experience that doesn't show decisions on scope, cost, reporting, and acceptance doesn't match owner-side PM work.
To move from a general contractor (GC) PM role to owner-side work, shift the focus from field execution to governance, portfolio oversight, and risk management. Show how your decisions protected the owner’s budget, schedule, and quality goals.
In interviews, back up your experience with specific results: how you managed contingency funds, resolved critical path delays, and handled cost or design changes. Highlight your work in preconstruction planning, executive reporting, stakeholder coordination, and formal project controls, along with your experience with complex MEP systems and commissioning readiness.
Show results, not proprietary documents. Use nonconfidential project summaries that include the facility type, IT capacity in megawatts, total project value in U.S. dollars, and your scope of responsibility. Describe the decisions you could make, the systems you used to track progress, and the outcomes.
Compare the starting contingency with the amount used. Explain how you handled variances or brought schedules back on track. Leave out confidential contract terms, security-sensitive details, and customer-specific data.
Do not accept work with unresolved defects. Unsafe conditions or failed redundancy must stop turnover. A trade’s report that a fix is complete does not count as verified closure. Log failures in a controlled deficiency register, with an owner, due date, corrective action, and retest requirement for each entry.
The designated technical reviewer must verify test completion before formal acceptance. When deadlines put pressure on the team, safety, quality, and contractual requirements come first - not meeting a date without verification.
