What is the difference between this checklist and the general commercial quote assumptions checklist?

The general assumptions checklist covers scope definition, exclusions, site conditions, procurement, client responsibilities, and commercial terms for any commercial job. This checklist is data-center-specific: it targets the assumptions that are unique to or amplified by mission-critical facility work — redundancy configurations, cooling architecture, rack density, OFCI coordination, phased commissioning, and the commercial structures that protect margin when those assumptions shift. Use both on data center work.

DATA CENTER QUOTE ASSUMPTIONS

Data Center Quote Assumptions Checklist

Q: What is the most commonly missed assumption in data center quotes?

Rack density. Many data center quotes are priced at a stated kW-per-rack assumption — often 8 to 12 kW — that gets revised upward to 40 to 80 kW per rack when the owner signs a tenant with GPU-intensive AI workloads. The cooling and electrical infrastructure designed for the original density cannot serve the revised load without fundamentally different piping, pumping, cable sizing, and power distribution. The repricing is not incremental. It is structural.

Q: How does OFCI scope change the assumptions a contractor needs to document?

OFCI — owner-furnished, contractor-installed — equipment creates a scope boundary that is easy to get wrong. The contractor must document what they are responsible for receiving, storing, protecting, rigging, installing, and commissioning — and what the owner is responsible for delivering on time, in spec, and in install-ready condition. If the OFCI equipment arrives late, incomplete, or requiring field modification, the documented assumption gives the contractor a defensible basis for a change order.

Margin loss on data center work does not usually come from bad estimating. It comes from assumptions that were never written down — redundancy tier, rack density, utility energization date, cooling architecture, OFCI scope boundaries, commissioning sequence, and a dozen other inputs that are still unresolved when the quote goes out. This checklist forces those assumptions into the open before pricing is locked.

Answer first

The data center quote assumptions checklist is a pre-submission review covering twelve groups of pricing inputs — redundancy tier, rack density, cooling architecture, utility energization, OFCI scope boundaries, commissioning sequences, and commercial terms — that are frequently unresolved when data center quotes are submitted. Each unresolved input is handled one of three ways: named as a stated assumption inside the quote, converted to an exclusion, or priced as a separate allowance that adjusts when the facts are confirmed. The checklist is used by estimators and preconstruction managers pricing electrical, mechanical, plumbing, fire protection, or low-voltage scope on data center projects — new construction, expansion, or retrofit.

Who this checklist is for

Estimators, preconstruction managers, and commercial contractors pricing electrical, mechanical, plumbing, fire protection, or low-voltage scope on data center projects — new construction, expansion, or retrofit. If the project involves redundant power distribution, high-density cooling, owner-furnished equipment, phased commissioning, or mission-critical turnover requirements, this checklist applies before the quote is submitted.

Key terms

Redundancy tier

Backup configuration for power and cooling — N, N+1, 2N, or 2(N+1). Higher redundancy means more equipment, conduit, piping, and controls.

Rack density

Power load per server rack in kW. Drives cooling sizing, electrical distribution, and floor layout.

Cooling architecture

Air-cooled, water-cooled, direct liquid, or rear-door heat exchangers. Determines chiller, piping, pump, and heat exchanger scope.

Utility power

Service capacity, energization date, voltage, and transformer ownership. Frequently unresolved at bid date on data center projects.

OFCI / OFE

Owner-furnished, contractor-installed equipment. Creates a scope boundary requiring documentation of receiving, rigging, installation, and commissioning responsibilities.

Commissioning

Multi-stage testing: functional performance, integrated systems testing, Level 5 commissioning. More extensive than standard commercial work.

Exclusions

Scope removed from the quote when the cost of being wrong is high and the probability of change is also high. Not included at any price.

Change triggers

Documented conditions that activate a price adjustment — e.g., rack density exceeding the assumed value by more than 20 percent.

Data center quote assumptions

The unresolved inputs a data center price depends on, written into the quote so the price is defensible when inputs change.

Published April 2026 · Last reviewed April 2026 · Written by the Quoteloc team — construction pricing specialists

Data center revision and change-order risk General assumptions checklist Pricing volatility hub

Why data center quotes are assumption-heavy

On a standard office fitout, the spec is usually locked before bids are collected. On a data center, the spec is often still being engineered while bids are due. The utility service agreement may not be signed. The cooling load calculation may still be in progress. The owner may be procuring switchgear, generators, or UPS units under separate contracts that define the scope boundary differently than you assumed. Rack density can shift from 12 kW to 50 kW per rack between bid date and award.

