Daily Occurrence Book Example: A UK Guide for 2026

Last updated: 17 October 2026

Pulse Operations's guidance shows a daily occurrence book example should include a timestamped, factual entry recording who, what, where and when — such as "02:14 — PC checked north fire escape, door secure, no issues, signed JS" — written at the time, not reconstructed afterwards. UK security teams use these books to log patrols, incidents and handovers across every shift, often with 28 events recorded per page in a standard printed format.

Key Takeaways

• A daily occurrence book (DOB) is a chronological, shift-by-shift log of events at a site, used by security officers, receptionists and duty managers to record patrols, visitors, incidents and handovers.
• A standard A4 security log book contains 200 serially numbered log sheets printed over 100 double-sided pages, with room for 28 events per page, according to Interconnective (2026).
• Courts treat undocumented occurrences with scepticism: as one industry commentator put it, "if an occurrence has not been systematically and properly documented, then it cannot be relied upon as having taken place in exactly the manner alleged" — City Security Magazine.
• Pulse Operations records show 96.2% of checkpoints across live operations carry a watermarked photo over a trailing 90-day period (as of July 2026), turning the occurrence book from a narrative into an evidenced record — see the benchmark.
• A digital, tamper-evident occurrence book removes the single biggest weakness of a paper DOB: the ability to add, edit or backdate an entry after the fact.

What is a daily occurrence book and what is it used for?

A daily occurrence book is a chronological written record, kept by security or front-of-house staff, that logs every notable event during a shift at a specific site. It is used to document patrols, visitor movements, deliveries, alarm activations, incidents, equipment faults and shift handovers in one continuous, time-ordered account.

The term originates from policing, where the Occurrence Book (OB) is described as "one of the most important records at a police station" — Kenya Police Service. UK private security has adopted the same concept at site level, distinct from the custody-record or crime-report function of a police OB.

In commercial settings, the DOB sits at the centre of site governance. A shopping centre security team, a residential block's concierge desk, or a construction site's gatehouse all rely on it to answer the same question every client eventually asks: what actually happened here, and when?

A completed book becomes the first document any manager, client or insurer reaches for after an incident. It is also the document the Security Industry Authority (SIA) — the statutory regulator of the UK private security industry under the Private Security Industry Act 2001, which had 369 employees in 2024/25 per Wikipedia — expects to see referenced during an Approved Contractor Scheme (ACS) audit, alongside rotas, licences and screening files.

What information should each daily occurrence book entry contain?

Every DOB entry needs five fixed elements: the date and exact time, the officer's name or identifier, the location, a factual description of what occurred, and a signature or digital sign-off. Missing any one of these weakens the entry's evidential value.

The description itself should answer who, what, where, when and — where relevant — what action was taken. Good entries avoid opinion, speculation and abbreviation that only the writer understands.

A strong entry typically includes:

• Timestamp — to the minute, not just the hour
• Officer identity — full name or employee/licence number, never initials alone
• Precise location — "Car park B, level 2, bay 14," not "car park"
• Observed fact — what was seen or heard, stated plainly
• Action taken — who was called, what was checked, what followed
• Sign-off — a signature, initials, or in a digital system a locked timestamp

Entries recorded at a shopping centre, a Mayfair residential block, or a construction hoarding gate all follow this same structure, regardless of sector. The difference is volume and risk profile, not format.

Who is responsible for writing in the daily occurrence book?

The officer, receptionist, or duty manager physically present during a shift is responsible for writing their own entries in real time. Responsibility does not transfer to a supervisor reviewing the book later; the person who witnessed the event must be the one who records it.

On a licensed security contract, this duty usually falls to an SIA-licensed security officer working under a Security Industry Authority licence, whether as a door supervisor, CCTV operator or static guard. In reception or concierge settings, it falls to whoever holds the front desk — often unlicensed staff working to the same documentation standard.

A site supervisor or duty manager then carries a secondary responsibility: reviewing, countersigning and querying entries before the book is archived. This review step is where gaps get caught — a missed patrol, an ambiguous entry, a page left blank.

Pulse Operations's founder has observed how this handover point is where paper books most often fail. As Mo Hassan, Founder, Pulse, puts it: "A paper occurrence book is written at the end of the shift by whoever's left standing. Ours writes itself as the shift happens — every patrol, incident and check call lands in it with a timestamp, and nothing can be quietly rewritten afterwards. That's what an insurer actually wants to see."

What does a completed daily occurrence book entry look like?

A completed entry is a short, factual block of text tied to a precise time, written in plain language without jargon or guesswork. Below are three realistic examples covering a routine patrol, a minor incident, and a handover note.

Routine patrol entry:

23:47 — PC D. Osei. Perimeter patrol commenced, east gate to loading bay. All fire exits checked and secure. CCTV camera 6 (car park) found misaligned — reported to control room, logged as fault ref FM-0472. Patrol completed 00:03, no further issues. Signed DO.

Minor incident entry:

