Datacenter turnover QA before white-space acceptance

Direct answer

Before a datacenter white space is accepted, record the exact room or phase boundary, release authority, latest drawings, punch log, room condition, raised-floor or slab status, pathways, penetrations, power, grounding, telecom, cooling, airflow, fire/life safety, leak detection, security, commissioning evidence, O&M and training records, photos, open exceptions, and final release decision.

The packet belongs before owner acceptance, tenant fit-out, IT load-in, or operations handoff because later work hides the conditions that decide whether the room was ready. Cabinets, cable, containment, access-control work, owner equipment, and operating restrictions can block floor panels, penetrations, labels, sensors, alarms, firestopping, and unfinished punch items.

Use this field note as documentation guidance only. The owner standard, project drawings, specifications, commissioning plan, AHJ, commissioning authority, engineer of record, security requirements, manufacturer instructions, qualified trades, operations team, and site safety plan control the actual acceptance, energization, commissioning, inspection, and release.

White-space acceptance is not rack readiness

A raised-floor packet and a rack-readiness record can support the turnover package, but they do not prove the room is accepted. The white-space packet asks a broader question: can this data hall, suite, phase, or owner boundary be handed over with the systems, access, evidence, and exceptions clearly documented?

Rack readiness usually focuses on cabinet IDs, route, final row, floor path, power/cable/cooling handoffs, stabilization, and move-in release. White-space acceptance also covers room cleanliness, architectural closeout, ceiling and wall condition, doors and seals, pathway completion, firestopping, life-safety systems, leak detection, security, controls, alarm visibility, commissioning records, O&M data, training, spares, warranty/startup records, and operations acceptance.

That distinction prevents a common dispute. A row may be ready for cabinets while the room is not ready for owner acceptance. A room may be accepted with exceptions while a specific row remains held. The packet should make those boundaries visible instead of burying them in meeting notes.

Define the boundary and acceptance authority

Start by naming what is being accepted. The boundary might be Data Hall 1, Phase 2 white space, Suite A, Room 1200, a tenant cage, a row block, an electrical room handoff that supports the white space, or a demarcation between base building and tenant fit-out.

Attach the latest drawing or owner turnover map and mark the boundary. Include revision numbers for architectural, structural, electrical, mechanical, plumbing, fire protection, telecom, controls, security, and equipment layout drawings where those disciplines affect the handoff. If the project has an Owner's Project Requirements document, Basis of Design, commissioning plan, acceptance checklist, or owner standard, identify the version used for the walk.

Then name the decision authority. The packet should say who can accept, hold, accept with exceptions, or release a partial area. That may involve the owner, owner's representative, commissioning agent, GC, facilities operations, security, AHJ, engineer, landlord, tenant, or specialty trade depending on the contract. The field note should not guess. It should point to the project procedure and capture the actual decision.

Room condition and visible closeout

The room condition record should be boring and specific. Capture floor, walls, ceiling, doors, frames, seals, windows if present, ceiling grid, access panels, dust control, cleaning status, paint or finish damage, water marks, temporary covers, trash, abandoned material, and open punch items.

Raised-floor and slab details belong here because they affect acceptance beyond rack movement. Record panel condition, pedestal or stringer observations, grid labels, cutouts, edge trim, grommets, missing tiles, rocking panels, access limitations, exposed openings, floor protection, and any referenced load or rolling restriction. Do not invent a structural approval in the QA note. Refer to the accepted floor packet, structural documents, manufacturer instructions, or owner standard.

Photograph the room before owner gear or tenant work fills it. Wide photos should prove the boundary and condition. Close photos should identify defects, labels, penetrations, panels, access doors, sensors, and punch items. A photo folder with no location reference is much weaker than a drawing marked with photo numbers.

Pathways, penetrations, and hidden access

White-space turnover is the last practical chance to confirm many pathway and penetration conditions before they are blocked. Record overhead cable tray, ladder rack, basket tray, conduit, busway, sleeves, underfloor pathways, floor openings, wall penetrations, ceiling penetrations, brush grommets, edge protection, pull boxes, access panels, labels, and abandoned temporary openings.

Firestopping and smoke or dust separation should be tracked to the responsible approving process. The packet should show which penetrations are complete, which are temporary, which are awaiting inspection, and which remain open by design. Do not let a general firestop complete note replace location photos, labels, inspection status, and exception ownership.

Also record access that will be lost after acceptance. If a panel, tray, valve, detector, damper, junction box, leak detection cable, controls device, or security component will be difficult to reach after racks or containment arrive, document its status before the handoff.

Power, grounding, and telecom handoffs

