CheckpointGuardSecurity Guard Incident Report Template
Use the direct downloads to record an incident or reported issue. Page 1 is a blank form; page 2 is a clearly fictional completed example. Edit the DOCX or print the PDF. No account or email address is needed.
Record the event clearly
Identify the site, reporter, event time and exact location. Separate the time of the event from the time you wrote the report. If a time is approximate or an event was reported by somebody else, say so and identify the source where appropriate.
Describe what you observed in chronological order. Keep an account from a witness separate from your own observations. A report records an account of events; it does not automatically prove disputed facts or establish who was responsible.
Actions and notifications
Record what you did, who you contacted, when they were contacted and any response. Follow approved site instructions and escalation arrangements. The form does not instruct you to investigate beyond your authority or replace emergency procedures.
Add relevant record references rather than copying unnecessary personal details into every document. Handle names, contact information and attachments through your organisation's approved access and retention procedures.
A fictional unresolved defect
The completed example concerns a service door that did not latch at Harbor Point Offices - Fictional Example. The reporter documents the observed defect and supervisor notification. It remains open because no repair was confirmed. No real people, customers or events appear in the example.
| Record | Fictional entry |
|---|---|
| What was observed or reported | At 22:25 I checked the service door on the assigned route. The door did not latch when closed. I do not know when the defect began. |
| Notifications/escalation; time and recipient | Example Supervisor B acknowledged the message at 22:32. No repair completion was confirmed. |
| Follow-up/status; responsible person; next action | Open. Example Supervisor B to obtain a maintenance update. Incoming guard to receive the unresolved issue at handover. |
Keep follow-up separate from the initial account
Name the next action and responsible person where known. Mark unknown details as unknown and unresolved items as open. Record later updates with their own time and author rather than making an unconfirmed outcome appear to have been known earlier.
Incident report or daily activity report?
Use an incident report for the detail of one event or reported issue. Use a daily activity report for the shift's chronological activity. Cross-reference them where useful; neither needs to repeat the other's full contents.
Review operational records in CheckpointGuard
CheckpointGuard supports reporting alongside recorded patrol activity, messages and SOS alerts. An SOS record shows an alert; it does not establish the final incident outcome. This generic form is not an automatic CheckpointGuard export or a legal compliance certification.