Unless you're tuned in as an AHJ yourself, you've likely made a few "code calls" to a code authority and asked a litany of questions to make sure your project's design meets the local requirements.
I'm not even sure if the term "code call" is a common term, but I've heard it enough that I suspect you already know what I'm talking about regardless of where you call home.
I enjoy this process now, but I didn't always. Fresh out of school I'm pretty sure I was visibly shaking the time I first made a code call. I was sure that within seconds my cover would be blown and it would be all too obvious that I had no idea what I was talking about. Despite my awkwardness (I make a good engineer, right??) nothing went sour and since then I've slowly learned and repeated many many times.
There was even one of my favorite code calls that I made about an elementary school to coordinate local fire alarm requirements. It was only right after the call late on a Friday afternoon that I found out that the fire marshal I just spoke with was hired onto our team and was starting the following Monday. They say fire protection is a small world, right? He turned out to be one of the most knowledgeable people I know and one of my favorite people to work alongside.
The Joys & Pains of Code Calls
Code calls also come in many different flavors.
Sometimes I'm just shocked by how friendly and helpful code authorities are. I once made a call at 15 minutes till 5pm on a Friday to a small town in Arkansas, thinking I would just leave a voicemail. After my questions, I asked if the department conducted flow tests, and while he said they did, he apologized that because of a prior commitment he couldn't do it then but would be happy to do it first thing Monday morning. I almost fell out of my chair. Very helpful and caring people in this field.
On the contrary, sometimes the hardest part about a code call is just finding the right person to speak with who is actually responsible for plan review of fire protection systems and getting a few minutes of their time. Not to pick on New York City because I love the people there and speak with a handful of you regularly, but if you're trying to get a hold of someone to verify or coordinate a few particulars of your system... well... good luck! Maybe it's because they knew I can't stand the Yankees.
I also sometimes get AHJs who simply say all they do is 'per code' and they aren't interested in talking specifics. The whole point of the call is filling in the gaps where a code or standard does not direct but rather defers decisions to the AHJ.
Want a siamese fire department connection with national thread, or a Storz-type? Either way is code compliant. As an engineer I can make either way work.
Is a wall-mounted FDC permissible, or does it need to be freestanding? Either location is compliant, but NFPA 13 says the location needs to be coordinated with the AHJ.
What I've gathered and refined over hundreds of code calls is my cheatsheet I currently use today. Just like the design cheatsheet, if you're using the Toolkit you can quickly highlight categories for your record keeping.
What's even better about this tool, though, is that you can quickly fill in the content (while on the call) and then right after save as a PDF and email to the AHJ themselves. Want them to have a record of the call and a quick way to verify your notes? Great! You now have a logged code call and the AHJ has an opportunity to review your notes.
The process of calling, taking notes, and composing the email used to take close to an hour total. This tool alone brings that total time to about 15-20 minutes. That's three-quarters of an hour you could save on every job you make the call!
A Radical Big-Picture Concept
One of my longer big-picture ideas to help the industry is to beta test and, if successful, open up a larger code-call database. I envision this as a database that brings designers and code authorities together to make local requirements clear and help jurisdictions get installations that reflect their preferences and mandates.
Want to know what hydraulic safety factor is required for sprinkler systems in Springfield, Illinois? Great - a quick query in the database reveals that and a clean list of other local requirements.
Want to know what type and location for FDC's that Tucson, Arizona requires? Great, we'd have that too.
This would clearly have a huge value for designers and engineers - but what I'm really curious about is how to incentivize code authorities to take the survey or help us populate the database. If you're an AHJ, email me (firstname.lastname@example.org) or comment below about whether you'd be open to the idea of making your local requirements public in a database.
I would have to think that AHJ input would only help local authorities get installations that match their needs - but I also know that getting action out of anyone is only possible with mutual benefit and sometimes incentives.
Just like the Design Cheatsheet posted a couple weeks ago, this form is integrated into the updated version of the MeyerFire Toolkit ready for download today. Below is a blank and filled-in template.
If you're already a Toolkit user, you can download the code call cheatsheet today by logging in here. If you're not using the Toolkit, you might consider joining in on what's quickly becoming what some consider the best tool for fire sprinkler design under $200. See more about it here.
The Questions on My List
The current code call checklist I use today has had items added and scratched over years of finding out what's important and what questions always get the same answers.
That being said, there's no real one defined list that matches everyone's preferences. What questions do you ask that you feel are important to the design that's not explicit in code? Comment below.
Join the Cause
Our line of work in helping save lives and property is extremely important, but you already know that. This site is built to help you excel in fire protection. If you're not already subscribed to these free weekly resources & articles, you can do so here for free.
Get Free Articles via Email:
+ Get calculators, tools, resources and articles
+ Get our PDF Flowchart for Canopy & Overhang Requirements instantly
+ No spam
+ Unsubscribe anytime
Get access to every tool, the downloadable Toolkit, Sprinkler Database, Calculators and more:
Joseph Meyer, PE, owns/operates his own Fire Protection Engineering practice in St. Louis, Missouri. See bio on About page.