12.2 Zone Schedules & Legends

12.2 Zone Schedules & Legends

Quick Answer: Plans show where; schedules and legends define what each symbol is and how it is wired and identified. Build a device schedule (type, candela, base, circuit, address/zone), a zone or node map that matches conventional vs addressable architecture, a complete legend, and wire/cable gauge notes that feed installation and Chapter 13 calcs. If schedule and plan disagree, the set is not ready.

Section 12.1 covered symbols, risers, and plan orientation. This section is the tabular and legend layer of blueprint 2.3.3—the content AHJs and estimators read when symbols alone are insufficient.

Why Schedules Exist

A floor plan symbol answers location. It rarely carries every attribute needed to buy, install, program, and calculate the system:

Without schedules, installers guess candela, programmers invent descriptors, and voltage-drop authors invent loads.

Device Schedule Anatomy

There is no single mandatory table format, but Level II-ready schedules typically include columns such as:

Candela and base type—frequent omissions

Notification appliance schedules that list “strobe” without candela and wall vs ceiling are incomplete for serious review. Detector schedules that omit isolator/relay/sounder base hide SLC segment design and auxiliary functions. Level II reviewers treat those blanks as defects, not optional polish.

Counts and roll-ups

Useful schedules also support counts by type and by circuit:

• Number of speaker-strobes on NAC-2 at each candela
• Number of addressable points on SLC-1 (including modules)
• Conventional device counts per IDC for wire and EOL planning

Those roll-ups become inputs to battery, voltage-drop, and amplifier calcs in Chapter 13 and related design sheets.

Zone Maps vs Node/Point Maps

Conventional: zone (IDC) thinking

A zone schedule / zone map for conventional initiation typically shows:

• Zone number and signal type (alarm zone, supervisory zone, etc.)
• Description ("Floor 2 smoke," "Sprinkler riser 1 waterflow," "Valve tampers")
• Device types included and approximate count
• FACU terminal or IDC number
• EOL location note

Annunciation may be by zone LED or zone text—not by individual detector identity. Drawings should not pretend each conventional smoke has a unique digital address.

Addressable: node / loop / point thinking

Addressable documentation replaces pure zone lists with point maps:

• Loop/SLC number and pathway class
• Point address and device type
• Software zone or group assignment (for programming logic and selective evacuation)
• Module points tied to mechanical or suppression interfaces

Software zones on addressable systems are logic groups—they are not the same thing as a conventional IDC. Exam stems often test whether you know that an addressable “Zone 3” in programming may be a display/control group, while the physical pathway is still SLC-1 Class A with individual addresses.

Scenario: A renovation adds addressable detection but leaves conventional NAC circuits. The schedule must show addressable point IDs for smokes and circuit/NAC IDs for horns-strobes. A single “Zone 2” column for everything confuses both the programmer and the AHJ.

Legend Completeness

The legend is the dictionary of the drawing set.

What belongs in a complete legend

1. Every device symbol used on any sheet (smoke, heat, duct, pull, beam, flame, modules, appliances, panels, boosters, EOL markers, cloud revision marks if used as symbols)
2. Line types (existing to remain, new, demo, future, match line)
3. Abbreviations (FACU, SLC, NAC, IDC, EVACS, SS, AHU, EOL, CD, WP)
4. General notes pointers ("See FA-001 for mounting heights")
5. Symbol variants (ceiling vs wall strobe; weatherproof pull)

Incomplete legend failures

Best practice: full legend on a general sheet and a condensed legend on busy plans, or a clear “LEGEND ON FA-000” note on every plan sheet.

Wire Gauge and Cable Schedules

Basic technical drawings should state what conductors are assumed—not leave wire size as tribal knowledge.

Typical content

Wire schedules may be a table, a general note block, or both. What matters is one authoritative assumption set shared by:

• Installers ordering cable
• Voltage-drop calculations (resistance per foot depends on AWG)
• Conduit-fill calculations (Chapter 9 of the NEC uses conductor dimensions)

Trap: Plans say “14 AWG NAC” in a general note while the voltage-drop sheet used 12 AWG to “make the drop pass.” That is a documentation integrity failure—not clever engineering. Either change the design wire size everywhere or fix the layout/load.

Cross-Document Consistency Checks (Level II Review Habit)

Before submittal or rough-in, walk this checklist:

1. Count: Devices on plans ≈ devices on schedule (explain residuals: spares, future, demo).
2. Identity: Every schedule Mark appears once on a plan (or is explicitly “spare in box”).
3. Circuit: Schedule circuit IDs exist on the riser.
4. Type: Legend wording matches schedule type matches cut sheet.
5. Notification attributes: Candela/wattage present for appliances that need them.
6. Architecture: Conventional zones vs addressable points used correctly.
7. Wire: Gauge/type notes match calc sheet inputs.
8. Interfaces: Waterflow/tamper/elevator/HVAC tags match the sequence of operation matrix.

Scenario: Schedule lists 40 × 75 cd strobes on NAC-1. Plan shows 40 symbols but 10 are tagged NAC-2. Riser loads NAC-1 with 40. Voltage drop and battery alarm load will not match the real building. Consistency checks catch this before copper is pulled.

Zone/Node Maps for Annunciation and Control

Beyond parts lists, schedules support operational geography:

• Which devices light which annunciator LEDs or text lines
• Which floors evacuate or relocate together (EVACS)
• Which points drive elevator recall vs HVAC shutdown

A simple zone map graphic (building outline with zone boundaries) helps conventional systems and some AHJs. Addressable projects often use point lists by floor plus a cause-and-effect matrix (Chapter 10 package content). Level II drawing work keeps those operational maps aligned with physical circuit drawings.

Exam Focus

Expect stems that:

• Ask what belongs in a device schedule vs only on a symbol
• Distinguish conventional zone identity from addressable point identity
• Flag an incomplete legend
• Tie wire gauge notes to voltage-drop assumptions
• Identify plan/schedule/riser conflicts as submittal defects

Prefer answers that demand complete, coordinated tabular data—not “the symbol is enough” or “the field will decide candela.”