Inputs arrive late

Utility capacity confirmation, cooling load calculations, equipment vendor selection, and OFCI delivery schedules are frequently unresolved at bid date. Each one can reprime a significant portion of the electrical or mechanical scope after the quote is committed.

Inputs change after award

The owner signs a tenant with higher compute requirements. The utility delays energization. OFCI equipment arrives with different terminal configurations than the design specified. Each change is an assumption failure that reprices scope already under contract.

Cost of being wrong is high

On a $1.24 million electrical bid for a 30 MW data center, $90,200 in unrecovered costs from four assumption failures consumed the entire contingency and eroded margin by 34%. Three of the four failures were assumption failures, not estimation failures. The estimating was correct. The inputs changed.

The discipline this demands is assumption governance: explicitly identifying every input your price depends on, stating what happens when each one changes, and refusing to price certainty that does not exist. This checklist is the mechanism. For the full analysis of why data center projects carry higher revision and change-order risk, see the data center revision and change-order risk guide.

The checklist: twelve assumption groups to run before the quote goes out

Work through each group. Flag any item that is unresolved. Unresolved items must be handled one of three ways: named as a documented assumption inside the quote, converted to an exclusion, or priced as an allowance that adjusts when the fact is confirmed. Do not leave an unresolved input as a silent default.

1. Basis of design

What is the design status, and what has the engineer committed to?

☐Design stage. Are the drawings issued for construction, or are you pricing from design-development or schematic documents that will change? State the drawing revision and issue date the quote is based on.
☐Engineer of record. Is the engineer of record identified, and have they reviewed the design for the specific equipment and configurations you are pricing? Or are you pricing a performance specification that leaves the design burden on the contractor?
☐Redundancy tier. Is the basis of design N, N+1, 2N, or 2(N+1)? Redundancy determines how much equipment, conduit, cable, piping, and controls you are pricing. A 2N electrical distribution design carries roughly twice the material and labor of an N design for the same load.
☐Tier classification. Is the project targeting Uptime Institute Tier II, III, or IV? Tier classification affects redundancy requirements, commissioning depth, and the cost of integrated systems testing. State the assumed tier.

2. Scope boundary

Where does your scope end and someone else's begin?

☐Trade division boundaries. Are the division boundaries between electrical, mechanical, plumbing, fire protection, and low-voltage clearly defined? Who owns the fire pump feed? Who owns the chiller electrical connection? Who owns the BMS integration?
☐Utility point of demarcation. Where does the utility's scope end and the contractor's begin? Transformer pad, primary conduit, metering, and service entrance switchgear ownership must be defined.
☐General contractor responsibilities. What does the GC provide versus what you assume is in place? Structural openings, shafts, fire-stopping, access flooring, ceiling grid, temporary power, and hoisting are frequent scope-gap areas.
☐Owner direct-contract scope. Is the owner contracting any trades directly — technology, security, fire alarm, commissioning agent — that interact with your scope? Document the interface points.

3. Capacity, density, and phasing

What load is the design built to serve, and in how many phases?

☐Total facility load in MW. What is the total power capacity, and is the contractor pricing the full build-out or an initial phase? State the assumed load.
☐Rack density in kW per rack. What is the assumed kW per rack? This single assumption drives cooling system sizing, electrical distribution design, cable tray loading, and floor tile layout. If the owner signs a tenant with GPU-intensive workloads and the density goes from 12 kW to 50 kW per rack, the cooling and electrical infrastructure designed for the original density cannot serve the revised load.
☐Phasing plan. Is the project single-phase or multi-phase build-out? Which phases are you pricing? State the assumed phasing because multi-phase work changes mobilization costs, equipment sizing, and schedule assumptions.
☐Future expansion provisions. Does the quote include conduit stub-outs, spare breaker positions, pipe capped for future, or structural provisions for future equipment? Separate these from base scope so the client can accept or remove them.

4. Electrical assumptions

Power distribution, utility coordination, and equipment-specific inputs

