Per-MW pricing, regional variance, and cost drivers for owners scoping hyperscale & AI builds.
Salary benchmarks across the 14 mission-critical disciplines.
My rule for multi-site EHS: no verified controls, no work release. Across hyperscale and gigafactory campuses, I use one shared framework, with named owners and checks for each site’s hazards - from mobilization through handoff.
Here’s what I focus on:
I hire for the hazards each team will face - not titles alone. And I keep one requirement at every milestone: <u>verify the fix in the field</u> before approving the next step. That keeps safety tied to the schedule, not separate from it.
Multi-Site EHS: Verified Controls Before Work Release
Once standards are set, assign staffing and contractor controls based on each phase and its risks.
Plan coverage by workfront, shift, and risk - not site size or a fixed staffing ratio. Turn the standards into site-level staffing, contractor controls, and phase-specific oversight. Review workforce size, contractor count, overlapping activities, travel between work areas, and hazard severity. At hyperscale and gigafactory campuses, account for construction crews working beside commissioning teams. Name a qualified coverage lead and backup for each high-risk activity.
Program and regional leaders should close coverage gaps across sites, while site EHS managers coordinate local oversight. Contractors provide their own supervision and safety coverage. CSP/CHST credentials can help screen candidates, but they don’t prove task-specific competence or replace designated-role requirements.
Before mobilization, review project experience, safety programs, EMR, OSHA history, insurance, and site-specific safety plans. Require named supervisors, qualification records, and site-specific orientation before granting site access. Include reporting deadlines, audit access, corrective-action owners, and stop-work expectations in contractor requirements.
After mobilization, check field practices through daily walks and a weekly sample of pre-task hazard analyses. Verify qualifications, permits, and supervision where the work happens - not just in submitted files. A missing coverage owner or unsigned hold point stops the work. Escalate repeated deficiencies and overdue critical actions. Stop energized work performed without approval or a failed fire watch immediately. Restart only after verifying the correction. Use these checks to decide whether the site can take on the next phase.
Use scenario-based interviews supported by verified project experience. Ask candidates how they would coordinate electrical turnover, challenge an incomplete critical lift plan, separate live testing from construction, investigate a serious event, and escalate unresolved cross-site risks.
Look for NFPA 70E fluency and clear contractor intervention - not credentials alone. Give recruiters each role’s phases, shifts, reporting scope, and required technical skills. These hires must be able to run the controls for energized work, heavy lifts, and live testing.
Use one release matrix across campuses to control work when installation and commissioning overlap. Once contractor readiness is confirmed, shift from people controls to task-release controls. Each work package should name its owner, affected systems, approval authority, and conditions that void approval. Link these hold points to hyperscale and gigafactory delivery schedules, especially where work meets live systems. EHS verifies the control process; designated technical authorities approve the work.
As systems energize, controlling their boundaries becomes the main risk-control priority.
Identify every energy source and require approved isolation before releasing work. Assign switching and isolation duties to qualified, authorized personnel. Hold energization if boundary information or approval is missing.
Before releasing a lift, have the designated lift authority review the load, lift plan, and site conditions. Confirm exclusion zones and other field controls. Reassess the plan whenever weather, load, or site conditions change.
Once commissioning starts, live-system boundaries must govern the schedule.
At the construction-to-testing handoff, keep the energized-area map current and mark turnover boundaries in the field. Reconcile permits daily and before any switch or boundary change. Assign each boundary one named owner to control access and confirm system status.
Hold conflicting work whenever testing could affect unfinished construction or another crew’s isolation. Restart only after the system owner and affected authorities verify the fix and update permits and boundaries.
After work is released, use audit and incident data to decide whether the next phase can stay open. Feed field findings back into coverage, contractor oversight, and look-ahead release decisions. Carry unresolved hazards into the next release gate. Standardize audit evidence across campuses so records are complete for audit and turnover review[2].
Track corrective actions through field-verified closure. Assign each action to the party that controls the hazard, set a clear deadline, and check that the fix works in the field. Hold the next release gate until that verification is complete. When findings repeat, tighten supervision or change the sequence of affected work.
Escalate serious incidents immediately through the program chain. Meet regulatory reporting deadlines separately. Investigate failed controls and the system conditions that contributed to the event, then check whether other campuses have the same weakness. Use repeat findings to adjust contractor oversight at every site.
Use consistent definitions and reporting periods to compare matching phases and scopes, including contractor-level detail. For similar scopes, normalize results by work hours. The goal is to spot recurring control failures - not rank sites by raw incident totals.
Pair injury rates with control checks, environmental obligations, and open corrective actions. Low injury rates alone do not prove readiness.
Use these comparisons to decide which sites can pass the next release gate.
Build gates into design reviews, logistics plans, look-ahead schedules, and commissioning plans. Define the evidence and approvers for each gate. Release work only after required evidence is verified and approvals are complete. Resolve unacceptable risk before release.
Scale the operating framework, not a single site template. Align shared standards with local risks, staffing by phase, contractor accountability, and verified controls for high-risk work. Manage campuses as one program so lessons from one site improve execution at the next.[3]
Once the operating model is in place, readiness checks, fast escalation, and field-verified closure help protect the schedule by identifying gaps early.
Use readiness findings to address the next staffing gap. Match unresolved risks at milestone gates with construction safety leadership for field execution, an EHS manager for commissioning and operations, or specialists for arc-flash, lithium-ion thermal runaway, or hazardous gas risks.[1][2] Hire to the hazard and phase, not the title.
Plan at the program level. Use capital plans and project timelines to forecast staffing and resource needs 12 to 24 months ahead. Set up a central program office to keep safety standards, reporting, and audits consistent.
Rotate commissioning teams across sites as project phases change. This helps maximize coverage without adding permanent overhead. Bring EHS into preconstruction planning and align safety protocols with commissioning milestones to avoid last-minute resource gaps during electrical energization.
Base “go/no-go” decisions on documented, verifiable controls: applicable permits, LOTO, Energized Electrical Work Permits, and isolation verification. Give each corrective action an owner and a deadline, then verify closure in the field - not just on paper.
Use structured investigations to identify issues with training, supervision, schedule pressure, procedures, or trade interfaces. Turn the findings into visible changes supervisors can enforce. Route unresolved items through a single escalation path to program safety leadership before critical commissioning proceeds. [1][2]
Before fieldwork begins, hold a formal safety scope workshop to identify where corporate standards exceed local requirements. Use a standards matrix to map each work package to the applicable local and project-specific codes [1].
During preconstruction, work with local authorities having jurisdiction (AHJs) to ensure site-specific safety plans reflect regional requirements [2]. Add those requirements to site-specific risk registers and permit-to-work systems so teams apply them consistently across campuses [1].
