Cost guidesProject-level planning
/ 2026 estimate planning

Data-center construction cost guide: how to build a comparable estimate in 2026.

A practical guide for preconstruction buyers, general contractors, and trade contributors: organize the estimate by parent discipline, carry a canonical WBS code and unit basis, and separate observed quotes from gated aggregates.

Evidence note: the numeric examples in this guide are observed values from the existing seeded anonymized quote records. They are not market benchmarks, forecasts, or a claim about a project total.

01 / Estimate architecture

Start with the project structure, then price the line items.

A useful early estimate is a controlled map from project scope to comparable lines. It should answer what is being bought, who owns each boundary, which unit measures it, and what evidence supports the current number.

  1. 1

    Define the estimate basis

    Record the project basis that changes scope: electrical architecture, redundancy intent, cooling approach, site and building-shell assumptions, delivery window, and owner-furnished equipment. Keep assumptions visible instead of burying them in a blended total.

  2. 2

    Organize by parent discipline

    Use the catalog taxonomy as the project spine. The current repository covers the parent disciplines below; each is a place to identify scope, quantity, adjacent-trade boundaries, and a quote owner.

  3. 3

    Choose the canonical WBS line

    Select the narrowest available code that describes the purchased scope. A line such as UPS-02.N+1.MOD is not interchangeable with a frame, battery, or bypass line; their units and exclusions differ.

  4. 4

    Carry the same basis into trade input

    Ask each contributor for the WBS code, unit basis, scope narrative, unit cost, region, lead-time note, and exclusions. Like-for-like comparison comes before aggregation.

The repository parent disciplines

  • Electrical power
  • Mechanical and cooling
  • White space and fit-out
  • Modular and containerized infrastructure
  • Fire and life safety
  • Controls, building management, communications, security, and low voltage
  • Civil, site, structural, and building shell
  • Plumbing, fuel, and support infrastructure
  • Commissioning and specialty construction services

Browse the full taxonomy in the WBS catalog or use the WBS × CSI crosswalk when a procurement package needs division context.

02 / Scope normalization

Map a WBS code to a quote without losing the boundary.

The WBS code is the comparison key, but the scope note is the guardrail. Read the catalog's included and excluded work before comparing two submissions or combining them into a package estimate.

Example: a BSW-07.PLUG.1600 submission is per LF and the catalog includes the straight length, hangers, and one joint per 10 ft. Tap-off boxes, elbows, and the source feeder are excluded. A quote that rolls those items into the same number is not comparable until the scope is split or the inclusions are explicitly reconciled.

03 / What moves the number

Treat drivers as scope questions, not unsupported percentages.

The catalog and contribution form support useful questions about cost and delivery. They do not, by themselves, prove a universal market premium. Ask for the project-specific input and preserve it with the quote.

Configuration

Voltage, equipment form, redundancy, and thermal-density choices determine which code and unit basis applies.

Quantity and geometry

A per-LF, per-kW, per-kVA, per-RT, per-cfm, or per-each line needs a stated quantity and a clear measurement basis.

Trade boundaries

Adjacent work such as feeder cable, piping, source equipment, rooms, controls integration, or structural support may be excluded by the selected line.

Delivery and commissioning

Capture lead-time assumptions, testing, checkout, and commissioning notes in the submission instead of folding an unpriced allowance into unit cost.

04 / Evidence discipline

What the current evidence can—and cannot—say.

The current public corpus contains catalog definitions, seeded anonymized quote records, and benchmark pages whose aggregates are gated by contributor coverage. The examples below are useful for understanding the data shape, not for declaring a market rate.

Observed seeded quote

MVS-01.SWBD.MV

15kV MV switchgear lineup

287,400 / ea

15kV MV switchgear lineup, 6-section, Arc-resistant IEC 62271-200 · us-east

Observed seeded quote

UPS-02.N+1.MOD

Modular UPS module (N+1)

2,180 / kW

Modular UPS 50kW frame, N+1 redundant, lithium-ready · eu-west

Observed seeded quote

GEN-03.MWDIESEL

2–5MW diesel genset

725 / kW

3MW Tier-IV diesel genset, EPA Tier-4 Final, SCR-equipped · apac-ne

Observed seeded quote

CRC-05.CRAC.30

30kW perimeter CRAC

4,650 / RT

30kW perimeter CRAC, downflow, EC fans, R-454B refrigerant · eu-north

Observed seeded quote

BSW-07.PLUG.1600

1600A plug-in busway

612 / LF

1600A plug-in busway, 100% neutral, IP54 feeder section · apac-se

Observed seeded quote

MVS-04.FEEDER.MV

15kV MV feeder cable

112 / LF

15kV MV feeder cable, single-core 630mm² Cu, XLPE · us-west

Benchmark gate

The benchmark methodology uses a gate of 3 distinct contributors for a regional aggregate. Until a code and region clear that gate, describe the aggregate as gated or unavailable; use the catalog definition and any clearly labeled observed quote instead.

Cost database vs. benchmark

The cost database is a browseable quote feed. A benchmark is a governed aggregate by code and region. Do not turn the former into a range, median, or project total, and do not repeat a scope guide's pricing claim without following its cited WBS line.

Open the cost database

05 / A repeatable handoff

Move from early estimate to comparable trade input.

  1. 01Create the early estimate by parent discipline and make the project basis visible.
  2. 02Select one canonical WBS line for each purchasable scope and record its unit basis.
  3. 03Use the catalog scope note to write inclusions, exclusions, quantity, region, and delivery assumptions into the request.
  4. 04Compare only like-for-like submissions. Split bundled scope when it crosses a WBS boundary.
  5. 05Submit the normalized quote through the existing contribution flow. A scope CTA such as /submit?code=BSW-07.PLUG.1600 carries the validated WBS context into the form.
  6. 06After review, use the WBS detail and benchmark state to understand what is available; do not infer an aggregate while the contributor gate is unmet.

Ready to contribute a real scope?

The existing /submit flow handles signed-out authentication, preserves the WBS context, validates the catalog unit, and sends the quote into the current review workflow.

06 / Scope drilldowns

Use the scope guides for the next level of detail.

This overview explains the project-level method. These existing guides carry the scope-specific definitions and link back to the same WBS and contribution ecosystem.

Electrical distribution and switchgear

MV/LV lineups, breakers, relays, and their scope boundaries.

Read the scope guide

Generators and fuel support

Genset, exhaust, enclosure, day-tank, and paralleling scope.

Read the scope guide

Return to the full cost-guide index for the complete corpus.