Study guide
9.3 Record Drawing Updates After Changes
NICET Fire Alarm Systems Level II Exam
Track your progress as you read
Finished sections get a check mark.
1 Exam Overview & Open-Book Strategy
1.1 Exam Facts, Eligibility & Logistics 1.2 Open-Book References & On-Screen Navigation 1.3 Certification Path & Performance Measures
2 Installation: Work Planning
2.1 Work Plans from Field Conditions 2.2 Drawings, Specs & Code Interpretation 2.3 Jobsite Safety & Trade Coordination
3 Installation: Circuits, Pathways & Survivability
3.1 Pathway Classes A, B, C, D, E, N & X 3.2 Survivability Pathway Levels 0–3 3.3 NEC Article 760, NPLFA/PLFA & Raceways 3.4 SLC Topology, T-Taps & Supervision
4 Installation: Equipment
4.1 Initiating Devices (Level II Applications) 4.2 Notification Appliances & NAC Design 4.3 Control/Monitor Modules & FACU Hardware 4.4 Voice EVACS Speakers & Intelligibility Basics
5 Installation: Commissioning
5.1 Acceptance Testing & Commissioning Sequence 5.2 Record of Completion & As-Builts 5.3 Functional Verification of Interfaces
6 Installation: System Interfaces
6.1 Elevator Recall Phase I & II 6.2 Shunt Trip & Heat Detector Placement 6.3 HVAC Shutdown & Duct Smoke Detectors 6.4 Suppression Interconnections (Waterflow, Tamper, Releasing, Clean Agent, Hood)
7 Maintenance: Periodic Testing
7.1 ITM Framework (NFPA 72 Chapter 14) 7.2 Device Test Methods & Frequencies 7.3 Interface, Waterflow & Tamper Tests 7.4 EVACS, Elevator & Special Function Tests
8 Maintenance: Impairments & Troubleshooting
8.1 Impairment Programs & AHJ Notification 8.2 Troubleshooting SLC, NAC & Power Faults 8.3 Corrective Actions & Retest Requirements
9 Maintenance: Documentation
9.1 Required Records & Retention 9.2 Inspection & Test Reports 9.3 Record Drawing Updates After Changes
10 Submittals: Shop Drawing Packages
10.1 Shop Drawing Package Contents 10.2 Cut Sheets, Calculations & Sequence of Operation 10.3 AHJ Submittal Expectations
11 Submittals: Site Survey
11.1 Occupancy, Construction & Fire Protection Features 11.2 Layout Constraints & Field Verification 11.3 Pathway Routing & Survivability Field Checks
12 Submittals: Basic Technical Drawings
12.1 Symbols, Risers & Floor Plans 12.2 Zone Schedules & Legends 12.3 Drawing Notes for Voltage Drop & Conduit Fill
13 Submittals: Power Supply & Loading
13.1 Standby & Alarm Load Basis (24 h + 5/15 min) 13.2 Battery Sizing with 20% Aging Derating 13.3 Voltage Drop Calculations 13.4 Conduit Fill & Wire Sizing (NEC Chapter 9)
14 Layout Knowledge: Supervising Station
14.1 Supervising Station Types (Chapter 26) 14.2 Transmission Paths & 90-Second Alarm Window 14.3 Protected Premises vs Supervising Station Roles
15 Management & Supervision
15.1 Coordinate Work Activities 15.2 Reporting Progress & Problems 15.3 Ethics & NICET Code of Conduct 15.4 Safety Leadership & Multi-Trade Coordination
9.3 Record Drawing Updates After Changes
Key Takeaways Explain This Topic AI
Update record drawings when devices are added, removed, or relocated; when pathways/circuits change; and when zoning or programming logic changes the operational map of the system
Field red-lines and revision clouds capture changes immediately; formal as-built revisions follow so the site set matches reality
Software configuration backups and version identity are part of record control after programming changes—drawings alone are not enough on modern FACUs
Level II technicians mark up accurately, escalate design conflicts, and never leave silent field changes that future ITM or emergency responders cannot see
Last updated: August 2026
9.3 Record Drawing Updates After Changes
Quick Answer: Whenever the installed or programmed system no longer matches the site record set , update the records. That includes device adds/moves/removals, pathway or circuit changes, and zone/matrix programming changes. Use red-lines in the field, revision clouds and revision blocks on formal drawings, and software backups with version IDs for configuration. Level II technicians own accurate markups and honest communication—not silent “it works now” changes.
Section 5.2 covered as-builts at original acceptance. Domain 2.2.3 returns to drawings because maintenance years are when records decay: renovations, tenant fits, NAC boosters, detector replacements with different addresses, and “quick” program edits. A system can still alarm while its drawings lie.
Why Post-Acceptance Drawing Control Matters
Record drawings drive:
- Periodic testing routes and device inventories
- Impairment scope (“which devices are on this circuit?”)
- Emergency responder understanding of FACU zones and building layout relationships
- Future design work and AHJ reviews for modifications
- Battery and voltage-drop validity when loads move or grow
Scenario: A tenant build-out adds eight notification appliances on NAC-2 and relocates four smokes. Nobody updates drawings or battery calcs. Two years later annual testing misses two new appliances hidden above a new cloud ceiling, and a battery replacement undersizes secondary power because the calc still shows the old load.
When As-Builts / Record Drawings Must Be Updated
Use this trigger table. If the field or program changed in a way that affects location, circuiting, or operational understanding, mark it.
Change type Drawing / record impact Related records to touch
Add device Floor plan symbol + schedule/address Point list, battery/VD calcs if load grows, sequence if new function
- Remove device Delete/cloud removal; note reason Point list, calcs if load drops materially
- Relocate device New coordinates/room callout Same circuit notes if home-run changes
Change candela / candela setting / candela-marked appliance Schedule and sometimes plan note VD calc if current draw changes
Pathway / circuit reroute Riser, plan route, junction notes; survivability notes if applicable Class A/B/X documentation, EOL locations
- New booster / power supply Plan + riser + panel schedule Battery calcs, circuit directories
- Module added for HVAC/elevator/door Plan location + interface note Sequence of operation matrix
Zone map / label / group programming change Zone schedule, annunciator map, matrix sheets Software revision archive
FACU replacement or major CPU/program rewrite Often full record refresh ROC/reacceptance docs, full software backup
Device adds, moves, and removals
Any physical device change that would mislead a tester using the old plan requires a mark. Relocations of a few feet still matter when ceiling clouds, hard lids, or room numbers change search patterns. Removals without drawing updates create “ghost devices” that inflate test scope and hide unauthorized deletions of required coverage.
Pathway changes
Cable reroutes, added T-taps (where permitted by design/class), isolator additions, conduit pathway moves for survivability, and EOL relocations belong on risers and critical plan notes. Survivability-level pathways are especially sensitive: a “temporary” sleeve through a nonrated path that becomes permanent is both a code and documentation problem.
Programming and zone changes
Not every soft edit needs a new architectural floor plan, but operational records must track:
- Zone/partition renumbering
- Label changes that AHJs and responding firefighters rely on
- Cause-and-effect matrix changes (which inputs drive which outputs)
- Network node maps on networked systems
If the annunciator LED formerly labeled “Floor 3 West” now means a different geographic area after a remodel, the zone map is wrong even if no smoke moved.
Exam trap: Believing “as-built updates only apply at original CO.” Maintenance-era changes create the same need for truth in drawings and configuration records.
Red-Line Practices
Red-lines are immediate field markups on a controlled print or electronic markup layer. Discipline:
Mark as you go , not at demobilization from memory.
Use consistent symbols: add, delete (X with cloud), relocate (arrow from old to new), note circuit IDs.
Initial and date each significant markup set.
Keep red-lines in a known place (job folder / site cabinet “working set”) until formal revision.
Never have three conflicting red-line sets with no “current” designation.
Good red-line habit Bad red-line habit
Cloud around changed area with note “SD moved 6'-0" north, new addr L1D077, 2026-08-05 JR" Scribble without address or date
- Separate delta sheet listing all adds/deletes Pencil dots nobody can interpret
- Photo of ceiling coordinates attached to PDF markup “I’ll remember” oral history
- Sync with panel point printout the same day Red-line plan vs panel addresses diverge for months
Red-lines are temporary control , not a permanent excuse to avoid issuing a revised record set. For small service work, a clearly revised single-line plan and updated schedule in the site cabinet may be enough under the contract; for larger mods, formal shop revision and AHJ re-submittal may be required. Level II technicians follow the project’s document-control process and escalate when scope exceeds markup-only authority.
Revision Clouds and Revision Blocks
When drawings are formally revised:
Revision clouds (and deltas) highlight what changed so reviewers do not re-read the entire sheet blindly.
Revision blocks record revision number/letter, date, description (“Add 6 speakers Area B; update NAC-2”), and approver as required by the firm’s CAD standards.
Superseded sheets are marked obsolete so the site cabinet does not contain two “current” Floor 2 plans.
Scenario: Contractor issues Rev C with clouds around new devices but leaves Rev B unmarked in the FACU cabinet. An ITM tech uses Rev B and fails to test new appliances. Document control failed even though Rev C existed in email.
Site set rules of thumb:
One current record set at the approved location.
Obsolete prints removed or boldly stamped SUPERSEDED.
Electronic folders use clear names ( Record_FireAlarm_Floor2_RevC_2026-08-05.pdf ).
Owner receives the current set, not only the installing salesperson.
Software Configuration Backups & Version Control
Modern systems are software-defined. Drawing updates without program control still leave a hole.
What to capture after programming changes
- Artifact Purpose
- Revision ID / date / checksum (or manufacturer equivalent) Identifies accepted configuration
- Offline backup file Recovery after CPU/panel failure or corruption
- Change log Who changed what matrix rows and why
- Password / access-level notes (controlled distribution) Prevents unauthorized life-safety edits
- Point list export Reconciles field devices to program
- Level II version-control habits
Before editing, save a pre-change backup labeled with date and reason.
After editing, save a post-change backup ; confirm the panel shows the new revision identity.
Retest affected cause-and-effect rows (and document the retest—Section 9.2).
Update sequence-of-operation sheets when matrix behavior changed.
Store backups with the owner package and company file—not solely on one laptop.
Do not “borrow” passwords in ways that leave the system without an authorized access path for the responsible party.
Trap: Restoring an old backup to clear a trouble and accidentally rolling back a year of legitimate zone changes—without comparing revision IDs first.
Trap: Changing elevator recall groups in software while floor plans and firefighter instructions still show the old primary floor narrative.
Level II Role Boundaries
Level II should Level II should not
Red-line actual device moves and circuit changes discovered or performed Silently delete required devices from drawings to match an incomplete install
Update point lists and attach panel exports after address changes Assume design authority to reduce coverage without approval
Flag conflicts between field conditions and approved design Stamp/seal drawings unless legally authorized
Ensure software backups exist after edits they perform or assist Leave the only backup on a personal device and wipe local copies
Notify supervision/owner when as-builts are known false Ignore drawing updates because “maintenance doesn’t do paperwork”
Ethics alignment: falsified as-builts are as serious as falsified test reports. Both mislead emergency response and future maintenance.
Practical Closeout Checklist After a Change Order / Service Modification
Complete physical and programming work; clear unintended troubles.
Functionally retest affected devices and interfaces; record results.
Red-line plans/risers/schedules the same day.
Export software backup; record revision ID on the job ticket and site log.
Revise battery/VD calcs if loads or cable lengths changed materially.
Issue formal drawing revision per company/AHJ process; replace site set.
Brief owner on new zone labels, bypasses, or operational differences.
File ITM/modification report with cross-references to the new revision.
Exam Focus
Choose answers that update drawings and software records whenever the field or matrix changes , use red-lines then controlled revisions , and treat versioned backups as mandatory after programming edits. Reject “maintenance never touches as-builts,” “panel labels alone replace drawings,” and “old backup is fine without revision identity.” Silent changes are documentation failures even when the horn still sounds.