Yes, I agree with your statement, just not with where and how those requirements may be indicated. I make compliance indications via my plan review comments, and let the RDP make the revisions they need to meet those requirements, plus any other revisions that might be required due to meeting those requirements. As an example, on my last review, I did not mark up the non-compliant CPT distance by adding an additional exit, which is what the code requires when the CPT exceeded 75' for this projects conditions. Rather, I made my comment specifically, indicating which code sections were applicable when the CPT exceeded 75 ft for a single exit space, and allowed the RDP to design their solution and amend their CDs. We communicated over the phone and internet, as too other compliance issues their alternative solutions may or may not cause, and eventually they were able to submit a complaint design that reduced the CPT to less than 75', thus not requiring an additional exit, but required extensive revisions to the CDs, that could not, in my opinion, be simply red-lined. I have stated the other reasons why I don't mark-up RDP plans, and that is also our current departmental policy. Furthermore, I do not have any objections to marking-up an RDP plan that will not be issued as field construction document for the purposes of plan review. That is not altering the design, or making design decisions, without RDP oversight, but rather assists in the analysis and review for code compliance. Neither policy is necessarily a better policy, simply different, and we simply and respectfully disagree.