Begin with people, areas and exceptions

Map permanent staff, casuals, contractors, cleaners, visitors and after-hours users. Then divide the premises into meaningful zones: public, staff-only, operational, high-value and safety-sensitive. Most design errors appear in the exceptions, such as early deliveries, weekend maintenance, shared tenancies or a manager who works across sites.

Build access levels around roles rather than programming one-off permissions for every person. Role-based groups make changes easier to review and reduce the risk of old access accumulating.

Decide what accountability is worth

A shared keypad code can control a door, but it rarely proves which person used it. Named cards, fobs or mobile credentials allow individual revocation and clearer event records. Two-factor methods may be appropriate for limited high-risk areas, but extra friction can produce workarounds if applied indiscriminately.

Event history is useful for investigating exceptions and system health. It should not be treated as infallible proof of a person’s location, nor quietly repurposed for attendance or performance monitoring without governance and appropriate advice.

Include physical and operational costs

The controller and reader are only part of the project. Door repairs, locking hardware, power supplies, batteries, cabling, network work, licences, enrolment, out-of-hours installation, training and documentation can materially affect scope.

A cheaper proposal may omit necessary door work or assume the client will supply network services and credentials. An itemised door schedule makes quote comparison more meaningful than comparing a single total.

Design for change

Staff numbers, tenants and business hours change. Confirm how quickly access can be removed, whether administrators can be delegated, how multiple sites are handled and whether new doors require additional controllers or licences.

Growth planning does not mean buying an enterprise platform for a small site. It means avoiding choices that make the next realistic change disproportionately difficult.

Turn policy into a practical access matrix

The final matrix should reflect the organisation’s actual roles. It should be reviewed when departments move, tenancies change or responsibilities are reorganised.

Questions a commercial buyer should ask

• Which door hardware and building works are included?
• Can each person be removed without changing everyone else’s credential?
• Who owns the server, network connection, cloud tenancy and configuration backup?
• Which functions keep operating during internet, server or communications failure?
• Are integrations native, licensed software connections or simple relay interfaces?
• What client work is assumed, including network ports, power, permits and access?
• What training, drawings, schedules and test records form part of handover?

Example starter and leaver workflow

For a starter, an authorised manager requests a role, location and start date. An administrator assigns an approved access group, issues the credential and records the recipient. The user is shown how to report a loss and why they must not lend the credential.

For a leaver, access is disabled at the agreed time rather than waiting for a card to be returned. Alarm authority, intercom directories, mobile apps and remote services are reviewed at the same time. The physical credential can then be recovered or marked as lost without delaying revocation.

Frequently asked questions