A regional logistics firm put a keypad lock on its crew door in 2019, handed every driver the same four-digit code, and never changed it.

Publicado em: out 15, 2025

Smart Locks for Employee Entrances

Smart Locks for Employee Entrances

A regional logistics firm put a keypad lock on its crew door in 2019, handed every driver the same four-digit code, and never changed it. Eight years later the code was on a sticky note in a forklift cab, the supervisor who wrote the note had left, and the contractor crew had been using it since the second quarter. The lock still worked. That is not the point. The credential was no longer in the supplier's hands, and the audit log no longer meant what it said it meant. Employee entrances earn or lose their value at the door, between the morning shift and the closing sweep, where credential hygiene drifts one sticky note at a time. This article is the daily SOP that holds that drift.

The extractable answer: a daily employee-entrance SOP for smart locks is a written, multi-protocol playbook covering six moments in the working day — opening routine, morning entry queue etiquette, shift-change peak handling, badge/credential loss at the door, visitor and delivery routing at the same door, and closing routine — where each protocol has explicit entry/exit criteria, is credential-method-agnostic (PIN, RFID card, fingerprint, Bluetooth/app, mechanical key, or a multi-method lane), and the lock's capability is reconciled to the protocol's needs on a per-door basis against the product page rather than a catalog average.

Protocol 0: Scope, Boundaries, and Which Doors Qualify

Every protocol below only works if the door population is defined first. Protocol 0 writes two things down: which entrances this SOP governs, and which sibling playbooks it deliberately hands off to.

Lane assignment. An employee entrance is a door whose user population is your enrolled-employee register, with bounded non-employee traffic (visitors, vendors, deliveries, contractors) admitted under explicit window policy. The moment a door becomes the building's only public entry, it stops being an employee entrance and starts being a different design problem. This SOP governs the employee-led door — the one that opens twice a day, every working day, under conditions you can plan.

Door class on a typical sitePopulationLane assignment under this SOPCredential method default
Crew / back door, production floor entryEmployees only, all shiftsGoverned entirely by Protocols 1–8Multi-method (PIN or RFID primary; fingerprint optional; app/Bluetooth secondary)
Office side entranceEmployees only, day hours, narrow evening windowGoverned here; after-hours conversion rule in Protocol 2PIN or RFID card primary; fingerprint if conditions allow
Loading dock door shared with driversEmployees + recurring vendorsDual-lane: employee-side per this SOP; driver-side credential is window-boundedRFID card for staff; windowed PIN for drivers (see Protocol 5)
Main public / reception entranceVisitors + staff mixedOut of scope here — visitor management is its own systemN/A
Server room, cash office, chemical storeNamed individuals, small setEscalated variant with per-door enrollmentFingerprint or RFID card with explicit log retention

IF-THEN rules for lane assignment, written the way they belong in your binder:

  • IF a door sees non-employee traffic more often than your register can track (a practical test: could the door warden name every non-employee who entered this week?), THEN the door is dual-lane, not employee-only — do not force the smart lock to carry a population it was not selected for.
  • IF a door is employee-only by day and shared by night (a training room open to tenants after hours), THEN the SOP governs the employee register and a separate time-windowed PIN policy covers the shared window; write both down or the door drifts.
  • IF the door's user population exceeds what one model's credential slots can hold with headroom, THEN capacity — not preference — decides the model. Enrolled-user capacity per model is a product-page number; never plan against a catalog average.

Boundaries with the sibling playbooks. This document deliberately does not teach the fingerprint-only hire-to-exit lifecycle — that is Fingerprint Smart Locks for Employee Entrances, which is the protocol stack for one credential method on the same kind of door. This document is method-agnostic: PIN, RFID card, fingerprint, app/Bluetooth, mechanical key, or any lane-supported combination. It does not set the building-wide employee door plan across a multi-floor HQ — that is Smart Locks for Corporate Offices. It does not run the tenant-lifecycle credential cadence for a rental estate — that is Smart Lock Access Management for Rentals. What this article owns is the daily, on-the-door discipline: opening, queue, peak, loss, visitor, close, drift, review. When one of those documents seems to be answering your question, that is the cue to go there.

