Ask an FPE | Series
In This Post:
- What a Code Compliance Approach Report (CCAR) is and what it covers
- How CCARs are used to document and justify fire protection system design equivalencies
- How architects and project teams can use a CCAR as a proactive planning tool
- What happens when building and fire code noncompliance goes unaddressed, or project execution is misaligned with design intent
One of the most common ways building and fire code compliance issues surface is not through fire protection engineering negligence, but through system complexity.
In this installment of Ask an FPE, Sparc President Steven Venditti, P.E., explains what a Code Compliance Approach Report is and when it becomes essential to project success. More than a compliance document, CCARs can be a strategic tool to help project leaders maximize construction planning and mitigate fire safety risks from the start.
What Is a Code Compliance Approach Report?
A CCAR, which is also known as a Code Summary or Code Compliance Report, is a project-specific document that identifies the applicable building and fire code requirements and establishes the basis for how the design will meet them.
At its core, a CCAR does three things:
#1. Identifies which code requirements apply
The International Building Code alone exceeds 700 pages, and its sections frequently cross-reference one another. There’s also the International Fire Code to consider, and your local jurisdiction is able to modify codes even further. Even a single occupancy classification can trigger requirements across multiple chapters, and if you have properties across multiple jurisdictions, the applicable code editions and local amendments may differ from site to site.
A CCAR filters all of that down to the specific provisions relevant to your building type, occupancy, construction classification, and intended use.
Related Reading: How Do Building & Fire Codes Differ for New Construction vs. Existing Buildings?
#2. Documents where the design complies
A CCAR lays out, section by section, how the design meets each applicable requirement. This creates a clear, reviewable record for the project team and the Authority Having Jurisdiction (AHJ).
#3. Identifies compliance gaps and establishes a feasible path forward
When a design cannot meet a prescriptive requirement, the CCAR documents that gap. To address it, you’ll need to work with your team and potentially a fire protection engineering expert to develop a design equivalency, which is an alternative approach that achieves an equivalent level of safety as the code-prescribed solution through a different means. For example, performance-based designs offer more flexibility for complex or multi-site building projects where systems overlap.
When should a project use a CCAR?
A CCAR is not a document reserved for complex projects. Many project teams use one on relatively straightforward buildings precisely because the value is in the process: working through applicable code requirements systematically so nothing gets missed.
That said, a CCAR becomes especially important when:
● Physical or structural constraints make it difficult or impossible to meet a specific prescriptive requirement.
● The project involves an existing building with conditions that predate the current code.
● The design introduces something unconventional (such as a unique occupancy mix, an atypical layout, or fire protection systems that interact in nonstandard ways).
● The AHJ requests additional justification for an alternative design approach or specialty system like BESS.
How does building complexity and occupancy type impact the code compliance approach report?
The value of a CCAR becomes especially clear on projects with multiple structures or overlapping uses.
Consider a campus with five buildings: an underground parking garage, a hotel, an office building, and two mixed-use structures. Some systems interface with the garage; others are standalone.
Analyzed in isolation, the design for each building’s systems might appear straightforward. But as an interconnected campus, the picture changes. You might think the hotel is classified as Group R-1. But does it include conference rooms? This can create the need for additional code compliance considerations for accessory occupancies and other requirements. The parking garage beneath an occupied structure triggers an entirely different construction classification.
If you look at each building individually, it’s easy to miss requirements or misapply them. A CCAR provides the full picture: how all the buildings and systems interface, what code sections govern each condition, and where the project stands against each requirement.
How does a CCAR support design equivalencies?
A design equivalency isn’t a workaround. It’s an engineered solution that demonstrates the proposed design achieves an equivalent level of protection intended by the applicable code. Each equivalency requires documentation rigorous enough to withstand scrutiny by the AHJ during plan review and potentially by others in the future. This means the expert or team proposing it needs a robust understanding of what the building or fire code was written to achieve.
Common fire protection system design equivalencies include:
- Smoke detection enhancements, such as early-warning detection in areas where it isn’t strictly required, to demonstrate a higher level of protection.
- Voice evacuation systems that provide live or customized notifications that exceed the capability of a standard fire alarm.
- Fire-rated compartmentation, using passive (and sometimes with active) features to limit the spread of fire or smoke, where travel distances or egress configurations present challenges.
- Suppression system modifications, such as increasing design density to provide enhanced sprinkler performance.
- Egress alternatives, using hand calculations or fire modeling to demonstrate that occupants can safely evacuate under the proposed conditions.
The key distinction is that a design equivalency isn’t about swapping one fire safety device or component out for another. It’s about demonstrating that multiple interconnected systems work together to fulfill the code’s underlying intent: life safety.
To achieve timely AHJ approval and improve construction coordination (and execution), project leaders need to ensure system designs are clear, code-compliant, and defensible. A CCAR is a document that captures and centralizes all system-reliant construction decisions to streamline communication and critical project success.
At what point in the project lifecycle does a CCAR apply?
A CCAR can be developed and reviewed during the schematic design phase, even before the drawings are finalized, to guide integrated design decisions rather than reactive modifications. When architects and construction teams have a clear picture of applicable requirements from the earliest planning stages, they can make informed choices about layout, materials, occupancy configuration, and systems before those choices become expensive to change.
It can also be shared with the AHJ to demonstrate due diligence. Arriving at plan review with a clear, well-organized record of your code compliance efforts builds credibility with the reviewer and reduces the risk of design equivalencies being misinterpreted and projects being delayed.
Used this way, a CCAR functions as a checklist and a coordination framework. It’s a resource the architect can reference while designing, and a document the project team can use to verify that all requirements are being addressed as the design evolves.
What’s the risk of building without a CCAR in place?
The risks of operating without a CCAR, or without the thorough, project-specific code analysis it represents, tend to surface at the worst possible moments.
A design approved on paper may not function as designed. For example, smoke control systems rely on software modeling to verify that exhaust and pressurization will perform correctly given the actual building geometry. Stair pressurization systems require precise fan sizing.
If a misalignment problem or miscalculation is discovered after construction, you now have to wait for new equipment with long lead times and rehire vendors who may no longer be available for rework, delaying final approvals while the building sits idle. This is also where a third-party review can provide an added layer of verification before construction begins.
Related Reading: Can Third-Party Fire Protection System Reviews Help My Project Team Avoid Construction-Phase Conflicts?
How can I navigate building and fire code compliance confidently and cost-efficiently?
When a project runs into code challenges, the solution isn’t always to redesign pre-installed systems or push forward in hopes of AHJ approval. The decisions made at these critical junctures can make or break a project’s budget, timeline, and profitability.
Understanding how to use a CCAR gives project teams a structured way to document compliance, justify alternative approaches, and engage with the AHJ from a position of preparation rather than reaction. It’s a planning tool, a coordination resource, and a submission document all in one.
The cost of addressing a compliance issue during plan review is a fraction of the cost of addressing it during inspection. And the cost during inspection is a fraction of the cost of modifying installed systems in a finished building.
A CCAR doesn’t eliminate all project risk. But it establishes a defensible, code-aware baseline for all construction decisions, unifies siloed system installations by providing construction managers with a common language, and keeps projects moving.
Keep Your Project On Track With Real-World Fire Protection Engineering Insights. Schedule a Call.
This post is intended for educational purposes only. Please refer to the latest ICC, NFPA, and local jurisdictional documents to understand current building and fire code requirements. Consult a licensed fire protection engineer for guidance specific to your project.
About the Author
Steven Venditti, P.E. President | Sparc
Steven Venditti, P.E., has a Bachelor of Science and a Master of Engineering in Fire Protection Engineering from the University of Maryland. Mr. Venditti is a Professional Engineer (P.E.) licensed in multiple states. He has over 21 years of experience in fire protection engineering, including sprinkler and fire alarm system design, performance-based design of smoke control systems utilizing computer fire modeling, as well as fire investigations, code consulting, and interpretation. He has applied these skills to various facilities, such as office buildings, hotels, assembly spaces, and mixed-use complexes. Mr. Venditti has extensive expertise and knowledge of various codes and design standards, including NFPA, IBC, and local building codes.
