
Two hundred doors across a campus means offline classroom locks for daily teaching, with online control reserved for perimeter, office and shared buildings.
This page presents a representative typical configuration for a school campus with about 200 controlled doors, a scale that suits a K-12 campus, an academy group or a vocational college with several buildings. School access has to work for people who may not carry a phone, must survive long holidays and must not depend on a network link in every classroom. Classroom, office, store and equipment doors are therefore usually battery keypad or card locks on a staff master hierarchy, where teachers hold a teaching-level credential and the custodial team holds a wider maintenance level; exterior perimeter doors, reception and the front office sit on the online layer with time schedules and audit. Where a campus already issues ID cards, the card format and encoding must align with that system, and where it does not, cards and PINs can be phased in building by building. Fire and lockdown behaviour is agreed with the safety lead before any hardware is specified: egress stays mechanical and free at all times, while lockdown follows a documented local procedure rather than a lock that could trap occupants. Door counts, reader placement, battery cycles and integration scope on this page are planning estimates; confirmed quantities and specifications are provided per project quotation after a site survey and a review of the school safety plan.
| Site profile | Planning estimate of one school campus with about 200 controlled doors across teaching blocks, admin, sports and support buildings. |
| Openings in scope | Estimate classrooms, offices, stores, labs, gym, cafeteria, perimeter and stair openings; the final list follows a building-by-building survey. |
| Credential architecture | Offline keypad or card locks for teaching doors on a staff master hierarchy, with online perimeter and office control and dated visitor codes. |
| Software/integration | Central console for perimeter and admin schedules with audit, plus local management of offline locks and optional alignment with an existing ID card system. |
| Network/power | Battery locks with planned battery cycles across holidays; hardwired readers at perimeter and reception; mechanical override on every door. |
| Compliance evidence | Fire and stair doors keep listed hardware with one-motion egress, 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. |
Two hundred doors on a school campus split naturally into two layers: a large offline teaching population that must keep working through network or power interruptions, and a smaller online perimeter layer that the office and safety lead actually watch. The design keeps those layers separate and documents egress and lockdown behaviour before lock selection.
| Opening group | Configuration choice | Why at this scale |
|---|---|---|
| Classroom and teaching doors | Battery keypad or card locks on a staff hierarchy | A few hundred teaching doors are impractical to cable and must keep working on days without network coverage. |
| Front office and reception | Online readers with visitor codes and audit | Visitor sign-in and late arrivals need staffed issuance and a record of entry. |
| Exterior perimeter doors | Online readers on time schedules | Perimeter control is the layer the school actually monitors after hours and during events. |
| Gym, cafeteria and auditorium | Readers on events or shared staff groups | Shared facilities follow activity schedules rather than individual room assignment. |
| Storage and equipment rooms | Offline or online locks with maintenance roles | Science, sports and cleaning stores need access that is narrower than the teaching group. |
| Stair and fire doors | Listed exit hardware with mechanical override | Egress must stay free and mechanical; lockdown is a documented procedure, not a locked exit. |
| Evidence level | What this page states |
|---|---|
| L1 - Authorized named case study | An L1 record names the school or district, the buildings and the delivered scope under signed authorization. We do not currently publish an L1 record for a 200-door school project. |
| L2 - Verifiable public reference | An L2 record would point to a checkable public source such as a district facilities notice or procurement record. No such reference is cited on this page. |
| L3 - Photos and records under NDA | L3 evidence includes building photographs, device schedules and commissioning records shared under NDA with qualified buyers during an RFQ. |
| L4 - Genericized project record | An L4 record retains the campus layout, door mix, staff hierarchy and holiday operating lessons of a comparable school without naming the district. |
| L5 - Representative typical configuration | This page is an L5 representative typical configuration for planning discussion, not a delivered project record; L1 to L4 evidence is provided to qualified buyers under NDA per RFQ. |
This planning BOM supports campus-level budgeting and is not a quotation. Door counts come from building surveys, and the offline to online split depends on which openings the school intends to monitor centrally.
| Component | Quantity logic | Notes |
|---|---|---|
| Classroom and teaching locks | One per teaching door, plus a maintenance allowance | One lock generation keeps batteries, keypads and spare parts manageable across campus. |
| Perimeter and office readers | One per monitored exterior or admin opening | These doors carry the schedules, audits and visitor handling the office relies on. |
| Controllers and network | Per building for the online layer only | Only monitored openings need cabling, which keeps infrastructure cost proportionate. |
| Central console and roles | One tenancy for the campus | Staff hierarchy, audit retention and holiday rules are confirmed for the named platform. |
| Credential stock | Per staff member plus visitor and contractor supply | Staff turnover and visitor volumes drive consumable planning. |
| Battery management | Planned replacement cycles per building | Long holidays are the practical test of battery life and replacement scheduling. |
| Override keys and cylinders | One per lock, controlled by facilities | Custodial override stays documented and auditable across a large door population. |
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 | A single small school may run entirely offline; a large campus needs an online perimeter and admin layer. | Decide which openings must be monitored before counting hardware. |
| Campus layout | Multiple buildings add gateways, controllers and separate key hierarchies per site. | Plan building by building rather than campus-wide at once. |
| Term calendar and holidays | Long closures change battery planning, deep-clean access and security checks. | Agree holiday rules with facilities and security. |
| Existing ID card system | Districts that issue student or staff cards need format alignment from the start. | Confirm card technology with district IT early. |
| Staff turnover | High turnover demands fast credential revocation and bulk reissue procedures. | Design a simple issuance workflow for the office team. |
| Safety and lockdown policy | Local procedures determine which doors may be electronically controlled at all. | Review the safety plan before specifying any hardware. |
| Network availability | Older buildings may lack reliable network or power in teaching wings. | Survey connectivity before committing to online readers. |
Send your campus plans, door schedule and safety policy summary with a Request Similar Configuration note. We confirm the offline and online split, staff roles and egress behaviour; 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