How security companies plan night patrol routes for each shift
Client sites in visiting order for every patrol car, rebuilt each evening from the night's list. Security patrol route planning without a whiteboard, and with roads in view.
Part of the guide Workflow automation
Good security patrol route planning gives each car a route that passes every client site on tonight's list in a sensible order, starts and ends at the base, and is rebuilt every evening because the list changes: a client adds a site, a shop asks for an extra check after a break-in, a warehouse is closed for a holiday. Plan it from the night's list at the start of the shift, share the sites fairly between the cars, check the roads, and hand each crew its order with directions.
The readers here are control room supervisors and operations managers at mobile patrol and alarm response companies. The article answers the questions they ask most, works through a made-up night shift, lists the mistakes that leave sites unvisited, and shows how an AI employee builds the routes before the briefing.
Why plan the route fresh every night?
A fixed patrol sheet goes out of date within weeks. Contracts start and end, clients ask for extra visits, and some sites only need checks on certain nights. When the sheet is redrawn by hand, it tends to keep the old order with new stops squeezed in, and cars cross their own paths. A route rebuilt from the current list each evening keeps the drive short and makes sure every booked visit is in it.
How are sites shared between cars?
With several cars on shift, the stops should be split so each car gets a compact part of the patch and about the same number of visits. The Route planner can share the stops between 2 to 10 cars, each with a tidy loop from the base and back, or make one route for each car when you have already assigned sites to crews. Each stop gets its place in the order, the distance and minutes from the stop before, the route's totals, and a directions link for the phone in the car.
Should the order be the same every night?
For the drive, the shortest order is best. For security, a patrol that arrives at the same site at the same minute every night is easy to watch and avoid. Planning tools find the efficient order; the variation is a decision your company makes. Common ways to vary it:
- Run the plan from a different start on alternate nights, so the loop turns the other way.
- Split the night into two passes, with high-risk sites visited in both and others in one.
- Let the supervisor swap two or three stops after the plan arrives.
What about the roads tonight?
A closed road between two sites can add a long detour. The Traffic incidents block checks for closures, roadworks and other incidents around each site, from online maps, and adds them to the stop, so the briefing can flag the stops with an incident nearby. It reports incidents; it does not reroute the car around them, so the crew still needs to look at the note.
A night shift, made up as an example
Take a patrol company in Johannesburg with three cars on the night shift and 36 visits booked across banks, jewellers, a few warehouses and a business park. At 20:30 the flow reads tonight's visits from the bookings table, checks for road incidents around each site, shares the visits between the three cars from the base and back, and writes a short briefing per car.
| Car | Visits | Drive | Stops with an incident nearby |
|---|---|---|---|
| Car 1 | 12 | 1 h 50 | 1 |
| Car 2 | 13 | 2 h 05 | 0 |
| Car 3 | 11 | 2 h 20 | 2 |
Invented sites, times and incidents, for illustration only.
The supervisor reads the three briefings at 20:45, swaps two of Car 3's stops so a jeweller is checked earlier, and the crews leave at 21:00 with the order on their phones.
Mistakes that leave sites unvisited
- Too many visits for one car. A route can hold up to 50 stops, but a crew cannot do 50 site checks in one shift. Cap visits to what fits with time on site.
- Sites without a position. A site whose address cannot be placed is listed after the routes without a visit order. Keep latitude and longitude in the bookings table.
- Planning too early. Late requests come in during the evening. Run the plan just before the briefing.
- No record of what was planned. Keep the night's plan, so a client asking whether their site was on the route gets a quick answer.
The AI employee that prepares tonight's routes
In xMap Flows the evening planning becomes one flow:
- Schedule: every evening at 20:30.
- My data: the bookings table, with each site and the nights it is due.
- Filter: sites due tonight.
- Traffic incidents: around each incoming place.
- Route planner: shared between 3 cars, from the base and back.
- xMap LLM: a briefing per car with the stops that have an incident nearby first.
- Email to the supervisor, with a map of the three routes.
The supervisor gets the plan in the Team inbox before the briefing. The night patrol routes past banks and jewellers template is a ready version, incidents in my patrol zones, every hour keeps watch through the night, and storm briefing for guards adds the weather. For more on crews and their AI helpers, see the AI employee for field operations.
Questions
How many patrol cars can the plan handle?
The route planner shares stops between 2 and 10 cars in one go, or makes one route per car when sites are already assigned to crews.
Does the route avoid road closures on its own?
No. Incidents near each site are added to the stop and the briefing, but the order is planned for usual traffic. Crews should check the flagged stops.
Can a crew start from home instead of the base?
When the shift starts at the base, plan from there. For crews that start elsewhere, assign their sites first and plan one route per crew.
Is the same order given every night for the same sites?
For the same stops and start, yes, because it is the shortest. Vary it on purpose, for example by starting from a different point on alternate nights.