Last week I received an email from an architect, asking if I would update a post from 2009.  Naturally, I was curious about how this old information was being used.

The topic of the 2009 post was temperature rise fire doors.  These doors limit the transfer of heat from one side of the door to the other during a fire, and are required by the International Building Code (IBC) for opening protectives on some interior exit stairways, ramps, and exit passageways.  Each edition of the IBC includes an exception stating that these doors are NOT required if the building is equipped throughout with an automatic sprinkler system.

The architect requesting the update had been submitting a copy of my 2009 post to the code officials on projects where temperature rise doors were not required because of the presence of a sprinkler system.  Because the post was written so long ago, the code references were outdated and did not include the edition that had been adopted in their current project’s jurisdiction.

I created an updated document for the architect to submit to the code official, but this request made me think about whether this type of summary is needed for other topics.  Are there other issues that I should address in a simple document that could be shared easily?  Something cleaner than printing out a blog post?

Check out the temperature rise summary here, and let me know if there are other topics that would be helpful for me to cover in a similar summary.  Maybe there are questions that come up frequently, where a simple document would be handy?

WWYD?

You need to login or register to bookmark/favorite this content.