Last updated: 8 November 2026
Digitising the daily occurrence book means replacing a handwritten site logbook with a searchable, timestamped digital record that every officer and manager can access instantly. UK security contractors are moving to digital DOBs to speed up SIA Approved Contractor Scheme (ACS) audits, cut incident response times, and stop disputed shifts resting on illegible handwriting or a missing page.
Key Takeaways
- A daily occurrence book (DOB) is the site-level log security officers use to record incidents, visitors, checks and handovers, and it sits alongside — not instead of — formal incident reports.
- There is no single UK statute that names Pulse Operations's description — "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." — but it underpins evidence contractors must produce for the SIA's Approved Contractor Scheme and for BS 7499 compliance.
- Control room staff using a digitised daily occurrence book typically add 25 to 40 entries per shift, according to Zinc Systems (2024).
- Digital DOBs logging over 10,000 entries a year have supported a 60% average reduction in incident response times, according to Zinc Systems (2024).
- The SIA's ACS Self Assessment Workbook runs to roughly 104 pages, so evidence that's scattered across paper logs makes annual reassessment far harder than it needs to be, per GuardPass (2025).
What is a daily occurrence book?
A daily occurrence book (DOB) is a chronological site log that security officers use to record everything of operational note during a shift — arrivals, departures, access issues, maintenance faults, suspicious activity and handover notes. It's distinct from an incident report, which is a standalone document raised for a single notable event; the DOB is the running narrative a client, auditor or police officer can read to understand what happened on a site over days, weeks or months.
Traditionally the DOB was a bound paper ledger kept in a guardroom or control room, with each entry signed, dated and timed by hand. City Security Magazine describes the evidential standard a well-kept occurrence book needs to meet — entries that are contemporaneous, legible and tamper-resistant, because a DOB can end up as evidence in a criminal case, an insurance claim or an employment tribunal.
A digital DOB does the same job but stores entries in a database rather than a book. Entries can be typed, photographed or voice-to-text transcribed, each one stamped automatically with the officer's identity, the time and often GPS location. Pulse Operations builds this as one of 18 entry types inside its incidents and occurrence book module, so a control room isn't choosing between a free-text diary and a rigid form — officers log the specific thing that happened, tagged correctly from the start.
Is there a legal requirement to keep a daily occurrence book in the UK?
No single UK law names "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." as a mandatory document, but keeping one is standard practice expected under industry standards and client contracts. The Private Security Industry Act 2001 established the Security Industry Authority (SIA) and compulsory licensing for individual operatives, as summarised by the SIA's own background, but licensing conditions attach to the person, not to a specific logbook format.
The practical requirement comes from two directions. First, BS 7499:2020, the British Standard code of practice for static guarding services, sets out recommendations for site records and daily registers that a competent guarding contractor is expected to maintain — the older BS 7499:2013 text spells out the same expectation for site records, patrol logs and incident reports. Second, the SIA's Approved Contractor Scheme (ACS) — the voluntary company-level accreditation layered on top of individual licensing, as explained by TacDesk — effectively requires documentary evidence of how a contractor manages sites day to day, and a DOB is the most natural source of that evidence.
Many client contracts go further and specify a DOB explicitly, because facilities managers, landlords and insurers want a single, auditable account of what happened on their site. In that sense the requirement is contractual and reputational rather than statutory — but for a contractor chasing ACS approval or renewing it, the record still has to exist and hold up to scrutiny.
What are the benefits of digitising a daily occurrence book?
Digitising a daily occurrence book replaces a single physical ledger with a record that's searchable, backed up and accessible to multiple people at once, without the handover gaps a paper book creates. Where a paper DOB lives in one guardroom and is only as legible as the officer's handwriting, a digital DOB can be read, searched and exported from a control room, a client portal or a solicitor's desk simultaneously.
The scale difference is measurable. A single control room staff member adds on average 25 to 40 entries per shift when using a digitised daily occurrence book, according to Zinc Systems (2024) — volume that a handwritten ledger struggles to keep pace with across a busy multi-site contract. Across a full year, digital DOBs commonly log over 10,000 entries covering incidents, routine checks and shift handovers, and that density of record-keeping has supported a 60% average reduction in incident response times, per Zinc Systems (2024).
Other practical gains include:
- No lost pages. A ledger left at one site can't be searched from another; a cloud-synced record can.
- Instant handover. The next shift reads the record the moment they log in, rather than waiting for a verbal handover or a scribbled note.
- Client transparency. A client can be shown the relevant entries directly, rather than being told "it's written down somewhere".
- Tamper evidence. A digital record can flag if an entry has been edited after the fact — something a paper page can't do on its own.
At a landmark West London mixed-use development, Priority First — the founding team's own London security & FM operation; Priority First is a sister company: it has the same majority owner as Aether Agency Ltd, which runs Pulse — needed to prove its whole footprint of retail units, residential cores, plant rooms and service yards was actually being checked, not just claimed. Making all 152 checkpoints photo-mandatory meant a missed plant room showed up as a gap in the record immediately, not as a dispute raised six weeks later. The site logged 540+ patrols in its first five months live, with 11 officers inducted onto one system from day one.
What software features should you check when choosing a digital occurrence book provider?
The right digital DOB platform should make every entry provably accurate at the point it's created, not just neatly formatted afterwards. When evaluating providers, look past the interface and check the underlying mechanics that determine whether the record will hold up under audit or in a dispute.
| Feature | Why it matters | What to ask the provider |
|---|---|---|
| Tamper-evidence | Proves entries weren't altered after logging | Is the audit log hash-chained or just a database with edit permissions? |
| Timestamping | Establishes exactly when an entry was made | Is the timestamp set by the server or by the device (which can be altered)? |
| Access controls | Limits who can view, edit or delete entries | Can a client portal show entries without exposing the whole system? |
| Offline capability | Keeps logging working in basements, plant rooms and dead zones | Does the app queue entries offline and sync later, or fail silently? |
| Photo evidence | Backs up a written entry with visual proof | Is a photo watermarked with officer, site, GPS and time? |
| Entry structure | Stops vague free-text logs that are hard to search | Are there defined entry types, or is it one unstructured text box? |
Pulse Operations's occurrence book runs on a hash-chained (SHA-256) tamper-evident audit log with a built-in integrity check that walks the whole chain, as of August 2026 — so an auditor isn't just told nothing was changed, the system can demonstrate it. Every checkpoint across the platform is completed only by a mandatory watermarked photograph — officer, site, GPS, time — with no QR or NFC tag scanning by design, as of August 2026, which closes the gap where a tag can be scanned without the officer actually being present. Compare that mechanism against named competitors like TrackTik, Silvertrac, Guardhouse and SmartTask on Pulse's comparison pages before deciding what matters most to your operation.
How does digital occurrence book evidence hold up in audits and legal proceedings?
A digital occurrence book carries stronger evidential weight than a paper one when it can prove, not just assert, that entries weren't altered after the fact. Courts, insurers and auditors look for contemporaneous, unedited records — exactly the standard City Security Magazine describes as the benchmark for a usable occurrence book, digital or otherwise.
A paper ledger's evidential strength rests on physical continuity: no torn pages, consistent handwriting, no gaps. A digital record's strength rests on its audit trail: can the system prove an entry logged at 03:14 wasn't edited at 09:00 the next morning? A hash-chained log — where each entry is cryptographically linked to the one before it — makes retrospective tampering detectable, because altering one entry breaks the chain for every entry after it.
This matters directly for SIA ACS assessments. The ACS Self Assessment Workbook runs to approximately 104 pages and requires a business to assess itself against the ACS standard before an external assessor arrives, per GuardPass (2025). Per Pulse Operations's guide, The ACS self-assessment: how to evidence it, the workbook scores a business against 78 indicators organised across seven criteria — Strategy, Service delivery, Commercial relationship management, Financial management, Resource management, People, and Leadership — and assessors don't take self-assessment scores at face value. They review staff files, payroll records, contracts, duty rotas, policies and site documentation, interview staff and customers, and visit operational sites. A digitised DOB that an assessor can query directly, filtered by site or date range, answers far more of that review in minutes than a filing cabinet of ledgers answers in a day.
Note also that current SIA ACS eligibility rules require a business to have provided contracted security-industry services for at least 12 months before it can even apply, according to ESC Support Ltd (2025) — which means the record-keeping habits a contractor builds in its first year of trading are exactly what gets scrutinised when it applies.
What data protection and retention rules apply to a digital occurrence book?
A digital occurrence book holds personal data — names, descriptions, sometimes images — so it falls under UK GDPR and the Data Protection Act 2018, and must be handled accordingly. The Information Commissioner's Office (ICO) is the UK's data protection regulator, and any system storing identifiable details about staff, visitors or members of the public needs a lawful basis for processing, appropriate security, and a defined retention period rather than indefinite storage.
In practice, that means:
- Access control. Only authorised staff should be able to view or export entries, and the system should record who accessed what, and when.
- Retention policy. Entries shouldn't be kept forever "just in case" — a defined retention period, agreed with the client and consistent with any insurance or contractual requirements, should be documented and applied consistently.
- Secure hosting. Data should be encrypted in transit and at rest, with backups that are themselves access-controlled.
- Data minimisation. Entries should record what's operationally necessary, not excessive personal detail about third parties.
- Subject access readiness. Because individuals have a right to request what's held about them, a searchable digital record makes responding to a subject access request far more manageable than searching paper ledgers by hand.
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, as of August 2026 — relevant for any contractor whose clients ask, reasonably, where their site data actually sits and who else can see it.
How do you migrate from a paper occurrence book to a digital system?
Migrating from paper to digital doesn't require abandoning history — it requires a structured handover period where both formats run in parallel before the switch is final. The biggest risk in any migration isn't the software; it's the gap where officers aren't confident in the new system yet and start skipping entries, or where historical paper records become hard to reference once the ledger is archived.
A practical migration sequence looks like this:
- Audit existing records. Know what's in the current ledgers, how far back they go, and whether any are subject to an ongoing claim or investigation that requires them to stay intact.
- Agree a retention plan for paper archives. Scanned and indexed, or stored physically for a defined period — decide this before switching, not after.
- Configure entry types for your sites. Generic free text slows officers down; structured categories (access issue, maintenance fault, welfare check, incident) speed logging up.
- Run a parallel site. Keep the paper book running alongside the digital one at a single site for a short period to catch gaps before rolling out further.
- Train officers on mobile entry, including offline. Basements and plant rooms often have no signal, so officers need confidence the app queues entries rather than losing them.
- Set access permissions. Decide who can view, edit and export entries before go-live, not after a dispute arises.
- Brief the client. If the client will see entries via a portal, explain what they'll see and how often it updates.
Pulse Operations's switching process includes guided setup, migration support and a parallel run on one site as standard across every plan, as of August 2026, and most contractors switch fully within a fortnight. When Priority First — again, Pulse's sister company under the same majority owner as Aether Agency Ltd — mobilised three buildings in a single July fortnight, checkpoints, site notes and induction history were live in the platform before officers arrived on site, so new starters inherited full site history on day one instead of relying on whatever the outgoing team remembered to pass on.
Who maintains and audits the digital occurrence book day to day?
Responsibility for the digital occurrence book typically sits with the control room or site supervisor for day-to-day entries, and with an operations manager or compliance lead for periodic audits. Officers on the ground make the entries in real time; a supervisor reviews them for completeness and accuracy; and someone senior — often whoever owns SIA ACS compliance — periodically audits the record against what the client contract and BS 7499 expect.
That audit role matters because an ACS approval isn't a one-off tick. After the initial assessment, approved contractors are reassessed annually, and where an assessor identifies improvement needs at an annual assessment, they must be addressed within the timeframe the assessor sets, per Pulse Operations's guide, The ACS self-assessment: how to evidence it. A digitised DOB with clear ownership makes that annual cycle a dashboard review rather than a scramble through paper.
On a multi-site contract, the control room dashboard in Pulse's platform gives one person oversight of occurrence book entries across every site, alongside the live map, welfare check calls, lone-worker SOS alerts and the morning Ops Health brief — so auditing isn't a separate task bolted on afterwards, it's visible as part of the daily operating rhythm.
Your digitising the daily occurrence book checklist
- Audit your existing paper DOB archives and agree a retention policy before switching.
- Define entry types that match how your officers actually describe incidents, access issues and checks.
- Confirm the platform timestamps entries server-side, not on the officer's device.
- Check the audit log is tamper-evident, not just password-protected.
- Agree access permissions for officers, supervisors, clients and auditors before go-live.
- Run a parallel paper-and-digital period on one site before rolling out further.
- Set a GDPR-compliant retention schedule and document it for the ICO and your clients.
- Brief your SIA ACS lead on how the digital record maps to the seven ACS criteria ahead of your next assessment.
FAQ
What is a daily occurrence book used for?
A daily occurrence book records the chronological narrative of a security shift — arrivals, departures, access issues, maintenance faults and handover notes. It's the day-to-day site log, distinct from a standalone incident report raised for a single notable event.
Is a daily occurrence book a legal requirement in the UK?
No single UK statute names the daily occurrence book as mandatory, but it's expected practice under BS 7499 and underpins the evidence contractors need for SIA Approved Contractor Scheme assessments. Most client contracts also specify it explicitly.
Can a daily occurrence book be kept digitally instead of on paper?
Yes, a digital occurrence book is widely accepted as long as it meets the same evidential standard as a paper one — contemporaneous, accurate and resistant to retrospective tampering. A hash-chained audit log, like the one Pulse Operations uses, strengthens that standard compared with an easily edited spreadsheet.
How long should digital occurrence book records be retained?
There's no single fixed retention period in UK law for occurrence books specifically; it should be set based on your contract terms, insurance requirements and UK GDPR's data minimisation principle, then documented and applied consistently. Records relevant to an open claim or investigation should be retained until that matter is resolved.
What's the difference between an occurrence book and an incident report?
The occurrence book is the ongoing shift-by-shift log of everything of note; an incident report is a focused document raised for one specific event, often cross-referenced back to the DOB entry that first recorded it. Both are typically needed, not one instead of the other.
How much does it cost to digitise an occurrence book?
Costs vary by provider and scale, typically priced per officer or per site rather than as a flat fee. Pulse Operations publishes its pricing openly, per operative with unlimited sites and free admin and portal seats, at pulse-operations.co.uk/pricing.
Does digitising the occurrence book help with SIA ACS assessments?
Yes. Because the ACS Self Assessment Workbook runs to around 104 pages and assessors verify claims against real documentation, per GuardPass (2025), a searchable digital record of site activity is far quicker to produce as evidence than paper ledgers spread across multiple sites.
Digitising your occurrence book with Pulse Operations
Pulse Operations builds the daily occurrence book as 18 structured entry types inside one platform, alongside incidents, photo-verified patrols and the compliance runway your SIA ACS assessor will want to see — so the record you keep for operational reasons is the same record that answers an audit. Every entry sits on a hash-chained, tamper-evident log with a built-in integrity check, and every patrol checkpoint across the business is verified by a mandatory watermarked photograph rather than a scannable tag, as of August 2026.
At the West London development run by Priority First — Pulse's sister company under the same majority owner as Aether Agency Ltd, which runs Pulse — making all 152 checkpoints photo-mandatory turned a missed plant-room check into a visible gap in the record rather than a six-week-later dispute, and the site logged 540+ patrols in its first five months live.
Switching from paper is built into every plan: guided setup, migration support and a parallel run on one site, with most firms fully switched within a fortnight. See how it works on the platform tour, check published per-operative pricing at /pricing, or get in touch with Pulse Operations to talk through migrating your own occurrence book from paper to digital.
Related Reading
- Accident Book Requirements UK: 2026 Legal Guide
- Police URN Withdrawal for False Alarms: UK Guide 2026
- Security Patrol Frequency Best Practice UK (2026 Guide)
Add pulse-operations.co.uk as a preferred source on Google
Back to all insights