10.3 AHJ Submittal Expectations

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:

1. Confirm the proposed system meets the adopted codes and standards
2. Confirm documents are complete enough to install and inspect against
3. Coordinate life-safety features across trades (sprinkler, elevator, HVAC, egress)
4. 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

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:

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

Field set discipline

1. Only the approved-for-construction revision is used for install (or the explicitly allowed interim set under written AHJ direction).
2. Red-lines during install feed a future record set—they do not secretly replace the permit set without process.
3. Electronic folders use clear names including revision and date.
4. 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:

1. 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).
2. Clouded revisions — Changes findable without a scavenger hunt.
3. Updated dependent documents — If device count changes, update BOM, calcs, SOO, and cut sheets together.
4. Clear revision identity — New letter/number; do not overwrite files in a way that erases history needed for disputes.
5. Complete package or clearly identified partial — If only certain sheets change, say so and ensure the index is truthful.

Response quality spectrum

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

1. Read the local fire alarm submittal checklist before first issue.
2. 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).
3. Ask early whether PE seal, wet stamp, digital seal, or third-party peer review is required.
4. Submit complete PDFs/sets in the order the checklist expects.
5. After approval, archive the approved set and circulate it to field leadership the same day.
6. 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:

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

1. Submittal — complete package (10.1–10.2)
2. Review — comments or approval
3. Resubmittal — controlled revisions (this section)
4. Approved for construction — field set control
5. Installation + red-lines — capture deviations
6. 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.