
Zoned branch access from lobby to vault corridor, dual-control and opening procedures, auditable credential lifecycle, and evidence-led procurement.
Bank branches concentrate risk into a small set of doors: the public lobby after hours, cash areas, server and telecom rooms, vault corridors, offices holding sensitive records and back-of-house receiving. Access engineering here is built around control concepts that predate smart locks — dual control, time locks, segregation of duties, opening and closing routines — with electronic credentials adding scheduling, immediate revocation and a stronger audit record. Procurement is evidence-led: per-SKU documentation, test behavior and supply-chain verification carry more weight than features, and installation respects alarm panels, mantrap logic and insurance requirements. Branches in a network standardize on one approved specification so regional facilities teams can repeat the rollout. The government and regulated supply page covers similar evidence expectations, the data center page covers rack-level control, and the standards page covers documented requirements.
| Door zones | Lobby, staff corridor, cash and vault areas, records, server room and receiving each hold segregated credentials |
| Dual control | Sensitive openings can require two authorized credentials or a credential plus alarm-panel action, never one person silently |
| Audit lifecycle | Issue, change and revocation of staff and vendor credentials follow a documented, auditable process |
| Time procedures | Opening, closing and holiday schedules formalize who may arm, disarm and enter, with records retained by policy |
| Evidence procurement | Per-SKU documentation, test evidence and supplier verification are requested before specification approval |
| Alarm coordination | Access hardware is coordinated with the named alarm and monitoring systems rather than installed alongside them |
| BOM shape | Approved branch lock set, readers for controlled doors, integration scope, branch rollout kits and audit spares |
Electronic access manages the building; regulated cash and vault procedures typically retain mechanical and time-lock discipline on top.
| Dimension | Electronic credentials alone | Electronic plus retained dual control |
|---|---|---|
| Cash areas | One badge can enter silently | Two-person or credential-plus-panel rule enforced |
| Vault corridor | Schedule-based entry | Time-lock and opening procedures preserved |
| Audit strength | Records who badged | Records who and under what dual authorization |
| Staff loss | Fast revocation | Fast revocation plus key-holder process update |
| Insurance fit | May not satisfy policy | Designed around insurer and internal requirements |
| Typical fit | Offices and admin zones | Cash, vault and high-risk rooms |
Branch doors separate into public, staffed and regulated categories; only the latter take specialized hardware and procedures.
| Opening | Typical door | Lock approach |
|---|---|---|
| Main entrance | Glazed facade with revolving or balanced door | After-hours reader at a controlled side door, public flow unchanged |
| Staff / mantrap door | Security interlock door | Reader coordinated with mantrap logic and alarm state |
| Cash / vault corridor | Heavy rated security door | Access layer added without changing the vault’s certified opening hardware |
| Server / telecom room | Metal service door | Narrow IT credential with records and emergency break-glass preserved |
| Records / offices | Timber or glazed interior door | Department credentials scheduled by role and project need |
| Receiving / back door | Metal delivery door | Dual-staff or scheduled vendor access with camera coverage |
This example illustrates a typical configuration, not a specific customer project. Branch type and internal risk policy drive the final list.
| Component | Typical logic | Notes |
|---|---|---|
| Controlled-door readers | After-hours, staff and back doors | One approved specification repeated across the network |
| Sensitive-zone hardware | Cash-corridor and records controls | Specified around existing certified vault hardware |
| Integration scope | Alarm, monitoring and identity platform work | Named systems and dual-control rules confirmed in writing |
| Branch rollout kit | Standardized hardware, credentials template and signage | Enables repeatable regional deployment by facilities teams |
| Audit spares | Controlled readers and locks in branch stock | Swaps follow documented change control, not ad-hoc visits |
No, and they should not be expected to. Electronic access governs who reaches the cash corridor and when, while the vault’s certified opening hardware, time-lock discipline and two-person rules remain in force; the smart layer records the approach and coordinates with alarm state rather than replacing the regulated mechanism. Banks design sensitive doors as electronic control plus retained mechanical procedure, and every interaction between the two is documented for internal risk and insurer review. This conservatism is deliberate in a regulated environment.
Expect to request per-SKU technical specifications, evidence for the security and environmental claims, test or conformity documentation relevant to the market, manufacturing and supply-chain information, and a written statement of firmware update and support policy. Because regulated procurement is evidence-led, the package is reviewed before specification approval, not after a pilot. Suppliers experienced in regulated programs provide this documentation consistently; generic claims or refusal to verify the supply chain are treated as disqualifying signals rather than commercial friction.
Vendor credentials are scoped to scheduled windows — the cleaning contract’s hours, an ATM service visit, a planned HVAC window — and separate from staff groups, with back-door entry paired with camera coverage and dual-staff rules for anything near sensitive zones. A lost vendor credential is revoked immediately without waiting for the contractor to return a badge. Every after-hours vendor opening appears in the record the branch manager reviews, and recurring vendor lists are re-certified on a fixed cycle rather than living forever in the system.
Integration is scoped against the named alarm panel, monitoring station and identity platform, including who may disarm, what state permits which door, and how leaver events propagate — confirmed in writing per system and version. Mantrap logic, duress behavior and emergency egress stay unchanged and are re-tested after installation. Branches that prefer no deep integration still benefit from scheduled credentials and audit on doors, so the program can begin at the access layer and deepen integration by phase rather than betting the rollout on one interface project.
The BOM repeats one approved hardware specification across door zones and separates sensitive-zone controls, integration work and standardized branch kits, with MOQ and lead time confirmed in writing per quotation. Networks typically pilot one branch against defined acceptance tests before regional volume. Send the branch type list, controlled-door schedule, platform names and internal policy summary, and the quote maps hardware to zone and rollout phase so security, facilities and procurement review the same document.
Send the branch type list, controlled-door schedule and platform names — receive a zone-mapped BOM with evidence scope and written MOQ and lead-time terms.
Discuss your project (RFQ)Project configurationsLast updated: October 31, 2026 · Reviewed by the Smart Lock Factory editorial team