One of the things I feared most when I had my first real job was that I was going to be exposed as a complete fraud.

Yes, I had a degree. That degree had a grand total of 9 credit hours specifically to fire protection, which statistically is more than roughly 90% of our industry starts out with.

But, see, the problem was… that I knew nothing.

I knew this.

But my fear was that when I made my first phone call to someone on the other line, they’d quickly know this too.

​And that all came in the form of my first ‘code call.’

THE CODE CALL
We used the term code call, I don’t know what you might call it, but it’s just a touchpoint check in with the AHJ to be sure that (1) we’re on the right track with applicable codes and standards, and (2) that we coordinate jurisdictional needs.

What good is a set of engineering bid plans, if we halfhazardly threw an FDC in the wrong spot? Or the fire alarm control panel? If we referenced the wrong codes? If we stipulated too low of a hydraulic safety factor? If we located the hose connections on the wrong landings?

The answer is no good at all. If we’re not helping clarify and coordinate the needs of the project with the jurisdiction, then we, as consultants, are simply getting in the way and making things more difficult than they need to be.

IMPOSTER SYNDROME
​Back to that phone call.

How long would it take for the person on the other line to realize that I knew very nearly absolutely nothing about fire protection?

That if they asked one clarifying question, it would call my bluff and I’d have no escape? Ten seconds? Twenty seconds? It wasn’t an irrational fear, nor was it overwhelming.

I made that call. And more after it. And I did make a fool of myself. I once asked “do you require duct detectors to be located on the supply side, return side, or per code?”

The response: “Why would it be anything other than per code?”

Ope. Game’s up. I have no idea. Time to pack the bags and find a new career.

 
All drama aside, I survived. Sometimes failed. I learned. I slowly grew to understand the purpose behind our list of questions.

Who were these people I was calling?

That’s half the game. Sometimes it’s a Fire Marshal. Sometimes it’s a plan review as part of the building department. Or fire department. Sometimes it’s the volunteer combination of Fire Chief/Marshal/Inspector/Reviewer.

Sometimes they were the nicest people I’ve ever met. Sometimes hostile. Just goes with the territory.

I’ve had jurisdictions that wouldn’t pick up the phone unless I called from a local area code. And I’ve had others apologize because they wouldn’t be able to run a flow test for me until Monday morning. (I had called on a Friday. At 4:45pm). 

Diatribe aside, I’d like to share the list of questions that I ask – (1) – so you can critique and help us all improve upon the list of questions – and (2) – so that future generations of inexperienced callers might not have to suffer the imposter syndrome that I did with those first few calls.

WHO IS THIS FOR?
Here is my developed list of questions that I would ask today for a code call. This is very specifically used for consultants to coordinate requirements with AHJs before a bid set is issued.

Why isn't this used for contractors? Would I ask this when doing shop drawings?

No; I might coordinate FDC types and locations. Coordinate standpipes. Coordinate some fire alarm or waterflow questions. However, a designer at the shop drawing stage is not the person to determine the scope. They can and should coordinate, but not determine scope.

A consultant's role is to determine the scope, so principally these questions are supposed to happen before bids ever take place. These do have cost impacts.

MY LIST OF QUESTIONS (AND NOTES)
Below it is a very short  context for why I ask the question. Code basis can wait for now. This is long enough as is.

What I ask from you is what you would tweak?

If you’re an AHJ, how can I better ask the question?

How can I better clarify the intent of the question?
 
OPEN-RESOURCE FOR CODE CALLS
We’re actively working on an open and free tool just for code calls. Some time ago we tried a spinoff code call database, but the enthusiasm for jurisdictions to volunteer information wasn’t something that we could get to scale.

So I’d like to try this from a different angle.

My hope is that, if we construct this open tool right, and educate around the process in the open, it could be a tremendous resource for both designers and AHJs to meet in the middle and have coordinated projects that meet the needs of each jurisdiction.

Easier and better results, every time.

So, here’s the list of questions that I would ask today, almost like a script.

My own personal notes are italicized below each question.
 
BRIEF INTRO
Thanks for taking my call. I’m Joe Meyer, designing the [project] at [address]. It’s going to have [fire alarm/sprinkler/standpipe system(s)], and I’d like to ask you a few questions to make sure we’re coordinated with your department. Should take about five minutes. Is that OK?
  → Note: If the time isn’t good, or they’d prefer an email, I’d go that route instead.
 
