Digital Daily Occurrence Book: UK Compliance Guide 2026

Last updated: 3 November 2026

A digital daily occurrence book is a tamper-evident electronic log that records incidents, visitors, welfare checks and handover notes on a security site, replacing the paper DOB. UK guidance under BS 7499:2020 expects these records kept for at least 12 months after contract end, per COREDINATE (2025).

Key Takeaways

• A digital daily occurrence book is an electronic, timestamped replacement for the paper logbook used on security and FM sites to record incidents, visits and handovers.
• UK practice under BS 7499:2020 typically requires occurrence and patrol records to be kept for at least 12 months after a contract ends, according to COREDINATE (2025).
• UK employers with ten or more staff must keep a statutory accident book under the Social Security (Claims and Payments) Regulations 1979, retaining entries for at least three years, per LogIncident (2025).
• The Security Industry Authority employed 369 staff in 2024/25, the body that assesses occurrence book evidence under the Approved Contractor Scheme, according to Wikipedia (2024).
• Pulse Operations completes every checkpoint with a mandatory watermarked photograph rather than a tag scan, building the occurrence record automatically as officers patrol.

What is a digital daily occurrence book?

A digital daily occurrence book is a cloud-based or app-based record that captures every notable event on a security or facilities site — incidents, visitor movements, equipment faults, welfare checks and shift handovers — with a timestamp, author and often a photograph attached to each entry. It is the electronic successor to the paper DOB that sat in a site guard hut, where officers wrote entries by hand at the end of a shift.

On most modern platforms the occurrence book is tamper-evident, meaning entries cannot be edited or backdated without the system recording that an edit took place. Pulse Operations runs its occurrence book across 18 distinct incident types, from access control breaches to alarm activations, so officers log a consistent event type rather than freehand prose that varies by shift.

The purpose is twofold. First, it gives the site a continuous, admissible written record of what happened and when. Second, it gives the client — a shopping centre manager, an estates director, a facilities contractor — visibility of that record without having to walk to the guard hut and read a logbook. Pulse Operations' client portal exposes that same record to the client in real time, under the operator's own brand.

How does a digital occurrence book differ from a traditional paper logbook?

A digital occurrence book differs from a paper logbook mainly in verification, search and tamper resistance, rather than in what gets recorded. The underlying event — an intruder sighting, a leak, a missed delivery — is the same; the mechanism for proving it happened is not.

Paper logbooks rely on legibility and trust. A bored or rushed officer can write "all quiet, no issues" for an entire shift, and a client reading it six weeks later has no way to tell whether that entry reflects a genuine patrol or a five-minute writing exercise at the end of a night shift. Pages can go missing. Ink can be altered. There is no audit trail showing who accessed the book or when.

A digital system timestamps every entry automatically and, in Pulse Operations' case, chains entries together using a hash-chained (SHA-256) tamper-evident log with a built-in integrity check that walks the whole chain — so any attempt to alter a past entry breaks the chain and is visible. The officer app is native iOS and Android, built offline-first with self-healing sync, so entries made in a basement plant room with no signal still log correctly and sync once connectivity returns.

What legal or regulatory requirements apply to occurrence book entries in the UK?

UK occurrence book entries sit under several overlapping frameworks rather than one single law, and businesses need to satisfy all of them, not just one. The Private Security Industry Act 2001 established the Security Industry Authority (SIA), the statutory regulator for the private security industry, and created the licensing regime that underpins who may legally carry out guarding work in the first place.

The SIA runs the voluntary Approved Contractor Scheme (ACS), and its assessor guidance lists the daily occurrence book among the core documentation assessors examine when approving or reassessing a contractor, per the SIA Approved Contractor Scheme Assessor Guide, which explains that the ACS workbook scores a business against 78 indicators organised across seven criteria, 33 sub-criteria and each indicator carries a required baseline achievement level scored as zero, with extra points for evidenced good practice.

BS 7499:2020, the British Standard for static guarding, sets expectations for daily registers and site records of occurrences. UK GDPR applies the moment an occurrence book entry names an individual — a visitor, a trespasser, a member of staff — which means businesses hold a lawful basis for processing and must respond to subject access requests. The Information Commissioner's Office is the UK regulator for data protection, and its guidance applies to occurrence book data in the same way it applies to CCTV footage or HR files.

Where RIDDOR-reportable incidents occur — certain injuries, diseases and dangerous occurrences — the Health and Safety at Work etc. Act 1974 and the Reporting of Injuries, Diseases and Dangerous Occurrences Regulations require separate notification to the Health and Safety Executive, in addition to the occurrence book entry.

What should be logged in a daily occurrence book, and who maintains it?

A daily occurrence book should log every incident, access event, equipment fault, welfare check and handover note that affects a site's security or operational status, not just serious incidents. Typical entries include intruder alarms, suspicious persons, lost property, contractor arrivals, keyholding access, fire alarm activations, CCTV faults, and the condition of the site at shift change.

