Staff areas need written house-rule clauses before hardware: roster-only access, time windows, privacy overlays and a signed after-cleaning sweep.

Geplaatst op: apr. 29, 2024

Smart Locks for Staff Areas

Smart Locks for Staff Areas

The main door is policed. The server room is policed. The four doors that almost never are — the office breakroom, the staff locker room, the lactation room, the prayer room — are precisely the doors where the building's culture shows up in writing. They are also the doors where a single unreturned fob, a single borrowed code, a single propped-open shift can quietly become policy. This handbook is the fix: a library of numbered house-rule clauses for office staff areas, drafted in adoption order, each tied to the lock capability it assumes.

Direct answer: Smart locks for office staff areas are best deployed under a written staff-area access handbook — numbered clauses defining each welfare door's allowed persons, allowed credential type, allowed hours, privacy rules, escort rules and handover procedure, with the electronic lock chosen door-by-door to enforce exactly those clauses. The clauses come first; the hardware specification falls out of them. The four rooms (breakroom, locker room, lactation room, prayer room) share a credential hierarchy and an out-of-hours etiquette but diverge sharply on privacy, scheduling and the after-cleaning sweep.

Apartment-side guidance — concierge office, laundry plant room, waste-store, on-call flat — lives in the sibling Smart Locks for Apartment Staff Areas. Biometric fitout specifics for shared staff rooms live in Fingerprint Smart Locks for Staff Rooms. Portfolio-level office procurement lives in Smart Lock Procurement for Office Buildings. This article covers the office staff-area domain only.

How to Use This Handbook

The handbook is organised in numbered Parts. Parts I–II set the frame (definitions, door classification, the register). Parts III–VI are the house-rule clauses themselves, one Part per room: breakroom, locker room, lactation room, prayer / multi-faith reflection room. Parts VIII–IX are the cross-cutting duties that touch every room: out-of-hours etiquette and the after-cleaning sweep. Part VII is the credential hierarchy — the privilege map that binds the four rooms together. Part X is audit, breach and change-control. Part XI is the hardware reconciliation — a table mapping each clause family to the device capability it depends on. Part XII is adoption.

Reading conventions:

  • Clauses are blockquoted. Lift them into your office rules verbatim, substituting bracketed fields (Office, role list, Window, Interval) with local values.
  • Every clause carries a usage note explaining what behaviour it prevents and which lock capability it presumes.
  • Capability blanks rule. Wherever a clause needs a device behaviour — does the lock support per-credential expiry? Does it enforce time windows on the device? Does it log events? — the number and the yes/no is a capture item to verify against the model’s published specification or in writing with the supplier before the clause is signed. This handbook never invents a capability.
  • Biometric specifics are deliberately not re-litigated here. Credential enrollment technique for shared staff rooms is covered in the fingerprint staff-room playbook. This article governs the staff-area domain: who may hold what, at which door, during which hours, with which privacy expectation, and how it survives the cleaning crew.
  • Apartment staff areas are a different document. The resident-facing definitions in Apartment Staff Areas — "residents are never staff", concierge office, laundry plant room — do not apply here. Office staff areas are governed by employment contract, lease, HR policy and accessibility law, not by resident-vs-staff boundaries.

Fact discipline: this handbook states no prices, no order quantities, no delivery timelines, no warranty terms, and no certification claims. Commercial terms are resolved through a quote request; per-model capabilities through each product page; sample lock trials through order samples.

Part I — Frame Clauses

An office staff-area handbook without definitions is a list of grievances waiting to happen. These clauses set the vocabulary before the lock list arrives.

Clause 1 (Staff Area Defined). A staff area is any space within Office to which visitors, contractors and members of the public have no lawful access in the ordinary course of business, regardless of whether the door physically faces a public corridor. Staff areas include, at minimum: the breakroom, the locker room, the lactation room, the prayer or multi-faith reflection room, and any service riser reached through a staff door.

Usage note. The "regardless of door orientation" wording matters. Office plans are redrawn; a door that opens onto a corridor the public uses can still govern a staff welfare room. This clause prevents the argument "it's our corridor too."