The power handoff should identify the equipment and status without pretending to approve energized work. Record switchgear, UPS, batteries, PDU, RPP, busway, panel, branch circuit, receptacle, whip, labeling, panel schedule, one-line reference, capacity allocation where the owner tracks it, testing status, commissioning status, and open exceptions.

Grounding and bonding should be visible in the record. Identify the room grounding bar, bonding points, rack or pathway bonding handoff, raised-floor or static-control requirements where applicable, test or inspection status if required, and the responsible electrical reviewer. Do not turn the QA packet into a grounding design. Name the drawing, standard, test record, or qualified person that controls the acceptance.

Telecom needs the same discipline. Record meet-me room or demarc references, fiber and copper pathways, tray or ladder labels, patch field status, carrier handoff status, test record status, abandoned cable removal, cable-management hardware, and open work that could be hidden by tenant equipment.

Cooling, airflow, controls, and alarms

Cooling turnover should separate equipment status from room acceptance. Record CRAH, CRAC, AHU, fan wall, chilled-water, condenser-water, refrigerant, humidification, condensate, leak detection, containment, blanking, tile, diffuser, return path, damper, sensor, and controls status as the project requires.

Airflow details matter even before IT load is installed. Record hot aisle and cold aisle intent, containment doors or curtains, perforated tiles, diffusers, sealed cable openings, brush grommets, blanking-panel plan, open floor holes, temporary covers, and any known bypass or recirculation exception. The packet should say installed, staged, pending, or not in scope instead of implying every airflow item is complete.

Controls and alarms should be reviewable by operations. Record BMS graphics, local displays, sensor names, alarm points, trend logs, setpoint responsibility, network handoff, and unresolved controls issues. If functional testing or integrated systems testing is still pending, say that clearly. Acceptance with pending commissioning is different from final commissioned acceptance.

Fire/life safety, leak detection, and security

Fire/life safety items need a careful status record. Capture detection, notification, suppression or preaction status, fire alarm interface, dampers where applicable, clean-agent or sprinkler scope where applicable, permits, inspection status, impairment status, EPO where applicable, and AHJ or fire protection reviewer notes. The QA packet should show the evidence trail. It should not give fire protection approval.

Leak detection also belongs in the room acceptance record when the project includes it. Record cable or sensor routes, panel labels, alarm mapping, test status, photos, low points, drain or condensate relationships, and open exceptions. Water history or visible staining should be written into the room condition record, not treated as a separate rumor.

Security controls can be decisive for owner acceptance. Record doors, locks, card readers, biometrics if used, cameras, intercoms, mantraps, cages, visitor route, key control, temporary access, commissioning or testing status, and security punch ownership. Keep sensitive details in the proper project system. The public-style QA note can say security punch item S-14 remains open without exposing credentials, camera blind spots, or access-control settings.

Commissioning, O&M, and training evidence

Turnover should connect field condition to commissioning evidence. Depending on the project, that may include prefunctional checklists, startup reports, functional performance tests, integrated systems tests, alarm tests, trend logs, deficiency logs, issue closeout, seasonal testing plans, and commissioning authority acceptance.

The packet should also include closeout information that operations will need after the contractor leaves. Record O&M manual status, systems manual status, record drawings, approved submittals, installed equipment data, serial numbers where required, spare parts, attic stock, warranty/startup documents, maintenance requirements, vendor contacts, and training attendance.

Do not hide missing training or manuals behind a clean walk. If operations has not received the systems information needed to run the room, the turnover decision should say whether acceptance is held, accepted with exceptions, or limited to a construction boundary.

Minimum white-space turnover packet

Use the owner checklist, commissioning forms, quality management system, AHJ records, and contract closeout forms first. Add a short packet where those systems do not make the room acceptance decision easy to review.

Before acceptance walk checklist

Run this check before signing the room over or allowing fit-out work to erase the turnover condition.

• Mark the exact white-space boundary on the current drawing.
• Confirm the acceptance authority and allowed decision states: accepted, held, partial release, or accepted with exceptions.
• Walk the room with the latest punch log and issue log.
• Photograph wide views of the room, aisles, entrances, pathways, panels, and ceiling.
• Photograph close-ups of defects, penetrations, labels, access panels, sensors, alarms, and exceptions.
• Confirm floor or slab status, cutouts, grommets, edge protection, and access limits.
• Confirm pathways, penetrations, and firestopping status by location.
• Record power, grounding, and telecom status without treating pending tests as complete.
• Record cooling, airflow, controls, trend, and alarm status.
• Record fire/life safety, leak detection, EPO where applicable, and security status through the proper authority.
• Attach commissioning evidence, open deficiencies, O&M status, systems manual status, training status, spares, startup records, and warranty documents.
• Write the final release decision and name every exception that survives acceptance.