Responsibility for maintaining the book normally sits with the officer on duty at the point an event occurs, with the site manager or control room reviewing entries daily and the operations director or compliance lead auditing them periodically. On a platform like Pulse Operations, the control room — covering a live map, welfare check calls, lone-worker SOS and dispatch — sees entries as they are logged rather than at the end of a shift, so a pattern of break-ins at the same loading bay over several nights is visible immediately rather than buried across separate handwritten pages.

Common categories worth a dedicated entry type include:

• Security incidents (intrusion, theft, vandalism, aggression)
• Health and safety events (injuries, spills, trip hazards)
• Access control (lost badges, forced entry, contractor sign-in)
• Fire and life safety (alarm activations, false alarms, evacuations)
• Equipment and maintenance faults (CCTV down, lighting out, lift faults)
• Welfare checks and lone-worker confirmations
• Weather or environmental events affecting the site
• Shift handover notes and outstanding actions

Pulse Operations structures its occurrence book around 18 defined incident types precisely so that entries are consistent across sites and shifts, which matters when an auditor or client is comparing records across a 24-site portfolio rather than reading one officer's personal writing style.

In practice: when the founding team mobilised three buildings for Priority First — a sister company that shares the same majority owner as Aether Agency Ltd, which runs Pulse — in a single July 2026 fortnight, checkpoints, site notes, prior issues and inductions were loaded into the platform before officers set foot on site. New officers started with full site history on day one rather than relying on whatever the outgoing team happened to remember, cutting what is traditionally weeks of bedding-in to days from the handshake to the first photographed patrol.

How long must occurrence book records be retained under UK GDPR?

Occurrence book records must be retained long enough to satisfy contractual, insurance and regulatory needs, and UK practice under BS 7499:2020 typically sets that minimum at 12 months after contract end, according to COREDINATE (2025). That is a floor, not a ceiling — many contracts and insurers require longer, particularly where a claim or dispute is possible.

A related but separate obligation applies to accident records. UK employers with ten or more employees must keep a statutory accident book under the Social Security (Claims and Payments) Regulations 1979, and those entries must be preserved for at least three years, per LogIncident (2025). An occurrence book entry describing an injury does not replace this statutory accident book — both records may be needed side by side.

UK GDPR adds a data minimisation and storage limitation duty on top of these retention floors: personal data within occurrence entries should not be kept indefinitely "just in case", and businesses should document their retention schedule as part of their Article 30 record of processing activities. COREDINATE's own platform is in daily use by over 1,300 customers worldwide, an indication of how widely digital retention and audit-trail functionality has already replaced manual filing for this exact problem, per COREDINATE (2025).

Pulse Operations 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, which matters for operators who need to demonstrate where occurrence book data physically sits and who can access it.

What features should UK businesses look for in a digital occurrence book system?

Features worth prioritising include tamper-evidence, offline resilience, photo verification, client visibility and transparent pricing, because these are the points where paper logbooks and weaker digital tools fail most often. A system that simply digitises free-text entry without an audit trail solves the legibility problem but not the trust problem.

Tamper-evidence matters because an occurrence book that can be quietly edited after the fact has little evidential value in a dispute or insurance claim. Pulse Operations' audit log is hash-chained using SHA-256 and tamper-evident, with a built-in integrity check that walks the whole chain to confirm nothing has been altered.

Offline resilience matters because many sites — basements, plant rooms, rural compounds — have patchy signal. An officer app that only works online will produce gaps in the record exactly where coverage is weakest; Pulse Operations' app is offline-first with self-healing sync, so entries queue locally and sync once a connection returns.

Photo verification matters because a written entry alone is unfalsifiable either way. Pulse Operations completes every checkpoint with a mandatory watermarked photograph — officer, site, GPS, time — deliberately avoiding QR or NFC tag scans, because the photograph itself is the proof of completion rather than a scan that only proves a phone was near a tag. Across live operations this produces a 96.2% photo-verification rate on checkpoints over a trailing 90-day period as of July 2026, a figure published at pulse-operations.co.uk/benchmark.

"Because operators are busy and quote-gated pricing wastes their time. Our prices are on the website, per operative, seats free. If a platform makes you book a sales call just to learn the cost, ask what else they'd rather you didn't compare." — Mo Hassan, Founder, Pulse

Finally, published pricing matters operationally, not just commercially: a platform that forces a sales call before revealing cost tends to be the same platform that hides integration limits and contract terms. Pulse Operations publishes every tier openly at /pricing, priced per operative, with unlimited sites and free admin, control room and client portal seats on every plan.

Digital occurrence book or paper logbook: making the switch

The trade-off between staying on paper and moving to a digital occurrence book is largely a trade-off between familiarity and defensibility. Paper requires no training and no subscription cost, but it produces a record that is hard to search, easy to lose and effectively unfalsifiable in either direction — nobody can prove an entry is false, but equally nobody can prove it is true.