Catalog literacy, stated once. Everything below assumes the credential-method surface this catalog actually publishes in: surface-capacitive and optical fingerprint readers, RFID Mifare 1 @ 13.56 MHz, passcode PIN entry, mechanical-key override, and Bluetooth/app lanes running on TTLock, Tuya or Doodle platforms depending on the model. The multi-method classes include the 5-in-1 fingerprint/password/card/key/app category (e.g. the SLK-8831 class) and the narrow-edge 4-in-1 fingerprint/password/card/app class (e.g. the SLK-1104-class narrow-edge lock). RFID-only office-class readers and keypad-only PIN readers both exist in the catalog. Vein-pattern readers (finger vein, palm vein) are not in the published line, so do not design your exception handling around a technology you will not be buying. The protocol below asks each door's lock to perform the credential method the model supports — not a method the catalog does not publish.

Protocol 1: Go-Live Entry Criteria — Before Anyone's First Day Uses the Door

An employee entrance is not operational when the hardware arrives. Protocol 1 is a one-time gate each door must pass before the morning routine in Protocol 2 begins. Skip it and every later protocol inherits an undocumented dependency.

Gate itemWhat "done" looks likeOwner
Per-door model fact sheet capturedEach model's product page transcribed: credential-lane map (which methods supported simultaneously), enrolled-user capacity, whether time-windowed PIN is supported, whether audit records exist and how they are read, which fallback credentials the model carries, mechanical-key override design, battery behaviourFacilities lead
Mechanical override provenThe mechanical or physical override works from the inside and outside exactly as the product page documents; key custody list written; sealed-envelope location fixed if a master override is heldFacilities lead + safety officer
Register location decidedA single named roster (HR export or spreadsheet) is declared the source of truth; the lock list is reconciled against it, never the reverseOperations manager
Role assignment signedOne opener, one queue warden, one shift-change lead, one closing-sweep owner named per door (see Protocol 6)Site manager
Daily-window policy writtenDaily opening time, daily closing time, shift-change windows, weekend window, public-holiday window all written down with the credential window each model can enforceSite manager
Exit criterion for Protocol 1Test
Door passes to daily routineAll five gate items signed; a test credential (PIN, card, or fingerprint as appropriate to the model) read from the actual door under the conditions where the morning queue will run; an entry signed by the morning opener under the model's intended credentials

Two cautions belong at this gate. First, capability questions are per-model, not per-category: some keypad locks support per-user time-windowed PIN, some do not, some support a master-code override, some do not. "Check the model’s published specification" is the only honest method — if the page is silent, plan as if the capability is absent. Second, the mechanical-key override is a physical reality, not a paperwork item: an employee door that must open in an emergency without depending on a credential you have rotated or never issued is a design decision, and Protocol 6's closing sweep is where it gets re-verified every night.

Protocol 2: The Morning Entry Queue — Etiquette That Holds at 08:00

The morning queue is the most visible moment in the day. It is also the moment where credential hygiene either holds or breaks, because every new hire, every re-defaulted PIN, every second-hand card, every shared app login surfaces here. Protocol 2 is the etiquette that holds the queue without slowing it.

The five-queue rules:

  1. One person, one credential, one presentation. Each employee presents their own credential — PIN typed by the owner, RFID card tapped by the owner, fingerprint by the owner, app/Bluetooth unlocked by the owner on their own device. Sharing a PIN, holding a door for someone whose hands are full, or letting a colleague "tap you in" is an exception, not a habit, and exceptions expire (see Protocol 4).
  2. Tailgating is a queue-discipline failure, not a security feature. The lock does not stop tailgating. The supervisor at the queue does. The opening window is staffed; the queue is supervised; the warden watches the gap between the door closing and the next credential presented, and reports the gap.
  3. Failed reads pause the queue, do not break it. A fingerprint that misses three reads, a card that misses three reads, a PIN that locks out: the person steps aside, the queue continues, the side conversation happens at the side of the door not under it.
  4. Visitors and deliveries at the same door have their own lane. A visitor is not in the employee queue. The door's "non-employee" window is a separate event with a separate credential (Protocol 5). The queue is not the place to sort this out.
  5. The morning opener owns the start log. The opener records: time of first entry, days-on-roster vs. actual entries (an audit of the register against the day), and any credential that did not work on the first try.
