2.1 Document Control, Records Retention Schedules & Revision Tracking

Document Control as a Review Skill

NFPA 1030 JPR 8.2.4 requires processing plan-review documents so required permits are issued according to AHJ policies. Document control makes the technical review traceable: a reader should be able to determine what was submitted, which revision was reviewed, what deficiencies were communicated, and what the authorized disposition covered. It supports later field verification and future alterations without treating a permit file as an informal collection of email attachments.

Start by assigning the project its tracking identifier and recording the applicant, site, scope, received date and included documents. Check the AHJ’s completeness criteria. Professional seals, signatures, file formats and submission methods depend on the applicable law and published procedure. Do not invent a universal PDF/E requirement, demand a particular commercial review platform, or assume a pasted seal is legally valid in every jurisdiction.

Build a Reproducible Submission Register

A submission register lists the plan sheets, calculations, specifications and supporting reports together. A sheet number alone is insufficient when several versions exist. Capture each document’s revision and date, then associate the review comments with that version. The calculation package should identify the same system and layout as the drawings. A revised sprinkler plan paired with an old hydraulic report is an incomplete evidence chain even if both files open successfully.

An electronic approval mark should identify the issuing authority and scope. Retain an unambiguous approved set and prevent later working copies from being mistaken for it. Access controls, backups, audit trails and signature validation can support integrity. Their specific technology should follow the AHJ’s system and the governing professional-signature requirements; a study guide cannot establish their legal sufficiency.

Review Revisions Without Losing Context

A revision cloud highlights changed drawing content, and a delta marker can connect the change to a revision register. These are useful drafting conventions and may be required by the submission procedure. Ask for a response identifying how each deficiency was resolved, with sheet references and updated calculations. Preserve the previous review rather than overwriting it with the applicant’s response.

Clouds help direct attention but do not prove that every relevant change was disclosed. Compare versions and consider consequences outside the highlighted area. If a new partition moves the smoke boundary, check detector coverage, sprinkler obstructions, exit access, door hardware and the cause-and-effect matrix. A clouded architectural revision can change an unclouded fire-alarm assumption. Record additional review needs instead of restricting examination mechanically to the clouds.

For example, revision 2 shows a corridor through an open office. Revision 3 adds a storage room that projects into the route. The reviewer should verify the corridor width and travel path, determine the new room’s protection requirements, and reconcile system layouts. A response saying “all comments addressed” is not evidence that these dependencies were checked. Conversely, a change in a title-block phone number does not justify inventing a new hydraulic calculation requirement.

Retention and Disclosure Are Different Questions

Records retention determines how long a record must be kept and how disposal is authorized. Public disclosure determines whether a requester may receive it and what exemptions, redactions or procedures apply. A record can be retained permanently while containing information subject to a particular disclosure restriction. The examiner should not confuse these two decisions.

Use the applicable state or local retention schedule and the AHJ’s records-management procedure. There is no single NFPA-mandated lifetime-plus-years retention period for every municipal plan file. Litigation holds, investigations and other preservation duties may suspend normal disposal. Identify the official record copy, responsible custodian and backup arrangements; do not delete a superseded drawing merely because the current revision has been approved.

In the United States, federal Freedom of Information Act rules govern federal agency records; state and local agencies generally follow their applicable state public-records laws. Security-sensitive or proprietary plans may have relevant protections, but a facility’s label does not automatically exempt every drawing. Refer a request to the designated records official and counsel. Apply the actual exemption and required segregation/redaction process rather than automatically releasing everything or denying the entire request.

Closing the Record

At closeout, reconcile the approved drawings, accepted revisions, inspection records, test reports and record drawings. Identify outstanding conditions and who resolved them. Store performance-based limitations and O&M documents where future reviewers can find them. A later change of use should trigger access to those limitations rather than a search through individual employees’ inboxes.

The exam habit is to follow a document from intake through disposition while preserving its identity and dependencies. A clean file is not merely tidy: it lets another competent reviewer reproduce the technical basis, understand the authorized work and recognize when a later proposal changes the assumptions.