Educational guidance on registers and logs — what each records, who maintains it, what it typically contains and how long it is generally kept. Informational only — template examples, not official documents or legal advice; a register documents activity, it does not by itself prove compliance, and employers remain responsible.
What a security patrol log is
A security patrol log records that security patrols took place — the checkpoints visited, the times, the officer and any issue found — so there is a record of the site being checked and of anything that needed action.
This page is an educational overview with a simplified example. It is not an official template, not jurisdiction-specific and not legal advice — the employer or security provider decides the patrol routine and what is recorded.
Purpose
- Record that patrols were carried out and when.
- Capture checkpoints visited and the route.
- Note anything found and the action taken.
- Support security review and incident follow-up.
Who maintains it
- Security officers record their patrols.
- A security supervisor or provider reviews the log.
- A facilities or security lead owns the arrangement.
- The employer or provider decides the patrol routine.
When it is used
- On each scheduled or ad hoc patrol.
- When something unusual is found.
- During reviews of security cover.
- When following up a security incident.
Typical fields
- Date, time and the officer on patrol.
- Checkpoints visited and the route.
- Anything found and the action taken.
- Any incident reference raised.
- Sign-off for the patrol.
- Example columns only — adapt to your site and the applicable law.
Common mistakes
- Recording patrols that did not actually happen.
- Vague entries that note nothing useful.
- No link between a finding and an incident record.
- Predictable patrol patterns recorded for anyone to see.
Document workflow
A security patrol log links routine checks to incidents: patrols are recorded here, anything found is raised as an incident log entry, and findings may feed the access, gate or maintenance records. Patterns inform the wider security review.
See the related documents below for what is commonly used with and completed after a security patrol entry.
Retention (high level)
Security records may hold personal data and are generally kept for a period set by the employer in line with its obligations and data-protection duties. This page does not state a required period — confirm with the applicable law and the official authority.
Completing and sharing as a PDF
A security patrol log is often kept on a sheet or system and exported to PDF for records. Exporting to PDF supports the record; it does not make a site secure or prove compliance.
Employer checklist
- Make sure patrols are genuinely carried out and recorded.
- Capture useful detail, not just a tick.
- Link findings to incident records and action.
- Protect any personal data and control access to the log.
Worker notes
- Record patrols honestly and note what you find.
- Raise anything unusual through the incident process.
- Follow the patrol routine and report gaps in cover.
Country considerations
Security arrangements, any licensing of security work and data-protection rules vary by country, with a different official authority in each. This page is general and high-level — not a statement of any country’s law and not legal advice.
Confirm current requirements with the official authority for your country and a qualified professional.
Who is responsible
The employer or security provider is responsible for the patrol arrangement, protecting personal data and for compliance. This page is an educational overview with a template example; it does not make a site secure or compliant and does not transfer responsibility.
Export, edit and share documents
The documents, policies and templates this involves can be exported, edited, signed, stored and shared as PDFs with the HELPERG PDF Editor.
Free, printable HR & employment resources
Practical, ungated resources to put this into action — no signup.