Clause 2 (Door Classes). Every staff door is assigned exactly one of four classes: Class S (Staff-Roster) — entry restricted to a defined roster of named roles; Class T (Timed-Staff) — roster plus an allowed-hours window enforced on the lock; Class P (Privacy) — roster plus a privacy overlay (single-occupancy, schedule, no-entry reason demanded); Class E (Emergency-Reachable) — normally locked, with a documented emergency entry path that does not rely on a functioning battery. Class assignments are recorded in the Staff Area Register (Part II).

Usage note. Class P is the clause most often skipped and most needed for lactation and prayer rooms: any room whose purpose collapses the moment a stranger walks through must carry a privacy overlay in writing, not in custom. Whether a given model can enforce single-occupancy, refuse concurrent entries, or refuse entry-without-reason is a product-page fact to verify in writing per model.

Clause 3 (Contractors and Visitors Are Never Staff by Default. No contractor fob, visitor badge or guest app-credential grants access to any staff area, for any reason, including "I'm just grabbing a coffee". Where a contractor or visitor needs a staff-area service — a lactation break, a quiet prayer, a hot drink — the interface is an escort (Part VIII) or a separately scheduled shared slot (Clauses 24 and 30), never a door.

Usage note. This single clause eliminates the most common staff-area breach: the "helpful" facilities manager who issues a cleaning crew fob and quietly never retracts it. It also disciplines hardware selection: staff-area locks must allow per-credential expiry so that contractor credentials cannot outlive their window (capability to verify in writing per model).

Clause 4 (One Handbook). This handbook supersedes ad-hoc door rules, kitchen Slack threads, and the office manager's white board. Where a staff-area rule conflicts with a general office rule, the staff-area rule governs that door. Amendments follow the change-control procedure in Clause 40.

Usage note. The "one handbook" principle is what makes Parts VII–IX enforceable: credential tiers and out-of-hours etiquette fail when they live in three documents and a Slack thread.

Part II — The Staff Area Register

Before any lock is specified, every staff door is entered on a register. The register is the contract between the rules and the hardware, and the document a new office or facilities manager inherits instead of a rumour.

Table 1 — Staff Area Register template (illustrative first entries for a 120-person floor).

Door IDSpaceClassAllowed persons (roster ref)Hours windowEscort rules applyCredential typePrivacy overlayEmergency pathNotes to confirm
WEL-01Breakroom (front door)SAll current employees + cleaning crew window06:00–22:00Yes (Part VIII)capture: card / passcode / appNoneMechanical key in custodyTime-window enforcement on device?
WEL-02Breakroom (appliance store)TOffice manager + cleaners window09:00–18:00YesCaptureNoneMechanical key in custodyPer-user deletion granularity?
WEL-03Locker room (entry)SRostered locker-holders only06:00–22:00No (peer roster)CaptureLocker-by-locker assignmentMechanical key in custodyPer-credential expiry support?
WEL-04Lactation roomPNursing parent roster + accessibility booking24h (booking)Yes (escort on request)capture: single-occupancySingle-occupancy, scheduledMechanical key in custodyRefusal of concurrent entry on device?
WEL-05Prayer / reflection roomPAll current employees + booked visitors24h (booking)YesCaptureSharing-schedule publishedMechanical key in custodySchedule display integrated?
WEL-06After-cleaning sweep boxCCleaning lead + duty managerAfter-hours onlyYesCard + separate custody keyAudit-loggedDocumented break-in pathAudit-record depth?

Usage note. The "Notes to verify in writing" column is where the handbook meets procurement reality. Each entry becomes a line in the capability questionnaire you send to the supplier or a checklist against the product page. The empty credential column is deliberate: credential type is a Part XI decision, made after the rules, not before.

Before the first row goes onto the register, Clause 2's taxonomy is worth sketching once, because each of the four classes commits the door to a different device behaviour:

classDiagram
    class StaffDoor["Staff Door"]
    note for StaffDoor "<<abstract>> · +Register entry WEL-nn · +Allowed persons roster reference"
    class ClassS_StaffRoster["Class S Staff Roster"]
    note for ClassS_StaffRoster "+Entry restricted to named roles · +No device time window assumed"
    class ClassT_TimedStaff["Class T Timed Staff"]
    note for ClassT_TimedStaff "+Roster plus allowed-hours window · +Window enforced on the lock"
    class ClassP_Privacy["Class P Privacy"]
    note for ClassP_Privacy "+Single-occupancy and booking rules · +No-entry reason never demanded"
    class ClassE_EmergencyReachable["Class E Emergency Reachable"]
    note for ClassE_EmergencyReachable "+Documented entry path independent of battery"
    class StaffAreaRegister["Staff Area Register"]
    note for StaffAreaRegister "+One row per staff door · +Capture questions per row"
    StaffDoor <|-- ClassS_StaffRoster
    StaffDoor <|-- ClassT_TimedStaff
    StaffDoor <|-- ClassP_Privacy
    StaffDoor <|-- ClassE_EmergencyReachable
    StaffAreaRegister "1" --> "many" StaffDoor : assigns exactly one class per Clause 2

Part III — Breakroom Clauses

The breakroom is the most heavily trafficked welfare room on a corporate floor. It is the only room where cleaning staff, contractors, employees and occasionally visitors are all legitimate users at different hours. The clauses below assume a single breakroom with an internal appliance store or hot-drink station; multi-room pantries scale by repeating the register.

Clause 5 (Roster, Not Face). Breakroom access attaches to the office roster, not to the individual. On any day, the roster names at most capture: number persons with breakroom access; a contractor or temporary worker receives access through a separate window (Clauses 8, 12), never a personal credential that outlives the engagement.

Usage note. This presumes the lock can issue and delete or expire credentials at manageable granularity — a device capability to verify in writing per model on the product page. Where a model cannot delete a single credential without disturbing the rest of the roster, Clause 5 is unenforceable and the breakroom should rely on a shared-post credential under Clause 6 instead.

Clause 6 (Shared Post Credential Discipline). Where the breakroom lock uses a shared staff credential (card or code issued to the post), the shared value is recorded only in the custody register (Clause 26), is treated as compromised on every departure of any person who knew it, and is changed on a fixed interval of capture: interval or on any departure, whichever comes first.

Usage note. Cross-reference rather than repetition: rotation mechanics for passcode devices are written out clause-by-clause in the SLK-1104 password access conventions referenced in the fingerprint staff-room playbook. This clause binds that machinery to the breakroom post specifically.

Clause 7 (Peak Hour Traffic Wave). The breakroom is governed by traffic, not by roster alone. During the named peak windows — typically late morning, lunch, and late afternoon — the breakroom door is held open under standing presence; outside the peak windows, the door is locked and roster-only. The published peak windows are recorded in the register (Part II).

Usage note. Whether the "held open" state is enforced by the lock (a public-class mode), by a staff-roster member physically holding the door, or by a time-schedule on the device, depends on the model — capability capture per Part XI. Equipment-wise, propping a locked door defeats the rule; the lock or the policy must own that state.

Clause 8 (Allergy and Dietary Corner Is Inside). Any segregated shelf, fridge or cabinet used to support allergy- or religion-driven dietary requirements is reachable only from inside the breakroom, never from a corridor hatch or pass-through. Where the segregated zone requires a further lock, it follows Clause 5 (roster) or Clause 6 (shared post) and is recorded as WEL-07 in the register.

Usage note. A low-tech clause that determines interior fit-out, not hardware — but it prevents the "I'll just grab the oat milk" pattern that defeats every breakroom access rule and quietly undermines a colleague's allergy plan.

Clause 9 (Hot Drink Discipline). Where the appliance store is governed by a separate lock (WEL-02), the appliance store credential is held by the office manager and one named deputy only. After-hours, the appliance store is locked and reopens only at the published time on the next business day.

Usage note. This presumes the lock supports differentiated grant (managers get the appliance store, employees get the breakroom) — capability to verify in writing per model.

Clause 10 (Contractor Slug Defaults). Cleaning, vending and coffee-machine technicians enter under Part IX escort rules and during the published cleaning window. Their credential is auto-expiring — never a standing roster credential — and is re-issued on each engagement.

Usage note. Auto-expiring contractor credentials are the difference between a roving breach and a closed book. Whether a given lock can issue an expiring credential on a defined date without re-enrollment is a per-model capability to verify in writing.

Part IV — Locker Room Clauses

The locker room is the staff-area door where the population moves slowest but the asset density is highest — wallets, keys, devices, often medication. The clauses below assume individual lockers inside a single locked room; per-locker electronic locks live in the fingerprint staff-room playbook.

Clause 11 (Roster, Not Cardholder). Locker room access attaches to the locker holder's roster, not to the card holder. A card found in a desk drawer after the rotation does not grant locker-room access on the next rotation; the locker-room credential is re-issued to the new rotation's roster.

Usage note. Re-issuance at rotation speed presumes the lock can delete and re-issue a credential without disturbing other holders — capability to verify in writing per model.

Clause 12 (Personal Credential, Not Shared). Every locker-room credential is personal. Sharing a credential — handing the card to a colleague to fetch a forgotten jacket — is a breach (Clause 39) even where the act is benign. The lock does not enforce it; the people who enforce it are the locker holder and the duty manager.

Usage note. This clause is the reason a "just hold my card" pattern is a documented breach, not a cultural quirk. Devices that share an unlock event log between concurrent uses make this clause easier to police — capability to verify in writing per model.

Clause 13 (Lost Credential Lock-Down). A lost or stolen locker-room credential is reported the same shift. The credential is deleted from the lock the same business day. Replacement credentials are issued only after the holder's identity is verified against the HR roster, not against the report alone.

Usage note. Same-day deletion is the threshold at which locker-room locks pay for themselves. Whether the chosen model can delete a single credential without touching others is a per-model capability to verify in writing.

Clause 14 (Medication Locker Overlay). Where a small subset of lockers is used to store employee medication (insulin, prescribed controlled drugs), that subset is on a separate lock with its own register entry (WEL-08). Access is restricted to the named holder of the medication and to one named welfare officer; the medication locker is never on the same lock as personal effects.

Usage note. A medication locker is a Class P door in spirit, even where its occupants are few. Whether the chosen lock can issue a tightly-held credential to a single named user (and refuse others) is a capability to verify in writing per model.

Clause 15 (Shower or Wash Room Accessible). Where the locker room contains a shower or wash room, that room is treated as Class P — single-occupancy by default — and follows Clauses 24–26 with the same booking discipline as a lactation room.

Usage note. Privacy expectations scale with the activity, not with the building class.

Part V — Lactation Room Clauses

The lactation room is the staff-area door whose purpose collapses the moment it is misused. It is governed not by traffic but by booking, single-occupancy and a documented refusal rule.

Clause 16 (Booking Required). Lactation room access requires a booking. The booking is recorded against a named roster entry and a time window. Walk-in requests are accommodated only when the room is empty and the prior booking has ended.

Usage note. Whether the lock can hold a schedule (per-user, per-time-window) and reject unbooked entry is a per-model capability to verify in writing. Where the lock cannot enforce a schedule, the booking lives in the calendar and the lock remains locked until the booked slot, with the prior holder's passcode disabled at the booking boundary (capability to verify in writing).

Clause 17 (Single-Occupancy). The lactation room is single-occupancy. The lock refuses a second entry while the first is inside. The first occupant may extend the booking or vacate the room; the lock does not permit an override of the single-occupancy rule by a manager.

Usage note. Refusal of concurrent entry is a capability to verify in writing per model. Where the lock cannot refuse a second entry, the room must rely on a visible-from-outside occupancy indicator and the duty manager as backstop, with the privacy overlay weakened accordingly.

Clause 18 (No Reason Stated). No person inside or outside the room may demand the reason for a booking, the contents of any bag brought in, or the identity of the nursing parent. Staff who witness the booking do not share the booking detail outside HR or welfare officers bound by Clause 22.

Usage note. "No reason stated" is the rule that protects the room from becoming a place where asking is treated as routine. It is enforced by culture, not by hardware.

Clause 19 (Visitors and Contractors Are Not Admitted). Lactation room access is for nursing parents on the office roster and for named welfare officers. Visitors, contractors and any non-roster person may not enter, including for "just checking in".

Usage note. Cross-link to Clause 3: contractors are never staff by default.

Clause 20 (Refusal of Unscheduled Entry). A person carrying a valid staff credential but without a booking is refused entry by the lock at the booking boundary. The refusal event is logged. The logged event is reviewed by the welfare officer weekly, not by line management, and is used only to detect credential misuse, never to discipline a booked occupant.

Usage note. "Refusal of unscheduled entry" is the operational expression of Clauses 16 and 17. Whether the lock supports this refusal at the schedule level is a capability to verify in writing per model.

Clause 21 (Cleaning Window). The lactation room is cleaned between bookings, never during a booking. The after-cleaning sweep (Clause 32) is the only authorised cleaning event.

Usage note. The clause binds the Part VIII etiquette to the Part IX sweep.

Part VI — Prayer / Multi-Faith Reflection Room Clauses

The prayer room is the staff-area door whose second usage serves the most diverse set of users. It is governed by a sharing schedule, a no-observance-imposed rule and a footwear and ablution overlay.

Clause 22 (Sharing Schedule Published). The prayer room is open during office hours to any current employee, with a sharing schedule published on the door or on the booking system. Slot length is fixed; back-to-back slots are the norm; buffer time is allowed between slots for any required preparation.

Usage note. The publishing method is policy, not hardware; the lock enforces only that a booked slot is the slot that opens. Whether the lock supports per-slot schedule enforcement is a capability to verify in writing per model.

Clause 23 (No Observance Imposed). No person may impose a particular religious observance, reading, or ritual on the room or on another user. Furniture, soft furnishings and orientation markers that meet a single faith are withdrawn or replaced with neutral alternatives. A multi-faith reflection room is not a prayer room for one faith.

Usage note. A furniture and procurement contract, not a hardware rule.

Clause 24 (Footwear and Ablution Overlay). Where the room requires shoe removal, a footwear storage shelf is provided outside the room. Where ablution is a stated practice of one or more users, an adjacent wash facility is provided and signed.

Usage note. The clauses bind facilities (the shelf, the washroom signage) to the room.

Clause 25 (Reflection-Only Usage Permitted). The prayer room may also be used as a quiet reflection room — meditation, decompression, mental-health break — without a stated observance. The same booking, sharing-schedule and refusal rules apply. A reflection booking is not a subordinate opening to a prayer booking.

Usage note. The clause makes the room's mental-health utility explicit so the booking rule is not a religion-only rule. Whether the lock distinguishes the booking type by code is a capability to verify in writing per model.

Part VII — Credential Hierarchy Clauses

The four rooms share a single credential hierarchy. The hierarchy is what binds the rooms to one another and to the office roster.

Clause 26 (Master Roster Credential). A current employee on the office roster receives a Class S (Staff-Roster) credential valid at the breakroom (WEL-01) and the locker room (WEL-03) during the published hours. The credential is non-transferable, expires on the holder's last day of employment, and is deleted from every staff-area lock on that date.

Usage note. Auto-expiry on last-day is a capability to verify in writing per model.

Table 2 — Credential hierarchy (privilege tier × door × default window × privacy overlay).

TierHolder profileBreakroomLocker roomLactation roomPrayer roomDefault windowPrivacy overlay
Tier 1 — MasterCurrent employeeYesYes (assigned locker)Yes (booked)Yes (booked)06:00–22:00 + booking-boundSingle-occupancy where Class P
Tier 2 — DeputyOffice manager + 1 named deputyYesYesYesYesExtendedSame
Tier 3 — Welfare officerHR welfare officerYesYesYes (admin only)Yes24h with audit logSingle-occupancy
Tier 4 — Cleaning leadCleaning vendorYes (cleaning window)Yes (cleaning window)Yes (after-cleaning sweep)Yes (cleaning window)Window onlyAudit-logged
Tier 5 — ContractorNon-roster vendorWindow onlyWindow onlyNoWindow onlyWindow onlyRefused by default
Tier 6 — VisitorPublic visitorN/AN/AN/AN/AN/ARefused

Clause 27 (Deputy Tier Limits). A Tier 2 (Office manager or named deputy) credential is held by exactly two named persons at any time. A deputy credential grants entry to the appliance store (WEL-02) and the medication locker (WEL-08) but is logged on every authority read.

Usage note. Logged authority reads are the receipt that catches a deputy going somewhere they should not. Whether the lock produces a separate audit trail for higher-privilege credentials is a capability to verify in writing per model.

Clause 28 (Welfare Officer Audit Immunity). A Tier 3 (Welfare officer) credential is held by exactly one named person. It is the only credential permitted to enter a Class P room outside a booking for the purpose of an inspection or welfare check, and the inspection is logged with a written reason captured in the duty log the same shift.

Usage note. Welfare-officer exceptions are a privilege and an audit item at once. The duty log is paper or electronic; the lock logs the entry; the duty log names the reason.

Clause 29 (Cleaning Lead Time-Box). A Tier 4 (Cleaning lead) credential is held by exactly one named cleaning lead per shift. It is valid only during the published cleaning window and is auto-disabled at the window's end. Auto-disable is enforced by the lock, not by policy alone.

Usage note. Time-boxed credentials are the difference between a roving breach and a closed book. Whether the lock supports time-window enforcement on a per-credential basis is a capability to verify in writing per model.

Clause 30 (Visitor Refusal). A visitor may use the prayer room or reflection room only when booked in advance through the welfare officer, and only when the building's accessibility or open-house rules apply. The visitor credential is a separate, single-use, expiring code — never a standing pass.

Usage note. Single-use, expiring visitor codes are a capability to verify in writing per model.

Part VIII — Out-of-Hours Etiquette Clauses

Out-of-hours — late evenings, weekends, public holidays, late-shift cleaning — is when the staff-area rules drift fastest. The clauses below govern every staff door between the published close of business and the published open of the next business day.

Clause 31 (Locked but Accessible). Every staff door is locked outside the published hours. A current employee with a master roster credential may still enter; a deputy, welfare officer or cleaning lead may enter only within their privilege window. The lock's time-window behaviour is the source of truth — policy does not second-guess the lock.

Usage note. The clause binds the published hours to the lock's actual behaviour. Whether the lock can hold a per-credential time window that varies by tier is a capability to verify in writing per model.

Table 3 — Out-of-hours behaviour by door × privilege tier × window.

DoorTier 1 masterTier 2 deputyTier 3 welfareTier 4 cleaningTier 5 contractorNotes
Breakroom (WEL-01)Yes (06:00–22:00); refused outsideYes (06:00–22:00)Yes (audit-logged)Yes (cleaning window only)Window onlyTime-window on device?
Appliance store (WEL-02)No (manager only)Yes (within window)Yes (audit-logged)NoNoRefusal of Tier 1
Locker room (WEL-03)Yes (06:00–22:00)YesYesYes (window only)NoAsset-density rule applies
Lactation room (WEL-04)Yes (booked, 24h)Yes (audit-logged)Yes (audit-logged)Yes (after-cleaning sweep)NoBooking is source of truth
Prayer room (WEL-05)Yes (06:00–22:00); refused overnightYesYesYes (window only)NoOvernight refusal

Clause 32 (Lone-Worker Rule). A current employee entering any staff area alone between 22:00 and 06:00 checks in with the duty manager on arrival. The check-in is a one-line note on the duty log; the check-out is a second note. The check-in exists so the duty manager knows who is in the building, not so the duty manager supervises.

Usage note. Lone-worker check-in is the minimum governance the building owes its cleaners and night-shift staff. It is enforced by the duty log, not by the lock; the lock records the entry and exit.

Clause 33 (Late-Session Door Discipline). A staff member remaining in a staff area after 22:00 — for an extended shift, a booked overnight lactation session, a booked overnight reflection session — closes the door behind them on leaving for any reason. The door does not remain propped open on a late session.

Usage note. Propping defeats every rule. The clause is enforceable because the door is staff-controlled and a peer can challenge a propped door; the lock's role is to refuse entry to anyone whose credential has not been re-validated for the late session.

Clause 34 (Weekend and Holiday Window). On weekends and public holidays, every staff door follows the published weekend window — typically a shorter roster and a single named cleaning window — recorded on the register's "Hours window" column. The window is enforced by the lock and is not a discretionary policy.

Usage note. A weekend window is policy; the lock's enforcement of it is hardware. Whether the lock can hold two distinct windows (weekday / weekend / public holiday) is a capability to verify in writing per model.

Clause 35 (Cleaning Crew Escort). A cleaning crew member working outside their cleaning window must be escorted by the cleaning lead (Tier 4) or by the duty manager. The escort rule applies even to a single cleaning crew member entering a single staff room; one cleaner alone is treated as a worker to be accounted for, not as a roving contractor.

Usage note. Cross-link to Clause 10. The escort rule binds Clause 10's window-only rule to Part VIII.

Part IX — After-Cleaning Sweep Clauses

The after-cleaning sweep is the most quietly important event in the staff-area cycle. It is the moment when a locked door is re-armed, a sweep log is signed, and the room is signed off until the next booking. A missed sweep is the difference between a clean room and an unaccounted room.

Clause 36 (Defined Sweep Steps). The after-cleaning sweep is the following steps, in order: (i) the cleaning lead confirms the room is empty; (ii) all surfaces and appliances are wiped down to the building-published standard; (iii) the consumable stock (soap, paper, tea, milk) is checked and topped up; (iv) the bins are emptied; (v) the door is closed and the lock is re-armed; (vi) the sweep log is signed at the door by the cleaning lead and the duty manager.

Usage note. The clause is a checklist. Whether the lock supports a "re-arm" step in its own API (or whether re-arming is mechanical — closing the door) depends on the model; confirm per model.

Table 4 — After-cleaning sweep checklist (per room × step × accountable role).

StepBreakroomLocker roomLactation roomPrayer roomAccountable role
Confirm room emptyYesYes (per shower/wash if present)Yes (booking log)Yes (booking log)Cleaning lead
Wipe-downYes (appliances + surfaces)Yes (lockers + benches)Yes (chair + counter)Yes (carpet/rug + surfaces)Cleaning lead
Consumable top-upTea / coffee / milk / soapSoap / paperSoap / paperNone unless providedCleaning lead
Bins emptiedYesYesYesYesCleaning lead
Door closed and lock re-armedYesYesYesYesCleaning lead
Sweep log signedYesYesYesYesCleaning lead + duty manager

Clause 37 (Missed Sweep Buck-Stops). A sweep that is not signed off before the next booking opens is a breach (Clause 39). The cleaning lead of that shift is named in the breach record and the next sweep is run by the duty manager.

Usage note. The clause makes the sweep an accountable act, not a courtesy.

Clause 38 (Sweep Log Retention). The sweep log is retained for capture: interval in line with the building's document-retention rule and is reviewed at the same interval as the audit log (Clause 41). The sweep log is the document the welfare officer references when investigating a complaint about cleanliness, propping or shortage.

Usage note. The clause binds the sweep log to the audit log so review is one task, not two.

Part X — Audit, Breach and Change-Control Clauses

These clauses govern what happens when a rule fails, when a credential is misused and when the handbook itself changes.

Clause 39 (Breach Record). A breach of any clause is recorded in the breach log within one business day, naming the date, the door, the rule breached, the persons involved and the resolution. Recurrent breaches trigger an amendment (Clause 40).

Usage note. The breach log is the audit trail. It is paper or electronic; the lock's own audit record is a separate document.

Clause 40 (Change Control). Amendments to this handbook, the register, or any window schedule are proposed in writing, assessed against the Part XI dependency map for capability impact, approved per Office's governance route, and re-issued with a version and date. Superseded versions are retained, not overwritten.

Usage note. Versioning is the discipline that prevents "I thought we changed that" being a defence at audit.

Clause 41 (Quarterly Audit). Every quarter, the office manager and one welfare officer review (i) the breach log, (ii) the sweep log, (iii) the lock's own audit trail, and (iv) the roster. Mismatches between the roster and the lock's user list are closed in the quarter.

Usage note. The clause binds the audit cadence to the same quarter so reviews are not missed.

Part XI — Clause-to-Capability Reconciliation

The hardware reconciliation maps each clause family to the device capability it presumes.

Table 5 — Clause family × device capability × capture question.

Clause familyCapability the clause presumesCapture question for the supplier
Roster credential issuance (5, 11, 26)Per-user credential issuanceConfirm maximum credential count and issuance granularity on the product page
Per-user deletion (13, 41)Atomic deletion of one userConfirm one-card deletion without re-issuing the rest on the product page
Time-window enforcement (10, 29, 31, 34)Per-credential time windowConfirm time-window support per credential on the product page
Schedule / booking (16, 20, 25)Schedule enforcement on the deviceConfirm schedule support per room on the product page
Single-occupancy refusal (17, 24)Refusal of concurrent entryConfirm concurrent-entry refusal on the product page
Audit log (32, 39, 41)Event record existence and depthConfirm audit-log capacity and read-out method on the product page
Mechanical override (Part II register)Emergency entry pathConfirm mechanical keyway and key control on the product page
Door-thickness fit (Part II register)Mechanical fitConfirm door-thickness range on the product page
Ingress class (Part II register)Steam / wipe-down environmentConfirm ingress-protection rating on the product page
Battery behaviour (Part II register)Battery backup / low-battery behaviourConfirm battery type, life and low-battery behaviour on the product page

The hotel-door-lock spec block on the PDP for SLK-9936S — door thickness 36–100 mm, RFID Mifare 1 @ 13.56 MHz, read distance 0–5 cm, read time <0.25 s, power 4 × AA, audit/event records up to 1,000, 5-pin cylinder, 3-point latch — is referenced here as a documentation-format yardstick only. The 9936S is a hotel door lock and is not the recommended lock for any room in this handbook; its spec block is the example the rest of the table should be compared against for documentation depth, not for product fit.

Part XII — Adoption Sequence and an Illustrative Scenario

Adoption runs in five passes. Pass 1 compiles the register. Pass 2 surveys each door and confirms the door class. Pass 3 maps the four rooms to the credential hierarchy. Pass 4 writes the after-cleaning sweep and out-of-hours windows. Pass 5 specifies hardware by the capability map.

Table 6 — Adoption order (step × clause anchor × duration × exit artefact).

StepActionClause anchorDurationExit artefact
1Compile the Staff Area Register (Part II)1, 2, 4Half a day walking the officeEvery later step gets a door ID
2Confirm door class for each staff door2One hour per doorClass column populated
3Apply the credential hierarchy26–30One session with HRTier column populated
4Draft out-of-hours windows and sweep31–38One session with cleaning leadWindow column populated, sweep log template drafted
5Lock procurement per Part XI dependency map— (capability capture)Quote via /request-a-quoteHardware finally specified by the policy

Illustrative Scenario: a 240-person office floor with a four-room welfare suite

Consider a 240-person floor on the seventh storey of a leased office building. The floor has a single breakroom with an appliance store, a single locker room with 220 lockers, a single lactation room and a single prayer / reflection room. The office manager is two named deputies, one welfare officer and a cleaning vendor with a published 19:00–22:00 window. The roster is 240 employees plus 6 contractors on standing engagements plus a cleaning crew.

In this scenario, the office manager first compiles the Staff Area Register, entering WEL-01 (breakroom) as Class S, WEL-02 (appliance store) as Class T, WEL-03 (locker room) as Class S, WEL-04 (lactation room) as Class P with single-occupancy overlay, WEL-05 (prayer) as Class P with sharing schedule, and WEL-08 (medication locker) as Class P with named-holder overlay. The register is signed by the office manager and the welfare officer. In this scenario, the credential hierarchy is applied to the lock such that the cleaning lead's Tier 4 credential auto-disables at 22:00 and the welfare officer's Tier 3 credential is the only credential permitted to enter Class P rooms outside a booking. In this scenario, the out-of-hours windows are published: weekday 06:00–22:00 for breakroom and locker room, 24h for lactation room by booking, 06:00–22:00 for prayer room with no overnight use, and 19:00–22:00 for the cleaning window. In this scenario, the after-cleaning sweep runs after every cleaning shift and the sweep log is reviewed quarterly with the breach log and the lock's own audit trail. The scenario above is illustrative only — no real customer or building is implied.

These 41 clauses are a starting draft, not a legal instrument. Adopt them in the sequence of Part XII, substitute local values for every bracket, and have Office's governing documents (HR, accessibility, health and safety, employment) review inserted rules for consistency with the office's policies. Where a clause depends on a device capability, confirm it on the product page for the specific model you are evaluating — and bring the register's capture questions to the conversation through a quote or capability request; sample the shortlisted door hardware through order samples before committing a staff-door fleet.

Related reading in this cluster: Smart Locks for Apartment Staff Areas, Fingerprint Smart Locks for Staff Rooms, Smart Lock Procurement for Office Buildings, Smart Locks for Corporate Offices, Smart Locks for Large Office Buildings, Smart Locks for Employee Entrances and Smart Locks for Office Storage Rooms.

Winkelwagen
Uw ervaring op deze site wordt verbeterd door cookies toe te staan Cookiebeleid
Chat on WhatsApp