☐Utility service capacity and energization date. Is the utility service agreement signed? Is the available capacity confirmed? Is the energization date committed? Each of these inputs affects switchgear sizing, conduit routing, generator sizing, and temporary power planning. If any are unresolved, flag them.
☐Service voltage and transformer configuration. What is the service voltage? Who owns the transformer? Is it pad-mounted, indoor, or unit substation? State the configuration.
☐Switchgear and distribution equipment. Is the switchgear sole-sourced or open to multiple manufacturers? What is the assumed lead time? Is the pricing from a locked supplier quotation or catalog? For a structured approach to long-lead risk, use the long-lead equipment risk planner.
☐Generator and UPS assumptions. Are generators and UPS units owner-furnished or contractor-furnished? If OFCI, what is the contractor's scope for receiving, rigging, installing, and commissioning? What is the assumed fuel system scope?
☐Cable and conduit pricing basis. Copper and aluminum feeder pricing is volatile. State the pricing date and the supplier hold period. If the hold period is shorter than the procurement window, document the repricing trigger. Use the material escalation impact calculator to size the exposure.
☐Grounding and bonding requirements. Does the specification require a specialized grounding grid, copper bus bar in the raised floor, or bonding to building steel at specific intervals? Data center grounding is more extensive than standard commercial work.

5. Mechanical and cooling assumptions

Cooling architecture, heat rejection, piping, and equipment-specific inputs

☐Cooling architecture. Is the cooling air-cooled, water-cooled, direct liquid, rear-door heat exchangers, or a hybrid? State the assumed architecture because it determines chiller, cooling tower, piping, pump, and heat exchanger scope.
☐Chiller and cooling tower sizing basis. What is the assumed heat load the cooling system is designed to reject? Is the load calculation finalized or still in progress? If the cooling load changes after the quote is submitted, the mechanical scope changes in kind, not just in quantity.
☐Refrigerant type and availability. What refrigerant does the specification require? Is it available at current pricing? Some low-GWP refrigerants have limited supply and volatile pricing.
☐Piping material and routing. What is the assumed piping material — carbon steel, copper, stainless, or pre-insulated? Is the routing confirmed or assumed? Data center piping runs can be extensive and routing changes are expensive in occupied spaces.
☐Redundancy in cooling. Is the cooling system N, N+1, or 2N? Redundant chillers, pumps, and piping runs multiply material and labor. State the assumed redundancy level.

6. Controls and monitoring assumptions

BMS integration, DCIM, and controls scope boundaries

☐BMS platform. Is the BMS platform specified — manufacturer and protocol? Or is it a performance specification that leaves the selection to the contractor? Proprietary platforms may require a certified integrator at a significant premium over standard BMS work.
☐DCIM integration. Does the scope include integration with a Data Center Infrastructure Management system? Who provides the DCIM software? Who handles the integration between the BMS and DCIM?
☐Monitoring points. How many monitoring points are included — power meters, temperature sensors, humidity sensors, leak detection, airflow monitors? The count determines labor, conduit, cable, and programming scope.
☐Controls integration responsibility. Who integrates the fire alarm system with the controls for HVAC shutdown, smoke damper operation, and generator start? The interface between fire alarm and BMS is a frequent scope-gap area.

7. Network, security, and low-voltage assumptions

Structured cabling, security, and fire alarm scope boundaries

☐Structured cabling scope. Is structured cabling — copper and fiber for tenant connectivity — in your scope or the owner's? If in your scope, what is the assumed cable count per rack, pathway, and termination standard?
☐Security systems. Does your scope include access control, CCTV, or intrusion detection? Are the head-end and field devices owner-furnished? Document the boundary.
☐Fire alarm and notification. Is the fire alarm system in your scope or a separate contract? What is the assumed integration between fire alarm, HVAC shutdown, fire suppression release, and elevator recall?

8. OFCI, OFE, and prefabrication assumptions

Owner-furnished equipment creates scope boundaries that are easy to get wrong

☐OFCI equipment list. List every piece of owner-furnished equipment — generators, UPS units, PDUs, busway, switchgear, chillers, cooling towers, CRAC units, server cabinets. Each item needs its own scope boundary.
☐Contractor responsibility per OFCI item. For each piece of owner-furnished equipment, state what you are responsible for: receiving, unloading, storage, protection, rigging, setting in place, piping or wiring connections, testing, and commissioning.
☐Late or out-of-spec delivery. State explicitly: if OFCI equipment arrives late, incomplete, or different from the design specification, the contractor is entitled to a change order for resulting delay, re-sequencing, and rework. Without this, the contractor absorbs the cost.
☐Prefabricated assemblies. Are any scope sections assumed to be prefabricated or modular — electrical skids, piping racks, pump packages? Prefabrication changes labor assumptions, shipping logistics, and field connection scope.

