An educational library of workplace documents — purpose, who completes them, when they are used, typical fields, common mistakes and how they connect. Linked to workplace safety, workplace training, occupations, industries and employment documents. Informational only — template examples, not legal advice or official documents; employers remain responsible and using a document does not guarantee compliance.
What a security patrol log form is
A security patrol log form records that patrols of a site were carried out — the route, the checkpoints reached, the times, and anything found or dealt with, such as unsecured doors, unauthorised people or safety issues. It gives a dated record that the site was monitored.
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 decides the patrol arrangements and how they are recorded.
Purpose
- Record that patrols were carried out and when.
- Cover the route and checkpoints reached.
- Note anything found and the action taken.
- Support security and a response to any incident.
Who completes it
- The security officer carrying out the patrol.
- A supervisor who reviews the log.
- The employer decides patrol routes and frequency.
- Findings may feed access, lost-property or incident records.
When it is used
- During each patrol, at the times set.
- When something is found or actioned on patrol.
- When reviewing security cover for a period.
Typical fields
- Date, officer and shift.
- Route and checkpoints with times.
- Observations and anything found.
- Action taken and any escalation.
- Sign-off.
- Example fields only — adapt to your site and security plan.
Common mistakes
- Logging patrols that were not actually done.
- No times, so cover cannot be demonstrated.
- Findings recorded but not acted on.
- No link to access, lost-property or incident records.
Document workflow
A security patrol log form works with the gatehouse log and access records, and feeds the lost-property form or an incident report when something is found. It supports the wider security plan rather than standing alone.
See the related documents below for what is commonly used with a security patrol log.
Retention (high level)
Patrol logs are typically kept for a period the employer judges relevant for security and review, then disposed of securely as they may contain personal data. This page does not state a period — confirm with the applicable law and the official authority.
Completing and sharing as a PDF
Patrol logs are commonly kept digitally and exported as PDFs for records or investigations. Exporting to PDF supports the record; it does not make it official or guarantee compliance.
Employer checklist
- Set clear patrol routes and frequency.
- Require accurate times and honest logging.
- Make sure findings are acted on, not just recorded.
- Link findings to the right records and protect personal data.
Worker notes
- Carry out patrols as set and log them accurately.
- Act on and escalate anything you find.
- Do not record patrols you did not do.
Country considerations
Security and data-protection rules affecting patrol records vary by country, and the official authority differs. This page is general and high-level — not a statement of any country’s law and not a guarantee of validity.
Confirm current requirements with the official authority for your country and a qualified professional.
Who is responsible
The employer is responsible for site security, protecting personal data and compliance. This page is an educational overview with a template example; it does not determine your security arrangements 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.