Hotels generate a constant stream of small events.
A contractor arrives late. A fire door is found propped open. A guest reports suspicious behaviour. A master key is temporarily unaccounted for. A member of staff raises a welfare concern. A patrol identifies damage that was not there an hour earlier.
Most of these events need to be recorded. Some need to be escalated.
The challenge is knowing which is which.
That is where the Daily Occurrence Book, or DOB, has traditionally played an important role in hotel security operations.
It gives security teams a running record of what happened, when it happened and who was involved.
But a record is only useful if the information inside it helps people decide what happens next.
What is a Daily Occurrence Book?
A Daily Occurrence Book is a chronological record of events, observations and routine activity recorded by a security team during a shift.
Historically, this was often a physical book kept at a security desk. Today, many hotels use a digital equivalent, sometimes referred to as a Daily Occurrence Log (DOL).
The terminology varies, but the purpose is largely the same: create an operational record of the things that happen throughout the day.
That might include:
-
Patrol activity, visitor or contractor movements, key issues, access problems, guest complaints, maintenance concerns, suspicious behaviour, lost property, and more...
For a hotel that operates 24 hours a day, this running history can be particularly valuable.
The problem comes when everything is treated as just another entry in the log.
Not every occurrence needs an incident report
A useful way to think about the difference is simple; an occurrence needs recording, an incident needs managing.
-
A delivery arriving late may need to be logged, but a delivery driver entering a restricted area may require investigation.
-
A guest reporting a noisy corridor may be an occurrence, but a guest reporting threatening behaviour may need to become an incident.
-
A broken door handle might be recorded for maintenance, a broken access-controlled door that leaves a restricted area unsecured may need immediate escalation.
The event itself might initially look similar. What changes is the level of risk, urgency and follow-up required.
That distinction matters because a Daily Occurrence Book is designed to create a record.
Incident management is designed to drive action.
Why hotel security teams need both
A busy hotel can produce dozens, or even hundreds, of routine security observations over the course of a week.
Turning every one of those into a formal incident would create unnecessary administration and make it harder to identify what genuinely needs attention.
But keeping everything inside a general security log creates the opposite problem; important events can disappear among routine entries.
A note might say:
“Guest reported suspicious person on level three. Security attended.”
That tells you something happened, but doesnot necessarily tell you:
-
Who responded, what they found, whether CCTV was reviewed, whether the individual was identified, if management was informed and further action was required
For routine activity, that level of detail may not matter.
For a genuine incident, it often does.
When should a Daily Occurrence Book entry become an incident?
There is no universal rule that applies to every hotel. Different properties have different risk profiles, operating procedures and escalation policies.
But there are some useful questions security teams can ask.
Does somebody need to take action?
If the entry simply creates a record, it may remain an occurrence.
If somebody needs to investigate, respond, communicate or follow up, it may need escalation.
Is there an ongoing risk?
A spill that has already been cleaned up may simply need recording.
A damaged door that continues to leave an area unsecured may require active management.
Could there be consequences later?
Some events appear minor at the time but become important later.
Guest complaints, alleged harassment, suspicious behaviour, injuries and security concerns may all require a clearer audit trail.
Does management need visibility?
Not every occurrence needs to reach senior management.
But if an event has operational, reputational, legal or safety implications, it may need to move beyond the daily log.
Does the event need a clear outcome?
A Daily Occurrence Book tells you that something happened.
An incident record should tell you what happened next
The problem with relying on the security log alone
A security log can be extremely useful. But it becomes less effective when teams try to make it perform jobs it was never designed to perform.
One long chronological record can make it difficult to separate routine activity from events that need investigation.
Important information may be spread across multiple shifts. Updates may be added hours later.
Different security officers may describe similar events in completely different ways.
And once an issue starts involving several people, departments or actions, following the full story through a single log can become difficult.
The result is often plenty of information, but not necessarily clarity.
From a Daily Occurrence Book to a Daily Occurrence Log
Moving from a paper DOB to a digital Daily Occurrence Log does not change the basic purpose of the record. But it can make the information easier to use.
Digital logs can help security teams create more consistent entries, search historical records and share information across shifts without relying on handwritten notes.
They can also make it easier to connect routine operational records with formal incident processes.
For example, an occurrence that initially appears routine can be escalated if new information changes its significance. That creates continuity between:
-
What happened > what needed action > what was done about it
For hotel security teams, that is often more useful than simply replacing a paper book with a digital version of the same process.
