Life safety first: prove release on alarm and fault
Security must never impede escape. Doors on escape routes must release reliably on fire alarm and on relevant faults; that behaviour must be designed, witnessed at commissioning, and routinely tested during maintenance. The latest update to BS 7273-4:2015+A2:2023 clarifies the critical signal path between the fire alarm and release devices and gives more detail on when acoustic or radio-actuated mechanisms are appropriate. Build those tests into your periodic regime and record the results—auditors (and insurers) will expect to see evidence that the release logic has been proved under realistic conditions.
Engineer doors to behave beautifully—then keep them that way
Most “mystery faults” are mechanical, not electronic. A mis-hung door, a tired closer or a reed contact that’s drifted out of alignment will cause more nuisance alarms than a server ever will. Maintenance should include visual inspection of hinges and closers, confirmation that doors latch cleanly, checks that monitored keeps and contacts report correctly, and cleaning of readers and housings (especially at external doors exposed to dust, salt or rain). Where hygiene or wear-and-tear is a concern, consider hands-free journeys to reduce touch points and mechanical strain; we outline practical options and upgrade paths in our short guide.
(See: Hands-Free Access Control)
Power, standby and electrical safety
Deterministic behaviour depends on clean low-voltage power. Routine maintenance should verify power supply health, charger operation, and standby battery condition, and it should include controlled tests of mains failure to confirm the intended fail-safe or fail-secure behaviour at each door. Electrical work and inspection should conform to BS 7671 (IET Wiring Regulations); installations that follow BS 7671 are widely recognised by the HSE as meeting legal duties for electrical safety, which is an important assurance point when you hand over documentation.
If your architecture uses PoE for readers or controllers, factor switch firmware, PoE budgets and UPS coverage into your checks. For outdoor controllers, inspect for water ingress and verify earth bonding where specified.
Software, firmware and cybersecurity as part of BAU
Modern platforms are software-defined, so maintenance must include firmware and security updates for controllers, readers, gateways and management servers—or the cloud tenant where applicable. Administrator access should follow the NCSC’s identity and access management guidance: strong authentication, least privilege, secure administration paths, and auditable changes. Treat “security hygiene” (patching, credential rotation, disabling unused interfaces) as non-negotiable items in your maintenance plan, not ad-hoc tasks after an incident.
We also recommend segmenting access control onto a dedicated VLAN, enforcing MFA for admin accounts, and using privileged access practices for any workstation that administers the platform—especially in larger estates or critical environments. The NCSC’s principles for secure privileged administration are a sensible benchmark here, even for physical security platforms.
For an overview of how IP networking underpins modern security estates—and how to design that fabric for reliability—see our primer:
IP Security System Installation
Data protection is a maintenance activity, not a policy shelf-item
Access logs are personal data. Where biometrics are used for recognition (e.g., fingerprint or facial templates), the underlying data is typically special category under UK GDPR. That raises the bar for security, transparency and retention—and it means DPIAs, signage and periodic policy reviews belong in your maintenance calendar. The ICO’s guidance is unambiguous on what counts as special category biometric data and the duties that follow; build those checks into BAU rather than treating them as one-off project deliverables.
