Walk any patrol route on paper and the stairwells barely show up. They’re the line between two checkpoints — lobby to roof, garage level to garage level, floor 4 to floor 5 — not a checkpoint themselves. That’s how most routes get built, and it’s exactly backward, because the space between two monitored points is where a person who doesn’t want to be seen chooses to be. A proper stairwell patrol checklist security guard teams can actually rely on starts by treating that space as a checkpoint in its own right.
The Stairwell Patrol Checklist Security Guard Teams Actually Need
A stairwell is enclosed, has poor sightlines around every half-flight, usually has weak cell signal, and in a lot of buildings has no camera coverage at all above the first or second floor. It’s also, structurally, the fastest way to move between floors without using an elevator that logs a stop. Put those three facts together and you get the profile of the space where loitering, unauthorized access between floors, and quiet property damage concentrate — not because stairwells are inherently dangerous, but because they’re the part of the building least likely to have anyone checking.
A route that treats the stairwell as connective tissue between the door at the top and the door at the bottom checks both doors and calls it done. That confirms the doors were where they should be. It says nothing about what happened on the landings in between, and landings are where people who are avoiding the doors actually go.
What a real stairwell checkpoint looks like
The fix isn’t a longer patrol — it’s a checkpoint placed at the mid-landing, not just at the floor doors on either end. On a stairwell that spans more than a couple of floors, that means more than one scan point inside the stairwell itself, not just one at each end. A checkpoint at a landing does two things a door-to-door check doesn’t: it forces the officer to actually traverse the space rather than open one door, glance down, and close it, and it creates a timestamped record that someone was physically present between the two ends, not just at them.
That second part matters more than it sounds like it should. If an incident happens on a landing between two floors and the only checkpoints are at the doors, the record shows the doors were checked at 10:14 and 10:41 — it says nothing about the 15 minutes in between, and a landing incident could have started and ended in that window with no trace that anyone was ever positioned to notice it.
The specific things worth checking at a landing, not just a door
A door check answers one question: is it closed and does it latch. A landing checkpoint should answer a handful more, because it’s the only place on the route where an officer is actually standing inside the enclosed space rather than passing through it:
- Lighting. Stairwell lights burn out and stay out because nobody’s standing still long enough to notice — a five-second door-to-door pass doesn’t catch a dead bulb the way stopping at a landing does.
- Propped doors. Not just the two ends of the stairwell — interior fire doors between landings get propped for convenience by tenants moving equipment, and a propped fire door is a life-safety issue that a fast pass-through misses.
- Debris and personal items. Bedding, food wrappers, cigarette butts — the signs someone has been using the space repeatedly, which a single walk-through only catches if the officer is actually looking at the landing itself, not just the door ahead.
- Graffiti or damage on the mid-flight walls, which rarely shows up on the doors at either end and tells you the loitering has been going on longer than one shift.
None of that shows up if the route logic treats the stairwell as a straight line between two checkpoints instead of a space with its own checkpoint in the middle.
Why this gets skipped even at well-run companies
It’s not laziness — it’s route design inherited from buildings where it didn’t matter. A single-story retail strip or a two-floor office doesn’t have this problem; there’s no meaningful “middle” to a one-flight stairwell. The gap shows up specifically in mid-rise and high-rise properties, parking structures with multiple below-grade levels, and hospitals with long vertical circulation — buildings where the stairwell itself is long enough to have a middle worth checking, and where the route was often designed years before the building reached that scale.
The other honest reason: a landing checkpoint takes longer to reach than a door, and a route built under time pressure trims the checkpoints that don’t have an obvious door attached to them first. Checkpoint scanning that records exactly where and when each stop happened is what makes it defensible to add landing checkpoints to a route — the alternative is asking an officer to take your word for it that they walked the whole flight, which nobody outside the company will accept as evidence after an incident.
Building it into the route without inflating patrol time
Adding a landing checkpoint doesn’t have to mean adding a separate trip up the stairwell. If the route already sends an officer through the stairwell as a connector between two floors, the fix is simply requiring a scan partway through that existing traverse rather than only at the ends — the officer is walking through the space either way. The change is in what gets recorded, not in how much ground gets covered.
For buildings where the stairwell genuinely isn’t part of the normal route — say, an officer takes the elevator between checkpoints and only uses the stairs for emergencies — that’s the stronger signal the stairwell needs its own dedicated pass on the schedule, at a randomized time rather than a fixed one, precisely because a predictable gap in coverage is the one an occupant with bad intentions learns fastest.
What changes once landings are on the route
Nothing dramatic happens most nights. That’s the point — a well-covered stairwell is quiet because it’s a bad place to loiter, not because nothing was ever going to happen there. The value shows up the one time it doesn’t stay quiet, when a client asks what the patrol actually covered between the lobby and the fourth floor and the answer is a timestamped stop on the landing instead of a shrug.
If you want to see how checkpoint routes get built to cover the spaces between the obvious stops, explore CGuardPro or get in touch.