• Welcome to the new and improved Building Code Forum. We appreciate you being here and hope that you are getting the information that you need concerning all codes of the building trades. This is a free forum to the public due to the generosity of the Sawhorses, Corporate Supporters and Supporters who have upgraded their accounts. If you would like to have improved access to the forum please upgrade to Sawhorse by first logging in then clicking here: Upgrades

why I hate "policies"

P

peach

Registered User
Joined
Oct 17, 2009
Messages
2,834
Location
metro DC
They aren't codified, for one thing..

We failed an inspection yesterday because they didn't have AFCI's for all bedroom "outlets" which does not mean receptacles.

Jurisdiction doesn't agree since "you can't plug anything into the smoke detector or light fixture".. not what the code says.

Jurisdiction policy. Not code.. not local amendment.

Quit writing technical "policy".. bad medicine.

Thanks
 
I kinda agree

but thought code allowed it, at least the fire code sorry do not have the books

also if you are in a place that allows the city to admend the code, and yyou stick the policies in admendments, you wind up with another admendment code book thick as the base code
 
Peach is correct, in that "outlet" includes more than just a receptacle. I have not seen much written "policy", just word of mouth about what the local AHJ looks for or notices. It leads to the modern myth among trades that "every county's codes are different". In our state building, fire, and accessiblity are statewide. Localities are required to cobble their own admin procedures, which get state review.
 
Administrative policies often serve as a more formal definition or interpretation to "everybody having their own interpretation", and can help the code enforcement process serve the public. It depends more on the quality of the policy, requiring careful consideration and drafting, than it does simply having them. Bad policies are a negative. Good policies are a positive.
 
made them spell it out in an e=mail... save it for a rainy day. Need to include "policies" the next time you codify code amendments; make it law that everyone can read.. not just available once you start asking them.
 
Actually, that is exactly what I do. If I feel the need to commit an interpretation to policy, then at the next opportunity, I will codify it via ordinance, so it is out there. Unless it is more of an administrative nature, that just doesn't fit in a code, policies are really amendments to the code, waiting to happen. (and I really don't like having a bunch of amendments)
 
The change from receptacle to outlet occurred between the 1999 NEC where the AFCI requirement was introduced and the 2002 NEC - so yes, different jurisdictions can enforce the code differently.
 
It can be enlightening to READ the DEFINITIONS (outlet)...just sayin'...agree with peach. Thanks also to brudgers for pointing out the NEC language change.

From 2006 IBC:

104.1 General.

The building official is hereby authorized and directed to enforce the provisions of this code. The building official shall have the authority to render interpretations of this code and to adopt policies and procedures in order to clarify the application of its provisions. Such interpretations, policies and procedures shall be in compliance with the intent and purpose of this code. Such policies and procedures shall not have the effect of waiving requirements specifically provided for in this code.

If your going to create a policy it's not supposed to make things worse.
 
We write "Guidelines" to help the public and staff follow our interpretation of the code....we also reference our guidelines in our amendments. Probably not the best way, but it works for us.
 
You must log in or register to reply here.
Top