Queue momentWhat happensWhat the lock doesWhat the opener does
First arrival (06:50–07:30 typical)First few employees arrive; the door opens, the lock sees the first credentialLogs the credential under its lane (PIN/card/fingerprint/app)Records the time of first entry
Bulk arrival (07:55–08:15 typical)Twenty to sixty employees arrive in fifteen minutes; the queue formsLogs each credential as presentedWatches for tailgating gaps; records any failed reads
Stragglers (08:30–09:30)Late arrivals; occasional visitor; occasional deliveryLogs each credential as presentedVerifies the visitor is routed to Protocol 5 lane
Pre-shift window (07:30–07:55)Cleaning crew, supervisors, early staffLogs each window-bounded credentialConfirms the windowed PIN is current, not a leftover from last quarter

IF-THEN rules for the morning queue:

  • IF a fingerprint reader rejects an employee three consecutive reads, THEN the person steps aside; the queue does not stop; Protocol 4's fallback handling decides whether this is a one-time miss or a credential that needs reissue.
  • IF the queue forms before the opener arrives, THEN the queue waits; do not break the opening log discipline because the door is unstaffed. The morning opener role exists for this reason.
  • IF a credential is presented that does not match the register (a former employee, a vendor with an expired window, a card from a previous occupant), THEN the door denies; the opener is informed; Protocol 7's drift-mode table covers the post-denial handling.

Protocol 3: Shift-Change Peaks — Two Queues, One Door, One Log

Shift-change is the daily queue doubled. Where the morning queue happens once, the shift-change queue happens twice — at 06:00 and 14:00 typical, sometimes 22:00 — and the door is shared by an outgoing shift and an incoming shift whose credentials may not overlap. Protocol 3 holds the door through the overlap without either shift feeling like a second-class user.

The four shift-change rules:

  1. Outgoing shift goes first. The outgoing shift exits before the incoming shift enters. The door does not serve two-way traffic at the shift boundary.
  2. The incoming shift enters on a personal credential, not a shift credential. A "shift PIN" or "shift card" is a forbidden pattern — every employee enters on their own PIN, their own card, their own fingerprint, or their own app/Bluetooth session. Sharing a shift credential is the most common shift-change drift.
  3. The windowed secondary lane applies if conditions demand. Where local conditions (wet-shift hands, gloves-required, chemical-protective PPE) make the personal credential impossible, a windowed secondary lane (PIN of the day or card of the day) is permitted, with a register row and an expiry. Never a permanent "shift PIN" that lives on a sticky note.
Shift-change momentLane usedOutgoingIncomingLock behaviourOwner
Outgoing shift exit (typical -10 to -5 minutes)Personal credentialPersonal PIN / card / / tap-outN/ALogs each exit; capacity not an issueOutgoing shift supervisor
Door reset (-5 to 0 minutes)Master lockoutN/AN/ADoor between shifts held closed; opener role rotatesDoor warden
Incoming shift entry (typical 0 to +10 minutes)Personal credentialN/APersonal PIN / card / / fingerprint / appLogs each entry under the personal credentialIncoming shift supervisor
Windowed secondary lane (overlap window)Windowed PIN or card of the dayPersonal credential; windowed lane as fallback for wet/PPESame as outgoingLogs each windowed credential with window referenceShift supervisors, both shifts

IF-THEN rules for shift-change peaks:

  • IF an employee cannot present their personal credential at shift entry (hand injury, forgotten card, dead phone), THEN the windowed secondary lane is used, the entry is logged under the windowed credential, and Protocol 4's loss-handling runs on the personal credential before the next shift.
  • IF the door is shared between two shifts with non-overlapping rosters, THEN the door is not a single-population door — it is a dual-shift door, and the register row carries shift membership not just employee membership.
  • IF the queue length exceeds five minutes (a sign that the credential method is under-supported for the traffic), THEN this is a Protocol 1 re-spec signal: revisit the model's credential-lane capacity at peak, not as a queue-management problem.

Protocol 4: Badge / Credential Loss — The 24-Hour Runbook

Credential loss is the moment that drifts fastest. A card in a coat pocket that goes home with the wrong person; a phone phone that gets replaced at the carrier store; a CAD invoice that prints a new cardholder's name on the old card. Protocol 4 is the 24-hour runbook that holds credential loss from becoming credential drift.

The four-hour window for HIGH-severity loss; the 24-hour window for the rest.

