
Public buildings have to stay open to the public while keeping records, chambers and plant rooms closed, and every one of those movements must be auditable.
This page is a representative typical configuration for a municipal or government building with about 100 controlled doors, not a delivered project for a named authority. It shows how facility teams usually separate public circulation from staff-only zones while keeping a defensible record. Lobby and counter doors stay under supervised control during public hours, departmental corridors use reader groups so a transfer between departments is a permissions change rather than a new key, and records rooms, cash-handling areas and strong rooms apply two-person authorization with exportable audit history. Chambers and hearing rooms follow meeting calendars, plant and communications rooms stay with facilities and IT roles, and service doors accept time-boxed deliveries. Because continuity matters in public service, locks must keep working through network or power interruptions, and egress must stay code compliant at every door. Quantities, gateway ratios and specifications are planning estimates only; exact quantities and specifications are confirmed per project quotation.
| Site profile | A representative municipal, agency or civic building of roughly 100 controlled doors combining public counters with staff-only departments. |
| Openings in scope | Planning estimate of about 100 openings covering lobby and counter doors, departmental corridors, records rooms, chambers, plant rooms and service doors. |
| Credential architecture | Departmental reader groups, dual-authorization for sensitive rooms, calendar-driven chamber access and supervised visitor passes. |
| Software/integration | Central platform with audit export, group management and optional building-management linkage confirmed per project. |
| Network/power | Hardwired readers where possible, battery locks with offline capability elsewhere, and documented fallback during outages. |
| Compliance evidence | Electrical, radio and fire evidence for named SKUs are provided per RFQ; egress and accessibility follow local code. |
| Commercial terms | Current MOQ policy, sample terms and lead time are confirmed in writing per quotation; certificates and test reports for named SKUs are provided per RFQ. |
Separate the pathways rather than closing the building. Public circulation stays under supervision at a few lobby checkpoints, staff reach departments through reader groups, and sensitive rooms add a second authorization so no single person can open them alone. The result is an open public face with a defensible audit trail behind it.
| Opening group | Typical choice | Scale reasoning at 100 doors |
|---|---|---|
| Public lobby and counter doors | Supervised controlled opening with visitor passes | Public access stays open in hours but every entry is recorded. |
| Staff-only corridors | Reader locks grouped by department | Transfers between departments change permissions, not keys. |
| Records and strong rooms | Dual-authorization reader lock | Two-person rules protect sensitive records and cash handling. |
| Chambers and hearing rooms | Calendar-scheduled reader access | Access follows published meeting and hearing schedules. |
| Plant, IT and communications rooms | Hardwired reader with request-to-exit | Critical infrastructure stays with facilities and IT roles. |
| Service and loading doors | Outdoor-rated keypad with audit | Deliveries are time-boxed and recorded in the same system. |
| Evidence level | What this page states |
|---|---|
| L1 authorized named case | A named government authority case with identifiable facilities requires written authorization. None is published without NDA, so no such case is claimed here. |
| L2 public-reference case | Public procurement references to comparable civic buildings may be cited where independently published, without confirming we supplied them. |
| L3 NDA photo or record case | Photos and delivery records for similar civic buildings can be shared with qualified buyers under mutual NDA per RFQ. |
| L4 genericized record | Anonymized records keep door counts, departmental groups and audit logic while removing authority and site identity. |
| L5 representative typical configuration | What is published here is an L5 typical configuration: an illustrative 100-door civic plan for budgeting and RFQ discussion, not a statement of a delivered project. Higher levels are provided to qualified buyers under NDA per RFQ. |
This is a planning bill of materials for budgeting, not a quotation. Door counts follow the building survey, while reader, controller and dual-authorization quantities are confirmed against the departmental plan per project quotation.
| Component | Quantity logic | Notes |
|---|---|---|
| Component | Typical quantity logic | Notes |
| Reader locks | Around one per controlled door, counted from the door schedule | Departmental groups are configured centrally. |
| Dual-authorization controllers | One per sensitive records or strong room | Two-person release logic is specified with the authority. |
| Keypads | One per service or secondary entrance | Outdoor rating applies where the door is exposed. |
| Gateways | One per wireless coverage zone if battery locks are used | Heritage structures often need extra gateway zones. |
| Credential cards | Issued per employee and contractor role | Lost-card revocation is handled centrally. |
| Spare locks and batteries | A pool sized to building size and service response | Public-service continuity favours a local spare stock. |
Re-check the items below when your project is smaller or larger than the representative scale on this page.
| Scale factor | How the configuration changes | What to verify |
|---|---|---|
| Scale factor | Impact on configuration | Planning note |
| Public and staff flow | Open access and restricted access must coexist at one entrance | Design checkpoints before specifying hardware. |
| Department structure | Groups change with reorganisations | Keep group management in software, not on devices. |
| Records accountability | Audit retention becomes a legal obligation | Confirm retention and export format with records staff. |
| Procurement rules | Evidence and documentation are part of the award | Define the certificate pack required per RFQ. |
| Continuity of service | Outages cannot stop public service | Document offline behavior for every door tier. |
| Aging structures | Thick walls and heritage doors limit retrofits | Survey door thickness and cable routes early. |
Send your door schedule, departmental structure and audit requirements. We confirm reader and controller selection, dual-authorization logic, offline behavior and audit export; current MOQ policy, sample terms and lead time are confirmed in writing per quotation, and certificates and test reports for named SKUs are provided per RFQ.
Request Similar ConfigurationProject configurationsLast updated: November 1, 2026 · Reviewed by the Smart Lock Factory editorial team