Study guide

10.3 AHJ Submittal Expectations

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

10.3 AHJ Submittal Expectations

Key Takeaways Explain This Topic AI

AHJs expect complete, legible, code-edition-correct packages; stamps/seals are often required from a PE or other authorized designer—Level II technicians assemble packages under supervision and do not fake seal authority

Revision tracking (clouds, revision blocks, unique revision IDs, superseded-sheet control) keeps reviewers and the field on the same document set

Resubmittals should respond to each review comment with a clear disposition and updated drawings/calcs—not silent partial fixes

Common rejection reasons include missing calculations, incomplete device schedules, model mismatches, wrong code edition, incomplete SOO/interfaces, and unreadable or uncoordinated sheets

Last updated: August 2026

10.3 AHJ Submittal Expectations

Quick Answer: The authority having jurisdiction (AHJ) reviews fire alarm construction documents for completeness and code compliance before (or as a condition of) installation and inspection. Expect requirements for qualified design/seals where mandated , complete package contents , correct adopted code editions , and controlled revisions . Level II technicians assemble and revise packages accurately under the project’s design authority; they do not invent PE stamps or ignore written comments.

Sections 10.1–10.2 built the package. This section is about getting it through review and keeping document control honest after comments and field changes.

Who the AHJ Is and What Review Means

“AHJ” may be the fire marshal’s plan review staff, a building department, a third-party reviewer under local program rules, or another designated authority. Regardless of office name, the practical goals are the same:

  • Confirm the proposed system meets the adopted codes and standards
  • Confirm documents are complete enough to install and inspect against
  • Coordinate life-safety features across trades (sprinkler, elevator, HVAC, egress)
  • Establish an approved baseline for inspections and future modifications

Exam trap: Assuming “NICET certification alone always replaces PE seal requirements.” NICET credentials demonstrate individual competency; local law and contract decide who may prepare/stamp fire alarm construction documents.

Stamps, Seals, and Level II Boundaries

Situation Typical expectation Level II action

New system or major modification in a jurisdiction requiring PE documents PE (or other licensed design professional) seal on drawings/calcs as required Assemble package; route through engineer of record; do not apply a seal you do not hold

Design-build under a licensed designer’s supervision Designer seal; technicians produce CAD/schedules under supervision Follow redlines and design directives; document questions in writing

Minor device replacement in kind under maintenance rules May be outside full permit drawings—confirm local policy Do not assume “small job = no rules”

Owner-furnished design by third party Installing contractor still submits installation docs as required Reconcile conflicts before rough-in

  • What Level II should never do
  • Photocopy or digitally paste someone else’s seal
  • Sign “in the PE’s absence” without legal authority

Change spacing, notification strategy, or pathway survivability criteria silently after sealed approval without designer/AHJ process

  • Represent shop assembly work as sealed professional design when it is not
  • What Level II should always do
  • Keep the designer’s name, firm, and revision identity correct on sheets
  • Flag field conditions that invalidate approved assumptions
  • Prepare clean resubmittal sets when comments require drawing changes
  • Maintain a trail of which revision was approved for construction

Scenario: A sales manager pressure-loads a Level II tech to “just stamp it so we can pull permit.” The correct response is refusal and escalation. Seal fraud is a career-ending ethics and legal failure, not a customer-service favor.

What Reviewers Commonly Check

AHJ checklists vary, but recurring review themes include:

  • Review theme Package evidence
  • Code editions Cover sheet/notes state NFPA 72, IBC/IFC, NEC editions as adopted

Occupancy & building features Scope matches building (stories, voice vs tone, sprinkler present, high-rise features, etc.)

  • Initiating coverage concept Plans show required device types at expected locations for the design approach
  • Notification performance concept Candela/spacing/settings and sleeping-area features as applicable
  • Secondary power Battery calcs present and consistent
  • Circuit performance Voltage-drop calcs present for notification (and similar) circuits
  • Interfaces Elevator, HVAC, doors, suppression monitoring shown and described in SOO
  • Supervising station Path method identified; equipment data included
  • Listing/compatibility Cut sheets and system approach coherent
  • Pathway class/survivability Notes/riser match design requirements for the building
  • Legibility & scale Readable symbols, scales, and IDs

Level II assembly quality directly reduces comment cycles.

  • Revision Tracking
  • Why revisions matter

Multiple people use the drawings: plan reviewer, permit desk, installer, inspector, owner. If two “current” sets disagree, the wrong devices get installed and the wrong set gets inspected.

Revision control tools

  • Tool Use
  • Revision letter/number & date Unique identity for each issued set
  • Revision block description Short narrative of what changed (“Added 4 pulls Stair 2; revised NAC-2 VD”)
  • Revision clouds / deltas Graphical highlight of changes on affected sheets
  • Sheet index update Cover sheet lists current revision per sheet
  • Superseded control Old prints marked SUPERSEDED or removed from field sets
  • Transmittal / comment response letter Maps AHJ comments to dispositions
  • Field set discipline