APPLICABLE CODES & STANDARDS
1. Great. Your website says you’ve adopted the [2012/2015/2018/2021/2024 IBC or NFPA 101], is that correct?
  → Note: Doing the research ahead of time is key. Without it, it makes the listener feel like they’re doing the work.
 
2. Do you adopt any specific editions of NFPA standards like NFPA 13, 14, or 72, or just whichever edition is referenced by your building code?
  → Note: Many people don’t know this, but IBC Chapter 35 and NFPA 101 Appendix D or E will actually list which editions of NFPA standards are referenced. Some jurisdictions will adopt very specific editions, which is why I like to ask the question here.

Following questions noted with an asterisk (*) are only asked if necessary.

FIRE ALARM*
3. For fire alarm, we intend to locate the main control panel in [front entry/main electrical room/a back of house area]. If we do so, do you require an annunciator panel at the building’s front entry?
  → Note: For small buildings with one main entry where the FACU is located near the entry, no annunciator is usually needed. For larger or more complex buildings, when we might not want the FACU at the front entry, having an annunciator at the front is a very reasonable need.
 
4. Does the fire alarm monitoring require a listed Central Station Service, or is standard code-required monitoring, like a supervising station, acceptable?
  → Note: Jurisdictions that require a listed Central Station service usually know what it is, and will recognize that it’s required. It’s more expensive and carries more stringent requirements than a normal supervising station, which is a code-minimum requirement.
 
DUCT DETECTION*
5. When duct detectors are needed, do you simply require locations to be per [the IMC/NFPA 90A], or do you require duct detectors to be located in specific locations, like the supply or return side of units in the ductwork?
  → Note: This is a question I could use help with. A simple ‘per code’ answer is wanted here, but some jurisdictions have insisted on locating duct detectors on the supply-side of units, or return-side, or both. If the jurisdiction has a specific requirement, I’d like to know that now rather than be surprised later, but most usually don’t, and as a result, it’s a lame question to ask in those cases.
 
6. Do you require duct detectors to initiate an alarm signal, or is it OK to have those report a supervisory signal to the fire alarm control panel?
  → Note: NFPA 72 allows duct detectors to initiate a supervisory signal, because they’re more prone to nuisance alarms than other devices. An alarm signal usually results in a truck rolling up to the building each time. Jurisdictions that are familiar with this topic are usually more than happy to have duct detectors on supervisory rather than alarm.
 
7. When a duct detector activates, can it shut down just that unit or do you require all units to be shutdown?
  → Note: To my understanding, this is just a preference. Not a huge deal either way unless we’re talking about a massive building or building complex where all units shutting down would be very uncomfortable and problematic.
 
SECURITY / KNOX BOX
8. Do you require a Knox Box?
  → Note: There’s likely a code path for this, but it’s not something I’ve hunted down to date. Most jurisdictions can readily answer this.
 
9. Is the Knox Box required to tie to the fire alarm system?
  → Note: These can be monitored by the fire alarm system. Most jurisdictions don’t require them to be monitored, but some will in areas that have higher crime rates.
 
FIRE SUPPRESSION - FIRE DEPARTMENT CONNECTION*
10. Do you mandate a maximum distance from a fire department connection to a nearest hydrant?
  → Note: Some jurisdictions care, others less so. There’s (to my knowledge) not a mandated distance, but some jurisdictions will require as close as 50 ft and others as far away as 400 ft.
 
11. Can the FDC be mounted on the building’s street-facing exterior wall, or does it have to be located remotely from the building?
  → Note: As a designer, my strong preference is to have the FDC on the building to save cost, protect the pipe from freezing, protect the pipe from mechanical damage, keep it clear from snow, and keep it easier to inspect, maintain, or repair. Operationally, depending on the building and the site, some departments are not going to want to send firefighters to the building face and would rather have a remote connection for some applications.
 
12. What type of FDC do you use [Dual-Inlet 2-1/2” / 4” Storz / 5” Storz]?
 
13. Do you require locking caps on the FDC?
  → Note: Some jurisdictions will have locking caps to prevent people from shoving debris, trash, or other ‘items’ into FDCs, and to prevent theft of the caps. Many areas have no need for locking caps.
 
BACKFLOW*
14. What type of backflow preventer do you require [double check, double check detector, RPZ, or RPZ detector]? We [will/will not] have antifreeze or chemical additives in the system.
  → Note: Some jurisdictions, like fire departments, may not want to answer this because it’s under the building or water department. But most are familiar with the requirements anyways. Some places require RPZs for everything fire protection (like an Illinois state mandate). By code, RPZs are required if an antifreeze system is used, or if chemical additives are added to the system (such as corrosion inhibitors like Vapor Pipe Shield).
 
