Smart Lock Access Management for Rentals
Smart lock access management for rentals is the standing-operating-procedure layer that keeps credentials correct across frequent tenancy change: every move-in gets a documented credential ceremony, every move-out gets a documented takedown ceremony with on-door verification, every occupied unit has a periodic credential reissue rule, every model in the fleet gets logged as either log-capable or sample-only after three per-model capability questions, and every lost-credential event runs a written runbook that closes the gap inside 24 hours. The hardware decision is upstream of this document. The cadence described below is what keeps the credentials honest once the locks are on the doors and the tenants are cycling.
This SOP is written for the single landlord, the small landlord-operator with fewer than 30 units, and the in-house facilities lead at a build-to-rent operator who owns the locks and runs the tenancy transitions personally rather than through a third-party management company. It is deliberately distinct from the operator-flank playbook for mixed-method standalone smart-lock fleets on a single owned apartment block (Smart Locks for Apartment Operators) — that document governs the steady-state operations cadence for one operated building; this document governs the tenant-rotation cadence that is the dominant failure mode for rentals. It is also deliberately distinct from the fingerprint-only run-time cadence (Fingerprint Smart Lock Access Management) — that document is sensor-specific and applies to a single biometric credential; this document is credential-type-agnostic across the PIN / RFID / app / mechanical / mixed-method lane set that a rental fleet commonly runs. If you are selecting locks instead of running them, start at the property-manager systems overview (Smart Lock Systems for Property Managers).
If you are running a multi-block build-to-rent programme rather than a small rental portfolio, the staged rollout applies — see Smart Locks for Rental Apartment Operators. If you are running nightly-stay or short-stay lets, the per-stay credential rhythm is the dominant frame — see Smart Locks for Short-Term Rentals. What follows assumes long- and mid-stay rentals on owned assets, with tenancy change weeks to years apart, where the cadence is the operating product.
One honest note on platform scope. Our catalog spans 79 published models, with 24 hotel-class, 18 keypad, 9 RFID, 10 outdoor, 6 face-recognition and 6 cabinet units among the 77 smart door locks; across the catalog the credential methods that exist today are fingerprint, passcode, RFID/IC card, mechanical key, app/Bluetooth (the TTLock / Tuya / Doodle family), remote control, 3D face on a small number of models, hotel-PC software on hotel-class locks, camera/cat-eye on a small number of intercom-capable models, and 4G on a single cellular line. Palm-vein, Matter, Zigbee, and Apple Home Key are not in this catalog; do not plan an operations cadence against capabilities that are not present in your product page. That sentence is the firewall for every protocol below: where a protocol depends on a model-specific capability, this playbook tells you to verify in writing the page rather than assume.
Protocol 0: Scope, Vocabulary, and Boundaries of This Playbook
Before the cadence starts, pin the vocabulary so each later protocol is executable by someone other than you.
| Term | Working definition for this playbook | Boundary |
|---|---|---|
| Rental unit | A residential unit owned by a single decision-maker, leased to a tenant on a defined tenancy term | Not a third-party-managed building; not a hotel; not a nightly stay |
| Tenancy window | The period between a move-in ceremony and a move-out takedown, written down in advance | A tenancy with no fixed end is still a window — its end is the next takedown ceremony |
| Credential pack | The set of credentials issued for the tenancy window: PIN, card, fingerprint, app account, mechanical key, in any combination the model on the unit door supports | One tenant can hold several credentials on one unit door |
| Reissue | Replacing one or more credential lanes for an in-place tenant without changing the tenancy — typically after a lost-credential event or a periodic cycle | Not the same as move-out takedown (which ends the tenancy) |
| Takedown ceremony | The documented sequence that revokes every credential lane a tenant holds, with on-door denial verification for each | Not a verbal "we'll change the lock"; a written, witnessed, countersigned procedure |
| Periodic reissue rule | A calendared decision to rotate one or more credential lanes for the occupied unit, on a schedule set by the landlord | Distinct from incident-driven reissue (lost credential) |
| Sample-only model | A lock that records no event log; the audit story lives in the receipt file rather than in the lock | Per-model determination — check the model’s published specification |
| Log-capable model | A lock that records access events to local memory or to an app/cloud lane; the cadence treats the log as a primary detection surface | Per-model determination — check the model’s published specification |
| Lost-credential runbook | The 24-hour sequence executed from the moment the landlord learns a credential is in unauthorized hands | Not a verbal "we'll change the locks"; a written procedure with IF-THEN decision points |
Three explicit non-goals for this document, named so you know where to go for them:
- Choosing the locks in the first place. What to buy, in which door class, is a procurement decision covered in the property-manager systems article linked above and in Smart Locks for Apartment Operators. This playbook assumes the fleet is committed and the credentials are running.
- Fingerprint-specific sensor mechanics. Capture technique, sensor degradation, ridge-read failures, wet/dry hand behavior, all of which belong to the standalone fingerprint cadence at Fingerprint Smart Lock Access Management. Where this playbook needs to issue or revoke a fingerprint lane, it does so by referring the reader to the fingerprint cadence for craft and to this playbook for timing.
- Hotel-style centralized software. Some locks on the market ship with hotel PC software and central database modes — those are built for nightly-stay operations, not landlord-run rentals. Where this playbook touches a centralized capability, it is in the context of "depends on model, check the model’s published specification."
Why Rental Tenancy Is the Hardest Case for Access
A standalone lock knows only the credential set currently stored inside it. Your tenant universe changes at every lease boundary — sometimes twice a year, sometimes twice a decade, but always changing. The lock changes only when a human physically interacts with it. That asymmetry is the source of every failure mode this playbook exists to prevent, and it is sharper in rentals than in owned apartments because the tenant-by-tenant transition is the operating event, not the weekly roster sync.
| Drift mode | What happens | Typical trigger | Consequence if unswept |
|---|---|---|---|
| Ghost credentials | A former tenant retains a working PIN, card, fingerprint, or app permission | Tenancy ended; takedown skipped or partial; prior tenant retained a copy of the PIN or card | Access exists where policy says it should not |
| Cross-tenancy code reuse | The same PIN or card is issued to the next tenant without being revoked in between | Landlord shortcut; tenancies back-to-back with no gap | Two separate tenants share the same credential without knowing it |
| Subletter leakage | Tenant shares the credential with a partner, friend, or subtenant not on the lease | Tenant hospitality; landlord not notified | The unit is occupied by people the lease does not name |
| Periodic drift | Tenant has held the same PIN for four years and forgotten which side of the family passed the code to whom | Long tenure + no reissue discipline | A credential that has been quietly multiplied |
| Windowed credential outliving its window | A cleaning or repair credential issued for a specific visit is reused for the next visit | Verbal "give the same card to whoever comes next" | The bounded credential becomes a standing one without policy |
| Mechanical key not returned | Tenant departs with the mechanical override still on their keyring | Move-out walk missed | The cylinder is compromised; the lock's electronic story becomes partial |
| Lockout surprise | Tenant is locked out at 2 a.m. and the landlord's standby procedure is undefined | Battery died; tenant exhausted PIN tries; firmware lock after too-many-fails | Reputation damage, locksmith fees, emergency overtime |
None of these failures is dramatic the day it happens. Each accumulates at roughly the pace of your tenancy rotation. A landlord running tenancies a year apart and a landlord running tenancies three years apart accumulate drift at different speeds but in the same shape. The counterweight is not software; it is a written cadence with named owners, time budgets, and signed documents. Landlords who run one spend, in our experience across deployments of this kind, a couple of hours per unit per year on the actual lifecycle events and an additional hour or two per year on the periodic review. Landlords who do not spend that time eventually spend a security incident instead, and the incident always costs more than the time would have.
One note on scale. Our catalog spans 79 published models across 77 smart door locks with 24 hotel-style, 18 keypad, 9 RFID, 10 outdoor, 6 face-recognition and 6 cabinet units; credential methods that exist today are fingerprint, passcode, RFID/IC card, mechanical key, app/Bluetooth (TTLock / Tuya / Doodle), remote control, 3D face on a few models, hotel PC software on hotel-class locks, camera/cat-eye on a small number of intercom models, and a single 4G line. Where this playbook depends on a model-specific capability — periodic reissue via remote app lane, log capacity for review, time-bounded PIN support, app-driven revocation, OTA remote unlock — the answer is always "check the model’s published specification."
Protocol 1: The Move-In Credential Ceremony
A tenant's first 72 hours on the property decide whether the lock program helps you or haunts you. The ceremony exists to make that period boring on purpose.
MI-1. Pre-arrival pack (the day before key handover). Pull the unit's door record from the operator file. Confirm the lock family on the unit door is the one you think it is — model, lane set, mechanical override present, battery fresh. Build the credential pack for that specific unit, not for the tenant in the abstract. A pack for a mixed-method unit typically contains a fresh RFID card or two (issued against your pool), a unique PIN (different per tenancy, never reused; absolute non-negotiable — see Protocol 2), an enrolled fingerprint if the unit door is biometric-capable and the tenant consents to biometric enrolment, an app-account invite for app-enabled models only, and one mechanical override key sealed against a key-control envelope. Which of these lanes are actually supported depends on the model on that door — check the model’s published specification before you promise a lane to a tenant.
MI-2. Identity verification at handover. Take a copy of the tenancy agreement and a government photo ID. The landlord (or the landlord's named representative) signs the credential receipt; a second adult — the tenant's co-signer if present, or a witness — countersigns. The tenant signs a one-page receipt that lists, line by line, every credential they receive, with serial where applicable (card number range, key envelope reference). The receipt is filed under the unit number and the tenancy start date; it is the document you will produce if the tenant later denies holding the card, claims they never received a code, or disputes who had the mechanical key at move-out. Issue against a written policy, not against your memory.
MI-3. Lane-by-lane test at the door. Before the tenant leaves the unit, watch them open the door with each credential in turn. PIN: enter it twice. Card: tap it twice, including on a low-battery cell if the lock reports one. Fingerprint: enrol two non-adjacent fingers of the dominant hand with the tenant present, then read both back twice. Mechanical key: turn, withdraw, reinsert, repeat. App: confirm the tenant has accepted the invite and unlocked once with it. The tenant signs a second line on the receipt confirming each lane tested. A credential that the tenant never tested in your presence is a credential that does not yet exist for audit purposes.
MI-4. Move-in handover file. File the signed receipt, the policy the tenant received (your standard tenant access policy, in plain language, not legalese), the key-control envelope reference, and a dated photo of the lock's battery indicator at handover. The photo is not paranoia: battery state at move-in is your baseline for any later complaint about a dead door.
MI-5. Tenant-side handover pack. Hand the tenant a single sheet listing what they hold, what they must return at move-out, what happens to the credentials when the tenancy ends, and how to reach you in a lockout. The sheet is a tenancy record, not a marketing document.
| Move-in step | Document produced | Filed under | Failure if skipped |
|---|---|---|---|
| Pack built | Credential receipt (draft) | Unit / tenancy file | Credential issued with no record |
| Identity check | Tenancy agreement + ID copy reference | Unit / tenancy file | Tenant later disputes identity |
| Lane-by-lane test | Receipt (countersigned) | Unit / tenancy file | "I never got a code that worked" |
| Handover photo | Battery indicator image | Unit / tenancy file | Battery complaint with no baseline |
| Tenant handover sheet | Copy signed by tenant | Unit / tenancy file | Tenant returns the wrong card at move-out |
IF-THEN rules for Protocol 1:
- IF the unit lock is biometric-capable AND the tenant declines biometric enrolment, issue the available non-biometric lanes only (PIN, card, mechanical, and app if the model supports it). Do not enrol a fingerprint under duress, and do not enrol a third party's fingerprint on someone else's behalf. Biometric data carries a consent rule you cannot wave away, and the route through that rule is your own counsel plus the model's product page on storage, not on this playbook.
- IF the tenant is a re-let into the same unit within seven days, treat it as a new move-in. Wipe every lane on the unit door before issuing new credentials. Never assume "the previous tenant cleaned it out."
- IF the lock supports an app lane AND the tenant declines the app, note it on the receipt. Some app-eligible models still generate passive audit records on app presence even without active tenant use; whether that is the case for your model is a product-page question, not an assumption.
- IF the unit lock is sample-only and cannot generate per-event logs, Protocol 4 below adapts: your audit is the signed receipt plus the periodic reissue register, not a lock-side event history. Check the model’s published specification whether the model on the unit door is log-capable at all.
- IF the tenant moves in with a partner, family member, or roommate not on the lease, the policy is the same: lanes are issued to the tenant named on the agreement. Additional occupants use the tenant's lanes under that tenant's responsibility. Document that on the receipt.
Protocol 2: The Move-Out Takedown Ceremony
Move-out is where landlords lose the audit. The window between a tenant's last day and the next tenant's first day is exactly when ghost credentials form. The takedown ceremony exists to make that window boring on purpose.
MO-1. Pre-inspection record (T-2 days). Pull the unit file. The day before the inspection, list every credential the tenant currently holds for that unit: card numbers, PIN, fingerprint count, app account, mechanical key envelope. You should be able to do this from the move-in receipt in Protocol 1 plus any subsequent reissues you have logged. If you cannot reproduce that list from your own file, the lock program has already drifted.
MO-2. Walk-the-door pass (T-1 day). Visit the unit. Confirm the lock's mechanical override works (turn it, withdraw, reinsert). Confirm the app account is signed out on the tenant's device if your model exposes that, or documented as out-of-scope if it does not. Open the battery compartment and read the indicator. Photograph the door and the lock.
MO-3. The takedown (T-day, before key return). Execute each lane in this order:
- Delete PIN. The PIN used by this tenancy is never issued to the next tenancy — the PIN is a single-tenancy artifact, period. Check the model’s published specification whether your model deletes a single PIN or only the full user slot.
- Delete or revoke RFID cards (block card serial at the lock's admin lane; do not only "stop recognising" them informally). Cards issued to the tenancy are filed back into the pool with the tenancy number written on them; they are not reissued to the next tenant until the next tenant's move-in.
- Delete enrolled fingerprints (clear the biometric template, not just the "user entry"; check the model’s published specification whether the model exposes a per-finger delete or only a wipe-all).
- Sign out / revoke the app account. The app account issued to this tenancy is closed, not paused.
- Retrieve the mechanical key envelope. If it is missing, file a missing-key incident and treat the lock cylinder as compromised until re-pinned or replaced (do not assume the next tenant will simply be issued a new PIN).
After every step, the operator performing the takedown signs the takedown sheet, and a second person countersigns. Two-person rule is the rule even when the landlord is solo — the witness can be a neighbour, a family member, or a trusted contractor, as long as the witness is named and signs.
MO-4. Wipe verification (T-day). Stand at the door with each removed credential in turn and confirm denial. PIN: enter the old code, watch for denial. Card: tap the returned card, watch for denial. Fingerprint: present the old print, watch for denial. App: present the app, watch for denial. Mechanical key: this one you cannot easily test (you have just retrieved it); instead, the second person inspects the key envelope and countersigns its retrieval. A door that fails the wipe verification is escalated to Protocol 6 before the next tenant is allowed to move in.
MO-5. Unit reset state. With every lane cleared, perform the lock's admin reset only if your model's product page tells you it is the correct takedown endpoint (some locks distinguish "delete user" from "factory reset"; the latter clears admin slots too, which is almost never what you want at move-out). Photograph the wiped-state indicator, file the takedown sheet, and mark the unit "ready for re-let."
| Move-out step | Document produced | Failure if skipped |
|---|---|---|
| Pre-inspection record | Credential list reconciled to file | List of held credentials is guesswork |
| Walk-the-door pass | Battery photo, lock photo, key envelope status | Move-out baseline missing |
| Lane takedown | Takedown sheet, countersigned | Ghost credentials live |
| Wipe verification | Signed wipe-verification record | Door still opens to a removed credential |
| Unit reset state | Reset-state photo, file closed | Unit handed over with undetermined state |
IF-THEN rules for Protocol 2:
- IF the tenant leaves without returning a card or a key, treat the credential as live until you can prove it is dead. Mechanical-key cylinders on a missing-key event get re-pinned or replaced before re-let, not just re-coded. The cost of pinning a cylinder is far less than the cost of an unauthorised entry.
- IF the lock is sample-only and cannot tell you which PINs or cards are currently active, you are relying on the file, not the lock. That is acceptable — the file is your source of truth — but it must be updated in writing at the door, with a witness, before the tenant leaves.
- IF the tenant disputes that they held a credential, the move-in receipt is the answer. The absence of a move-in receipt at this point is an operational failure that started at Protocol 1, and it does not get fixed at move-out.
- IF the unit will sit vacant for more than 14 days, the cleaning/maintenance access pattern changes (Protocol 3 below); the unit's lock is left in a "no active tenant, controlled owner windows" state, not in a "last tenant still resident" state.
- IF the same PIN was issued to the prior tenant and you are tempted to leave it in place, do not. The single-tenancy rule is absolute. Reissuing a PIN across tenancies is the cheapest-to-cause and most-damaging failure mode in a rental fleet.
- IF the tenancy ended abruptly (eviction, abandonment, dispute), the takedown happens at the date the tenancy legally ends, not at the date the tenant finally returns the keys. Treat all held credentials as live until the wipe verification confirms otherwise.
Protocol 3: Periodic Credential Reissue
Move-in and move-out are the events that get attention. The reissue rule is the one that prevents steady-state drift. The cadence of reissue depends on how often the unit turns over and how the lock is used in between.
PR-1. Reissue triggers. A credential is reissued — for an in-place tenant, without changing the tenancy — for any of four reasons:
- Periodic time trigger. A scheduled reissue of one or more lanes on the calendar — see PR-2 below for cadence options.
- Lost-credential event. A PIN, card, key, fingerprint, or app account the tenant reports lost, compromised, or copied. See Protocol 5 (lost-credential runbook).
- Relationship event. A new partner, a departing partner, a roommate change, a subletter situation. The landlord reissues the affected lanes and notes the change in the unit file.
- Door hardware event. A lock reset, a battery event, a firmware update, or a model swap. The landlord treats the lock's credential set as compromised on reset and reissues from the unit file.
PR-2. Periodic cadence by tenancy length. The cadence of a scheduled time-trigger reissue depends on how long the unit has been continuously tenanted and what kind of lane is in play.
| Tenancy length | PIN / code | RFID card | Fingerprint | App account | Mechanical key |
|---|---|---|---|---|---|
| Under 1 year | Reissue once at 9 months if still tenanted | Return on suspicion only | Return on suspicion only | Return on suspicion only | Return on suspicion only |
| 1–3 years | Reissue every 12 months | Return on suspicion only | Return on suspicion only | Re-enrol at 24 months | Return on suspicion only |
| Over 3 years | Reissue every 12 months | Reissue every 24 months | Re-enrol at 36 months | Re-enrol at 24 months | Return on suspicion only |
These are planning defaults, not vendor specs. A PIN that a tenant has held for four years and shared with the in-laws, the dog-walker, and the plumber is a PIN that the landlord should have rotated twice by then, regardless of whether the tenant thinks they have been careful. Check the model’s published specification whether your model supports single-PIN rotation (most do, by lane); confirm on the same page whether your model supports a per-tenant app account pause-and-replace (some do; some require a fresh account).
PR-3. The reissue ceremony (abbreviated). A scheduled reissue is shorter than a move-in but follows the same shape:
- Notice (PR-3.1). Notify the tenant in writing that a credential is being rotated. State the lane, the date, and the reason. The notice is filed.
- Old credential revoked (PR-3.2). Standing at the unit door, the operator (or the tenant, where the model supports self-service) deletes the old credential from the lock.
- New credential issued (PR-3.3). A new PIN, card, fingerprint, or app account is enrolled at the door, in the tenant's presence where possible.
- Old denial confirmed (PR-3.4). Stand at the door and confirm the old credential no longer opens the lock.
- Receipt updated (PR-3.5). The unit's credential receipt is amended in the unit file with the date, the lane rotated, the new credential reference, and the operator's signature.
PR-4. Standing vs windowed non-resident credentials. Non-resident credentials for cleaners, contractors, gardeners, pet-sitters, and the like must be issued under a written window (see PR-5) — never as standing credentials. A cleaner who has visited weekly for six months is a candidate for promotion to a standing-but-revocable credential on a separate pool, but only on a written decision on a written form. Promotion does not exempt the cleaner from periodic re-verification.
PR-5. The window design for non-resident credentials. Every windowed non-resident credential has four fields, written on the access-request form before the credential is issued:
- Who. Named individual, not "the cleaning crew."
- Which doors. Specific unit list, not "the property."
- Which window. Start date/time and end date/time.
- Which lane. Credential type and its expiry behaviour — time-bounded PIN, expiring app invite, expiring card, or fingerprint enrolled against that specific individual and removed at window end.
The form is filed; the second person countersigns; the window is run. At window end — to the hour, not the day after — the credential is removed by the operator standing at the door. The same two-person rule applies.
IF-THEN rules for Protocol 3:
- IF the tenant has not used a credential lane in 12 months, that lane is a candidate for removal — not for "preserved in case it's needed." A lane nobody uses is a lane someone forgot, and forgotten lanes are ghost-credential candidates.
- IF the reissue cadence hits while the unit is between tenancies, the reissue is bundled into the next takedown (Protocol 2) rather than executed separately.
- IF the unit is a long-tenancy rental and the tenant has held the same PIN for five years, treat the next reissue as a higher-priority event — historical accumulation is the highest-risk state.
- IF the landlord cannot reach the tenant on the day of a scheduled reissue, the reissue is rescheduled inside the same month, not skipped. A control that can be silently skipped is not a control.
- IF the model does not support per-PIN rotation and only supports PIN delete-and-recreate, the reissue is acceptable — the receipt file is updated — but the move-out takedown discipline must then be airtight to prevent cross-tenancy reuse.
Protocol 4: Log Review as a Per-Model Question
Every landlord eventually asks: "what does this lock know?" — meaning event history. Here is where most playbook advice goes wrong by assuming the answer. The honest engineering position: event logging is a per-model capability, and you must treat it as a question to your own product page, not a property of "smart locks" in general.
Three questions, per model, before any log-review routine can be written for the rental fleet:
| Capability question | Why it decides your routine | Where the answer lives |
|---|---|---|
| Q1. Does this model record access events at all (opens, denials, admin actions)? | If no, log review is off the table; the receipt file (move-in receipts, takedown sheets, reissue records, lost-credential runbooks) becomes your only detection lane — keep it disciplined | Product page / datasheet for the exact model |
| Q2. How many records does it hold before overwriting? | Determines the review interval: a small rolling buffer must be read weekly or findings vanish before they can be seen | Product page for the exact model — check the model’s published specification |
| Q3. How are records read or exported — admin gesture sequence, companion app, PC tool, or service interface? | Determines who can do the review (an admin-credential matter) and how long the monthly task takes | Product page and the manual shipped in the carton |
Fill this capture sheet once per purchased model and archive it with the unit file:
| Model (SKU as ordered) | Q1 records? | Q2 capacity | Q3 read/export method | Date confirmed | Source URL/revision |
|---|---|---|---|---|---|
| EXAMPLE: keypad class A batch X | ___ | ___ | ___ | ___ | ___ |
| ___ | ___ | ___ | ___ | ___ | ___ |
A necessary firewall on numbers. Some of our hotel electronic locks carry published audit-record figures — the SLK-9936S hotel lock, for example, specifies audit/event records up to 1,000 in its hotel-lock spec block. That figure belongs to that hotel model and to nothing else. It must never be quoted, assumed, or inferred for a unit-door residential rental model. Where a unit-door model logs, its capacity is its own product-page number. Where the product page is silent, the answer is "ask before ordering" — and /request-a-quote is the channel.
Log-review cadence for log-capable models.
- L-1. Monthly, align log reading with the re-verification walk so one trip serves both. Pull records for the period.
- L-2. Scan for three patterns only — you are a landlord, not an analyst: (a) opens outside expected hours for that tenancy (a non-resident credential reused outside its window is the most common rental-fleet finding); (b) admin actions (enrollments, deletions, resets) you cannot match to a receipt or reissue record; (c) repeated denials at the door (a stale credential someone keeps trying).
- L-3. Reconcile against the receipt file. Every unmatched admin action is either a forgotten entry in your own paperwork or an unauthorised change. Both are findings; only the second is urgent.
- L-4. If capacity is a rolling buffer, set the review interval shorter than the overwrite horizon — that arithmetic is exactly why Q2 gets asked before the routine is written, not after a month of lost history.
Sample-only models. Where the model records no log, write that into the unit file explicitly. Do not leave it ambiguous. Your control set is move-in / move-out / reissue / lost-credential runbook, plus negative-test sampling at handover — see Protocol 5 for negative-test discipline inside the lost-credential runbook.
Protocol 5: Lost-Credential Runbook
The lost-credential event is the highest-pressure event a landlord runs. It needs a written runbook that can be executed at 11 p.m. on a Sunday with one phone call to a witness and a wrench. The runbook below is written to close the gap inside 24 hours.
LR-1. Confirm the event (within 30 minutes of notification). Get the facts in writing: what was lost (which lane), when, where, who had access, who might have copied it. A landlord who has been told "the dog-walker saw the card on the kitchen counter" has a different event from one who has been told "the tenant's phone with the app was stolen at a bar." Get the report on a one-page form.
LR-2. Classify the event.
| Class | Definition | Response time |
|---|---|---|
| LOW | Card or key reported lost by tenant, never duplicated, no suspicion of adversary | Within 7 days; revoke on next scheduled visit |
| MEDIUM | PIN or app account compromise suspected (shared with non-tenant, written down where it was found, photographed) | Within 48 hours; revoke before next tenant or window activity |
| HIGH | Mechanical key lost, suspected copying, theft of phone with app, break-in pattern involving the unit | Within 24 hours; revoke all lanes, re-pin cylinder if mechanical, file incident |
Class is the landlord's call, not the tenant's. Err on the side of higher class until the facts are clear.
LR-3. Revoke the affected lane (within the response window). Stand at the unit door. Delete the affected PIN, block the affected card serial, revoke the affected app account, or — for HIGH events — re-pin or replace the mechanical cylinder. Photograph the lock state before and after.
LR-4. Reissue a replacement lane (same visit if possible). Where the tenancy continues, issue a replacement credential to the tenant at the door. The replacement is enrolled with the same two-person rule as a move-in (Protocol 1, abbreviated). The lost credential is tested for denial at the door, in the tenant's presence, before the operator leaves.
LR-5. Negative-test the lock (HIGH events only). For HIGH events, perform a negative test on every remaining lane: present the revoked card, expect denial; enter the old PIN, expect denial; present the stolen phone's app account, expect denial; if the mechanical key was the loss point, re-pin the cylinder, and confirm the old key no longer turns the lock. The lock that fails the negative test is escalated immediately — see Protocol 6.
LR-6. Document and file. The one-page form from LR-1 is updated with the response: which lane was revoked, which was reissued, when the negative test was run, who witnessed, and the final state. The form is filed against the unit number. The tenant is given a copy.
| Runbook step | Document produced | Filed under | Failure if skipped |
|---|---|---|---|
| Event confirmed | One-page event report | Unit / tenancy file | "When did you find out?" has no answer |
| Event classified | Class (LOW/MEDIUM/HIGH) on the form | Unit / tenancy file | Response window is guesswork |
| Lane revoked | Revocation record, pre/post photos | Unit / tenancy file | Revocation never happened |
| Replacement issued | Reissue receipt, countersigned | Unit / tenancy file | Tenant lacks working credential |
| Negative test | Negative-test record (HIGH only) | Unit / tenancy file | Revocation is unverified |
| Documentation closed | Updated event report | Unit / tenancy file | Cadence cannot learn from the event |
IF-THEN rules for Protocol 5:
- IF the lost credential was a mechanical key, the response is HIGH-class by default. Re-pin or replace the cylinder; do not assume the key is somewhere innocuous. A landlord who has been told "I lost it somewhere" has had a cylinder compromised; pin the cylinder before the next tenant activity.
- IF the lost credential was a tenant-side fingerprint (where the tenant enrolled a fingerprint through a model that allows tenant-side enrolment), the lock's biometric template for that finger is the credential. Whether the model allows per-finger template deletion or only a wipe-all is a product-page question; plan the response before the next tenancy event.
- IF the lost credential was an app account on a phone with no PIN lock on the phone, that is HIGH by default. Treat the app account as compromised even if the tenant intends to recover the phone.
- IF the tenant is uncontactable for 24 hours after a HIGH event, the landlord re-pins or replaces the cylinder unilaterally and files the action under the tenancy; reissuing when the tenant returns is cheaper than waiting.
- IF the lock is sample-only and does not support per-lane revocation through a UI, the runbook's revocation step is a physical replacement or a cylinder re-pin, not a remote lane delete. Check the model’s published specification which lanes the model lets you delete from the keypad and which require a physical reset gesture.
- IF the same credential is reported lost twice in a tenancy, the second report is HIGH by default. Patterns are the audit's most valuable output; a tenant who loses the same card twice is a tenant whose environment you do not yet understand.
Protocol 6: IF-THEN Decision Rules and Exception Handling
Operations manuals earn their keep on bad days. Pin this table inside the unit file or inside the operator's folder. These rules do not require guessing the lock's internals; each routes to a written protocol or to the product page / factory channel.
| IF | THEN | ELSE / ESCALATE |
|---|---|---|
| A negative test opens the door | Same-day: treat the credential as live, re-run the revocation per Protocol 5, re-test before end of day | Repeat failure → suspect model behavior, raise with factory via quote/support channel; consider door policy change |
| The same PIN appears on two tenancies | Same-day: treat both tenancies as compromised; re-issue immediately; investigate how the duplication entered the system | Documentation failure at move-in OR move-out; update the receipt template and the takedown worksheet |
| A re-let happens within 7 days and the previous tenant's PIN was not deleted | Treat as LIVE credential; do not issue the new tenant's credential until the old one is deleted and verified denied at the door | Document a stop-the-line entry in the receipt file; review the takedown ceremony with every operator |
| The mechanical key is missing at move-out | File incident; treat the cylinder as compromised; re-pin or replace before re-let | Do not accept "we'll find it" — the unit is held until the cylinder is replaced |
| A log (where the model records one) shows opens outside tenancy hours | Pull the receipt file; check the windowed-credential register; verify there is no unauthorised admin action | Pattern repeats → audit the admin role structure; see Protocol 4 L-2 |
| Product page does not answer Q1–Q3 clearly | Do not assume. Ask before ordering more units of that model; the answer shapes your SOP | Fleet already installed without answers → run capture sheet for every installed model this quarter |
| A tenant reports a fingerprint failure on move-in | Re-run the enrolment standard (the capture-quality pattern is covered in /blog/fingerprint-smart-lock-access-management); issue a non-biometric fallback lane in parallel | Sensor hygiene question becomes the next protocol — see Protocol 5 |
| Operator on holiday / role vacant | Named deputy runs the move-out and lost-credential protocols at minimum; reissue cadence moves within the month | Coverage gap >1 month → report as skipped control in the annual review |
| A lock was factory-reset for any reason | Its credential set is now empty while the tenancy may not be; re-enrol every current lane from the unit file before returning it to service | Anyone reports "lock doesn't work" afterward → orphaned-access defect, run Protocol 5 negative test for that unit |
| A tenant reports they shared their PIN with a non-occupant | Treat as MEDIUM-class lost-credential event per Protocol 5; revoke and reissue; document the conversation | Pattern recurs → add a written policy clause to the tenancy agreement before the next reissue |
The shape of these rules is the same as the shape of the rest of the playbook: none of them requires guessing the lock's internals. Each routes to a written protocol (the lost-credential runbook, the reissue rule, the per-model capture sheet) or to the product page / factory channel. That routing is the point.
Illustrative Scenario: One Quarter at Old Highbury
The following is an illustrative scenario, not a customer story.
Consider a small landlord, six rental units in two terraces, eight doors that carry credentials: 6 unit doors (a mix of multi-method models like the SLK-8831 5-in-1 class on three units and standalone keypad/RFID models on the other three) plus 2 shared-amenity doors (a bike store and a bin store) using keypad-only models. The landlord runs the tenancies personally, with a nephew as named witness for the two-person sign-offs.
The quarter opens with two pending move-outs: Unit 3 (March 31) and Unit 5 (April 30). The move-out takedown ceremonies for both clear cleanly: both tenants return their cards and key envelopes; both wipe-verifications are signed; both reissues for the next tenants are scheduled inside the seven-day mark. The Mechanical-key register finds one of the seven master override envelopes is unaccounted for — a HIGH-class event; the cylinder on the bike-store door is re-pinned the following Saturday with the nephew as witness, before any further tenant activity touches that door.
In April, Unit 1 reports a lost card (Tuesday morning, "left it on the bus"). The landlord classifies MEDIUM by default: the bus is public, the card could be photographed by anyone holding it. The card is blocked at the lock within 24 hours; a replacement card is issued at the door on Wednesday evening; the old card is tested for denial in the nephew's presence before the landlord leaves. Receipt updated, file closed.
In May, the landlord's annual review surfaces a pattern: Unit 6 has held the same PIN for 22 months. Per Protocol 3 PR-2, the periodic reissue cadence hits at 12 months. The PIN is rotated on the next scheduled visit, with the tenant present and the nephew as witness. The old PIN is tested for denial at the door before the landlord leaves. The receipt is annotated: "PIN rotated 2026-05-14, new PIN issued to tenant in person, old PIN tested for denial, cleared."
By the end of the quarter, the landlord has spent roughly 14 hours on the cadence — the two move-outs (3 hours each), the move-ins (2 hours each), the one medium-class lost-credential event (45 minutes), the periodic reissue on Unit 6 (1 hour), the cylinder re-pin (90 minutes), the protocol 4 capture-sheet update (3 hours), and the runbook review (1 hour). The findings closed cleanly: one unaccounted mechanical key (HIGH, resolved), one bus-card loss (MEDIUM, resolved), one overdue PIN rotation (caught by the review, resolved). The protocols ran as written; the protocols made the quarter boring on purpose.
For comparison: the same landlord in the same quarter without the playbook would have re-issued the bus card eventually, would have changed the PIN for Unit 6 in response to a complaint rather than a calendar, and would have filed the unaccounted mechanical key in the back of the drawer under "ask the nephew later." Each of those three lapses is a finding that compounds; the playbook is what stops them compounding.
Where This Playbook Hands Off to Other Articles
This document is one layer of a rental access operations stack. The articles it does not replace, and where to go for them:
- Property-manager systems overview. Smart Lock Systems for Property Managers is the higher-level routing guide — when you are scoping the fleet rather than running the cadence, this is the right instrument.
- Multi-method standalone operations cadence.Smart Locks for Apartment Operators is the operator-flank playbook for a single owned apartment block; that document is a daily/weekly/monthly/quarterly rhythm rather than the tenant-lifecycle rhythm this playbook runs.
- Fingerprint-only run-time cadence. Fingerprint Smart Lock Access Management is the sensor-specific standalone fingerprint SOP — useful where the rental fleet runs a single biometric credential rather than the mixed-method set this playbook covers.
- Long-tenancy credential durability.Smart Locks for Long-Term Rentals covers the family's-decade-on-the-property case — useful where the periodic reissue cadence in Protocol 3 needs adjusting for a stable household.
- Short-stay / per-stay turnover. Smart Locks for Short-Term Rentals is the credential method comparison for the nightly-stay regime; this playbook assumes long- and mid-stay tenancies on owned assets.
- Build-to-rent multi-block programme. Smart Locks for Rental Apartment Operators is the staged-rollout programme for an institutional build-to-rent operator; this playbook runs the cadence inside a unit on a programme like that one, not the programme itself.
Put the Cadence in Writing Before You Order the Next Batch
If you are standing up rental access on a second unit — or scaling a portfolio where the receipts have never been reviewed — the cadence above can be drafted now and pressure-tested against whatever the product pages say about logging, capacity, time-bounded PINs, and per-lane rotation on the exact models you choose. Bring your door classes, turnover rate, and the three log-capability questions to the table when you spec the hardware, not after install day.
Sample units taken from Order samples can be run through the move-in ceremony on the landlord's own bench; the move-out takedown and the lost-credential runbook are then reproducible in writing before the first tenant moves in. Fleet-scale quotation and lock-program scoping live at Request a quote. The cadence is yours to run; the lock program runs as well as the cadence demands; the cadence rewards you with predictable tenancies instead of unpredictable incidents.

