Patrol visits: how to supervise security guards across many posts
How to plan patrol visits across many guard posts, what a patrol officer should check, how to record findings, handle missed visits and use the records with clients.
- StrataMax team
- 11 min read
On this page
To supervise security guards across many posts, run scheduled patrol visits: a patrol officer or supervisor visits each post on a planned route, checks that the right guard is on duty and alert, inspects the post, and records findings, a conclusion and photos before moving on. Every visit ends as completed or missed, and the office reviews both.
That is the whole method. The rest of this guide is the detail that makes it work at 20, 50 or 200 posts: how to build the schedule, what the officer checks at each post, how to write findings that someone can act on, what to do about missed visits, and how to turn the records into something your clients value.
What is a patrol visit, and why does it matter?
A patrol visit is a supervision check on a guard post. It is different from a guard doing rounds inside a site. Here the person moving is the patrol officer (sometimes called a field supervisor or inspector), and the thing being checked is the post and the guard on it.
A security company sells presence and attention. The client cannot see whether the night guard at the rear gate was awake at 02:00. The patrol visit is how you find out, and the record of it is how you prove it.
Patrol visits do four jobs at once:
- Catch problems early. A sleeping guard, a broken gate light or a missing register is found before it becomes an incident.
- Keep guards accountable. Guards who know an officer can arrive at any hour behave differently from guards who expect nobody.
- Give the office facts. Decisions about transfers, warnings, training and equipment are based on recorded findings, not on memory.
- Show the client the service. A client who sees regular, documented visits is less likely to doubt the contract at renewal time.
How do you schedule patrol visits across many posts?
Start with a list of every active post, then group the posts into routes a patrol officer can cover in one shift.
Step 1: rate each post by risk
Not every post needs the same attention. A simple three-level rating is enough for most companies.
| Risk level | Typical posts | Suggested visit pattern |
|---|---|---|
| High | Banks, cash points, warehouses with high-value stock, posts with a recent incident | At least one visit every shift, including one unannounced night visit |
| Medium | Residential complexes, offices with night cover, factories | One visit a day, alternating day and night shifts |
| Low | Daytime-only offices, low-value sites with good lighting and CCTV | Several visits a week, at varied times |
These patterns are a starting point, not a rule. Adjust them for what the client contract promises, for how far apart the posts are, and for how many officers you have.
Step 2: build routes, not single visits
A patrol officer on a motorbike in Kathmandu can cover several posts in a shift if they are grouped sensibly. Group posts by area, then order them so the officer is not crossing the city twice. A route might be: Tamarind Court Residency (Main Gate, Rear Gate), then Cedarline Business Centre (Reception, Basement parking), then a warehouse further out.
Step 3: vary the times
If the officer reaches the same post at 22:00 every night, the guard learns to be alert at 22:00. Vary the order of the route and the hour of the visit. Keep at least some visits at the hours when guards are most likely to fall asleep, typically between 01:00 and 04:00.
Step 4: put every visit on the schedule
Each planned visit should exist as a record before it happens, with the post, the officer and the planned time. A visit that is only “in the officer’s head” cannot be marked as missed, so it never is.
A simple status flow keeps this honest:
| Status | Meaning |
|---|---|
| Scheduled | The visit is planned for a post, an officer and a time |
| In progress | The officer has arrived and started the visit |
| Completed | The officer finished the check and recorded findings and a conclusion |
| Missed | The planned time passed and the visit did not happen |
What should a patrol officer check at each post?
Give officers the same checklist at every post so that findings can be compared across posts and months. A good checklist has four parts.
The guard
- Is the right guard on duty, the one rostered for this post and shift? Note the name.
- Is the guard awake and alert?
- Is the guard in full uniform, with ID card, and carrying the issued equipment (torch, whistle, radio, baton where issued)?
- Is the guard sober and fit for duty?
- Does the guard know the post instructions: who may enter, who to call, where the fire extinguisher is?
The post
- Gates, locks and barriers working and secured.
- Lighting working, especially at gates, parking and perimeter.
- Fire extinguisher present, within its service date, and accessible.
- Guard booth or position clean and usable.
- Any damage to fences, walls or doors since the last visit.
The registers
- Visitor and vehicle register filled in properly, with times.
- Key register, if the post holds keys.
- Material in and out register, if the client uses one.
- Handover notes from the previous shift.
The client side
- Any request or complaint from the client’s site manager or residents.
- Any change on site the guard has not been briefed on (new tenants, construction, a new gate).
Officers should not tick boxes for things they did not look at. If a register was locked away and could not be checked, the finding is “visitor register not available”, not a tick.
How should findings and the conclusion be recorded?
A patrol record is only useful if the office can act on it. Each finding should say what was seen, where, and what was done about it.
Compare these two findings for the same problem:
| Weak finding | Useful finding |
|---|---|
| Light problem | Rear gate floodlight not working. Guard says it failed two nights ago. Reported to client site manager at 02:20. |
| Guard not good | Guard at Main Gate found seated with eyes closed at 01:45. Woke on approach. Verbal warning given. Second time this month. |
| Register ok | Visitor register complete for the day shift. Night entries 19:00 to 01:30 missing vehicle numbers for 3 entries. Guard told to record vehicle numbers. |
After the findings, the officer writes a conclusion: a one or two line summary of the post’s state at the time of the visit. For example: “Post secure. Lighting fault at rear gate reported to client. Guard performance acceptable.” The conclusion is what a manager reads first when scanning thirty visits from last night.
Photos
Photos settle arguments. Ask officers to photograph:
- The guard at the post (in uniform, at the position).
- Any defect: the broken light, the damaged fence, the missing extinguisher.
- The register page if it shows a problem.
Photos should be taken during the visit and attached to that visit, not sent separately on a messaging app where they will be lost among hundreds of others.
Start and end location
Recording where the officer was when the visit started and ended confirms that the visit happened at the post. It also protects honest officers: if a client claims nobody visited, the record shows otherwise.
What do you do about missed patrol visits?
Missed visits are normal. Bikes break down, an incident at one post keeps an officer longer than planned, an officer falls sick. What matters is that missed visits are visible and reviewed.
Rules that work:
- Never delete a missed visit. Mark it missed. If it is rescheduled, create a new scheduled visit and leave the missed one in the record.
- Record the reason. “Officer attending incident at Cedarline Business Centre”, “bike puncture”, “route too long”. The reason tells you whether it is a one-off or a planning problem.
- Cover high-risk posts the same shift. If a high-risk post was missed, send another officer or the operations manager before the shift ends.
- Review weekly. Look at missed visits by post, by officer and by route.
The weekly review answers different questions depending on the pattern:
| Pattern | What it usually means | What to do |
|---|---|---|
| Same post missed repeatedly | Post is at the end of a long route or hard to reach | Move it to another route or earlier in the order |
| Same officer missing visits | Workload, transport or performance issue | Talk to the officer; check route length; check bike and fuel claims |
| Many misses on one night | One incident pulled the officer away | Acceptable if recorded; consider a standby officer |
| Misses rising across all routes | Too few officers for the number of posts | Add an officer or reduce visit frequency on low-risk posts |
How do you act on what patrols find?
Findings that sit in a file change nothing. Assign each type of finding to someone.
- Guard conduct (sleeping, absent, out of uniform): goes to the operations or HR manager. Repeated findings for the same guard lead to a written warning, retraining or a transfer. Because the findings are dated and photographed, the decision is defensible.
- Equipment (missing torch, no radio, damaged uniform): goes to the store. Check what was issued to the guard and whether it was returned. If you track issue and return per guard, the patrol finding and the issue record can be compared directly. See our guide on managing guard uniforms and equipment.
- Site defects (lights, locks, fences): go to the client’s site manager, in writing, with the photo. Note in the record when the client was told.
- Security events (trespass, theft, damage, injury): these are incidents, not just findings. Open an incident record with severity and follow-ups. Our guide to incident reporting for security companies covers what that record should hold.
Close the loop at the next visit: the officer checks whether the floodlight was fixed and records it. A finding that appears on five visits in a row is a finding nobody owns.
How do patrol records help with clients?
Clients rarely see the patrol officer. They see the guard, and they see your invoice. Patrol records connect the two.
A short monthly patrol summary for each client can include:
| Item | Example for one client, Mangsir |
|---|---|
| Posts covered | Main Gate, Rear Gate |
| Visits scheduled | The number planned for the month |
| Visits completed | The number completed, with day and night split |
| Visits missed | The number missed, with reasons |
| Main findings | Rear gate floodlight out for 3 nights, fixed on the 12th; one guard warning for sleeping, guard replaced |
| Open items for the client | Damaged fence section near parking, reported on the 18th, not yet repaired |
Use real counts from your records. Do not round up completed visits or leave out missed ones. A client who later finds out about missed visits that were hidden will not trust the next report.
Patrol records are also useful when:
- A client complains that a guard was absent. You can show the visits on that night, who was found on duty, and the photos.
- A contract comes up for renewal. A year of documented visits and resolved findings is concrete evidence of service.
- Something goes wrong at the site. If there is a theft, the visit records from the nights before show what the post looked like and what was reported to the client.
Keep internal notes, such as disciplinary decisions about individual guards, out of the client copy. The client needs to know the problem was handled, not the details of an employee’s warning.
What does a good patrol programme look like in practice?
Take a company with 40 posts across 12 clients in Kathmandu valley and three patrol officers.
- Posts are rated: 8 high, 20 medium, 12 low.
- Each officer has a route of about 13 posts, grouped by area. Routes are swapped between officers every month so that no officer gets too familiar with the same guards.
- High-risk posts get a visit every shift. Medium posts get one visit a day, alternating day and night. Low-risk posts get a visit every two or three days at varied hours.
- Every visit is scheduled in advance. Officers start and end each visit on their phone, record findings and a conclusion, and attach photos.
- Each morning the operations manager reads the conclusions from the night’s visits and opens any incident records needed.
- Each Monday the manager reviews missed visits by post and officer.
- At the start of each Bikram Sambat month, a patrol summary per client goes out with the invoice or shortly after.
None of this needs a large team. It needs a schedule that exists in advance, a consistent checklist, and records that cannot quietly disappear.
Checklist: running patrol visits across many posts
- Every active post is listed with a risk rating (high, medium, low).
- Posts are grouped into routes an officer can cover in one shift.
- Visit frequency per post is written down and matches what client contracts promise.
- Visit times and route order are varied, including late-night visits.
- Every visit is scheduled in advance with post, officer and planned time.
- Officers use the same checklist at every post: guard, post, registers, client side.
- Findings say what was seen, where, and what was done.
- Each visit ends with a written conclusion.
- Photos are attached to the visit, not sent separately.
- Start and end location are recorded for each visit.
- Missed visits are marked missed with a reason, never deleted.
- Missed visits are reviewed weekly by post, officer and route.
- Guard conduct, equipment, site defects and incidents each have an owner.
- Open findings are re-checked on the next visit.
- Each client gets a monthly patrol summary based on real counts.
How StrataMax handles patrol visits
In StrataMax, patrol visits are scheduled against your posts and officers, and each visit moves through scheduled, in progress, completed or missed. Patrol officers start and end visits from the Android mobile app, record the guard checked, findings and a conclusion, attach photos, and the app records the start and end location. The office sees the visits in the web app on the same record as the guards, posts and clients, and incidents are recorded there with severity and follow-ups. See patrols and incidents in field operations for how it looks, or book a demo built around your own posts.
Frequently asked questions
What is a patrol visit in a security company?
A patrol visit is a scheduled check by a patrol officer or supervisor on a guard post. The officer confirms the right guard is on duty and alert, inspects the post, and records findings, a conclusion and photos so the office has a written record of the visit.
How often should a patrol officer visit each post?
There is no single legal frequency. Set it by risk: high-value or night-heavy posts and posts with recent problems get more visits, quiet daytime posts fewer. Write the frequency into the patrol plan and, where the client expects it, into the contract.
What should happen when a patrol visit is missed?
A missed visit should be marked as missed, not deleted or quietly rescheduled. Record the reason, reschedule the post the same shift if possible, and review missed visits weekly so a pattern of skipped posts or overloaded routes shows up early.
Should patrol records be shared with clients?
Yes, in summary. A monthly patrol summary per client, with visit counts, completed versus missed visits and the main findings and actions, shows the client what supervision they are paying for. Keep internal disciplinary notes out of client copies.