15. We intend to locate the backflow inside the building. Is this acceptable?
  → Note: This is a designer preference for longevity of the backflow, protection from damage and tampering, protection from freezing, service, maintenance, and cost. Some owners may want the floor space or jurisdictions might require it to be outside (though I don’t know why).
 
16. [If a double check is allowed, allowed to be inside, and there is only a single zone] We intend to use a backflow preventer that’s listed for a vertical orientation. Is it acceptable to install it vertically?
  → Note: RPZs have to be horizontal. If we have single-zone systems, designers generally prefer to use a ‘shotgun’ approach and save floor space. This is usually fine.
 
HYDRAULICS*
17. Do you mandate a safety factor for fire sprinkler systems?
  → Note: This is a topic that is book-worthy. NFPA 13 has no mandate other than to account for seasonal and daily fluctuation. It could be argued that a safety factor is implicit within NFPA 13. But to save everyone’s time and scrutiny, a simple 5 PSI or 10% safety factor tends to be common practice. Too high a safety factor isn’t necessarily a good thing because it could lead to needing a fire pump that introduces many new points of failure or could add unnecessary cost to a system.
 
18. Does your department conduct flow tests, can we conduct a flow test, or are those done by the water department?
  → Note: This is just practice-based by jurisdiction. Some don’t allow flow tests at all and use water modeling (California).
 
INSPECTOR'S TEST*
19. [If there are only wet systems] We usually locate the inspector’s test at the riser, which NFPA 13 allows for wet systems. Do you require it to be located remotely?
  → Note: If this is a dry or pre-action system, then the inspector’s test must be remote. If it’s wet, it’s allowed to be at the riser. That said, some jurisdictions have a preference which we’d want to accommodate here.
 
WATERFLOW*
20. Do you want a horn/strobe, or electric bell on the outside of the building for waterflow?
  → Note: Just a jurisdictional preference. Either of these are easier to accommodate than a water motor gong which had been the tradition for some time.
 
21. Is exterior access required for the sprinkler riser room?
  → Note: These are usually on the outside of the building since the water service entry cannot go more than 10 ft underneath the building without open trenches, per NFPA 13, but sprinkler riser rooms don’t always have an exterior door.
 
SITE
22. Just a few more questions. Do you require a post-indicating valve? There are no code mandates for one.
  → Note: Some jurisdictions want them, many don’t care. Just an opportunity to coordinate it early here.
 
23. Is Fire Flow ok to be determined using the International Fire Code Appendix B, or do you have some other method to calculate it?
  → Note: Fire Flow is wildly misunderstood and falls through the cracks of design scope. As a result, many jurisdictions don’t pay attention to it or aren’t familiar with it. If they don’t know or don’t care, Appendix B is a fine approach to use.
 
FIRE PUMP*
24. We have a fire pump on this project. Do you consider the electric power supply to be Reliable or not?
  → Note: NFPA 70 has specifics on how power is considered to be reliable or not. There are formal definitions, but it’s up to the AHJ on whether they consider the power utility at the site to be reliable or not. If it’s a point of contention or needing clarification, it’s worth spending time here because the cost to go from an electric fire pump to a diesel or add a generator can be substantial.
 
STANDPIPES*
25. We intend to have a [wet/dry manual/semi-automatic/automatic] standpipe system for this building, using [Class I 2½” / Class II / Class III] hose connections.
  → Note: In sticky projects using dry standpipes or high-rises, the type needs to be coordinated. In basic non-high-rise situations, a wet manual system is fairly straightforward, so it’s not a question as much as a coordination point.
 
26. We intend to locate hose connections on the floor level landings of stairs. Is that acceptable?
  → Note: The IBC and NFPA 14 have jogged back and forth on this, but they now correlate on the main-floor-level landings of stairways for hose connections. AHJs are permitted to require intermediate-level landings in both the IBC and NFPA 14, though, so it’s an important coordination point.
 
Thank you SO much for your time. Any questions for me, or anything else you feel I should have asked?


YOUR TURN
Alright - it's all out there - what would you tweak?

If you’re an AHJ, how can I better ask the question?

How can I better clarify the intent of the question?

What am I missing? Would absolutely love your commentary below. Your input can make this new collaborate tool much more helpful and hopefully impactful for the industry as we launch it and hopefully move things forward.

See you in the comments ↓↓

- Joe