I am a plans examiner. I examine plans to try and determine, within reason, that a proposed design will be in conformance to the code when it is constructed. I report my observations for code related issues. I don't consider the observations I make as code violations, since they are (supposed to be) in front of me before they are constructed. I restrict my comments to verifiable codes, and citing the code sections ensures I stay true to it. I view my purpose as pretty simple and definable with a few points of service:
-I try to identify a condition that will not pass field inspection once constructed, thereby saving time and money for applicants
-I try to identify a condition that requires further attention to specific codes so that once constructed it will be compliant
-I try to provide code related information to inspectors and constructors that if overlooked, will lead to a non-compliant condition once constructed
I don't pass or fail a review. I make comments, some of which require an answer from the applicant to help me determine if any of the aforementioned points of service need to be provided, or resubmittal because as a result of the comment a re-design is required, some of which don't, and are just alerts to the end users. (Some AHJ's want minimal redlines, some don't care, some DP's love them, some don't. That level of service is a moving target.)
The following is an example of an event from yesterday.
I had made a previous plan review comment to provide an accessible service counter in accordance with ANSI 117.1 904.3 because an accessible counter was not identified and I couldn't find an elevation that indicated they were aware of the requirement. The section I cited leaves them with two options, they can pick whichever they want. A response came back with a 30" wide, 36" tall counter, without knee/toe space, (a parallel approach). I could return another marked plan and provide them with another more specific comment for a parallel approach. I could also pick up the phone, call the DP and explain the concern. I chose the latter, and asked if I could simply red-line the plan to either provide a 36" counter for parallel approach, or provide a forward approach. This way I could move the plan forward without further delay. I explained that my job was to try to avoid a situation where the field inspector would go in and "fail" the condition and cause delays and expenditures a few months from now, by addressing it with minimal delay and no expenditures today.
I provided the nature of the condition that needed addressed, and the code section to guide them to the options. They didn't pay close enough attention, so I took further steps. (in this case they didn't want a red-line, but revised the drawing and I had it within a few hours, and still turned the plan over the same day). The DP was very happy with the end result.
I view my position as a service, and in many cases it is optional depending on the nature of the work and the rules of the AHJ. The value in a plans examination is to identify issues before they cost money, and hopefully in a more comprehensive manner than a field inspection since more time is afforded and a more holistic approach can be used. My methods save time and money for the applicants, and time and confusion for the inspectors. I humbly submit that I am a helpful part of the process, not a hinderance, although that belief is probably not shared by all.
So, a very long winded narrative on why I use code citations. My goal is to advance plans to issuance as quickly and efficiently as possible with savings for end users. Code citations serve to ensure I am not over-stepping, expedite responses by avoiding confusion, and explain my concerns and offer pathways to answers. Not everyone has the time, motivation and support to do it the same way, but I think if they did, they might find some value in it, and I think the end users would to.