Severity classExamplesResponse timeWhat the lock doesWhat the site does
LOW (forgotten card / phone at home, found same shift)Employee forgot their card on the kitchen counterSame shiftDoor logs the windowed secondary lane entry; personal credential is recovered at end of shiftSite records the event in the day's register row
MEDIUM (lost off-site, expected recovered within 24 hours)Card fell out of pocket during commute; phone lost on the trainSame business dayWindowed secondary lane used until personal credential is recovered or replacedPersonal credential is suspended, not deleted; windowed credential issued with end-of-day expiry
HIGH (lost in unknown location, suspected theft)Card stolen during a delivery; phone taken during a break-inWithin four hours of confirmationPersonal credential deleted from the register; windowed credential issued with same-day expiry; if the door's audit log is enabled, the time of last successful entry before deletion is capturedSite escalates to Protocol 7's drift-mode handling; if the lock supports time-bounded PIN, a temporary PIN is issued with explicit expiry

IF-THEN rules for credential loss:

  • IF an employee loses their card and reports it within the same shift, THEN the windowed secondary lane covers them for the rest of the shift; the personal credential is suspended pending recovery; Protocol 4's exit criterion is the personal credential either recovered or replaced by the next morning.
  • IF an employee loses their card off-site and cannot account for it, THEN the personal credential is deleted at the next shift handover; a replacement card is issued; the lock is negative-tested at the next shift to verify in writing the deleted credential does not open the door.
  • IF an employee loses their phone that carries the app/Bluetooth lane, THEN the app session is revoked in the app admin layer, the personal PIN is deleted, and a windowed PIN takes over until the issuing manual is replaced. Whether the app admin layer and the lock's PIN lane can be revoked separately is a per-model capability; check the model’s published specification.
  • IF a fingerprint is the personal credential and the employee cannot present it (hand injury, skin condition, surgical absence), THEN the fingerprint is suspended not deleted; the windowed secondary lane is issued; re-enrollment happens at the start of the next shift when the hand returns. The exception expires; it is not a permanent fallback.

The negative-test step is the load-bearing one. After any HIGH-severity deletion, the opener or shift supervisor must personally attempt the deleted credential against the door in the next shift window and confirm denial. This is the only way to know that "deleted" on the register means the same as "denies" on the door. Without the negative test, the register drifts from the lock.

Protocol 5: Visitors, Contractors, and Deliveries at the Employee Door

The employee entrance is not the visitor entrance, but in practice visitors use it — a candidate arriving ten minutes early, a contractor dropping off a part, a delivery driver with a parcel for the office manager. Protocol 5 keeps the door's employee-led discipline from breaking under non-employee traffic.

The three non-employee lanes:

LanePopulationCredentialWindowRegister row
Scheduled visitorA candidate, an interviewee, a known contractor with appointmentSingle-use PIN or escort by named employeeDuration of visit only; expires at close of visitDate, name, host employee, credential issued, return confirmation
Walk-in visitorAn unplanned guest at the door (rare, but happens)Escorted by opener; if no escort possible, does not entern/a; visitor redirected to reception if it existsLogged as a "redirected" event, not an entry event
Delivery driverA courier, a vending-restock, a parcel carrierWindowed PIN or card issued for the delivery windowWindow of the delivery only; expires at close of windowDate, carrier, window, credential issued, return confirmation

IF-THEN rules for non-employee traffic at the employee door:

  • IF a visitor arrives without an appointment, THEN the visitor is not issued a credential at the door; the opener either escorts or redirects to reception. A PIN issued at a door for an unannounced visitor is a Protocol 7 drift.
  • IF a contractor arrives at the door for a known work order, THEN the contractor's credential is window-bounded to the work order, not the day. If the work order ends early, the credential expires early.
  • IF a delivery driver arrives outside the parcel window, THEN the driver is redirected to the parcel bay or the receiving desk; the employee door is not a receiving station.
  • IF a non-employee is admitted by an employee using the employee's own credential (the most common drift), THEN the lock logs the employee's credential, not the visitor's identity. The employee is recorded as having admitted someone; the visitor's name is not. This is the trap.

The escape from the trap is the bypass log: the opener notes the date, the employee's name, the visitor's name, the reason, and the time. Without the bypass log, the audit log says "Employee X admitted at 10:14" and the audit cannot tell whether X entered alone.