Weak and strong turnover notes

Weak note: White space ready for turnover.

That note does not identify the boundary, drawing revision, authority, room condition, floor status, MEP status, telecom status, fire/life safety status, security status, commissioning evidence, O&M handoff, open exceptions, or release decision.

Stronger note: Data Hall 1 Phase 2 white-space acceptance walk completed against drawings A2.11, E6.22, M5.14, T3.04, FP2.08, and SC1.02, all revision 7. Boundary marked on turnover map from grids D through H and 4 through 11. Room cleaned and photographed before tenant fit-out. Raised-floor packet accepted for this boundary with two damaged panels replaced and rephotographed. Overhead ladder, busway, underfloor openings, brush grommets, and firestopped wall penetrations photographed by location. UPS/PDU/RPP labels, panel schedules, grounding bar, telecom tray labels, and fiber pathway test-status log attached. CRAH units, containment doors, perforated-tile layout, leak detection panel, BMS graphics, alarm trend export, and open controls issue Cx-18 attached. Fire alarm and preaction inspection records attached by the fire protection lead. Access-control readers and cameras tested by security, with camera view item S-7 accepted as owner exception. O&M manual index, systems manual draft, startup reports, spare filters, and operations training roster attached. Owner accepted Phase 2 white space with exceptions Cx-18 and S-7; no IT load allowed in Row F until Cx-18 is closed.

The stronger note works because it says what was accepted, what evidence supports it, what remains open, and what the exception prevents. It does not pretend every system is complete.

Common mistakes

The first mistake is treating room clean as turnover. Cleanliness matters, but it does not prove power, cooling, telecom, life safety, security, commissioning, or operations handoff.

The second mistake is mixing boundaries. If Phase 2 is accepted but the adjacent suite, electrical support room, or row block is still held, the packet should say so on the drawing and in the release note.

The third mistake is closing punch by conversation. A commissioning issue, security exception, firestopping item, or controls alarm should have an owner, date, evidence, and final resolution path.

The fourth mistake is hiding pending commissioning. A room can be visually complete while functional testing, integrated testing, trend review, alarms, O&M manuals, or training remain incomplete.

The fifth mistake is over-sharing sensitive security details. Preserve security evidence in the proper project system and keep public or broad-distribution notes at the punch-item and acceptance-status level.

Compliance and safety limits

This field note is not a design approval, commissioning approval, fire protection approval, electrical approval, security approval, AHJ approval, certification claim, energization authorization, or operations acceptance by itself. The owner standard, project drawings, specifications, commissioning plan, AHJ, commissioning authority, engineer of record, qualified trades, manufacturer instructions, security requirements, and operations procedures control the work.

Do not use this checklist to bypass lockout, energized-work rules, fire alarm impairment procedures, suppression-system procedures, security controls, access-control rules, lift or ladder safety, hot work, floor-loading reviews, confined-space rules, PPE, commissioning scripts, permits, inspections, shutdown procedures, or site-specific safety requirements. The packet preserves the acceptance decision chain. It does not authorize unsafe work or unapproved turnover.

Sources checked

• GSA, The Building Commissioning GuideUsed for commissioning planning, Owner's Project Requirements, Basis of Design, issues log, operator training, and commissioning-plan acceptance themes.
• VA, Whole Building Commissioning Process ManualUsed for functional performance testing, acceptance/testing phase commissioning, deficiency tracking, O&M manuals, systems manuals, and installed equipment data.
• UFGS 01 78 24.00 10, Facility Data RequirementsUsed for record drawings, O&M references, facility data structure, and closeout-data organization themes.
• NIH, Sustainable Data Center Design GuideUsed for data center lifecycle, cooling effectiveness, airflow, power/cooling, efficiency, maintainability, and owner requirement context.
• TIA, ANSI/TIA-942 StandardUsed for data center physical infrastructure scope across architectural, electrical, mechanical, fire safety, telecommunications, security, monitoring, redundancy, and maintainability themes.
• NFPA, NFPA 75 Standard DevelopmentUsed for information technology equipment and IT equipment area fire protection context.
• ENERGY STAR, Manage Airflow for Cooling EfficiencyUsed for airflow management, blanking panels, cable-opening sealing, floor-opening control, and cooling-efficiency handoff themes.
• Uptime Institute Journal, Improve Project Success Through Mission Critical CommissioningUsed for mission critical commissioning as a lifecycle process, stakeholder roles, transition to operations, baseline performance, operations training, and rigorous commissioning themes.

Related guides