Only the approved-for-construction revision is used for install (or the explicitly allowed interim set under written AHJ direction).

Red-lines during install feed a future record set—they do not secretly replace the permit set without process.

Electronic folders use clear names including revision and date.

When Rev C is issued, destroy or quarantine Rev B field copies.

Scenario: Electricians pull cable from Rev A hanging in the gang box while the office emails Rev C to the superintendent only. Inspectors later fail device locations that match Rev A. Document control failed.

Resubmittal Responses

When the AHJ issues comments, a professional resubmittal includes:

Comment response document — Each comment numbered with response: “Agree—revised Sheet FA-201 and Battery Calc BC-1” or “Disagree—see code path justification …” (with designer support).

Clouded revisions — Changes findable without a scavenger hunt.

Updated dependent documents — If device count changes, update BOM, calcs, SOO, and cut sheets together.

Clear revision identity — New letter/number; do not overwrite files in a way that erases history needed for disputes.

Complete package or clearly identified partial — If only certain sheets change, say so and ensure the index is truthful.

Response quality spectrum

  • Weak resubmittal Strong resubmittal
  • “Fixed” with no comment map Numbered responses to each AHJ item
  • Calcs unchanged after adding 20 appliances Battery/VD revised and referenced
  • Clouds missing Clouds + revision description
  • Argumentative tone without code basis Professional tone with edition citations from designer
  • Silent scope reduction to avoid a hard comment Honest design revision with owner awareness

Exam trap: Choosing “ignore written comments if the salesperson says the fire marshal likes us.” Personal relationships do not replace documented approval.

Common Rejection / Delay Reasons

Memorize these as a pre-submittal punch list:

  • Missing or inadequate calculations
  • No battery calc
  • No voltage-drop calc for NAC circuits
  • Calcs for a different project pasted in
  • Counts that do not match schedules
  • Incomplete device schedule / BOM
  • Symbols on plans with no schedule entries
  • Missing candela/watt settings
  • Missing circuit or address columns when the system type needs them
  • Quantities that cannot be summed to plan counts
  • Product data problems
  • Wrong models
  • Unreadable scans
  • Full catalogs without identification of selected products
  • Missing communicator or power-supply sheets for equipment shown on riser
  • Wrong code edition or missing code basis
  • Notes cite an edition not adopted locally
  • No edition listed at all
  • Mix of contradictory edition references across sheets
  • Incomplete operational documentation
  • No sequence of operation
  • Interfaces drawn but not described
  • Supervising-station method unclear
  • Drawing quality / coordination failures
  • Illegible reduced-scale plans
  • Backgrounds outdated vs architectural permit set
  • Missing FACU location or annunciator
  • Riser contradicts floor plans (circuit counts, panel locations)
  • No legend
  • Administrative / authority failures
  • Required seal missing
  • Wrong project address
  • Unsigned applications where required
  • Incomplete deferred-submittal conditions not addressed

Scenario: Package rejected for “incomplete.” Comment list: no battery calc, schedule missing candela, SOO absent, cut sheets for wrong horn model. All four are Level II-preventable assembly errors.

Practical AHJ Communication Habits

Read the local fire alarm submittal checklist before first issue.

Confirm adopted editions (do not assume the NICET reference set is the local set on a real job—though exam stems will track NICET’s stated references).

Ask early whether PE seal , wet stamp, digital seal, or third-party peer review is required.

Submit complete PDFs/sets in the order the checklist expects.

After approval, archive the approved set and circulate it to field leadership the same day.

For mid-project changes, determine whether a revision submittal is required before installing the change.

Level II Ethics Under Schedule Pressure

Pressure patterns and correct responses:

  • Pressure Correct response
  • “Install now; submit later” Escalate; explain rework/stop-work risk
  • “Leave the missing calcs out so review is faster” Refuse incomplete knowing misrepresentation
  • “Mark the comment complete without changing the sheet” Actual revision + honest response
  • “Use last job’s sealed title block” Never
  • “Tell the inspector a different revision is approved” Show the actual approval documents

These habits align with NICET professional conduct expectations and domain 2.4 supervision/ethics themes you will see later in the guide.

  • From Approval to Field to Record Set
  • Submittal — complete package (10.1–10.2)
  • Review — comments or approval
  • Resubmittal — controlled revisions (this section)
  • Approved for construction — field set control
  • Installation + red-lines — capture deviations
  • Acceptance package / record drawings — as-built truth (Ch 5 & 9)

Shop-drawing excellence at Level II is not only “pretty CAD.” It is reviewable truthfulness under AHJ and designer rules.

Exam Focus

Prefer answers that require complete packages , correct seal/authority boundaries , revision clouds/blocks and superseded control , and itemized resubmittal responses . Reject fake stamps, silent comment closure, install-before-approval as default, and packages missing calcs/schedules/SOO. When stems list rejection reasons, pick the set that matches real review failures: missing calcs, incomplete schedules, wrong edition, mismatched cut sheets, incomplete interfaces/SOO.