Plan for growth, governance and lifecycle cost
Choose platforms that scale across doors, sites and users without re-engineering. Confirm licence models, mobile credential costs and integration options you might need later (e.g. API access). Build governance into BAU: access reviews, leaver processes, audit trails and periodic system testing. From a standards perspective, NSI’s NCP 109 and BS EN 60839 give you a structured way to express requirements and measure compliance at each lifecycle stage—design, installation, commissioning and maintenance.
Finally, view cost over five to seven years, not just day one. Account for maintenance, spares, software updates and potential reader/credential upgrades. Often the “cheaper” choice costs more in administration or downtime.
A simple selection workflow you can defend
- Define outcomes with stakeholders (security, FM, IT, HR).
- Zone the building by risk and map user groups and flows.
- Write safety & privacy rules into the brief (BS 7273-4, UK GDPR for biometrics).
- Pick credentials by zone (cards/fobs, PINs, biometrics, mobile), agreeing two-factor where needed.
- Choose architecture (networked or cloud) that fits scale and IT posture; plan power/network properly.
- Specify integrations (CCTV, alarms, visitor management) and test cases. (See integration overview above.)
- Select standards-aligned kit and an installer who works to NSI NCP 109; require documented commissioning and training.
- Pilot, train, refine; then roll out with a maintenance plan and clear governance.
When you follow this sequence—and evidence key choices with recognised UK guidance—you get a system that’s both secure and workable, and a paper trail your auditors (and insurers) will appreciate.
