DCFR Insight 16 / Design Review + Constructability
Capacity DeliveryThe 90-Minute Data Center Architectural Package Review: What to Check Before Construction
A disciplined review should expose reference-design drift, life-safety gaps, unresolved interfaces, procurement risk, and field-sequencing failures before they become RFIs, rework, or energization delay.
The goal is release control, not comment volume
A high-value review does not attempt to redesign the project or redline every sheet. It asks whether the package is safe to advance to the next irreversible step: permit, procurement, fabrication, dry-in, equipment setting, commissioning, or construction. The reviewer looks for a small number of consequential issues that can trigger life-safety exposure, reference-design drift, field conflict, weather-tightness failure, major rework, or schedule loss.
0–10 minutes: freeze the review basis
Record drawing and model issue dates, approved Basis of Design, reference design, owner standards, project deviations, code edition and amendments, AHJ interpretations, insurer criteria, vendor requirements, and current decision log. If the governing baseline is unclear or the documents are not aligned, the review result should state that limitation immediately. A reviewer cannot judge conformance against an unstable basis.
10–25 minutes: run the module and reference-design sweep
Compare data hall modules, structural grid, room relationships, rated boundaries, circulation, service access, loading, equipment yards, louvers, roof zones, security, and expansion interfaces against the approved repeatable design. Classify every variance as accepted, jurisdiction-driven, technically justified, cost-driven, or unresolved. Untracked drift is dangerous because one architectural change can alter MEP distribution, fire protection, controls, procurement, commissioning, and portfolio repeatability.
25–40 minutes: read the code strategy through the actual plan
Verify occupancy and incidental-use assumptions, construction type, allowable area and height, fire separation distance, exterior-wall exposure, rated rooms, shafts, openings, penetrations, egress, accessible routes, exit discharge, fire apparatus access, fire-water assumptions, and special inspections. Do not rely on a generic code sheet if the plan and sections do not support it.
40–60 minutes: interrogate discipline interfaces
Review wall and roof penetrations, louvers and dampers, intake/exhaust separation, curbs, housekeeping pads, trenches and duct banks, busway and cable tray crossings, firestopping, structural embeds, drainage, door and removable-panel replacement paths, equipment clearances, security devices, and maintenance access. Compare architectural backgrounds with structural, civil, mechanical, electrical, plumbing, fire protection, controls, security, and vendor information.
60–75 minutes: test the installation sequence
Ask how the facility will be enclosed and equipped. Can temporary openings remain until large equipment is set? Can roof and wall work proceed without trapping unfinished interfaces? Are crane zones, laydown, weather protection, access roads, and safe trade sequencing credible? Can fireproofing, firestopping, sealants, and inspections occur before concealment? A dimensionally correct detail can still be impossible to execute in the intended order.
75–85 minutes: check release gates and long-lead interfaces
Identify which architectural decisions affect transformers, generators, switchgear, cooling modules, louvers, doors, wall panels, roofing, structural steel, precast, fire pumps, tanks, or modular assemblies. Confirm that openings, supports, loads, clearances, environmental conditions, and service routes are stable enough for release. Procurement should not outrun the interfaces that determine whether equipment can be installed.
85–90 minutes: issue a decision-ready summary
Classify findings as stop-ship, high, medium, or advisory. State whether the package should advance, advance with conditions, or hold. For each critical issue, identify requirement, location, cross-discipline impact, owner, due date, and closure evidence. A short prioritized register is more useful than hundreds of unranked comments.
The review should become a repeatable control loop
Record recurring deviations, accepted details, field failures, AHJ comments, commissioning issues, and closeout lessons so the next package review improves. Portfolio learning should refine the reference design without copying jurisdiction-specific acceptance blindly across sites.
90-minute architectural review sequence
| Time | Review gate | Primary questions | Hold condition |
|---|---|---|---|
| 0–10 | Basis | Are issue versions and governing requirements aligned? | Conflicting or unidentified baseline |
| 10–25 | Reference design | Where has the project drifted and is it approved? | Unresolved multi-system deviation |
| 25–40 | Code/life safety | Does the physical design support the stated strategy? | Egress, rating, fire access or AHJ gap |
| 40–60 | Interfaces | Do architecture, engineering and vendor systems agree? | Major opening, clearance or penetration conflict |
| 60–75 | Constructability | Can enclosure and equipment be installed safely in sequence? | Dry-in, access or concealment path not credible |
| 75–85 | Release/procurement | Are long-lead interfaces stable? | Fabrication depends on open decisions |
| 85–90 | Decision/closure | Who owns each critical issue and what proves closure? | Stop-ship item lacks owner or evidence |
Capacity-delivery review checklist
What to verify before the next release gate.
- Approved BOD, reference design, owner standards and deviations aligned
- Drawing, specification, model and vendor versions identified
- Module geometry, room relationships and expansion interfaces checked
- Occupancy, construction type, rated assemblies, egress, accessibility and fire access verified
- Envelope, opening, penetration, equipment and firestopping interfaces reviewed
- MEP, structural, civil, security, controls and vendor backgrounds coordinated
- Equipment delivery, replacement, maintenance, crane and temporary-opening paths tested
- Permit, procurement, fabrication, dry-in, commissioning and closeout gates mapped
- Comments ranked with owner, due date and closure evidence
What DCFR would flag
Delivery risks that should be visible early.
DCFR would flag unstable review bases, unapproved reference-design drift, code strategies unsupported by the plans, cross-discipline interface conflicts, procurement released ahead of geometry, and comments without accountable closure.
Professional confirmation required
Items requiring project-specific validation.
Final code compliance, engineering coordination, constructability, product and equipment selection, release for procurement or construction, testing, permitting, cost, schedule, and acceptance require confirmation by the Architect and Engineers of Record, qualified contractors, vendors, owner, insurer, commissioning team, and AHJ.
Final takeaway
A 90-minute review is successful when it identifies the few issues capable of stopping the project and converts them into controlled decisions before the next release gate.
Surface site, code, utility, and delivery risk before it becomes expensive.
DCFR converts early assumptions into planning-grade flags, confirmation registers, and decision-ready feasibility outputs.