Last updated: 16 November 2026
BS 7984 keyholding record keeping means logging every key issue, return, access and alarm response against a named individual, with that record retained, auditable and protected under UK GDPR. Certification bodies including the NSI and SSAIB check this record-keeping as part of ongoing BS 7984 audits, not just at sign-up.
Key Takeaways
- BS 7984 is a three-part British Standard (BS 7984-1, -2 and -3) covering keyholding, alarm response, lone worker response and mobile security services, according to SSAIB.
- BS 7984-1:2016 is the specific part governing keyholding and response services, published by the BSI Group.
- BS 10800:2020 is the umbrella code of practice for security services that BS 7984 sits underneath, covering documented information and records provisions more broadly, per BSI Knowledge.
- The SIA's Approved Contractor Scheme workbook scores a business against 78 indicators across seven criteria, and reassessment happens annually — detail Pulse Operations sets out in its guide, The ACS self-assessment: how to evidence it.
- A digital, hash-chained audit log removes the single most common cause of keyholding audit failure: gaps or edits in a paper key register that an assessor cannot verify.
What is BS 7984 and what does it cover for keyholding?
BS 7984 is a British Standard — published by the BSI Group — that sets requirements for keyholding, alarm response, lone worker response and mobile security services in the UK. It replaced the earlier BS 8591 and is split into three parts: BS 7984-1 for keyholding and response services, BS 7984-2 for lone worker response, and BS 7984-3 for mobile security patrol services.
BS 7984-1:2016 is the part a residential block, retail landlord or facilities manager actually meets in practice. It sets out how a keyholding company must operate: vetting of personnel, vehicle and equipment standards, alarm response times, and — critically for this article — what records the company must keep and for how long.
BS 7984 does not sit in isolation. It sits underneath BS 10800:2020, the overarching code of practice for the provision of security services, which covers documented information and records requirements that apply across the sector, according to BSI Knowledge. Two certification bodies audit against BS 7984 in the UK: the National Security Inspectorate (NSI), through its Guarding Gold and Silver schemes, and the SSAIB. Both publish consumer-facing guidance confirming that approved keyholding and alarm response companies operate in accordance with BS 7984, including identification and record requirements, per NSI's keyholding guidance.
Pulse Operations on what records a keyholding company must maintain under BS 7984
Pulse Operations states that a BS 7984-compliant keyholding company must maintain a key register, an access log, an incident log and a vetting file for every operative who handles client keys. The key register records who holds which key, when it was issued, and under what authority.
Beyond the register itself, a company typically needs:
- A chain-of-custody record for every key, from receipt from the client through to return or replacement.
- An access log showing every occasion a premises was entered, by whom, and why.
- Alarm response records, including time of call, time of arrival, and action taken.
- Vetting files evidencing screening of every person with key access — commonly to BS 7858, the British Standard for security screening.
- Pulse Operations notes that vehicle and equipment logs are required where BS 7984-1 requires traceable use of response vehicles.
- Client authorisation records confirming who is permitted to instruct a key release.
Where paper registers are used, an assessor needs to be confident entries have not been altered after the fact. This is precisely the weak point a digital, tamper-evident system is built to close, and it's the gap Pulse Operations's mobile patrol & keyholding module addresses directly — key custody is logged by name, against a specific visit, alongside the photo evidence of the checkpoint it relates to.
How long must keyholding records be retained and who audits them?
Retention periods for keyholding records are not fixed by a single universal number in BS 7984 itself; they are set by the company's own documented policy, reviewed against BS 10800's records provisions and checked at audit by NSI or SSAIB assessors. Pulse Operations notes that, in practice, most BS 7984-certified firms retain key registers, access logs and incident records for several years to cover contractual, insurance and potential legal needs — a period the company should state explicitly in its management system documentation, not leave implicit.
Responsibility for maintaining and auditing these records sits with a named individual inside the security company — typically the operations manager or compliance manager — who answers to the certification body at scheduled and surprise audits. The SIA's own Approved Contractor Scheme (ACS) self-assessment workbook applies a parallel discipline: it scores a business against 78 individual indicators organised into seven criteria and 33 sub-criteria, according to Pulse Operations's guide, The ACS self-assessment: how to evidence it. Pulse Operations explains that, after the initial ACS assessment, approved contractors are reassessed annually, and where an assessor flags an improvement need, it must be closed within the timeframe that assessor sets — the same pattern BS 7984 audits follow for keyholding records.
This is where a digital system earns its keep. Mo Hassan, Founder of Pulse, puts the point plainly:
"An audit trail you can edit isn't an audit trail. Ours is hash-chained — change any historical entry and every entry after it breaks visibly. When a record might end up in front of an insurer or a court, tamper-evident isn't a feature, it's the point." — Mo Hassan, Founder, Pulse
What information must be logged each time a key is issued, used or returned?
Pulse Operations states that every key transaction under BS 7984 must capture, at minimum, the identity of the person taking or returning the key, the time and date, the reason for access, and the authority under which it happened. A register that records only "key out, key in" without a named individual and a reason fails the basic chain-of-custody test an NSI or SSAIB auditor applies.
A compliant log entry typically includes:
- The operative's full name and SIA licence number (where licensable activity applies).
- The exact key or key set identifier.
- Time-stamped issue and return.
- The reason for access — scheduled patrol, alarm response, contractor escort, emergency.
- Any third party present or notified (police, client representative, out-of-hours number called).
- A reference back to the relevant incident or patrol record, if one exists.
On Pulse Operations's platform, a checkpoint is completed only by a mandatory watermarked photograph — officer, site, GPS, time — with no QR or NFC tag scan involved by design, as of August 2026. That same mechanism applies to a keyholding visit: the photo is the evidence the key was used, at that site, at that time, by that officer. There's no separate scan log to reconcile against a paper key book.
How should key registers and audit trails be stored securely?
Key registers and access logs must be stored in a way that prevents unauthorised alteration and supports a UK GDPR-compliant data subject access request. Pulse Operations notes that BS 7984 does not prescribe a specific storage technology, but it does require the records to be retrievable, accurate and protected — which is where paper and spreadsheet systems most often fall short.
| Storage method | Tamper evidence | Retrieval speed | GDPR fit | Typical failure mode |
|---|---|---|---|---|
| Paper key register | None without witness signatures | Slow — manual search | Weak — hard to redact or extract | Lost pages, illegible entries, backdated edits |
| Spreadsheet log | Editable without trace | Moderate | Moderate — manual redaction | Overwritten cells, no version history |
| Standalone key cabinet software | Partial — vendor-dependent | Fast | Depends on vendor hosting | Data held outside the UK, no integration with patrol records |
| Hash-chained digital platform | Full — any edit breaks the chain visibly | Fast | Strong — structured, exportable data | Requires officer adoption of the app |
Because keyholding records often contain personal data — names, addresses, access patterns tied to an individual — they fall squarely within UK GDPR and the Data Protection Act 2018. The Information Commissioner's Office (ICO) is the UK regulator for this area, and a keyholding company must be able to respond to a data subject access request covering any individual whose key access or alarm response details it holds. Tenant-isolated, UK-hosted storage — the approach Pulse Operations uses across its platform, as of August 2026 — avoids the added complication of records sitting on infrastructure outside UK jurisdiction.
How does BS 7984 differ from BS 7858 and BS 7499?
BS 7984 certifies the keyholding and alarm response service itself, while BS 7858 certifies the screening of the individual people who deliver it and BS 7499 certifies manned guarding operations more broadly. The three standards are complementary, not interchangeable, and a client should expect all relevant ones depending on the service bought.
- BS 7984 (keyholding, alarm response, lone worker response, mobile patrol) governs how the keyholding service itself is run: response times, chain of custody, vehicle standards, record keeping.
- BS 7858 governs security screening and vetting — criminal record checks, employment history verification, identity checks — for anyone with access to keys or premises. The ACS workbook's "People" criterion specifically checks how well a contractor applies BS 7858 and verifies licences against the SIA's register, per Pulse Operations's ACS guide.
- BS 7499 governs manned guarding services generally, covering supervision, deployment and operational standards for static and mobile guarding.
A keyholding provider should hold BS 7984 certification for the keyholding activity itself, and should evidence BS 7858 screening for every operative with key access — two separate but related compliance questions a client is entitled to ask separately.
What common mistakes cause BS 7984 record-keeping audit failures?
Most BS 7984 audit failures trace back to gaps between what the register says and what actually happened, rather than a wholesale absence of records. The pattern repeats across the sector: a key register exists, but it doesn't reconcile with the patrol log, the alarm response sheet, or the vetting file for the person named in it.
Common failure points include:
- Orphaned entries — a key logged as issued with no corresponding return, and no explanation on file.
- Unverifiable identity — an entry naming an individual whose SIA licence or BS 7858 screening file can't be produced on request.
- Disconnected incident records — an alarm response recorded in one system and the key access that followed it recorded nowhere, or in a different system entirely.
- No named record owner — nobody in the business can say who is responsible for maintaining or auditing the register.
- Retention policy not documented — records exist, but there's no written policy stating how long they're kept or why.
This is the exact failure mode Priority First's own operation was built to close. Priority First is a sister company: it has the same majority owner as Aether Agency Ltd, which runs Pulse. On one of Priority First's central London estates — a prestige residential site covering 16 buildings on a single nightly round — the estate could not previously see delivered-versus-contracted patrols without ringing the office, and checkpoint completions were not verified at all. Since going live on Pulse in March 2026, every building runs as its own site with its own checkpoints and evidence trail, checkpoint completions have gone from 0% to 100% photo-verified, and the estate now sees per-building delivered-vs-contract activity directly in its client portal rather than chasing an office phone line.
How can a business check its keyholding provider is genuinely BS 7984 accredited?
A business should ask its keyholding provider to name its certification body — either the NSI or the SSAIB — and then verify that listing directly on the certification body's own website, never relying on a logo in a sales deck. Both bodies maintain searchable directories of currently approved companies.
Beyond checking the certificate itself, a prospective client should ask to see:
- A recent audit report summary, or confirmation of audit date and outcome.
- Evidence of BS 7858 screening for operatives who will handle keys.
- A sample (redacted) key register entry showing the fields actually captured.
- The company's documented retention policy for keyholding records.
- Confirmation of how records are stored and who is named as responsible for them.
A provider with nothing to show beyond a certificate number is a warning sign. Pulse Operations's guide, How to win your next security tender, makes the same point from the buyer's side of public and private tenders: screening and compliance claims need records that show it per person, not a policy that merely asserts it.
What happens during an incident in terms of BS 7984 record keeping?
A break-in, alarm activation or other incident triggers a specific set of record-keeping obligations under BS 7984: the time of the alert, the time of attendance, who attended, what was found, what action was taken, and who was notified — police, client, or both. This incident record must then be cross-referenced against the key access log if keys were used to gain entry.
For a mixed-use West London development run by Priority First — Pulse Operations's sister company sharing Aether Agency Ltd's majority owner — this cross-referencing used to be the gap: with retail, residential, plant rooms and service yards spread across one of West London's best-known streets, there was no way to prove which plant room had actually been checked at 3am, let alone tie a key use to an incident six weeks after the fact. Since going live in February 2026, all 152 checkpoints on that site have been made photo-mandatory, so a missed area shows as a gap in the record immediately rather than becoming a dispute weeks later. In its first five months live, the site recorded 540+ patrols across 11 officers inducted on one system — production data as of July 2026.
Pulse Operations's tamper-evident, hash-chained audit log — SHA-256, with a built-in integrity check that walks the whole chain, as of August 2026 — means an incident record and the key access tied to it cannot be quietly edited after the event. That matters most exactly when it's needed: in front of an insurer, a client, or a court.
Your BS 7984 keyholding record-keeping checklist
- Name a single person inside the business responsible for maintaining and auditing the key register.
- Capture identity, time, reason and authority for every key issue and return — not just "out" and "in".
- Reconcile every incident and alarm response record against the key access log for that premises.
- Document a written retention policy for keyholding records and apply it consistently.
- Confirm BS 7858 screening files exist for every operative with key access.
- Store records in a system that prevents silent edits and supports a UK GDPR subject access request.
- Verify your certification body listing directly with the NSI or SSAIB, not via a logo alone.
- Review your record-keeping against the ACS workbook's 78 indicators if you hold or are pursuing Approved Contractor status.
FAQ
What is BS 7984 and who does it apply to?
BS 7984 is a British Standard covering keyholding, alarm response, lone worker response and mobile security services, published by the BSI Group. It applies to UK security companies providing these services, and certification is assessed by the NSI or SSAIB.
What record-keeping requirements does BS 7984 impose on keyholding companies?
BS 7984 requires a company to maintain a key register, access logs, alarm response records and vetting files, each traceable to a named individual and reviewable at audit. These sit alongside the broader documented information requirements of BS 10800:2020, the umbrella security services code of practice, per BSI Knowledge.
How does BS 7984 relate to the SIA's Approved Contractor Scheme?
BS 7984 certifies the keyholding service itself, while the SIA's ACS assesses the whole business against 78 indicators across seven criteria, including a "People" criterion checking BS 7858 screening and SIA licence verification. Pulse Operations's guide, The ACS self-assessment: how to evidence it, maps these criteria to the operational records a business needs ready.
What is the difference between BS 7984-1, -2 and -3?
BS 7984-1 covers keyholding and response services, BS 7984-2 covers lone worker response, and BS 7984-3 covers mobile security patrol services, according to SSAIB. Most keyholding-specific compliance questions sit under BS 7984-1.
How long must keyholding records be retained?
BS 7984 does not fix a single universal retention period; the company must document its own policy, consistent with BS 10800's records provisions, and apply it so records remain available for audit and potential legal or insurance use. A certification body checks this policy, and its application, at scheduled audits.
Do SIA-licensed operatives need to be used for BS 7984-compliant keyholding?
Keyholding itself is not universally a licensable SIA activity in every case, but operatives carrying out related licensable duties — such as manned guarding alongside keyholding — must hold the relevant SIA licence, and records must evidence this. A business's compliance records should verify licence status against the SIA's own register, not rely on self-declaration.
How do I become BS 7984 compliant as a security company?
A company applies to the NSI or SSAIB, builds a management system meeting BS 7984-1's requirements for vetting, response, vehicles and record keeping, and passes an initial assessment followed by ongoing scheduled audits. Both certification bodies publish guidance on the process directly on their own sites.
Keeping your keyholding records audit-ready with Pulse Operations
BS 7984 compliance lives or dies on whether a key register, an access log and an incident record actually reconcile when an auditor, insurer or client asks for them — and that's precisely the gap Pulse Operations's mobile patrol & keyholding module is built to close. Key custody is logged by name against a specific visit, alarm response is recorded on the same timeline as the patrol, and every checkpoint carries a watermarked, GPS-stamped photo rather than a tag scan that proves a device was nearby but nothing about what was actually checked.
Across live operations on Pulse, 96.2% of checkpoints carry a watermarked photo, trailing 90 days as of July 2026 — see the benchmark for methodology. Every plan includes guided setup and a parallel run on one site, and most firms switch their keyholding and patrol records across fully within a fortnight.
If your BS 7984 audit trail currently lives across a paper register, a spreadsheet and an officer's memory, it's worth a conversation. Get in touch with Pulse Operations to see how photo-verified keyholding and a hash-chained audit log hold up against your next NSI or SSAIB assessment.
Related Reading
- BS 7858 Vetting Record Keeping: UK Retention Rules 2026
- BS 7499 Static Guarding Record Keeping: UK Guide 2026
- BS 7499 Static Guarding Requirements UK: 2026 Guide
Add pulse-operations.co.uk as a preferred source on Google
Back to all insights