We have found that one of the best ways to improve the permitting process is the development of a code data sheet(s). We have a standard code data sheet that includes all the code, zoning, occupancy, building type and construction type information. It also includes a plan(s), which show all rated walls, room sizes, occupancy capacities, exit separations, travel paths and distances, and exit capacities. We review this with the code agency in the preliminary meeting and include it in the front of the document set. This makes it easier for them to find the information they need for their review. It works to expedite the process. Tom
——————————————-
Thomas Dwyer AIA
Thomas A. Dwyer AIA
Scottsdale AZ
| I agree with having a code sheet, which can also be a “life safety plan”. Here in CA, for school submissions to DSA, we also have a separate fire dept sheet showing the fire lanes and with the local FD jurisdiction signoff so that sheet doesn’t get ‘marked up’ during plan check. We’ve used “life safety plans” for our medical projects as the wall fire and smoke rating indicators get very confusing when mixed with everything else on a typical architectural floor plan.
Depending on the project’s complexity there may be more than one ‘code sheet’ in the front of the set. For example a sheet with room and building exiting capacities may be separate from the code sheet showing occupancies, separations and construction types. We try to keep all of the code sheets and informational sheets out of the “A” drawings to separate them from construction and detailing, so as a rule we use “G” [for general] in the front of our sets. It’s a lot easier to tailor the presentation of code review requirements to the AHJ the project will be reviewed by while keeping your ‘regular’ document standards typical as well. ——————————————- |
|