9. Site logistics and access assumptions

How does material and equipment get to the installation point?

☐Equipment delivery and rigging. Can switchgear, generators, chillers, and cooling towers be delivered and rigged to the installation point without crane work, structural modification, or wall removal? State the assumed delivery route and rigging method.
☐Staging and storage. Where is on-site staging and storage? Is laydown area available? If equipment must be stored off-site, who pays for storage and transport?
☐Security and access protocols. Does the site require background checks, badging, escort requirements, or restricted work hours? Mission-critical facilities often have security requirements that constrain mobilization and labor scheduling.
☐Concurrent construction zones. Is part of the facility live or occupied during your scope? Working adjacent to active data halls or live power infrastructure constrains scheduling, noise, dust, and access — and increases labor hours.

10. Testing, commissioning, and acceptance assumptions

Data center commissioning is a multi-stage process, not a walk-through

☐Commissioning scope definition. Is the commissioning specification finalized? Does it include functional performance testing, integrated systems testing, and Level 5 commissioning? If the specification is not final, quote commissioning as an allowance that adjusts when the protocol is issued.
☐Integrated systems testing (IST). Does the commissioning scope include IST across the full power chain — utility feed, generator, UPS, transfer switch, PDU, and rack-level distribution — under load? IST is labor-intensive and schedule-constrained.
☐Third-party witnessing and testing labs. Does the specification require factory witness testing, third-party testing lab involvement, or commissioning agent observation during startup? Each adds scheduling constraints and cost.
☐IST rework provision. What happens when a system fails integrated testing? The rework cascades across trades, delays turnover, and creates schedule and cost exposure that standard commissioning allowances do not cover. Include a provision for IST rework.
☐Acceptance criteria. What constitutes acceptance? Is substantial completion tied to successful IST? Is there a performance period after IST? Define what acceptance means so the scope of commissioning work has a clear endpoint.

11. Commercial assumptions

Quote structure, validity, escalation, and payment terms

☐Quote validity. State the validity period. On data center work with long-lead equipment and volatile material pricing, 14 to 21 days is more realistic than 30 days.
☐Escalation mechanism. Does the quote include an escalation clause for long-lead equipment and volatile materials? Name the items, state the pricing date, and define the adjustment mechanism. For guidance on when escalation fits, see escalation clause versus absorbing risk.
☐Fixed vs. adjustable structure. Is the entire quote at a fixed price, or do you need a mixed structure — fixed on stable scope, adjustable or allowance-based on unresolved scope? When three or more major assumptions are unresolved at bid date, a single fixed price commits the contractor to absorbing cost changes on undefined scope. See when to use fixed versus adjustable pricing.
☐Contingency sizing. Is contingency sized to the actual risk profile of the unresolved assumptions — or is it a flat percentage? A flat 5% contingency on a job where the utility date, cooling load, and OFCI boundaries are all unresolved is insufficient. Size the buffer to the number and severity of unresolved inputs. Use the construction contingency calculator to model the exposure.
☐Liquidated damages and performance guarantees. Does the contract include liquidated damages, schedule penalties, or performance guarantees tied to the power or cooling system? The commercial exposure of a delayed generator startup on a data center is not the same as a delayed panel swap in a tenant space.
☐Payment terms and retainage. State the payment terms, retainage percentage, and draw schedule. Long-duration data center projects with phased turnover need milestone-based payment structures that align with the turnover sequence.

12. Handover assumptions

What gets delivered, when, and in what condition?

☐Phased turnover dates. Are phased turnover dates confirmed? Does the schedule assume sequential or concurrent turnover of data halls? Phased turnover with part of the facility live while another part is still under construction constrains commissioning, access, and noise.
☐As-built documentation scope. What as-built documentation is required — red-line drawings, O&M manuals, equipment warranties, commissioning reports, testing certificates? Data center handover documentation is more extensive than standard commercial work.
☐Training requirements. Does the scope include owner training on systems, controls, and emergency procedures? How many sessions, how many attendees, and what duration? Training is often in the spec but not in the budget.
☐Warranty period and callback obligations. What is the warranty period? Does it start at substantial completion or final acceptance? Are callback commitments or post-occupancy support required? Extended warranty obligations on generators, UPS, and cooling systems extend cost exposure beyond project close-out.

