Guide · Daily log
Hotel daily security log and occurrence book
The daily security log — often called the occurrence book — is the running record of a shift: patrols, checks, calls and events, big and small. Kept well, it is the first place a manager looks when something needs to be reconstructed later.
What every log entry should contain
- Time of the entry (and of the event, if different)
- Location, as precisely as possible
- What happened or what was checked, in one or two factual sentences
- Who made the entry
- Whether anything is still open for the next shift
Log entry or incident report?
Most entries stay in the log: a completed patrol, a door found open and secured, a noise complaint resolved. An entry should become a full incident report when there is injury, loss, damage, unauthorised access, police or emergency involvement, or anything a manager will need to review or act on.
The key is that the incident report starts from the same facts as the log entry, so the two never contradict each other.
Good shift-handover practice
- Read the previous shift's log before starting
- Hand over open items explicitly, not only verbally
- Note who received the handover and when
- Keep the log in one place the whole team can see
Common problems with paper or spreadsheet logs
Handwriting that cannot be read, entries added afterwards, no link between an entry and the report it led to, and no way to see which locations come up again and again. These are process problems more than people problems.
How Security Report AI handles the daily log
Officers add log entries with time and location during the shift. Any entry can be turned into a structured incident report that starts from the same words, and the shift log can be summarised for handover. Management sees log activity alongside incidents and follow-up.
Try it on a sample incident
Pick a sample scenario, generate the report and see what is flagged as missing — on fictional data, no account, nothing stored.