Last updated: 4 November 2026
Electronic occurrence book software replaces the paper daily occurrence book with a timestamped digital record that logs incidents, shift handovers and site activity under BS 7499:2020, the British Standard for static guarding. It matters now because enforcement of the Terrorism (Protection of Premises) Act 2025, known as Martyn's Law, begins from Spring 2027, and the Zinc Systems (2026) guidance notes that buildings with digital records already in place will be better positioned than those relying on paper.
Key Takeaways
- BS 7499:2020 requires security providers to maintain a daily register of occurrences, incidents and actions taken, recorded by time and date.
- Martyn's Law enforcement begins from Spring 2027, and buildings with digital operational records in place will be better positioned than those relying on paper when the SIA starts inspecting, per Zinc Systems (2026).
- COREDINATE's digital Daily Occurrence Book platform is used by 1,300+ customers worldwide, according to COREDINATE (2025), showing the market has already shifted away from paper at scale.
- A tamper-evident electronic log — one where every entry is sealed against silent editing — carries more weight in a dispute or SIA Approved Contractor Scheme (ACS) assessment than a handwritten book.
- Pulse Operations builds its occurrence book on a hash-chained (SHA-256) audit log with a built-in integrity check, as of August 2026.
What is an electronic occurrence book and how does it differ from paper?
An electronic occurrence book (e-OB) is a digital record-keeping system that logs security incidents, visitor movements, alarm activations and shift handovers against a timestamp, replacing the handwritten daily occurrence book that has sat on guard-house desks for decades. The underlying requirement comes from BS 7499:2020, the British Standard code of practice for static guarding, which specifies that a daily register must be maintained on all security assignments recording occurrences, incidents and actions by time and date.
The practical difference is tamper resistance. A paper occurrence book can be rewritten, a page can be torn out, and an entry can be backdated with nobody able to prove it happened. An electronic occurrence book timestamps every entry at the moment it's written, locks it once submitted, and — in a well-built system — chains each record to the one before it so any alteration breaks the chain and shows up immediately.
Some providers draw a distinction between a Daily Occurrence Book (DOB) and a Daily Occurrence Log (DOL), though in practice the SIA does not mandate a specific format or terminology for either. What matters to an assessor, a client, or a court is whether the record is contemporaneous, complete and unaltered — which is exactly what electronic systems are designed to prove.
Who is required to maintain an occurrence book under UK security licensing?
SIA-licensed security operatives working under the Private Security Industry Act 2001 are expected to maintain an occurrence record as a matter of professional practice, even though the Security Industry Authority (SIA) — the body that regulates the private security sector, sponsored by the Home Office — does not itself prescribe a legal format for the document. The obligation is embedded instead through contract specifications and British Standards.
Static guarding providers are the clearest case. BS 7499:2020 sets recommendations for managing guarding operations, and maintaining a daily register is one of its core provisions. Any security company seeking SIA Approved Contractor Scheme (ACS) status will be assessed against evidence that includes occurrence records, because the ACS workbook scores a business against 78 individual indicators covering service delivery and operational management, per Pulse Operations's guide, The ACS self-assessment: how to evidence it.
Beyond licensed guarding, the following typically keep an occurrence book:
- Mobile patrol and keyholding firms, logging each visit, access and alarm response.
- Shopping centres and retail estates, recording incidents, lost property and contractor access.
- Construction sites, logging deliveries, visitor access and security sweeps.
- In-house estates and facilities teams, particularly where Martyn's Law duties apply to publicly accessible venues.
- Event security teams, recording crowd incidents and medical callouts shift by shift.
What UK regulations and standards govern occurrence book record-keeping?
UK occurrence book record-keeping sits at the intersection of security standards and data protection law, with BS 7499:2020 governing what must be recorded and the UK GDPR and Data Protection Act 2018 governing how long it can be kept and who can access it. Neither regime specifies occurrence books by name, but both apply directly to the data inside them.
BS 7499:2020 is the operative standard for static guarding, specifying that occurrences, incidents and actions taken must be recorded by time and date. It's typically applied alongside BS 7858, the standard for security screening of personnel, and sits under the wider BS 10800 framework for provision of security services referenced by BSI.
Data protection obligations come from the Information Commissioner's Office (ICO), which enforces the UK GDPR and the Data Protection Act 2018. An occurrence book routinely contains personal data — names, vehicle registrations, descriptions, sometimes special category data such as health information from an incident. That means:
- Entries must be processed lawfully, fairly and for a specified purpose.
- Access should be limited to those who need it, which electronic permissions enforce far more reliably than a shared paper book sitting in a guard house.
- Retention periods should be defined and justified rather than kept indefinitely "just in case" — most operators align retention with their contract term plus a defined period for claims and audit, documented in a retention policy.
- Subject access requests can be answered faster when records are searchable rather than buried in handwritten pages.
For publicly accessible venues, the Terrorism (Protection of Premises) Act 2025 — Martyn's Law — adds another layer. Enforcement begins from Spring 2027, per Zinc Systems (2026), which means venues already running digital operational records will be in a stronger position than those still relying on paper when SIA inspections start. Pulse Operations tracks this requirement on its compliance runway alongside SIA licensing, DBS checks and statutory building compliance — see the compliance runway and the Martyn's Law guide.
What core features should electronic occurrence book software include?
Electronic occurrence book software should include timestamping, an audit trail, role-based user permissions and incident categorisation as its non-negotiable baseline, because these four features are what separate a genuine compliance record from a glorified notes app. Anything calling itself occurrence book software without them is a liability dressed as a solution.
| Feature | What it does | Why it matters |
|---|---|---|
| Timestamping | Locks the exact time and date to every entry at creation | Matches the BS 7499 requirement to record occurrences by time and date |
| Tamper-evident audit trail | Flags or blocks silent edits after submission | Protects the record's evidentiary weight in disputes and SIA assessments |
| Role-based permissions | Controls who can log, view, edit or approve entries | Supports GDPR's "need to know" access principle |
| Incident categorisation | Sorts entries by type — alarm, access, welfare, maintenance, security breach | Makes reporting and trend analysis possible instead of a wall of free text |
| Offline capability | Lets officers log entries without signal, syncing later | Keeps basements, car parks and rural sites covered |
| Search and export | Finds entries by date, site, officer or category in seconds | Speeds up subject access requests and client reporting |
Pulse Operations builds its occurrence book around 18 incident types and a hash-chained (SHA-256) audit log with a built-in integrity check that walks the whole chain — so if any entry is altered after the fact, the chain breaks and the gap is visible rather than silently overwritten, as of August 2026. The officer app is native iOS and Android, offline-first with self-healing sync, so entries logged in a basement plant room with no signal still land correctly once connectivity returns, as of August 2026.
"The assessors' pain is archaeology — records scattered across inboxes and cabinets. Run the operation in one system and the evidence assembles itself as a by-product of the work. Assessment prep should be an export, not an excavation." — Mo Hassan, Founder, Pulse
How does electronic occurrence book software prevent tampering with entries?
Tamper prevention in electronic occurrence book software relies on cryptographic sealing rather than trust, meaning each entry is mathematically linked to the one before it so any retrospective edit is immediately detectable. This is the single biggest practical advantage over paper, where a torn page or a rewritten line leaves no trace at all.
The mechanism that does this is called a hash chain. Each occurrence book entry generates a unique digital fingerprint (a hash) based partly on the content of the previous entry. Change anything in an earlier entry — the time, the wording, the officer name — and every fingerprint after it stops matching. Pulse Operations runs this using SHA-256 hashing with a built-in integrity check that walks the entire chain, as of August 2026, so a broken link is flagged rather than quietly accepted.
Checkpoint evidence works the same way. On Pulse, a patrol checkpoint is completed only by a mandatory watermarked photograph showing the officer, site, GPS location and time — deliberately with no QR or NFC tag scanning at all, as of August 2026. A tag scan proves a phone was near a sensor; a watermarked, geolocated photo is harder to fake and gives a client something to actually look at. Across live operations, 96.2% of checkpoints carry a watermarked photo over a trailing 90-day period as of July 2026 — see the full benchmark data.
Other safeguards worth checking in any system:
- UK hosting and tenant isolation. 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 — meaning one client's data cannot leak into another's environment.
- Role-based write access, so only authorised staff can create or amend entries.
- Immutable submission, where entries lock the moment they're submitted and corrections appear as new, linked entries rather than overwrites.
What mistakes do companies make switching from paper to electronic occurrence books?
The most common mistake companies make switching from paper to electronic occurrence books is treating it as a software rollout rather than an operational change, which leaves officers reverting to notebooks the first time the app feels unfamiliar. Software alone never fixes a records problem — adoption does.
Other recurring mistakes:
- No parallel run. Switching everyone over on day one, with no overlap period, means any teething issue becomes a gap in the record rather than a minor hiccup caught early.
- Ignoring offline sites. Basements, car parks, construction hoarding and rural estates often have poor signal — software that can't log offline and sync later simply fails where it's needed most.
- Migrating badly. Historical paper records get scanned as flat images instead of structured, searchable data, so the old book becomes a dead archive rather than a continuous history.
- Skipping training on categorisation. If officers aren't shown how to categorise incidents consistently, reporting becomes unreliable even though every entry is technically logged.
- No defined retention policy. Businesses migrate the record-keeping but never set out how long data is kept or who can access it under the Data Protection Act 2018, leaving a GDPR gap that paper's obscurity used to hide.
- Underestimating site handover. When a contract changes hands or new officers join, site history needs to travel with the record — not live in someone's head.
That last point is where mobilisation projects often come unstuck. Priority First — a sister company: it has the same majority owner as Aether Agency Ltd, which runs Pulse — added three buildings to its portfolio in one July 2026 fortnight. Checkpoints, site notes, prior issues and induction history were loaded into Pulse before officers arrived on site, so new starters had the full site history from day one rather than relying on handover conversations. What had previously taken weeks of bedding in across contract changes ran to days from the handshake to the first photographed patrol.
Pulse Operations builds every plan with guided setup, migration support and a parallel run on one site, and most firms switch fully within a fortnight, as of August 2026 — which addresses the two most common failure points directly: no overlap, and no structured migration.
How is an electronic occurrence book used day-to-day on a live contract?
An electronic occurrence book is used day-to-day to log incidents as they happen, record shift handovers between officers, and give supervisors and clients a live view of what's happening on site without waiting for a written report. It replaces the moment at shift end where an officer scribbles a summary into a book that nobody reads until something goes wrong.
In practice, a typical shift looks like this: an officer arrives, checks the occurrence book for open items from the previous shift, and begins logging as events occur — an alarm activation, a visitor signed in, a maintenance fault spotted on patrol, a welfare concern. Each entry is categorised, timestamped and visible to the control room in real time rather than discovered hours later.
At a landmark mixed-use development in West London, Priority First — again, the same sister-company relationship applies — manages retail, residential, plant rooms and service yards across 152 checkpoints with 11 officers. Every checkpoint is photo-mandatory, so a missed area shows up as a gap in the record immediately rather than becoming a dispute six weeks later when a client asks what happened. The site has run on Pulse since February 2026, with over 540 patrols logged in the first five months of production use as of July 2026.
Shift handover works the same way across the wider operation. Across Priority First's 24 sites, paper logs have given way to more than 4,900 patrols completed on the record and checked against production data, as of July 2026 — with every checkpoint backed by a watermarked photo, up from none before the switch. The client quote widely cited for this work — "we used to take everyone's word for it" — reflects exactly what an occurrence book is meant to solve: proof instead of trust.
Your electronic occurrence book software checklist
- Confirm the software timestamps every entry automatically and cannot backdate silently.
- Check whether the audit trail is genuinely tamper-evident, not just "edit history" that can be cleared.
- Ask how the system behaves offline — basements, car parks and rural sites need logging without signal.
- Verify incident categorisation matches your contract reporting requirements, not a generic default list.
- Confirm UK hosting and ask directly about tenant data isolation if you operate multiple client contracts.
- Request a parallel-run period rather than a single cut-over date.
- Check retention settings are configurable to match your GDPR retention policy, not fixed by the vendor.
- Ask for a live demo of how a client or auditor would pull a report — speed here matters under pressure.
FAQ
What is an electronic occurrence book?
An electronic occurrence book is a digital version of the daily occurrence book used in UK security operations, logging incidents, shift handovers and site activity with automatic timestamps rather than handwritten pages. It's built to meet the recording requirements in BS 7499:2020 while adding tamper-evidence that paper can't offer.
Is an electronic occurrence book legally admissible as evidence?
Yes, provided the record is contemporaneous, accurate and demonstrably unaltered, which is exactly what a tamper-evident audit trail is designed to prove. A hash-chained log, where any edit breaks a visible chain, gives a stronger evidentiary position than a paper book that could be rewritten without detection.
Does the SIA require a specific format for occurrence books?
No, the Security Industry Authority does not mandate a specific format or software for occurrence books. The practical requirement to maintain one comes from contract specifications and BS 7499:2020, the British Standard for static guarding, which requires a daily register of occurrences, incidents and actions.
How long should occurrence book records be retained?
Retention should be set by a documented policy under the Data Protection Act 2018, typically covering the contract term plus a period for potential claims or audit, rather than kept indefinitely. The ICO expects data to be held no longer than necessary for its stated purpose, so retention periods should be justified and reviewed rather than left open-ended.
Can electronic occurrence books be used across multiple sites?
Yes, electronic occurrence book software is designed to run across multiple sites from a single platform, with permissions controlling who sees which site's records. This matters for providers managing portfolios the size of Priority First's 24 sites — a sister company sharing the same majority owner as Aether Agency Ltd, which runs Pulse — where one login covers the whole estate instead of four separate systems and a spreadsheet.
How much does electronic occurrence book software cost in the UK?
Pricing varies by provider and is typically charged per operative rather than per site, with published tiers available to compare directly — see Pulse Operations's pricing for an example of per-operative pricing with unlimited sites and free admin and portal seats. Businesses should treat any quote that bundles vague "setup fees" with cautious scrutiny and ask for the full published rate card before committing.
What's the difference between a Daily Occurrence Book (DOB) and a Daily Occurrence Log (DOL)?
The two terms are often used interchangeably in UK security practice, with no single mandated definition from the SIA distinguishing them. What matters in either case is that the record is contemporaneous, categorised and tamper-evident — the label matters far less than the integrity of the entries inside it.
Securing your occurrence book with Pulse Operations
Switching from a paper occurrence book to a digital one is the exact problem Pulse Operations was built to solve — not as a bolt-on notes feature, but as a tamper-evident daily occurrence book with 18 incident types sitting inside the same platform as photo-verified patrols, the control room and the compliance runway. Every entry locks the moment it's submitted, and the hash-chained audit log means a client, auditor or assessor can trust the record without having to trust the guard house.
This isn't theoretical: it's how Priority First — a sister company sharing the same majority owner as Aether Agency Ltd, which runs Pulse — runs occurrence records and checkpoint evidence across 24 London sites, migrated from paper sign-in sheets and a spreadsheet nobody fully trusted.
If your business is still running on a paper book, or a digital system that nobody can prove hasn't been edited, get a demo of the occurrence book and incident logging inside Pulse Operations's security platform and see what a tamper-evident record actually looks like on a live site.
Related Reading
- Closing an Occurrence Book Entry: UK Guide 2026
- Daily Occurrence Book Example: A UK Guide for 2026
- Daily Occurrence Book PDF: Free Template & UK Rules
Add pulse-operations.co.uk as a preferred source on Google
Back to all insights