Commonly missed assumptions on data center quotes

These are the assumptions that get skipped most often — and the ones that cause the most margin damage when they prove wrong — see where margin actually leaks during data center design revisions. Each one has produced real cost on real data center projects.

Assumption	What happens when it is wrong	How to document it
Rack density at 12 kW per rack	Owner signs tenant with AI compute at 50 kW per rack. Cooling and electrical infrastructure cannot serve the load without redesign. Repricing is structural — 30 to 50 percent of mechanical and electrical scope.	State the assumed kW per rack in the quote. Add a clause: if density exceeds the assumed value by more than 20 percent, the quote is subject to revision.
Utility energization by a specific date	Utility delays energization by 11 weeks. Schedule compresses, overtime required, generator commissioning re-sequenced. A $1.24 million bid absorbed $37,400 in overtime and re-sequencing costs from this single failure.	State the assumed energization date. Exclude costs caused by utility delay. Or quote temporary power as a separate line with its own assumptions.
OFCI equipment matches the design specification	Owner buys generators from a different vendor. Terminal connections, mounting points, and vibration isolation do not match the installation plan. 86 additional labor hours and $11,200 in modified cable and connectors.	Create a separate OFCI section. State that contractor installation assumes equipment matches the design spec. If it does not, a change order is issued for rework.
Commissioning scope is standard	The commissioning specification requires Level 5 integrated systems testing across power, cooling, fire suppression, and BMS — under load — with third-party witnessing. This was not budgeted. The commissioning cost on a $1.24 million bid ran $28,000 more than the allowance.	Quote commissioning as a separate scope section with its own line items. If the commissioning spec is not final, use an allowance that adjusts when the protocol is issued.
Labor availability is standard	Qualified electricians in the project region are booked out 14 weeks. The contractor pays overtime at 1.5x or brings in travel crews with per diem. Labor cost increases 20 to 35 percent from the quote basis.	State the labor assumption: what craft level, what geography, what availability window. If the job requires certified medium-voltage terminators or refrigerant-handling technicians, name the requirement and exclude scope that depends on unavailable resources.
BMS integration is standard commercial	The specification requires integration with a proprietary platform that needs a certified subcontractor at a 40% premium. The BMS line priced at $37,800 from historical averages actually costs $53,100. The $15,300 gap was not caught by the margin check because the aggregate looked reasonable.	Identify the BMS platform and integration requirements. If the platform is proprietary, state the assumed integration cost and exclude scope that exceeds it without a change order.

When to convert an assumption into an exclusion or change trigger

Not every assumption belongs in the quote as a named condition. Some are too uncertain to price around — they need to be excluded. Others are defensible enough to state as an assumption but need a documented trigger so the cost of being wrong flows to the right party. Here is the decision framework.

Keep as a named assumption when:

→The input is likely to be confirmed before contract execution — the risk window is short.
→The cost of the assumption being wrong is manageable within contingency.
→You can state the assumption in specific, measurable terms — a date, a load, a model number, a capacity.

Example: "Quote assumes utility energization by August 15, 2026, per the utility service agreement dated March 28, 2026."

Convert to an exclusion when:

→The input is unlikely to be confirmed before contract execution and the risk window extends through procurement.
→The cost of the assumption being wrong is high and the probability of it changing is also high.
→You cannot price the risk accurately because the range of possible outcomes is too wide.

Example: "Quote excludes costs associated with utility energization delays. If energization is delayed beyond the assumed date, the contractor will submit a change order for resulting overtime, remobilization, and schedule re-sequencing."

Convert to an allowance when:

→The scope is real and will be executed, but the final parameters are not yet known.
→You can establish a reasonable baseline cost but need the ability to adjust when the facts are confirmed.
→The client needs a budget number for planning but accepts that the final cost adjusts.

Example: "UPS systems are quoted as an allowance of $148,000 based on vendor preliminary pricing. Final cost adjusts when the owner confirms the UPS vendor, model, and configuration. For the decision framework on allowances versus contingencies, see allowance versus contingency in contractor quotes."

The decision matters because assumptions, exclusions, and allowances carry different commercial weight. An assumption says "the price holds if this is true." An exclusion says "this is not included no matter what." An allowance says "here is a budget; the actual cost adjusts." Using the wrong mechanism — for example, assuming a utility date that is unlikely to hold instead of excluding the delay risk — transfers cost to your margin. Use the exclusions and assumptions builder to draft the right language for each item.