14:22 — Reception, Officer S. Kowalski. Visitor (male, approx. 40s, no ID badge) attempted to access level 3 lift lobby without signing in. Stopped at reception desk, directed to visitor sign-in. Visitor complied, gave name as "J. Carter," host confirmed by phone (M. Patel, Finance). No further action required. Signed SK.

Shift handover entry:

06:00 — Night shift to day shift handover, Officer R. Ahmed to Officer L. Fitzgerald. All checkpoints completed per schedule (12/12). One alarm activation at 03:15, zone 4 (stairwell B) — false alarm, motion sensor fault, engineer booked for 09:00 (ref PM-1183). Keys for suite 4B returned by cleaning contractor at 05:40, logged in key register. No outstanding issues. Signed RA / LF.

Each entry here follows the same discipline: timestamp first, named officer, specific location, observed fact, action taken, and a sign-off. This is the structure a DOB entry needs regardless of whether it ends up on paper or inside a digital occurrence book module.

Is a daily occurrence book a legal requirement in the UK?

A daily occurrence book is not a standalone statutory requirement for every UK business, but it is an expected standard of due diligence that supports obligations under contract law, health and safety law, and SIA licensing conditions. No single Act says "you must keep a DOB," yet its absence creates real legal exposure.

The Private Security Industry Act 2001 established the SIA and licensing regime for security operatives but does not itself mandate a specific logbook format. However, the ACS self-assessment workbook — the SIA's scoring tool for the Approved Contractor Scheme — scores a business against 78 individual indicators across seven criteria and 33 sub-criteria, per Pulse Operations's guide, The ACS self-assessment: how to evidence it. The Service delivery criterion is where assessors expect to see occurrence records, patrol logs and incident documentation as evidence, not assertion.

Under the Health and Safety at Work etc. Act 1974, employers must show they monitored and responded to risks on a premises — an undocumented shift leaves no trail to demonstrate that duty was met. Insurers, too, routinely request DOB extracts to assess liability claims, and courts take a dim view of undocumented events, as noted above by City Security Magazine.

For publicly accessible venues, the Terrorism (Protection of Premises) Act 2026 — commonly known as Martyn's Law — adds a further layer: readiness assessments and incident response plans benefit directly from a well-maintained occurrence record. Pulse Operations's Martyn's Law guide covers this obligation in detail.

Daily occurrence book or incident report form: what's the difference?

A daily occurrence book is a continuous, chronological log of every event across a shift, while an incident report form is a standalone document triggered by one specific, often serious, event. The DOB is the diary; the incident report is the formal statement extracted from it.

In practice, a serious entry in the DOB — an assault, a theft, a fire alarm activation with evacuation — should trigger a separate incident report that cross-references the DOB entry by time and page or entry number. The DOB proves the event was logged when it happened; the incident report provides the detail needed for escalation.

Pulse Operations's platform treats these as linked but distinct records: incidents and the daily occurrence book sit on the same system, covering 18 occurrence types, so a serious entry can be flagged and escalated into a full incident record without re-keying anything. The security services page covers how this connects to live patrol data.

Should the occurrence book be physical or digital?

A physical occurrence book is a bound, serially numbered paper record, while a digital occurrence book is an electronic log typically built into an operations platform with timestamps generated automatically. Both remain legitimate, but they carry different strengths and weaknesses that matter for evidential reliability.

A standard paper DOB, such as the A4 format sold by Interconnective, runs to 200 serially numbered log sheets over 100 double-sided pages, deliberately bound so pages cannot be removed without detection. That serial numbering is the paper format's main evidential strength — it makes tampering visible.

Its weaknesses are practical: illegible handwriting, pages left blank during a busy shift, ink fading, and the physical book being lost, damaged, or simply left in the wrong cabin on a large site. There is also no way to check entries in real time from off-site.

A digital occurrence book, by contrast, time-stamps every entry at the moment it is written and can enforce mandatory fields before an entry saves. Pulse Operations's version goes further: a hash-chained (SHA-256), tamper-evident audit log with a built-in integrity check that walks the whole chain, so any attempt to alter a historic entry is detectable rather than merely discouraged (as of August 2026).

This matters beyond the UK, too — government modernisation projects elsewhere have reached the same conclusion.

Paper vs digital: the trade-off

Choosing between them is really a question of risk tolerance and site scale. A single small reception desk may manage perfectly well with a bound paper book and a diligent team. A multi-site security contractor managing dozens of officers across London cannot realistically audit handwriting across 20 sites every week — and that is exactly where a digital, photo-verified system earns its cost.

At a landmark West London mixed-use development, Priority First — Pulse's founding operation — needed to prove that all 152 checkpoints across retail, residential, plant rooms and service yards were actually being walked, not just logged from memory. Before Pulse, there was no way to prove which plant room was checked at 3am. Since going live in February 2026, all 152 checkpoints were made photo-mandatory, and the site recorded 540+ patrols in the first five months across 11 inducted officers — production data as of July 2026.

