A security patrol report format is a log with one row per checkpoint per round: date, site, guard, shift, round number, checkpoint, time checked, status, what was observed, the action taken, and who it was reported to. Filled in properly, it proves the rounds happened and gives the client a clear trail when something goes wrong.
The template on this page suits security agencies, facility management companies, housing societies, factories, warehouses and commercial buildings that run their own guards.
The columns a patrol log needs
| Column | Why it matters | Example |
|---|---|---|
| Date | For night shifts, use the actual calendar date of each check, so rounds after midnight fall on the next day. | 30-09-2026 |
| Site | Agencies run many sites; one sheet for all of them only works if every row names the site. | Shanti Heights |
| Guard | Who did the round. Essential when guards rotate across sites. | Ramesh Chauhan |
| Shift | Day, night or general. Lets you compare shifts and spot a weak one. | Night |
| Round no. | Shows how many rounds were done against how many were due. | 2 |
| Checkpoint | A fixed list per site: gates, parking, terrace, pump room, fire exits. Same names every time. | Terrace door |
| Time checked | When the guard was at the checkpoint. Gaps between times show a skipped or rushed round. | 01:10 |
| Status | All OK, observation or incident. The column the supervisor filters first. | Incident |
| Observation / incident | What was seen, in plain facts. | Terrace door found unlocked |
| Action taken | What the guard did about it. An observation with no action is only half a report. | Checked terrace, door locked |
| Reported to | Who was informed: supervisor, facility manager, client, police. | Supervisor Anil Rawat |
| Photo | Whether a photo was taken. Photos turn "the light was off" into evidence. | Yes |
A filled-in example
Part of one night shift at a residential complex, as it should appear in the log:
| Round | Checkpoint | Time | Status | Observation | Action taken |
|---|---|---|---|---|---|
| 1 | Main gate | 23:05 | All OK | ||
| 1 | Basement parking | 23:20 | Observation | Light near pillar B4 not working | Informed maintenance |
| 2 | Terrace door | 01:10 | Incident | Door found unlocked | Checked terrace, locked door, told supervisor |
The "All OK" rows matter. A log that only lists problems cannot show that the other checkpoints were visited at all.
How to write observations that are useful
Guards often write "all OK" for the whole shift, or a vague line like "security problem on terrace". Neither helps the supervisor or the client. A useful observation answers four questions:
- What exactly was seen? "Terrace door unlocked", "two-wheeler parked in fire exit", "water leaking from pipe near lift 2".
- Where, using the checkpoint name from the site list.
- When, to the minute.
- What was done and who was told.
Tip: give each site a printed list of checkpoints in round order, in the language guards read best. Use exactly those names in the sheet. It keeps rounds consistent across guards and makes the log easy to filter.
Six rules for a patrol log
- One row per checkpoint per round, not one line per shift.
- A fixed checkpoint list per site. "Terrace", "Terrace door" and "Top floor" are three different places to a spreadsheet.
- Fixed choices for shift and status. The template uses dropdowns for both.
- Record the time at the checkpoint, not the time the log was written.
- Every observation gets an action. Even if the action is "informed supervisor".
- Serious incidents get a separate incident report. The patrol log notes it and moves on; the incident report carries the full detail.
Common mistakes
- The whole shift written at 6 AM. Every time is suspiciously round, and nothing unusual ever happened.
- A paper register that stays at the gate. The supervisor sees it once a week, and the client never does.
- Photos in a WhatsApp group with no context. A photo of a door with no site, time or action is hard to use later. See how WhatsApp groups compare with structured reporting.
- No record of the quiet rounds. If only incidents are written down, there is no proof the other rounds happened.
Patrol logs, guard tour systems and WhatsApp
If you need proof that a guard physically reached each checkpoint at a set time, a dedicated guard tour system with tags at each checkpoint does that job well. What it usually does not capture is the observation itself: what was wrong, what the guard did, who was told. That still has to be written down somewhere, and on most sites it ends up in a register or a WhatsApp message.
Getting guards to report in their own language
With vBol, a guard saves one WhatsApp number as a contact and, at a checkpoint, sends a short voice note, a photo or their location, in Hindi, Marathi, Bangla, Odia, Punjabi or any of the other languages vBol supports. Nobody has to type:
vBol transcribes the note, fills in the fields of the patrol record type Vritti sets up with you (site, checkpoint, status, observation, action taken) and reads it back on WhatsApp in the guard's language, with buttons to confirm or fix a field. Nothing is written until the guard confirms. The confirmed row goes into your Google Sheet, an Excel workbook on OneDrive or SharePoint, or Ekatm ERP, with the photo and GPS location attached.
At 7 PM the agency owner or operations manager gets one WhatsApp message: what was filed, by whom, and which guards sent nothing that day. The guide to tracking field staff daily reports covers how to use that list. There is no app, no login and no training for guards, and it works for five guards or five thousand. It is free for 30 days (up to 5 confirmed reports per person per day during the trial), then ₹199 per user per month for teams of up to 100 users, with a custom plan for bigger teams. See pricing.
Prefer to stay on a spreadsheet? Download the free template on this page. It has the columns above, dropdowns for shift, status and photo, and three example rows you can overwrite.
Frequently asked questions
What is a security patrol report?
A security patrol report, or patrol log, records each round a guard makes: site, guard, shift, the checkpoints visited and at what time, anything observed, and the action taken. It shows that rounds happened and gives a written trail for any incident.
What should a security guard write in a patrol log?
For every checkpoint: the time, whether everything was in order, and if not, exactly what was seen and what was done about it, including who was informed. Facts, not opinions: "terrace door found unlocked at 01:10" rather than "security issue on terrace".
What is the difference between a patrol report and an incident report?
A patrol report records every round, including the uneventful ones. An incident report is a separate, detailed account of one serious event such as a theft, injury or break-in. The patrol log should mention the incident and point to the full report.
How often should security guards do patrol rounds?
That depends on the site and the contract with the client. Whatever the frequency, write it down as part of the post instructions so every guard and supervisor knows what a complete shift looks like.