Worked example: what the checklist catches on a 30 MW data center electrical bid

A mid-size electrical contractor prices the power distribution scope for a 30 MW data center. The total bid is $1.24 million. Here is what happens when the checklist is not run — and what it would have caught.

What went wrong

Utility service delayed 11 weeks

The energization date was assumed but not documented. When the utility delayed, the contractor absorbed $37,400 in overtime and re-sequencing costs.

OFCI generators arrived with modified terminal configurations

The owner changed vendors. Terminal connections did not match the installation plan. 86 additional labor hours and $11,200 in modified cable and connectors.

Rack density increased from 12 kW to 35 kW per rack

The PDU and rack power distribution scope repriced at $41,600 in additional material plus 62 additional labor hours. The density assumption was not stated or bounded.

Total unrecovered cost: $90,200 on a $1.24 million bid

$48,200 contingency consumed. $42,000 direct margin erosion. Three of the four cost events were assumption failures — the contractor estimated correctly based on available information, then watched the information change after commitment.

What the checklist would have forced

→Group 4 (Electrical): Utility energization date flagged as unresolved. Converted to exclusion or allowance. The $37,400 does not come from margin.
→Group 8 (OFCI): OFCI scope boundary documented. When generators arrive different from spec, the change order is already supported by documented terms.
→Group 3 (Capacity): Rack density assumption stated at 12 kW with a revision trigger at 20 percent variance. The $41,600 repricing is caught before commitment, not absorbed after.
→Group 11 (Commercial): Contingency sized to actual risk profile instead of a flat 5%. Escalation clause added for copper-heavy cable scope with 22% material concentration.

Frequently asked questions

Why do data center quotes need a different assumptions checklist than standard commercial work?

Because data center work carries simultaneous uncertainty across power capacity, cooling architecture, rack density, OFCI scope boundaries, commissioning sequences, and phased turnover. Standard commercial jobs rarely have more than one or two unresolved inputs at bid date. Data centers routinely have five or more. For the full analysis, see the data center revision and change-order risk guide.

What is the most commonly missed assumption in data center quotes?

Rack density. Many quotes are priced at 8 to 12 kW per rack. When the owner signs a tenant with GPU-intensive AI workloads, density moves to 40 to 80 kW per rack. The cooling and electrical infrastructure designed for the original density cannot serve the revised load. The repricing is structural, not incremental.

Should every data center assumption be written into the quote document?

Every assumption that affects price, schedule, or scope should appear in the quote the client receives and accepts. Assumptions in a separate file that the client never saw are weaker than assumptions printed directly below the pricing they support. Specific, measurable assumptions are billable. Vague assumptions are arguable.

How does OFCI scope change the assumptions a contractor needs to document?

OFCI equipment creates a scope boundary that is easy to get wrong. Document what you are responsible for — receiving, storing, protecting, rigging, installing, and commissioning — and what the owner must deliver on time, in spec, and in install-ready condition. If OFCI equipment arrives late or different from spec, the documented assumption gives you a defensible change order basis.

When should a data center assumption become an exclusion?

When the cost of being wrong is high and the probability of the assumption changing is also high. If the utility agreement is signed, an energization date assumption is reasonable. If it is not signed, exclude the cost of delays caused by utility energization — or use an allowance that adjusts when the date is confirmed.

How should commissioning assumptions be documented?

State the assumed commissioning scope — which systems, how many phases, whether IST is included, whether third-party witnessing is required — and the assumed duration and crew level. If the commissioning specification is not finalized, exclude scope that depends on undefined testing sequences or quote commissioning as a separate allowance.

What is the difference between this checklist and the general assumptions checklist?

The general assumptions checklist covers scope definition, exclusions, site conditions, procurement, and commercial terms for any commercial job. This checklist is data-center-specific: it targets assumptions unique to or amplified by mission-critical work — redundancy, cooling architecture, rack density, OFCI coordination, phased commissioning, and the commercial structures that protect margin when those assumptions shift. Use both on data center work.

Should I use the power project quote complexity checklist alongside this one?

Yes. The power project quote complexity checklist scores the job across eight risk categories — scope clarity, existing conditions, outage risk, long-lead equipment, engineering coordination, installation conditions, testing, and commercial exposure — to determine whether the quote structure needs to change before it goes out. Use it to assess complexity. Use this checklist to document the specific assumptions. They complement each other.