How long should daily occurrence book records be kept, and what about GDPR?

Occurrence book records should typically be retained for a minimum of six years to align with general civil litigation limitation periods under the Limitation Act 1980, though insurers and specific contracts may require longer. Retention periods are not fixed by a single occurrence-book law, so the governing contract or insurer requirement should set the policy.

Because occurrence books often contain personal data — names of visitors, vehicle registrations, descriptions of individuals involved in incidents — they fall within scope of the UK General Data Protection Regulation (UK GDPR) and the Data Protection Act 2018, both overseen by the Information Commissioner's Office (ICO). Data must be held only as long as necessary, kept secure, and accessible only to those with a legitimate need.

A digital occurrence book simplifies this considerably: access can be restricted by role, entries can be retained on a defined schedule, and redaction or deletion of personal data at the end of a retention period can be applied consistently across every site, rather than relying on someone remembering to shred a paper book. Pulse Operations's platform is UK-built and UK-hosted, with tenant isolation enforced in the data layer and verified by an automated cross-tenant test suite on every build — a relevant point for any business handling occurrence data under UK GDPR (as of August 2026).

Your daily occurrence book checklist

Use this checklist when setting up or auditing a site's occurrence book practice:

• Confirm every officer logs the exact time, to the minute, not a rounded figure
• Require full names or licence numbers on every entry, never initials alone
• Specify the exact location for each entry — building, floor, zone, or checkpoint reference
• Separate observed fact from opinion; strip out speculation before it's written down
• Cross-reference any serious entry to a formal incident report by time or entry number
• Set a fixed retention period aligned to your insurer's and client's contract terms
• Review and countersign the book at every shift handover, not just weekly
• Audit a sample of entries monthly against rota and patrol schedule data

FAQ

What is a daily occurrence book example?

A daily occurrence book example is a sample log entry showing the structure of a real shift record — typically a timestamp, officer name, location, factual description of an event, and a sign-off. The examples earlier in this article, covering a routine patrol, a minor incident, and a shift handover, show the standard wording format used across UK security sites.

What should be included in a daily occurrence book entry?

Every entry should include the date and exact time, the officer's identity, the precise location, a factual description of what happened, any action taken, and a signature or digital sign-off. Missing the timestamp or officer identity is the single most common weakness that undermines an entry's value as evidence.

Is a daily occurrence book legally admissible in court?

A properly maintained daily occurrence book can be used as evidence in civil or criminal proceedings, provided it was written contemporaneously and can be shown not to have been altered after the fact. Courts routinely treat undocumented events with scepticism, as noted by City Security Magazine, which makes tamper-evidence — whether serial numbering on paper or a hash-chained digital log — central to its reliability.

What is the difference between a daily occurrence book and an incident report?

A daily occurrence book is a continuous log of every event across a shift, while an incident report form is a standalone document covering one specific, serious event in detail. Serious DOB entries should cross-reference a separate incident report rather than duplicate its full content.

How long should daily occurrence book records be kept?

Most UK businesses retain occurrence book records for at least six years to align with the general limitation period under the Limitation Act 1980, though specific insurer or client contracts may require a longer period. There is no single statute fixing the retention period for commercial occurrence books, so the governing contract should be checked.

Who is responsible for writing in the occurrence book?

The officer, receptionist or duty manager on shift at the time of the event is responsible for writing their own entry, not a supervisor reviewing it afterwards. A site supervisor or duty manager then holds secondary responsibility for reviewing and countersigning entries before the book is archived.

Should a small business use a paper or digital occurrence book?

A small single-site reception can manage with a bound paper book and a diligent team, but any business managing multiple sites or officers benefits from a digital system that time-stamps entries automatically and prevents undetected edits. The trade-off is largely one of scale: paper works until auditing handwriting across many sites becomes impractical.

Securing your records with Pulse Operations

Every example in this article shows the same underlying problem: a daily occurrence book is only as trustworthy as the process that writes it, and a paper entry written hours after the fact can't prove when it was really made. Pulse Operations's occurrence book module covers 18 occurrence types and writes each entry with a locked timestamp the moment it happens, on the same platform as photo-verified patrols and incident logging.

At Priority First — the founding team's own London security and FM operation, where Pulse was built before being offered to other operators — occurrence records now sit alongside 4,900+ checked patrols and 100% photo-backed checkpoints, replacing what used to be paper sign-in sheets and a spreadsheet nobody fully trusted.

If your current occurrence book can't answer a client's 7am question with proof, not just a signature, get in touch with Pulse Operations for a walkthrough of the occurrence book and incident logging module, or see published plans on the pricing page.

Related Reading

• Closing an Occurrence Book Entry: UK Guide 2026
• Accident Book Requirements UK: 2026 Legal Guide
• Silvertrac Alternative 2026: Best UK Options Compared

★ Add pulse-operations.co.uk as a preferred source on Google