
Twenty doors fit one panel and one site, so the deciding question is workflow: schedules, visitor handling and integration with an existing access system.
This page presents a representative typical configuration for an office floor or small office building with about twenty controlled doors, the scale of a serviced office, a professional-practice building or a single-tenant headquarters floor. At twenty doors the whole estate still fits one access panel and one logical site, so the main design question is not hardware volume but workflow: which doors stay open during business hours, which need a badge at all times, who may issue visitor credentials, and how access hands over to an alarm or intercom after hours. Reception, the main entry and a staff entrance are normally online readers tied to schedules; meeting rooms, training rooms, quiet rooms and storage take scheduled or credential-only control; the comms room, server room and finance store need stricter access and a complete audit; kitchen, terrace and lift lobby follow building rules. Where an access control system already exists, readers should speak Wiegand or OSDP to it instead of creating a parallel system, and door hardware must match the egress and fail-safe or fail-secure requirement on each opening. Door counts, controller topology, credential formats and integration scope are planning estimates here; confirmed quantities and specifications are provided per project quotation after a walk-through and a review of fire and security requirements.
| Site profile | Planning estimate of one office floor or small building with about twenty controlled doors, a reception point and a small comms or server room. |
| Openings in scope | Estimate around 20 doors covering entrance, reception, meetings, offices, comms, storage, kitchen and service openings; final list follows a walk-through. |
| Credential architecture | Staff badges or mobile credentials by role, dated visitor and contractor codes, and a cleaner window outside office hours. |
| Software/integration | One site controller or cloud console with schedules and audit; Wiegand or OSDP link to an existing access system where one is installed. |
| Network/power | Hardwired or PoE readers on principal doors; battery locks acceptable on low-traffic interior doors; fail-safe or fail-secure chosen per opening. |
| Compliance evidence | Fire-rated and egress doors keep listed hardware and one-motion release, and certificates and test reports for named SKUs are provided per RFQ. |
| Commercial terms | Current MOQ policy, sample terms and lead time are confirmed in writing per quotation; warranty terms are confirmed in writing per quotation. |
Twenty doors suit a single controller with a clear schedule structure. The design separates public-facing openings, staff-only rooms and high-security rooms into three role tiers, then keeps visitor handling at reception so that daily operation does not depend on every employee issuing codes.
| Opening group | Configuration choice | Why at this scale |
|---|---|---|
| Main entrance and reception | Online reader plus intercom and release button | The public face of the floor needs monitored entry, visitor handling and a documented release path. |
| Staff and side entrance | Online reader on a schedule | A second entrance shortens morning queues and supports after-hours staff without opening the lobby. |
| Meeting and training rooms | Online or battery locks with booking schedules | Bookable rooms need time-bound access that matches the room booking rather than a permanent badge. |
| Comms and server room | Online lock with strict roles and full audit | Network and records equipment demands narrow access lists and reviewable entry history. |
| Storage and finance room | Online lock with separate role group | Stock and cash areas should not share the general staff group or its schedules. |
| Kitchen, terrace and lift lobby | Readers matched to building rules and egress | These openings usually sit under landlord or base-building policy rather than tenant control alone. |
| Evidence level | What this page states |
|---|---|
| L1 - Authorized named case study | An L1 record names the tenant or building, the installer and the delivered scope under signed authorization. We do not currently publish an L1 record for a 20-door office project. |
| L2 - Verifiable public reference | An L2 record would point to a checkable public source such as a building announcement or tenant fit-out notice. No such reference is cited on this page. |
| L3 - Photos and records under NDA | L3 evidence includes fit-out photographs, device schedules and commissioning records shared under NDA with qualified buyers during an RFQ. |
| L4 - Genericized project record | An L4 record retains the door count, floor layout, integration approach and handover lessons of a comparable fit-out without naming the tenant or address. |
| L5 - Representative typical configuration | This page is an L5 representative typical configuration for estimation and dialogue, not a delivered project; L1 to L4 evidence is provided to qualified buyers under NDA per RFQ. |
This is a planning BOM for fit-out budgeting, not a quotation. Reader counts follow the door schedule, and controller, power and integration items depend on what already exists in the base building.
| Component | Quantity logic | Notes |
|---|---|---|
| Online readers | One per controlled door in scope | Entrance, meeting and secure rooms drive the count; interior low-traffic doors can use battery locks. |
| Access controller or panel | One site controller for the floor | Twenty doors rarely justify multiple panels unless the base building mandates separate systems. |
| Power and cabling | PoE or local power per reader location | Existing containment and ceiling routes determine whether PoE is practical. |
| Credentials and visitor codes | Staff badges plus a dated visitor allowance | Reception-issued visitor codes keep temporary access out of the permanent badge list. |
| Integration module | Wiegand or OSDP link where a system exists | Avoiding a second console keeps one audit trail and one access list for security. |
| Exit devices and request-to-exit | Per egress door as specified | Free egress and fail-safe behaviour are legal requirements, not options. |
| Override keys and cylinders | One per lock, controlled stock | Facilities keep mechanical override under a documented key-control procedure. |
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 |
|---|---|---|
| Door count | Below ten doors a stand-alone smart lock set may suffice; above forty, zoned controllers and panel planning return. | Match the controller architecture to door count and future growth. |
| Existing access system | Buildings with a base-building system need reader compatibility, not a parallel platform. | Confirm Wiegand or OSDP support before ordering readers. |
| After-hours operation | Sites with late shifts need cleaner and contractor windows and alarm handover. | Define out-of-hours rules with security and cleaning contractors. |
| Visitor volume | Client-facing floors need reception-issued codes and escort rules; back-office floors need few. | Choose visitor workflow before specifying intercom hardware. |
| Door hardware condition | Heritage or heavy doors may need different lock bodies than new fit-outs. | Survey frames and fire labels before finalizing lock models. |
| Tenure and landlord scope | Leased floors divide responsibility between tenant and landlord for entrance doors. | Agree who owns and services each opening in the lease schedule. |
| Growth and subletting | Plans to sublet or add floors should favor expandable controllers and role structures. | Check license and capacity limits for future doors. |
Send your floor plan, door schedule and any existing access control details with a Request Similar Configuration note. We confirm reader choice, controller topology, egress behaviour and integration scope; 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