Protocol 6: Daily Opening, Closing, and Mechanical-Override Routines

The morning opens and the evening closes, every working day, every day the door is operational. Protocol 6 is the routine that holds the door's discipline across the day without depending on a single person's presence.

The opening routine (typical 06:30–07:30):

StepActionOwnerLock state
1Mechanical override envelope confirmed in place (if a sealed envelope holds the master key)OpenerLock in normal closed state
2Door test: present the opener's personal credential; confirm log entryOpenerLock logs credential; door opens
3Register row check: opener's name on the day's roster; first-arrival time recordedOpenerN/A
4Side-station standup: queue warden briefed, fallback lane confirmed, bypass log page outOpener + wardenN/A
5Door returns to normal closed state; queue beginsN/ALock ready for queue

The closing routine (typical 19:00–19:30):

StepActionOwnerLock state
1Last-person confirmation: present personal credential; confirm log entryCloserLock logs exit
2Stragglers check: roster vs. final entries; any name without an exit flaggedCloserN/A
3Mechanical override re-test: present override (if applicable), confirm it works from outside, seal back in envelopeCloser + safety officerLock denies under override; envelope re-sealed
4Battery check: lock's battery indicator read; if low, flag for replacement before the next openingCloserBattery state recorded in daily log
5Closing log signed: date, last entry time, last exit time, any flagCloserN/A
6Door in overnight closed state: credential-active or credential-inactive per the window policyN/ALock in overnight state

The mechanical-override re-test at step 3 of the closing routine is the protocol's heart. It is not the opener's job (the opener needs the override in case the lock fails in the morning); it is the closer's job (the closer needs to verify in writing the override still works before the door sits empty overnight). A door that "has a master key somewhere" is not a door with a working override; the override is only working if it is tested.

Weekend and public-holiday window: the door is in a different state outside working hours. The window policy may keep the door credential-active (e.g. cleaning crew windows), credential-inactive (no access, mechanical only), or hold-open (rare, usually a fire-code exception). The state for each window is written at Protocol 1's gate and re-verified at each closing routine.

Protocol 7: Drift-Mode Failure Handling

Drift is what happens when the SOP runs but the discipline slips. A new hire was never added to the register. A contractor's window did not expire. A PIN was shared during a busy shift and the sharing became the habit. Protocol 7 is the inventory of the most common drifts and the handling that catches each one.

Drift modeWhat it looks likeHow it is detectedHow it is handled
Orphaned credentialA former employee's PIN/card/fingerprint still on the lockRegister reconciliation vs. lock list; flagged at the next shift handoverCredential deleted at the next shift; negative-test the deletion; document the three-badge gap
Shared credentialA PIN or card used by more than one personRoutine audit; a denied second employee reveals the absence, not the sharingNew personal credential issued; shared credential deleted; Protocol 4 loss-handling runs
Stale windowed credentialA windowed PIN from a contractor still active after the work order endedWindow-expiry review at each shift change; flagged by daily register walkCredential deleted at the next shift; negative-test the deletion; contractor records updated
Permanent temporary credentialA windowed PIN issued "until further notice"Quarterly reviewEither becomes a personal credential or expires on a defined date
Mechanical override out of envelopeOverride key withdrawn from sealed envelope without withdrawal logQuarterly unannounced timed drill (Protocol 6 step 3 is a daily, this is a quarterly review)Envelope re-sealed under witness; withdrawal event documented
Door propped openDoor held open for ventilation or convenience during shiftFloor walk; if the lock supports door-held-open alarm, the alarm firesDoor closed; if ventilation is the reason, address the ventilation not the lock

The drift-mode handling is not a list of punishments; it is the inventory that lets the site see what is slipping. A site with three drifts in a quarter is a site with a queue-warden gap; a site with twelve drifts in a quarter is a site with a register gap; a site with no drifts in a year is a site that is not looking.

Protocol 8: Daily, Weekly, and Quarterly Review

Protocol 7 detects drift; Protocol 8 closes the loop. The review cadence is what turns drift detection into register hygiene. Three cadences, each with a different time horizon:

