Field reporting for a security agency means turning three kinds of events into short, dated records: the patrol round that shows a guard did their job, the incident report that shows what happened when something went wrong, and the supervisor visit that shows someone checked. A client is much easier to keep when the agency can show these on the day they are asked for.
The three reports
| Report | Filed by | How often | What it proves |
|---|---|---|---|
| Patrol round | Guard | Every round, per the schedule | The area was covered and was clear, or was not. |
| Incident report | Guard, then supervisor | Only when something happens | What occurred, what was done, who was told. |
| Supervisor visit | Supervisor | Per site, per visit | Post was manned, guard alert, register up to date. |
Patrol round: the columns
| Column | Why it matters | Example |
|---|---|---|
| Date and time | Rounds are about timing. A round logged at the wrong hour is a finding. | 30-09-2026, 02:15 |
| Site or post | Same name every time so it can be filtered. | Sai Residency, Gate 2 |
| Guard | Who did the round. | Mahesh Yadav |
| Areas covered | Basement, terrace, perimeter, meter room. | Basement, terrace, perimeter |
| Status | Clear or issue found. A fixed choice. | Clear |
| Observation | What was unusual: a broken lock, a stranger, a light out. | Terrace light not working |
| Photo and location | Evidence for anything not clear. | Photo of the light fitting |
A filled-in example
| Time | Site | Guard | Status | Observation |
|---|---|---|---|---|
| 22:10 | Sai Residency | Mahesh Yadav | Clear | All gates locked |
| 02:15 | Sai Residency | Mahesh Yadav | Issue found | Terrace light not working, informed supervisor |
| 05:40 | Lakshmi Warehouse | Devraj Gowda | Clear | Nothing to report |
Incident report: what to capture
Ask for five things, in this order, and keep the guard's own words in the last one:
- What happened in one sentence.
- When and where, to the nearest minute and the exact spot.
- Who was involved, by name or description.
- What the guard did and whom they informed.
- Remarks in the guard's own words, plus a photo if there is something to show.
An incident record from a night shift might read like this:
| Time and place | What happened | Involved | Action and informed |
|---|---|---|---|
| 30-09-2026, 01:40, Gate 2 | Unknown person tried to enter without a visitor slip | Man, about 30, grey shirt | Stopped at gate, phoned resident, asked to leave; supervisor Kiran Shetty informed at 01:50 |
Supervisor visit: what to capture
Site, date and time, guard on duty, whether the post was manned and the guard alert, whether the register is current, anything the guard raised, and what you told them. One row per visit, so you can show a client that their post was checked on specific dates.
Rules that make the reports worth having
- Record clear rounds too. "Nothing to report" is a report. Its absence is the finding.
- Use fixed status words. Clear / issue found can be counted; "all ok", "fine" and "normal" cannot.
- File incidents at once, not at shift end.
- Do not rely on memory. A round reported the next morning is a reconstruction.
- Keep a list of who did not report. The pattern of gaps tells you more than the reports themselves.
What to review each week
Reports only pay off if someone reads them. A short weekly routine is enough:
- Missed rounds. Compare the rounds scheduled for each post with the rounds recorded. A pattern at one post or one shift is a supervision issue, not a guard issue.
- Repeat observations. The same broken light or unlocked gate logged four nights running means the client, or your own maintenance, needs a nudge.
- Incidents and response. Read each incident once: how quickly was it filed, and was the supervisor informed?
- Supervisor coverage. Which sites were visited least? Those are the ones a client will ask about first.
Common mistakes
- Registers that are filled in for the whole shift in the last ten minutes.
- Guards who are asked to write in English when they think in Hindi, Marathi or Kannada.
- Incident details scattered across phone calls and a WhatsApp group, so nobody can reconstruct the order of events.
- Supervisor visits that exist only as a signature in a register at the site.
The shorter version of this, with a downloadable sheet, is the security patrol report format.
Doing this with vBol
vBol, a product of the Indian company Vritti, lets a guard or supervisor save one WhatsApp number as a contact and send a voice note, photo or location after a round, in their own language:
vBol transcribes it, extracts the fields and reads the record back in the guard's language with buttons to confirm or fix a field. Nothing is saved until they confirm. The row goes into your Google Sheet, an Excel workbook on OneDrive or SharePoint, or the matching module in Ekatm ERP, with the photo and GPS location attached. Every evening at 7 PM the owner or manager gets one WhatsApp message listing what was filed, by whom, and which guards sent nothing that day.
Be clear about what is built in. Site reports (inspection, installation or maintenance, with photo, headcount, blockers and safety observation) are a built-in record type. A patrol round, an incident report or a supervisor visit with your own columns is a record type Vritti sets up with you, along with the destination sheet. vBol records what guards report; it does not check that a round took place.
An honest limit: vBol's summary reaches managers as an evening digest, not as an emergency alarm. For a live incident the guard should still phone the supervisor first, and file the record straight afterwards.
Guards install nothing and never log in, and they message vBol's number rather than a group. It works for a five-guard site or five thousand staff. It is free for 30 days (up to 5 confirmed reports per person per day), then ₹199 per user per month for teams of up to 100 users, with a custom plan for larger teams. See pricing.
Frequently asked questions
What should a security guard patrol report include?
The date and time of the round, the guard, the post or site, areas covered, anything unusual, and a photo or note where something needed attention. A round with nothing to report should still be recorded as clear.
How is an incident report different from a patrol report?
A patrol report is routine and records that a round happened. An incident report is an exception: what happened, when, who was involved, what the guard did, and who was informed. It needs more detail and should be filed immediately.
How can a security agency check that guards are actually patrolling?
Ask for a short report after each round and compare it with the schedule. A photo or shared location with the report adds evidence, and a daily list of guards who sent nothing shows gaps quickly.
Can guards report in their own language?
Yes. With vBol a guard sends a WhatsApp voice note in Hindi, Marathi, Kannada, Tamil or another language, and the record is read back to them in that language to confirm before it is saved.