When it comes to fire protection and fire codes, the details matter—especially the language used in the codes and standards that govern life safety systems. At Oliver Fire Protection, we often encounter questions from building owners, contractors, and even industry professionals about the difference between the words should and shall in fire codes. It might seem subtle, but understanding the distinction can have a major impact on compliance, safety, and liability.

Why Wording in Fire Code Matters

Fire codes like those from the National Fire Protection Association (NFPA) and the International Code Council (ICC) are legal documents. Every word is chosen deliberately and carries specific meaning. This isn’t just technical jargon—it’s language that can determine whether a system passes inspection or, even more critically, whether it protects lives during a fire emergency.

“Shall” vs. “Should”: What’s the Difference?

In code language:

• “Shall” means mandatory. If a standard says something “shall” be done, it’s a requirement. It must be followed, and not doing so can result in code violations, fines, or worse—unsafe conditions.
• “Should” means recommended. It’s considered best practice, but it’s not legally binding unless adopted by a specific jurisdiction or contract. Following a “should” recommendation might improve system performance or safety, but failing to follow it won’t necessarily result in a violation.

Real-World Example: Sprinkler System Design

Let’s say the code states:
“Sprinkler heads shall be spaced no more than 15 feet apart.”
That’s not a suggestion—it’s a rule. Install them further apart, and you’re out of compliance.

Now imagine the code says:
“Sprinkler heads should be placed to avoid direct discharge onto HVAC equipment.”
In this case, it’s a recommendation. It’s wise to follow it, but if there’s a reason you can’t (say, due to structural limitations), you may still be in compliance as long as the mandatory requirements are met.

Common Misunderstandings in Code Interpretation

Misreading code language happens more often than you’d think. Here are a few examples we see regularly:

• “Should means optional.”
  Not exactly. “Should” is advisory, but it’s based on real-world experience. Ignoring it might not be a code violation, but it could still create functional or safety problems.
• “We can get around a ‘shall’ with AHJ approval.”
  Only in rare cases. The Authority Having Jurisdiction (AHJ) has some flexibility, but “shall” clauses are typically enforced strictly—especially when they relate to life safety.
• “Older buildings are exempt.”
  Not always. Some “shall” requirements may apply to existing buildings depending on local amendments, renovation scope, or occupancy change.

Why This Matters to You

For our customers, understanding these terms helps clarify what’s required by law versus what’s simply advised for best performance. You don’t want to find out after the fact that a “shall” was treated like a “should”—especially during an inspection or incident investigation.

For our industry peers, clarity on code language ensures we give clients correct and defensible guidance. It also strengthens our relationship with AHJs and helps avoid costly redesigns.

FAQ: ‘Should’ vs. ‘Shall’ in Fire Code

Q: Can my system still pass inspection if I ignore a “should”?
A: Technically, yes. But if the “should” is related to system performance or safety, ignoring it could cause long-term issues.

Q: Who decides what counts as a “shall”?
A: The code writers (NFPA, ICC, etc.), but the AHJ interprets and enforces these terms locally.

Q: What happens if I violate a “shall”?
A: You’re non-compliant. This can lead to failed inspections, legal consequences, or increased liability.

Navigating Code Language with Confidence

Here are a few tips from the team at Oliver Fire Protection:

• Never assume “should” and “shall” are interchangeable.
• When in doubt, ask your local AHJ. They have the final say on interpretation.
• Stay current with code editions—language and requirements can evolve.
• Treat “should” as a safety flag. It’s often based on field-tested best practices.

Need Help Interpreting Fire Code? We’ve Got You.

The language of fire protection can be technical, but it doesn’t have to be confusing. At Oliver Fire Protection, our experts are here to help you understand what’s mandatory, what’s recommended, and what’s best for your property.

Let’s make sure your fire protection is done right—from design to compliance.

Reach out today for a consultation!