Building permits and inspections

Once land use approvals are in place, the project needs permission to build. Building permits confirm that the design complies with the building, fire, plumbing, electrical and energy codes, and inspections during construction confirm that what is built matches the approved design. For a data centre, the permitting stage is unusually complex: the buildings are large and often classified unusually, the electrical and mechanical systems are enormous, there are fuel tanks and battery rooms, and owners want to build in phases and start some work before the whole design is finished. This lesson covers the codes that apply, how data centres are classified, the permit process including phased and fast-track permits, the specific code issues data centres raise, inspections and occupancy, and practical ways to keep permits off the critical path.

The codes

In Canada, building regulation is provincial. Most provinces adopt the National Building Code of Canada (NBC), National Fire Code (NFC), National Plumbing Code and National Energy Code for Buildings (NECB), produced by the National Research Council, with provincial amendments; Ontario, Québec, British Columbia and Alberta publish their own codes based on the national models (for example the Ontario Building Code and Québec's Construction Code). Electrical installations follow the Canadian Electrical Code (CSA C22.1) as adopted by each province, enforced by the provincial electrical safety authority rather than the municipal building department. Municipalities, or in some provinces provincial agencies, issue building permits and carry out inspections.

Data centres also draw on standards that codes reference or that owners adopt:

• Electrical: CEC Section 26 (installation of equipment, including battery rooms), Section 46 (emergency systems) and Section 64 (energy storage), and CSA C282 for emergency power.
• Fire: NFPA 75 (protection of IT equipment) and NFPA 76 (telecommunications facilities), often adopted by owners or insurers, and CAN/ULC-S524 and S537 for fire alarm installation and verification (DCE-440).
• Energy: the NECB as adopted, which applies to the building envelope, lighting and HVAC; data centre IT loads are treated as process loads, though some owners also apply ASHRAE 90.4.
• Structural: NBC Part 4 for loads, including seismic design based on the site's hazard values, and importance categories for buildings whose operation must continue after a disaster (DCE-430).

Classifying a data centre

Codes assign each building, or part of a building, an occupancy classification that drives fire separation, construction type, maximum area and height, sprinkler requirements, egress and more. Data centres do not fit neatly into the traditional categories:

• The data halls are usually classified as Group F, Division 2 (medium-hazard industrial) or sometimes Group F, Division 3 (low-hazard industrial) or Group D (business and personal services), depending on the combustible load and the authority's interpretation.
• Offices, loading docks and storage areas may have different classifications, requiring fire separations or treating the building as mixed use.
• Battery rooms, generator rooms, fuel storage and electrical rooms bring hazardous materials and high-energy equipment provisions.

Because classification has large cost implications, it should be agreed with the authority early, ideally in a pre-application meeting with a written code analysis, rather than discovered during plan review.

The permit process

A building permit application includes architectural, structural, mechanical, electrical, plumbing and fire protection drawings and specifications, a code analysis, energy compliance documentation, and supporting reports such as the geotechnical report. Plan reviewers in each discipline check the submission and issue comments, the design team responds, and once all disciplines are satisfied the permit is issued, often with conditions. Separate permits or approvals are typically required for:

• Electrical work, through the provincial electrical safety authority (for example the Electrical Safety Authority in Ontario), with plan review for large installations.
• Plumbing, mechanical systems, elevators, fire alarms and sprinklers.
• Fuel storage tanks, under the fire code and, in some provinces, the technical safety authority (for example TSSA in Ontario).
• Pressure vessels and boilers, where present.
• Demolition, excavation and shoring, and work in public roads.
• Signs, fences and temporary construction buildings.

Phased and fast-track permits

Owners rarely wait for a complete design before building. Many authorities issue phased permits: a site work and excavation permit, then foundations, then structure and shell, then interior and mechanical-electrical systems, each based on the drawings completed for that stage. Phasing allows construction to start months earlier, but it carries risk: later design changes can conflict with work already built under an earlier permit, and the authority may impose conditions. Some jurisdictions offer expedited review for a fee, third-party plan review by qualified private reviewers, or dedicated staff for major projects, which large data centre developers often fund.

Code issues specific to data centres

• Large open floor areas and travel distances: data halls can be hundreds of metres long, so egress design must meet maximum travel distances while preserving security, often with controlled exits that release on fire alarm.
• Sprinklers versus alternatives: owners often prefer pre-action sprinkler systems (pipes dry until detection) to protect IT equipment from accidental discharge, and may add clean-agent gaseous suppression in critical rooms; codes and insurers set the minimum (DCE-440).
• Battery energy storage: lithium-ion UPS batteries raise thermal runaway and explosion concerns, addressed through listings, test data (UL 9540A), separation, ventilation, detection and maximum quantities (DCE-340).
• Fuel: large diesel quantities in day tanks and bulk tanks require fire code compliance for tank construction, location, secondary containment, venting and fill points, and limits on quantities inside buildings.
• Electrical: very large services, medium-voltage equipment, arc-flash hazard and selective coordination requirements (DCE-310).
• Roof equipment and seismic or wind restraint of mechanical units and cable trays.
• Energy code compliance for buildings whose dominant load is IT equipment, where prescriptive rules written for offices may not fit, so performance or alternative paths are used.

Where the design departs from the code's prescriptive requirements, Canadian codes allow alternative solutions that achieve at least the level of performance required by the code's objectives and functional statements, documented and accepted by the authority. Data centres frequently use alternative solutions for egress travel distance, building area and fire suppression.

Inspections and occupancy

Inspections occur at defined stages: footings and foundations before concrete, structural framing, underground and in-wall services before cover (as in ELEC-130), fire-rated assemblies and penetrations, mechanical and electrical rough-in, and final inspections for each discipline. Fire protection systems require acceptance testing witnessed by the authority, including sprinkler hydrostatic tests and fire alarm verification. Some codes require special inspections, carried out by qualified independent inspectors engaged by the owner, for critical structural work such as concrete strength, welding and high-strength bolting.

When construction is complete and inspections are passed, the authority permits occupancy (an occupancy permit or permission to occupy, depending on the province). Partial or phased occupancy, allowing the first data hall to operate while the rest is under construction, requires that life safety systems, exits and fire separations serving the occupied part are complete and accepted.

Commissioning (DCE-450), which tests every system under load to prove it performs as designed, is separate from code inspections but runs in parallel with them at the end of construction, and the final inspections are often scheduled to coincide with integrated systems testing.

Keeping permits off the critical path

• Hold pre-application meetings with the building and fire officials, with a written code analysis.
• Agree on classifications, alternative solutions and phasing in writing early.
• Submit complete, coordinated packages; incomplete submissions generate comment cycles that cost more time than they save.
• Track every permit and approval in a register with owners, dates and dependencies.
• Fund expedited or third-party review where available, and maintain a respectful working relationship with reviewers and inspectors, who will see the project many times.
• For repeated campus buildings, seek approval of a standard design that later buildings can reference, shortening subsequent reviews.

Lesson 9 covers the separate approvals needed for power and fuel infrastructure, which often set the critical path even when the building permits are ready.