A digital system requires officers to adopt a new app and a business to budget for software, but it produces a record that a client, an insurer or an SIA ACS assessor can trust without taking the operator's word for it. For operators preparing for an ACS reassessment — which happens annually once initial approval is granted, per the guide The ACS self-assessment: how to evidence it — a searchable, tamper-evident occurrence book turns a weeks-long evidence-gathering exercise into an export.

Pulse Operations' guided onboarding includes migration and a parallel run on one site before full cutover, and most firms switch fully within a fortnight.

Your digital daily occurrence book checklist

• Confirm which of the 18-type (or equivalent) incident categories your current logbook actually distinguishes between, and consolidate where entries are duplicated or vague.
• Check your contract and insurance terms for the minimum retention period, remembering BS 7499:2020 practice sets a 12-month floor after contract end.
• Identify any occurrence entries that also trigger a statutory accident book entry under the Social Security (Claims and Payments) Regulations 1979.
• Document your occurrence book data as part of your UK GDPR Article 30 record of processing, including who can access it and for how long.
• Test offline logging on your weakest-signal site before relying on any digital system there.
• Ask any vendor to show, not describe, how an edited or deleted entry appears in the audit trail.
• Request published pricing before a sales call, and compare per-operative cost against unlimited-site and free-seat terms.
• Run a parallel trial on one site for at least a fortnight before retiring the paper book entirely.

FAQ

What is a digital daily occurrence book?

A digital daily occurrence book is an electronic log that records security and facilities incidents, visits, faults and handovers on a site, replacing the handwritten paper DOB. Entries are typically timestamped, searchable and, on tamper-evident platforms, cannot be altered without the alteration being visible.

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

A daily occurrence book is a continuous running log of everything happening on a site during a shift, while an incident report is a standalone document focused on one specific, usually more serious, event. Most digital occurrence books, including Pulse Operations' platform, let a single logged entry be escalated into a full incident report without re-entering the same details.

Is a digital daily occurrence book compliant with BS 7499 and SIA ACS?

A digital occurrence book can satisfy BS 7499:2020 and SIA ACS documentation requirements provided it retains records for the expected minimum period and produces evidence an assessor can review. The SIA Approved Contractor Scheme Assessor Guide confirms assessors review site documentation, staff files and policies directly rather than taking a self-assessment score at face value.

How long must occurrence book records be kept in the UK?

UK practice under BS 7499:2020 typically requires occurrence and patrol records to be kept for at least 12 months after contract end, according to COREDINATE (2025). Separately, statutory accident book entries must be kept for at least three years under the Social Security (Claims and Payments) Regulations 1979, per LogIncident (2025).

Are digital occurrence books better than paper logbooks?

Digital occurrence books are generally more defensible than paper logbooks because they produce timestamped, tamper-evident and searchable records rather than handwritten pages that can be lost or altered. Paper remains simpler to start with but offers no audit trail and no remote visibility for clients or site managers.

How much does digital occurrence book software cost in the UK?

Costs vary by vendor and are usually priced per operative, per site, or as a flat monthly platform fee. Pulse Operations publishes its tiers openly at /pricing rather than requiring a sales call, with pricing charged per operative and unlimited sites included.

How does a digital occurrence book integrate with other security systems?

A digital occurrence book typically sits alongside patrol management, incident logging, compliance tracking and a client-facing portal within the same platform, rather than as a standalone tool. Pulse Operations combines its occurrence book with photo-verified patrols, a live control room, a compliance runway covering SIA, BS 7858 and Martyn's Law, and full facilities and work order management in one system.

Securing your occurrence record with Pulse Operations

Every problem this article covers — unverifiable paper entries, lost pages, retention gaps, ACS assessors asking for evidence that does not exist — is the exact gap Pulse Operations was built to close. The occurrence book sits alongside photo-verified patrols and a live control room, so an entry logged at 3am in a plant room is visible to a manager, a client and an auditor the same morning, not six weeks later during a dispute.

Pulse Operations was built inside Priority First, a sister company that shares the same majority owner as Aether Agency Ltd, which runs Pulse — the founding team needed to prove overnight work to clients rather than ask to be believed, and built the occurrence book and patrol system they couldn't buy elsewhere. At a landmark West London mixed-use development, 152 checkpoints across retail, residential and plant areas were made photo-mandatory, with 540-plus patrols logged in the first five months live since February 2026, turning "was everything checked at 3am?" from a question into a record.

If your occurrence book currently lives on paper, in a spreadsheet, or across a handful of shift-handover WhatsApp messages nobody can search, take a look at how Pulse Operations' mobile patrol and keyholding service and compliance runway work together, or get your pricing directly from pulse-operations.co.uk/pricing — no sales call required.

Related Reading

• Daily Occurrence Book Example: A UK Guide for 2026
• Daily Occurrence Book PDF: Free Template & UK Rules
• Closing an Occurrence Book Entry: UK Guide 2026

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