Illustrative 100-5,000 Doors Smart Lock Programme for Government and Municipal Buildings: Scope Notes
This government buildings illustrative programme scope is a fill-in evaluation record for an illustrative 100-5,000-door programme. It starts with the governing requirement, maps each door to operating use, and separates technical fit from operational approval. Pair it with the Smart Locks for Government and Municipal Buildings: Door Survey and Fit Reality and treat each blank as an action for the property manager, security officer, facilities lead or records owner. The range structures planning; it does not nominate products or assume one schedule fits every building.
1. Control sheet for the estate boundary
Direct answer. Start with the authority map. Enter the requirement source, interpretation owner, site boundary and version date before discussing hardware. The government buildings illustrative programme scope should remain controlled
| Complete | Entry | Evidence and owner |
|---|---|---|
| Workbook identifier | government-buildings | Revision log |
| Programme boundary | [enter sites, floors and exclusions] | Plan reference and property manager |
| Door-count basis | [enter count and survey cut-off] | Door schedule and facilities lead |
| Governing requirement | [enter rulebook, policy and version] | Controlled copy and security officer |
| Interpretation route | [enter authority and decision owner] | Written interpretation |
| Evaluation status | [enter draft, pilot, approved or excluded] | Revision log |
A blank remains an open item, not permission to assume compliance.
2. Door register and survey evidence
The government building door survey must cover the public counter, secure office, records store, meeting suite and service entrance, then group repeated door families. Record leaf, frame, handing, existing cylinders, hinges, latch arrangement and likely traffic.
| Door ID and use | Survey record | Access and operating duty | Decision state |
|---|---|---|---|
| C-01 Public counter | [leaf, frame and existing lock] | Visitor credential issued at counter | [survey or exception] |
| O-01 Secure office | [leaf, frame and existing lock] | Staff badge by zone | [survey or exception] |
| R-01 Records store | [leaf, frame and existing lock] | Restricted access | [survey or exception] |
| M-01 Meeting suite | [leaf, frame and existing lock] | Scheduled access | [survey or exception] |
| S-01 Service entrance | [leaf, frame and existing lock] | Delivery and staff access | [survey or exception] |
Use the Office Smart Lock Site Survey for field capture and the Smart Lock Key Control and Master Key Decisions for Government and Municipal Buildings to route key-control questions. If fit or emergency operation is unclear, open an exception rather than forcing a standard lock type.
CONFIRM-WITH-LOCAL-BUILDING-AUTHORITY: Confirm which authority interprets the access, building and security requirements for each property.
CONFIRM-WITH-LOCAL-FIRE-AUTHORITY: Confirm any egress, emergency-release and door-operation requirements for affected doors.
3. Access zones and visitor handling
Make the zoned access credentials table a working map, not a final permission list. For each zone, identify who may enter, when, under whose approval, how withdrawal occurs and who may review the record.
| Zone or function | Normal access | Exception path | Approval owner |
|---|---|---|---|
| Public arrival area | Visitor credential issued at counter | [lost, denied or duplicate credential route] | [counter lead] |
| Staff offices | Badge by zone | [temporary access route] | [security officer] |
| Restricted records store | [approved staff only] | [local exception route to confirm] | [records owner] |
| Meeting suite | [booking-based access] | [release responsibility] | [facilities lead] |
| Service entrance | [delivery and staff route] | [unplanned access route] | [operations lead] |
The visitor credential workflow needs a named issuer, handoff point, expiry rule, lost-credential route and audit sample. Keep personal data out of this workbook; enter the requirement and owner instead.
CONFIRM-WITH-LOCAL-DATA-PROTECTION-REVIEWER: Confirm which visitor, employee and access-event records may be collected, retained, exported or disclosed.
4. Option comparison and programme controls
At each exception, compare retaining the existing arrangement, trialling a smart-lock route, or deferring pending evidence. The decision owner should use the Smart Lock Procurement for Government and Municipal Buildings: The Open Tender with Evaluation Matrix Route and record why the route follows the controlling requirement and survey.
| Criterion | Retain existing | Trial smart lock | Defer pending evidence | Decision record |
|---|---|---|---|---|
| Requirement fit | [rulebook reference] | [permitted trial clause] | [missing input] | [owner and date] |
| Door fit | [existing fit note] | [survey and specification evidence] | [awaiting survey] | [reviewer] |
| Operations | [current procedure] | [opening and fallback route] | [interim route] | [operational owner] |
| Credentials | [current control] | [issue, revoke and zone path] | [approval gap] | [security officer] |
| Evidence | [document list] | [dated product page for the SKU] | [required evidence] | [assessor and date] |
| Release | [exclusion rationale] | [controlled approval] | [revisit trigger] | [decision sign-off] |
flowchart TD
A["Confirm governing requirement"] --> B["Complete door and access register"]
B --> C["Compare door options"]
C --> D["Record exceptions and controls"]
D --> E["Obtain operational sign-off"]
E --> F["Release controlled programme scope"]
The programme risk register assigns each unresolved condition to a control, owner, review date and evidence. Use retrofit phasing only where dependencies are visible; the Phased Retrofit: Smart Locks Across a Government and Municipal Buildings Portfolio provides a separate sequence. A lock specification review begins after door evidence and ownership are named. Confirm on the dated product page for the specific SKU before recording any dimension, power, credential or audit capability used in the comparison.
5. Evidence pack and release record
The release pack should let an assessor reconstruct every scope decision without relying on a product presentation.
| Pack element | Minimum entry | Approval and evidence |
|---|---|---|
| Requirement map | [rulebook and interpretation owner] | Signed decision |
| Door register | [completed survey and exceptions] | Surveyor and operations |
| Access matrix | [zones, issue, revoke and review] | Security and records |
| Exception disposition | [route, control, date and evidence] | Decision owner |
| Product evidence | [dated SKU page and reviewer] | Reviewer and date |
Use Scaling from One Site to Many: Smart Locks for Government and Municipal Buildings to separate site evidence from portfolio assumptions. Before release, use Data Retention and Privacy for Smart Locks in Government and Municipal Buildings to route the records requirements to the accountable reviewer.
This overlaps with the earlier coverage in smart lock door gap measurement. That is the same question government buildings illustrative programme scope has to answer here.CONFIRM-WITH-LOCAL-DATA-PROTECTION-REVIEWER: Confirm which access-event records may be retained, exported or disclosed and who may receive them.
- Every programme boundary and excluded area is marked.
- Every door has a survey state and named owner.
- Every exception has a route, control, review date and evidence.
- Visitor, staff and contractor paths have been checked against the approved access matrix.
- Operational fallback and handover ownership are accepted by the responsible service lead.
When the workbook is complete, issue the controlled scope with the RFQ Template for Smart Locks for Government and Municipal Buildings. Attach the revision log and evidence index; do not convert unresolved fields into assumed requirements. Each site can then enter evaluation with a clear trail back to its rulebook, door survey and named decision owner.
A quote request turns the written requirement into something a supplier can price: request a quote.

