ok so the riser diagram. every submittal has one, and it's usually the first sheet a reviewer actually sits with, before the battery calc, before the device matrix, before any of it. it's the one page that's supposed to show the whole system at a glance, panel down to the last device on the last circuit. reviewers know that if this page is off, there's a decent chance the rest of the package drifted too.
what actually goes on it
a riser isn't a floor plan. it's a vertical, or logical, map. panel at the top or bottom depending how your CAD guy likes to draw it, and everything else hanging off it in order. at minimum, for most AHJs I've dealt with, you need the panel itself, make and model, plus any annunciators or remote panels. every circuit leaving the panel, SLC loops, NAC circuits, whatever the job's got. device counts per floor or per zone, not just "smoke detectors: 14" floating off in a note somewhere. end of line resistors or devices, and where each circuit actually terminates. the communicator, whatever's dialing out to the monitoring station, and what it's tied into. and primary and secondary power, the panel's own supply plus the battery.
leave any of that off and the reviewer's first comment is going to be about the thing you left off. this varies by jurisdiction too, I've had a smaller county reviewer wave through a riser that a bigger city AHJ would've bounced for not showing the communicator connection clearly. so don't take this list as gospel for your desk. check what your specific AHJ wants before you assume anything.
a real one, three floors
small job I did last year, addressable panel in a mixed use building, retail on the ground floor, offices on two and three. one SLC loop running through all three floors, three separate NAC circuits because of the floor count. roughly how the riser broke down:
| Floor | Devices Shown | Circuit | EOL Location |
|---|---|---|---|
| Ground (retail) | 2 pull stations, 4 smoke detectors, 3 horn/strobes | SLC Loop 1, NAC 1 | Horn/strobe at rear exit |
| 2nd (office) | 1 pull station, 6 smoke detectors, 4 horn/strobes | SLC Loop 1, NAC 2 | Horn/strobe, north stairwell |
| 3rd (office) | 1 pull station, 5 smoke detectors, 1 duct detector, 4 horn/strobes | SLC Loop 1, NAC 3 | Horn/strobe, south stairwell |
| Panel | FACP, DACT communicator, 24V primary + battery secondary | n/a | n/a |
that's the whole system on one sheet. three NAC circuits, one loop, communicator called out on its own since it isn't a device, it's how the panel talks to the monitoring station. add up the pull stations across floors and you get 4. smokes come to 15. a reviewer is going to do that same addition and check it against what's sitting in the device matrix and the battery calc.
why reviewers cross check it
this is the part that trips people up. the riser doesn't live on its own, it has to agree with the device matrix and the battery calc, because all three are describing the same system from a different angle. the matrix says what each device draws and where it's addressed. the battery calc turns that into a standby and alarm load. the riser is the picture tying it together.
a reviewer who's done this a while doesn't stop at the riser. they flip to the matrix and count rows. they flip to the battery calc and check the device counts feeding those load numbers. riser says 15 smoke detectors, matrix has 16 rows tagged as smoke, that's a flag, even when the design itself is completely fine and it was just a stray row somewhere.
the mismatch rejection, and how it actually happens
nobody sits down and deliberately makes these three documents disagree. it happens in revisions. you add a smoke detector to the third floor because the AHJ wants better stairwell coverage, you update the riser, and the matrix doesn't get touched. or the battery calc comes back short so you bump the battery size, but the device count that was wrong to begin with never gets fixed. each document gets edited on its own and they quietly drift apart from each other.
had this happen on my own work, caught it before submitting. matrix showed a duct detector at 01-09 on Loop 1, riser had it a loop over from where it actually landed. five minute fix once I saw it side by side, but only because I went looking. if I hadn't, that's a comment letter and another review cycle, for something that had nothing to do with whether the design itself was any good. it's one of the recurring patterns covered in the common AHJ submittal rejections writeup, riser mismatch shows up there a lot.
worth saying, some of this comes down to how sharp your specific reviewer is that week. I've had ones barely glance at cross document consistency and ones catch a single mismatched address on a forty device job. don't assume yours is the forgiving kind, and don't assume every jurisdiction reads a riser the same way either. ask around or check your AHJ's own checklist if they publish one.
keeping the three in sync
the real fix is just a pass at the end where you lay all three side by side before anything goes out. riser device counts against matrix rows, matrix currents against the battery calc load, circuit labeling consistent across all three sheets. maybe twenty minutes on a small job, longer on something bigger. still a lot cheaper than a rejection and a resubmit.
anyway. full disclosure, I built a tool called FireDeck that keeps these three in sync automatically since they all pull from the same project data instead of three separate documents somebody has to remember to update together. free trial at firedeck.app if that sounds like something worth a look.