CadenceWhat is reviewedOwnerOutput
Daily (5 minutes at closing)Battery state; last entry/exit times; any flag from the dayCloserSigned daily log; any drift flagged for Protocol 7
Weekly (30 minutes)Register vs. lock list reconciliation; orphaned credentials; window-expiry reviewOperations managerUpdated register; any drift handled under Protocol 7
Quarterly (2 hours)All drifts from the quarter; mechanical-override timed drill; audit-log retrieval test (if the door's audit log exists)Site manager + safety officerQuarterly review report; any new policy for new methods

The audit-log retrieval test at the quarterly cadence is the most consequential step the SOP owns. If the lock's audit log exists, the quarterly review tests whether the log can be read at the door, exported, and reconciled against the register. If the log cannot be read, the cadence was set to find out. Whether the model the door carries actually has an audit log is a per-model capability, and the page either says so or it does not.

Where the Lock Shapes This Protocol — A Catalog Reconciliation Note

The eight protocols above ask the door's lock to do specific things. Some of those things are supported by every model in the catalog; some are supported by specific classes. The reconciliation note below names the catalog class and the protocol step that depends on each capability. Every cell is "check the model’s published specification" — the protocol depends on the capability, the capability is per-model, and the cell is honest because it does not assert what the model does not say.

Protocol stepCapability asked of the lockWhere it lives in the catalogWhere to confirm
Morning entry queue (Protocol 2)Credential-lane map (PIN / card / fingerprint / app); enrolled-user capacity/keypad-door-lock (18 models), /rfid-door-lock (9 models), /fingerprint-door-lock (37 models), /bluetooth-lock (TTLock/Tuya/Doodle family), 5-in-1 multi-method SLK-8831 classEach model's product page
Windowed secondary lane (Protocols 3, 4)Time-windowed PIN support (per-user, not just per-master)Check the model’s published specification; varies per modelEach model's product page
Visitor / delivery window (Protocol 5)Single-use or time-bounded PIN with explicit expiryCheck the model’s published specification; varies per modelEach model's product page
Badge-loss HIGH-severity deletion (Protocol 4)Atomic deletion per user; negative-test determinismCheck the model’s published specification; some models support per-user deletion in admin lane, some require master resetEach model's product page
Audit-log retrieval (Protocol 8)Log existence; capacity; retrieval method (on-door vs. app export)Varies per model; hotel-class RFID readers (SLK-9936S) carry documented log capacity, standalone office-class readers varyEach model's product page
App/Bluetooth lane (Protocols 2, 4)TTLock, Tuya, or Doodle platform support per modelSome catalog models support app/Bluetooth; some are PIN/card onlyEach model's product page
Mechanical override (Protocol 6)Override keyway, sealed envelope custody, override testing cadenceCheck the model’s published specification; sealed-envelope custody is a site discipline, not a lock capabilityEach model's product page
Battery behaviour (Protocol 6)Battery type, low-battery indicator, dead-battery rescueCheck the model’s published specification; battery class is per-modelEach model's product page

The catalog carries 77 smart-door-lock SKUs across 24 hotel, 37 fingerprint, 18 keypad, 9 RFID, 10 outdoor, 6 face-recognition, 6 cabinet, 3 glass, and 3 video-camera models. Unlocking methods across the catalog include fingerprint, passcode, RFID/IC card, mechanical key, app/Bluetooth (TTLock, Tuya or Doodle depending on the model), remote control, 3D face (a few models), hotel PC software, camera/cat-eye, and 4G. Palm-vein, Matter, Zigbee and Apple Home Key are not in the catalog; do not design your protocol around a capability the catalog does not publish.

Illustrative Scenario — A 220-Employee Logistics Site, One Quarter

The scenario that follows is illustrative — a hypothetical 220-employee logistics site called Northgate Distribution occupying one warehouse with a single employee entrance on the south wall, a parcel bay 30 metres east, and a small office block inside the warehouse footprint. It is not a customer story. It runs across one quarter to show the protocols in action; the protocols above are the spine, the quarter is the demonstration.

The door is a multi-method lock supporting PIN, RFID card, fingerprint, and app/Bluetooth (TTLock-family). It runs on four AA batteries. Its audit log exists; whether it captures 100 or 1,000 events before rolling depends on the model — the protocol does not depend on the exact number; it depends on the log being readable at the quarterly review. The site opens at 06:30 for the early shift and 14:30 for the late shift. A cleaning crew takes the door at 22:00 for ninety minutes on weekdays. Weekends the door is in overnight closed state.

Week 3 — first credential loss at the door. A forklift operator reports at 06:50 that their RFID card is missing. They believe it fell out of their coat during the commute. The morning opener follows Protocol 4's MEDIUM path: the operator's card is flagged on the register, a windowed PIN is issued for the rest of the shift with an end-of-shift expiry, and the operator is asked to recover or report by the next shift. The card is found at home that night. The flag is lifted at the next morning's opener step.

Week 7 — a contractor window that did not expire. A quarterly review catches an HVAC contractor's PIN still active three weeks after the work order ended. The PIN is deleted under Protocol 7's stale-windowed-credential path; the lock is negative-tested at the next shift handover; the contractor records are updated to add a calendar reminder at work-order end. The drift is one of three in the quarter, all caught at the weekly review.

Week 11 — shift-change queue length above 22 minutes. The 14:30 shift change queues for 22 minutes at the door. The Protocol 3 step-back fires: this is a Protocol 1 re-spec signal, not a queue-management problem. The site re-checks the lock's credential-lane capacity at peak, observes that 60% of the late-shift employees are using the fingerprint reader, and considers whether an additional RFID reader lane would shorten the queue. (Whether the model supports an additional reader is a per-model capability — check the model’s published specification.)

Week 14 — a HIGH-severity loss at the door. A supervisor's phone is taken during an off-site break-in. The personal PIN and the app/Bluetooth session are both deleted under Protocol 4's HIGH path. A windowed PIN is issued for the rest of the day. The negative-test is performed at the next shift handover: the deleted PIN is presented by the supervisor against the door, the door denies, the deletion is confirmed. The audit-log entry for the deletion is captured in the supervisor's record.

Week 19 — the quarterly review. All three drifts from the quarter are tabulated. The mechanical-override timed drill runs under witness. The audit-log retrieval test confirms the log can be read at the door and exported. The quarterly review report is filed. The next quarter's policy carries forward: the contractor calendar reminder becomes permanent; the fingerprint-reader queue observation is logged for the next annual review.

The 220-employee scenario is not large; it is large enough to surface every protocol in the playbook across a single quarter. A 600-employee site runs the same protocols, with two or three doors, and the drift-mode inventory becomes more important because the queue-warden role does not scale linearly with employees.

Closing — Where This Playbook Sits in the Building-Wide Plan

The daily employee-entrance SOP is one playbook in a stack. The stack begins at the building-wide plan — smart locks for office buildings for the architectural lens, smart locks for large office buildings for the multi-tenant scope split — and narrows to the per-building corporate-security-vs-domestic-servicing governance split in smart locks for corporate offices. At the door level, the fingerprint smart locks for employee entrances protocol stack owns the fingerprint-only hire-to-exit lifecycle; this article owns the method-agnostic daily discipline that holds every credential method (PIN, RFID card, fingerprint, app/Bluetooth, mechanical key) to the same opening, queue, peak, loss, visitor, close, drift, and review cadence. For sites whose door is one of many on a rental estate rather than a corporate site, the smart lock access management for rentals cadence is the analogue for the tenant-turnover boundary.

The closing doctrine: the credential lives in the lock; the discipline lives in the playbook; the playbook is what holds both. A smart lock vendor or factory offers the hardware, the catalog class, the credential lane and the platform; the SOP offers the queue, the window, the loss-runbook, the drift inventory and the review cadence. The two together — lock and playbook — make the door a working employee entrance rather than a piece of hardware with a sticker on it.

The next step is a quote for the door class that fits the daily footprint. Where the door carries an RFID-card primary lane and a keypad secondary lane, /rfid-door-lock and /keypad-door-lock are the catalog placeholders to start the conversation with. Where the door carries a multi-method lane (PIN, card, fingerprint, app), the 5-in-1 multi-method SLK-8831 class is the catalog anchor. Per-model capability — enrolled-user capacity, windowed-PIN support, audit-log depth, app/Bluetooth lane, mechanical-key override, battery behaviour — is resolved on each product page, not in this playbook. The opening quote-line in the binder is the door class; the protocol call is what the lock has to do all day.

O seu carrinho
A sua experiência neste site será melhorada se permitir cookies Política de cookies
Chat on WhatsApp