13.1 AHJ Communications, Transmittals & RFI Tracking

13.1 AHJ Communications, Transmittals & RFI Tracking

Quick Answer: Treat every AHJ and project direction as a filing problem, not a memory problem. Capture verbal comments with who, date, the stated requirement, and a sheet or specification citation, then confirm them in writing through the supervisor. Transmittals prove what left the shop. RFIs prove which questions are still open. Work that depends on an open RFI stays on hold.

NICET Water-Based Systems Layout Level I scores Project Correspondences at 1–10% of the exam. Tasks 1.7.1 (document correspondences with AHJs) and 1.7.2 (document project correspondences) sit in that band. The slice is small, but a missing letter is how a shop loses an argument with the fire inspector six months later. Chapter 3 already covered bid-period addenda, RFIs, and change orders on the estimating side. This section is the field and AHJ file: what was said, what was sent, what is still open, and what you are allowed to install.

Verbal AHJ direction is not a record

Inspectors talk on the job. They point at a room, wave at a soffit, and say things like “that is fine” or “we can skip the spare heads.” None of that is closeout evidence. It is not evidence for the engineer of record either. Level I’s job is to turn speech into a document the shop can produce later.

Write five facts before anyone leaves the corridor:

1. Who spoke (name, agency, and role — fire inspector, plans examiner, owner’s representative).
2. Date and, if known, time and place (final inspection at the riser, walkthrough of Suite 200).
3. The requirement in the inspector’s words, not a paraphrase that quietly changes the meaning.
4. Sheet or specification reference so a later reader can find the drawing or Division 21 paragraph the comment touches.
5. What you did next — a confirming email or letter routed through the supervisor, not a private text from an apprentice to the AHJ.

Then send the confirmation. A useful note restates the five facts and asks the AHJ or design professional to reply that the statement is correct. File the sent message and any acknowledgment in the correspondence folder. If nobody acknowledges it, the log still shows that the shop asked in writing. “The inspector said we could skip the spare heads” is not closeout evidence until it is written and acknowledged. Spare-sprinkler rules in NFPA 13 (2022) 16.2.7 do not vanish because someone spoke in a stairwell.

Emails, letters, and inspection reports belong in the same register. A text message or hallway comment belongs there only after those five facts are copied into an email or letter. Do not “remember it for closeout.” Closeout will ask for a page, not a story.

Worked example — inspector allows a 2-in. deflector exception in one room

Approved working plans show pendent sprinklers in an exam room with deflectors in the ordinary unobstructed band taught in Chapter 8. On the finish walkthrough, Inspector Morgan Lee (City of Cedar Fire Prevention, 20 March 2026) states that a 2-in. deflector-to-ceiling distance is accepted in Room 104 only because of a shallow soffit that cannot be cut. That sentence is not a code rule you should memorize as a new 2-in. maximum. It is a site-specific AHJ statement about one room.

Level I writes those facts, cites Sheet FP-2 and the contract specification section for sprinkler placement, and sends a confirming email through the project supervisor the same afternoon. The email does not claim a floor-wide exception. When Lee replies “correct — Room 104 only,” that thread is the record. The as-built later notes Room 104 and points to that correspondence. The rest of the suite still follows the approved deflector rules. If Lee never replies, the shop still has proof it asked, and it does not copy 2 in. into every room as if a verbal comment rewrote NFPA 13.

Transmittals: proof of what left the shop

A transmittal is the cover sheet and log entry for a package that moved. It is not an approval, not a change order, and not an RFI. It answers six questions: what was sent, which revision, on what date, to whom, how many copies, and for what purpose.

Purpose language is part of the record. Shops commonly mark packages as follows:

Number the transmittals (T-001, T-002, and so on) and keep one log so you can prove sequence. If Revision C of the second-floor plan went to the AHJ on 12 March and Revision D went to the owner on 18 March, the log is how you stop someone from installing Revision B. Count copies. If the specification requires three paper sets plus a PDF, the transmittal lists 3 + PDF, not a vague “plans.”

Level I often fills the transmittal: drawing numbers, revision clouds, cut-sheet dates, and the purpose box. The supervisor signs. Never disguise an unasked design change as a “for approval” send — that belongs on an RFI or a change-order proposal. A transmittal that lists the wrong revision is a false record; correct it with a new numbered transmittal rather than erasing history.

RFIs: questions with a citation and a proposed answer

A Request for Information (RFI) is a numbered question to the design professional (and, when the contract says so, copied to the owner and AHJ). A complete RFI states:

• The question in one or two sentences.
• The contract document citation (sheet, detail, specification paragraph, or approved-submittal page) that created the conflict or gap.
• A proposed solution so the engineer can say yes, no, or not that — something else.
• The date an answer is needed, tied to fabrication or install, not “at your convenience.”

Log status as open, answered, or closed. Open means the question has left the shop and no written reply is in the file. Answered means a written reply is in the file. Closed means the reply has been distributed, related drawings or transmittals updated if needed, and the field is released or a change order has been opened. Do not start work that depends on an unanswered RFI. Hanging a branch line under a duct while RFI-017 (“are under-duct sprinklers required at this 48-in. duct?”) is still open is how a shop pays to take pipe down.

An RFI without a citation forces the engineer to guess which drawing you meant. An RFI without a proposed solution invites a vague reply that you cannot install from. Write the citation and the proposal even when you think the answer is obvious.

RFI versus change order on a live project

Chapter 3 treated RFIs and change orders as bid-period tools: addenda change the bid set; an RFI asks; a change order rewrites the deal after award. On a live job the same names appear, with a different risk. An RFI still asks. It does not change price or time by itself. A change order is the contract modification after award: added heads, extra arm-overs, a new inspector’s test drain, time, money.

If the AHJ’s written comment or the engineer’s RFI reply adds six sprinklers under a soffit that was not on the bid drawings, the layout file updates and the commercial file needs a change order. A transmittal of revised plans “for approval” without that change order leaves the extra work undocumented in the contract even if the fire inspector is happy. Meeting minutes help, but they do not replace an RFI when the contract drawings conflict with what the inspector just required, and they do not replace a change order when the answer adds cost.

Field RFIs often start from coordination (a new soffit, a duct that grew, a beam the architectural plan hid). The documentation sequence does not change: write the question, cite the sheet, propose an installable answer, wait, then issue a change order when the answer changes the deal. Installing first and RFI-ing later is how verbal AHJ comments leak into the ceiling with no paper trail.

What Level I actually files

Keep an AHJ correspondence log (letters, emails, inspection reports), a transmittal log, and an RFI log — or one numbered register with a type column. Scan wet-signed pages. Name files so a stranger can find 2026-03-20_AHJ-Lee_Room-104_deflector-confirmation. The exam item is not calligraphy. It is whether the shop can prove who said what before the ceiling closed.

When the field asks “can we hang it tomorrow?”, check the RFI log first. If the dependent question is still open, the answer is no. If it is answered and the reply changed count, hangers, or heads, check whether a change order exists. Then hang it. That habit is the whole domain in one sentence.