Best Practices
A well-installed access control system will only stay reliable if it’s actively cared for. Maintenance isn’t a nice-to-have: it’s how you preserve safety (doors releasing on fire), security (only authorised people getting in), and compliance (audit trails that stand up to scrutiny). In the UK, good maintenance also means aligning to recognised standards and guidance so your facilities, IT and Health & Safety teams can defend decisions when they’re audited.
At ACCL we design, install and support systems across single sites and multi-site estates, and we maintain them through structured, evidence-led programmes. If you want a plan you can take to procurement, our commercial access control installation team can translate the principles below into a right-sized preventive maintenance regime and call-out SLA.
(See: Commercial Access Control Installation)
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.
Specifics for wireless locks and gateways
Wireless locks are excellent for retrofits and internal zoning, but they move some maintenance into battery management and radio health. Agree a replacement cycle based on duty cycles, configure advance low-battery alerts, and include firmware updates for locks and gateways in your patch calendar. If your fire strategy relies on radio-actuated release anywhere on an escape route, make sure your design and testing align with BS 7273-4 category requirements and critical signal path supervision.
Documentation and training keep systems tidy
Maintenance delivers the most value when the system is transparent: as-built drawings, labelled terminations, configuration exports, retention policies and role matrices should be alive documents, not files that vanish after handover. Train administrators to add and revoke users correctly, run reports, and triage common faults; train reception on visitor flows so the audit trail stays intact. When staff change, re-run training. Otherwise governance drifts and incidents creep in unnoticed.
A pragmatic periodic schedule (what “good” looks like)
Every estate is different, but the cadence below works well in UK offices, campuses and light industrial sites:
- Monthly: confirm reader and lock operation at representative doors; review alerts and error logs; inspect external doors for weather-related wear; verify storage capacity and backups for on-prem servers.
- Quarterly: test a sample of escape-route doors for release on fire alarm and relevant fault; exercise CCTV and alarm integrations; update firmware where safe to do so; review admin accounts and disable unused roles.
- Bi-annually: inspect and load-test PSUs and replace any ageing standby batteries as indicated; review DPIA and signage if biometrics are in scope; reconcile HR leavers with access lists and remove stale credentials.
- Annually: conduct a full witnessed life-safety test across all relevant doors; re-validate retention and privacy settings; perform a configuration backup and restore test; and refresh administrator training and incident playbooks.
The exact frequencies should reflect your risk and regulatory context, but the point stands: put the checks on a calendar, log the results, and keep improving.
Bringing it all together
If you align maintenance to recognised UK guidance, keep life-safety behaviour at the top of the agenda, and treat software and data governance as BAU, your system will remain predictable, auditable and safe for years. That’s ultimately the cheapest way to run access control: fewer emergency call-outs, fewer compliance surprises, and less friction for your people at the door.
If you’d like ACCL to review your current regime, or build a preventive maintenance and response plan you can take to the board, our team can help scope, deliver and document a programme that fits your estate and risk profile.




