Corridor Detector Layout and an Incomplete Design Submittal
A submittal for a four-story, fully sprinklered 120,000 sq ft office building arrives with floor plans and a riser diagram but no sequence of operations matrix, no battery calculation, and no voltage-drop calculations for the 22 notification circuits. A plan note reads: "All corridor smoke detectors on the same zone per floor." The corridors are 7 ft 6 in wide with 9 ft smooth ceilings. One typical corridor is 96 ft long; the designer has shown three smoke detectors at 12, 42 and 72 ft from the west end. The contractor says the package is typical for this AHJ and wants to begin rough-in on Monday.
1. How should you respond to the request to start rough-in?
Read the worked answer
Hold rough-in. Not because the package is unusual, but because the missing items change where wire and boxes go and how the system behaves.
Missing or inadequate:
- Sequence of operations matrix - without it there is nothing to program or witness at acceptance, and no way to check that the notification strategy matches the building's evacuation plan.
- Battery and voltage-drop calculations - these drive panel/battery sizing and conductor sizing, and changing conductor size after rough-in is a tear-out.
- Circuit schedules - device counts and loading per circuit.
- Equipment data sheets and listings for the devices actually specified.
Recommended path: issue a formal review comment listing the deficiencies, require resubmittal, and document that rough-in was authorized (if at all) only for raceway and boxes that will not change. The cost of a two-week delay is small compared with relocating boxes, re-pulling a 22-circuit notification package, or discovering at acceptance that the voice system cannot do floor-by-floor paging.
2. Evaluate the note "All corridor smoke detectors on the same zone per floor."
Read the worked answer
It defeats the purpose of the system for this building.
Grouping an entire floor's corridor detection into one zone means:
- The panel cannot identify which corridor or which end of the floor is in alarm during a response.
- The voice system cannot do selective paging or floor-by-floor evacuation if the entire floor is a single input.
- Trouble-shooting and the required annual device-level testing become guesswork; there is no way to verify individual device operation at the panel.
Even where the devices are addressable (so the panel "knows" the address), the programming zone mapping matters - an addressable device collapsed into one software zone behaves like a conventional zone for notification and annunciation purposes.
Correct approach: map detection to the smoke compartment / floor / notification zone structure shown in the evacuation plan, keep device-level annunciation, and let the sequence of operations matrix define which input drives which notification zone. Add this to the review comments; it is a design issue, not a field issue, and must be resolved before programming.
3. Check the corridor detector layout for the 96 ft corridor.
Read the worked answer
The layout is short one detector.
For a corridor of this width (under 15 ft), detectors may be spaced along the centerline at up to 30 ft, with the end detectors within 15 ft of the end walls.
Check as drawn: 12, 42, 72 ft.
- 12 ft to the west wall - OK.
- Spacing 30 ft and 30 ft - at the limit, OK.
- 72 ft to the 96 ft east wall = 24 ft - exceeds the 15 ft maximum.
A compliant arrangement is four detectors at roughly 12, 42, 72 and 90 ft (last one 6 ft from the east wall), or space them evenly at 12, 36, 60, 84 ft, which keeps every spacing at 24 ft and both ends within 15 ft. The even layout is preferable because it gives margin if a diffuser or beam forces a shift.
Also verify before relocating boxes: no detector is within 3 ft of a supply diffuser, and confirm the ceiling is genuinely smooth (beams or joists above the smooth-ceiling limits change the spacing rule entirely). Issue the correction through the designer, not as a field change, so the as-built matches the approved plan.