Smoke control is a life-safety system. The goal is a tenable path for evacuation/relocation, not "clearing smoke" for property protection or firefighter overhaul.
Plain English:
512.1 scope + purpose
IMC 512 applies when the IBC or IFC requires smoke control (mechanical or passive). It sets minimum requirements for design, installation, and acceptance testing to support occupant movement in a fire event.
Key distinction: Smoke control under IMC 512 is different from smoke/heat removal in IBC/IFC Section 910 (different intent, different design approach).
512.2 general design requirements
If smoke control is required, the design must follow the applicable parts of IBC 909 and accepted engineering principles. Construction documents must show enough detail to actually implement the system and include supporting information/analysis demonstrating compliance.
512.3 special inspection + testing
Smoke control systems tied to IBC 909 require special inspections and tests to verify commissioning in the final installed condition. The submittal must clearly spell out procedures, methods, and what will be tested/inspected, aligned with IBC 1704 terms.
On Plans: Why it matters
Plan review stalls happen when smoke control is treated like "typical HVAC." If the drawings don't define the intent, the method, and the verification plan, it becomes a late field redesign with the AHJ, TAB, controls, and electrical.
Code Path: Where to show it
Life-safety / M-001: "IMC 512 / IBC 909 SMOKE CONTROL BASIS OF DESIGN" note (system type, zones, method, performance targets, duration, standby power references).
Control diagrams: sequences, interlocks, firefighter overrides, and what gets verified.
Commissioning notes: special inspection/testing scope, responsible parties, and acceptance criteria.
Check: Do
Identify early whether smoke control is triggered by IBC/IFC and which IBC 909 method applies.
Put the basis of design and acceptance testing plan on the drawings, not buried in emails.
Review Risk: Don't
Don't call a Section 910 smoke/heat vent or atrium exhaust "smoke control" without an IBC 909 basis and testing plan.
Don't leave commissioning as "TBD by contractor."
Field Tip:
Start every smoke control set with a one-page "SMOKE CONTROL NARRATIVE" that lists: zones, method (pressurization/airflow/exhaust), performance targets, activation inputs, equipment schedule, standby power source, and acceptance tests. If you can't summarize it on one page, the job will be painful.
Masterbuild QA Lens
Smoke control system scope and analysis requirements per 512.1-512.2 must be established before any design begins. Confirm the system type (pressurization, airflow, exhaust, or combination), the analysis method (hand calculation or computer model), and the AHJ acceptance of the method are documented on M-001. A smoke control system designed without AHJ pre-confirmation of the analysis method is a high-risk submittal.
Drawing / Submittal Check
For 512.1-512.3 (scope, intent, documentation): the smoke control documentation package must accompany the mechanical permit set. Confirm the package includes: system description, design basis narrative, air quantity calculations, sequence of operation, control system description, and testing protocol. Many AHJs require a separate smoke control permit - confirm the routing path before submittal.
Common Review Risk
Smoke control documentation submitted without the design basis narrative is routinely returned at intake. The reviewer needs the narrative to understand the system before evaluating the drawings. The narrative must explain: what the system is trying to accomplish, what the design assumptions are, and what the performance criteria are. A drawings-only submittal for a smoke control system will cycle until the narrative is submitted.
When To Escalate
Escalate when the smoke control system scope is not clearly defined - when the architectural program keeps changing after the smoke control design is started, or when the building permit and the fire alarm permit are being processed by different agencies with different smoke control requirements. Undefined scope is the leading cause of smoke control design rework.