Every new patrol contract looks like it fits on the existing route. One more gated community, one more parking structure, one more call-only site that “just needs someone to swing by twice a night” — and on a map, it does fit, because a map only shows distance. How many sites can one patrol vehicle cover before that math stops working? What a map doesn’t show is what happens to the ninth site’s response time when the vehicle is fifteen minutes away working an actual call at the fourth.
How many sites can one patrol vehicle cover: the question everyone asks backward
The usual way to size a vehicle patrol route is forward: how many addresses can we fit between the start of shift and the end of it, given the drive time between them? That question always has an answer, because it’s just arithmetic on a map. Add stops until the math runs out of hours, then stop adding.
The problem with that approach is that it optimizes for coverage, not for response — and clients don’t buy vehicle patrol for coverage. They buy it because something might happen and they want someone there fast. A route that visits every site on schedule but takes forty minutes to reach the one site that actually calls has technically delivered the contracted number of passes and completely failed the reason the contract exists.
The better question runs backward: what’s the slowest response time you’re willing to promise, for the worst-case moment on the busiest site on the route? Size the route to that number, then see how many stops fit inside it — not the other way around.
Why “worst case” and not “average”
Averages hide the failure. A route can average a fast response across a month of quiet nights and still fail catastrophically the one night three alarms trip within twenty minutes of each other on different ends of the route. Vehicle patrol response time isn’t a number you’re managing on average — it’s a number you’re managing on the worst plausible night, because that’s the night the client remembers and the incident report references.
This is also why “how many sites can one patrol vehicle cover” doesn’t have a single right answer that applies across a portfolio. A route of low-alarm-frequency HOA gates that rarely call in can carry more stops than a route mixing a construction site with an active break-in problem and a retail strip with a shoplifting pattern. The stop count isn’t the variable that matters — the response window is, and the stop count is just what falls out once you’ve set it.
What one additional stop actually costs
When a dispatcher or ops manager is asked to add a stop to an existing route, the honest cost isn’t the drive time to the new address. It’s the response time added to every other site on the route for the portion of the shift the vehicle is now somewhere else. A stop added at the midpoint of a route pushes out the worst-case response for the sites on both ends of it, even though none of those sites changed.
This is easiest to see with the site that generates the calls. If Site A calls in twice a week and Site F never calls, adding a stop between them doesn’t cost Site F anything it will notice — but if the geography works the other way, and the new stop sits between the dispatch point and Site A, every future call to Site A now takes longer to reach, on a route that looks identical on paper to the one before the change.
Sales teams selling vehicle patrol contracts rarely see this cost, because the pitch is site-by-site: “we can add your property to an existing route for less than a dedicated post.” That’s true in isolation and can still be the decision that quietly degrades response for every site already on that route. The fix isn’t refusing to add sites — it’s checking the worst-case math before agreeing to the price, not after a client on the existing route complains that the truck used to show up faster.
Sizing a route that can actually flex
A route built with headroom handles the mismatch between average night and bad night better than a route built to exactly fill the shift. That headroom looks like waste on a quiet week and looks like the reason nobody got hurt on the week it wasn’t quiet.
Headroom also absorbs the ordinary friction a route runs into that never shows up in the planning spreadsheet: a locked gate that needs a second attempt, a tenant who flags the officer down for something unrelated to the post, a stop that takes longer because the lot is unusually full that night. None of those events are dramatic on their own, and none of them get logged as an exception, but a route with no slack built in absorbs every one of them as delay to the next stop, and the site at the end of the route pays for all of it without ever knowing why.
Tracking actual response times against the route, not just planned drive times, is what makes this visible before a client notices it independently. A GPS-tracked patrol route shows where the vehicle actually was when a call came in, and comparing that against the promised response window turns “the truck seemed slow lately” into a specific, addressable pattern — a stop that needs to move, a route that needs to split, or a site that’s outgrown sharing a vehicle at all.
The same visibility helps when a client asks to add a stop. Instead of eyeballing the map, dispatch can show what the addition does to worst-case response across the whole route using the security patrol software record of how the route has actually performed, and price or decline the addition with an actual number behind it rather than a guess.
Dispatch has to see it in real time, not in a monthly report
None of this works if the only place route performance shows up is a report generated after the fact. The moment that matters is when a call comes in and dispatch needs to know, immediately, which vehicle can actually reach the site fastest — not which vehicle is nominally assigned to it. A dispatch view that shows live vehicle position against the routes they’re covering turns that from a guess into a decision, and it’s the same data that later proves, or disproves, whether a route has been overloaded.
The honest answer
There is no fixed number of stops one patrol vehicle can cover reliably, and anyone who gives you one hasn’t accounted for the mix of sites on the route. The number that matters is the response time you’re willing to stand behind for the worst night on the busiest site, and every stop you add after that number stops flexing is a stop you’re borrowing against a client who hasn’t called yet.
If you want to see what that math looks like against your own routes, explore CGuardPro or get in touch to walk through it with your actual site mix.