IBC Section 716 governs opening protectives in fire-resistance-rated assemblies. To apply it correctly for a specific door opening, you need to know the rating of the wall it penetrates, then cross-reference to the applicable door assembly standard, then check whether the listed assembly meets the specific requirements for that opening type and rating level. The chain runs from IBC to referenced standards to listed assembly data. Following that chain manually for every opening in a commercial project is not fast.
We built Kestrel Labs around that traversal problem. The system reads a building model while an architect is still drawing and flags conditions likely to fail plan review. With each compliance flag, it surfaces the relevant referenced standards, giving the reviewer a starting path instead of requiring the chain to be rebuilt from scratch. The aim is not to make code research disappear. It is to put the right references beside the design condition that triggered the review.
Why References Cause Delays
Code provisions rarely stand alone. A requirement in the IBC may point to an NFPA standard, which may point to a UL listing standard for a specific product. A reviewer has to identify the applicable section, follow its reference, check the product or assembly scope, and bring the result back to the model. That work is easy to postpone until review comments arrive.
Consider a two-hour fire barrier with a door opening. IBC Section 716 governs opening protectives in fire-resistance-rated assemblies, while NFPA 80 governs fire-door installation. UL 10C and UL 10B list specific door assembly configurations and tested ratings. The practical question is not simply whether a door is labeled. The assembly must match the IBC 716 rating rules, and the selected configuration must be supported by the applicable listing.
Following Reference Chains
Some chains are direct, while others depend on the system represented in the model. IBC 717 on ducts and air transfer openings references NFPA 90A. That standard carries installation requirements for fire and smoke dampers, including products covered by UL 555 for fire dampers and UL 555S for smoke dampers. The reviewer must connect the opening, the damper type, the standard, and the installation requirement.
Other examples cross disciplines. NFPA 13 on sprinkler systems references NFPA 72 for notification requirements, and referenced standards can contain further references to UL listing standards for particular products. A design review therefore involves more than matching text to a section number. It involves preserving the relationship between the modeled condition and each requirement reached through the chain.
IBC 714 governs penetrations through fire-resistance-rated assemblies. IBC 705 presents a different reference problem: exterior-wall conditions depend on fire separation distance and projected opening percentage. The next requirement changes with project facts. A lookup tool should expose the path without implying that every reference has one universal answer.
Where Automation Does Not Solve the Problem
Reference traversal is most useful when the triggering condition is well defined. It is less decisive when several code branches apply at once, when an interpretation is contested, or when a local amendment changes the standard chain. A model can identify a rated wall and surface IBC 714 or 716, but the reviewer still has to assess the project facts and decide which provisions control.
We are deliberate about the boundary of the value: surfacing reference chains cuts traversal time for well-defined conditions. It does not replace the judgment needed when multiple code branches apply, interpretations are contested, or local amendments change the standard chain.
Denver and Colorado use the IBC as a base code with local amendments. Edition matters: IBC 2021 updated referenced standards from IBC 2018, including NFPA 13 and NFPA 72. Results must account for jurisdiction and edition.
Applying the Method to Colorado Projects
For commercial mixed-use work in Colorado, a reviewer may need to move among IBC 508, 503, 506, 707, 713, 714, 716, 717, 1004, 1006, and 1016. Those sections touch occupancy, allowable area, fire-resistance conditions, penetrations, opening protectives, building systems, and egress. The relevant path depends on what the model contains and how the spaces are classified.
Suppose a mixed-use model places a duct and a door in a rated separation. The system can flag the door against the opening-protective requirements in IBC 716 and connect the duct condition to IBC 717 and NFPA 90A. It can also surface NFPA 80, UL 10C or UL 10B, and the applicable damper references when those standards are relevant. The reviewer then checks the actual assembly, product, and installation context.
This approach changes the order of work. Instead of finding references after a city comment, the firm sees the research path while design is moving. That can reduce repeated searching across sheets, specifications, code books, and product listings. It does not determine a local amendment or settle an ambiguous interpretation, but makes references easier to inspect.
What a Reviewer Gets From the Model
The useful output is a compliance flag tied to a modeled condition, not a detached standards list. Each flag includes relevant references so the reviewer can see why the path was surfaced and where to continue. This keeps the lookup connected to the door, penetration, duct, damper, or other element under review.
For our three-person founding team, that connection is the practical test. Kestrel Labs is not trying to replace the architect or code consultant. We are building for architecture and engineering firms that need to find likely problems before a permit set reaches review. The system checks the design as it is drawn, points to what may fail, and helps the firm investigate the supporting requirements.
