Smart-lock temporary access for rentals runs on written clauses: per-credential validity windows, named contractor pairing, lease-end surrender and audit.

Opublikowano: kwi 02, 2025

Smart Lock Temporary Access for Rentals

Smart Lock Temporary Access for Rentals

A rental property's front door does not behave like a homeowner's front door. It is shared, briefly, by people who have no relationship with the lock — and who will leave. The credential you give them is not a key; it is a window. The clauses in this handbook describe how that window is opened, how it closes, and what happens to the lock and the people around it during the brief hours in between.

Direct answer: Smart-lock temporary access for rentals is governed by a written policy handbook of numbered clauses that specify, for every category of person who might need the door, what credential they receive, what time window that credential is valid in, who is allowed to issue and revoke it, how that credential is paired to a named individual, how access is surrendered at lease end, and how disputes about access are routed. The lock hardware falls out of the clauses — not the other way around.

This article is the policy-side complement to two siblings. The credential-method comparison for short-term rentals sits in Smart Locks for Short-Term Rentals (scoring PIN codes, IC cards, fingerprint and keyboxes against a turnover calendar); the guest-side issuance workflow sits in Smart Lock Guest Access for Rentals. This article covers the policy spine underneath both: the rules that govern who may be issued what, and for how long, and under whose authority, regardless of which credential method the property has chosen.

How to Use This Handbook

The handbook is organised in numbered Parts. Parts I–II set the frame (definitions, the population registry, the door-class classification). Parts III–VI are the policy clauses themselves, one Part per slice of the temporary-access problem: window-of-validity policy (Part II), contractor and vendor name-tag pairing (Part III), end-of-lease closure and surrender (Part IV), dispute handling (Part V), and audit, breach and change control (Part VI). Part VII is the hardware reconciliation — a clause-to-capability map the property fills in against the chosen lock models. Adoption order closes the handbook.

Reading conventions:

  • Clauses are blockquoted. Lift them into your rental house rules verbatim, substituting bracketed fields (Property, role list, Window, Issuer) with local values.
  • Each clause carries a usage note. The note names what breach the clause prevents and what lock capability it assumes.
  • The capability-blanks rule. Wherever a clause needs a device behaviour — per-credential expiry windows, atomic revocation, audit-log read-out, keyway custody — 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; on the same point, the rule repeats every time the point recurs.
  • Method-agnostic. The handbook is silent on whether the property uses PIN codes, IC cards, mobile-app credentials or mechanical keys for its temporary access. Whichever lane the property uses, these clauses govern. Method-specific rules live in the sibling articles linked above.

Fact discipline. No prices, no order quantities, no delivery timelines, no warranty terms, no certification claims. Commercial terms resolve through a quote request; per-model capabilities through each product page. Where this handbook cites any specific SKU — including the SLK-9936S hotel-lock block in Part VII — it does so as a format ruler only, with an explicit no-porting firewall.

Part I — Frame Clauses

A temporary-access policy without a population registry is a list of text messages waiting to happen. These clauses set the vocabulary.

Clause 1 (Temporary Credential Defined). A temporary credential is any credential issued to a person who has no standing relationship with Property — including but not limited to a guest of a current tenant, a contractor engaged by the landlord, a vendor delivering goods, an inspector acting under public authority, a sub-renter approved in writing, or a short-stay guest under any rental arrangement of N nights or fewer. A tenant's own credential is not a temporary credential; it is the primary credential, governed by the lease.

Usage note. Excluding the tenant's own credential keeps every clause in the handbook readable. Tenants issue and revoke their own guests' temporary credentials under Part II; the landlord issues and revokes the tenant's.

Clause 2 (Population Registry). Every person who might in future receive a temporary credential is recorded in a single Population Registry held by Issuer. Records contain: full legal name, role category (Guest / Sub-renter / Contractor / Vendor / Inspector / Other), credential type, valid-from and valid-until, issuing person, revocation status, and the underlying authorisation document reference (booking reference, work order number, sub-tenancy agreement, inspection warrant number).

Usage note. The Registry is the document of evidence in a dispute; Part V routes most disputes to "show the Registry row." The Registry only works if it is filled in at the moment of issuance, not the morning after.

Clause 3 (Issuer Roster). A credential may only be issued by a person named on the Issuer Roster — a closed list maintained by landlord / property owner. The Issuer Roster is published to all tenants at the start of every tenancy and reissued on change. Each issuer is assigned a credential-class authority: Tenant Issuer (may issue Guest and Sub-renter credentials within the tenant's own unit), Manager Issuer (may issue Contractor, Vendor and Inspector credentials for the whole property), Audit Issuer (read-only access for dispute resolution).

Usage note. Splitting authority keeps the policy small and the audit honest. A tenant who can issue sub-renter credentials to anyone for any window is a property-management liability; a manager who can read every tenant's audit log is a privacy liability.

Clause 4 (Door Classes). Every door that participates in the temporary-access regime is assigned one of three classes: Class A — Tenant-Front Door (the door a tenant enters through; primary credential held by tenant, secondary by guests), Class B — Shared-Service Door (a door tenants do not use but vendors, contractors or inspectors do — risers, plant rooms, bin stores, roof accesses), Class C — Common-Entrance Door (the building's main entrance, courtyard gate, parcel room door). Class assignments are recorded in the Door Register and re-surveyed at every change of tenancy.

Usage note. Most rental properties assume they have only Class A doors. They usually have Class B doors too (the utility cupboard behind the kitchen, the riser in the hall closet) — and those Class B doors are where temporary-access discipline is weakest.

Clause 5 (Credential Lanes). The Property recognises four credential lanes: Lane 1 — PIN/Code (numeric code entered at a keypad, with a per-credential expiry window), Lane 2 — Card/Tag (RFID/Mifare-class credential presented at a reader, with a per-credential expiry window), Lane 3 — Mobile-app credential (issued through the lock's mobile app — on supported models, check the model’s published specification — and revocable from the app), Lane 4 — Mechanical key (cut for the cylinder, with keyway custody tracked in a separate Key Custody Register, governed by the keys-and-credential custody clauses in this Part). The Property declares in writing which Lane is the default lane for each Class of door.

Usage note. "The lock supports codes" is not a policy. "The lock supports codes and the default lane for Class A is Lane 1" is. The declaration disciplines procurement: a property whose Class B default is Lane 3 cannot buy a contractor who shows up with a standalone keypad model.

Clause 6 (No Standing Credentials Outside the Registry). No person holds a working credential outside the Population Registry. There are no "I gave the gardener a code once and forgot to delete it" credentials. There are no "the cleaner knows the master code" arrangements. Every active credential corresponds to a row in the Registry with an unexpired valid-until date. Audit at Part VI verifies the negative — a row exists for every active credential and no row exists for any expired credential.

Usage note. The single rule the entire handbook rests on — and the rule every property breaks first. The audit step exists to surface the break.

Part II — Window-of-Validity Policy Clauses

The temporary credential's defining attribute is not who it identifies — it is when it is valid. These clauses govern the window.

Clause 7 (Default Validity Window). A temporary credential is valid from issuance for a window bounded by a single start instant and a single end instant. The default window for role category is Duration; longer or shorter windows require written justification appended to the Registry row. A credential may not be issued for an indefinite or open-ended window.

Usage note. "Indefinite" is the word that kills governance: a code that has not been told when to die will outlive the relationship it was issued for and survive into the next tenant, the next vendor, the next dispute. Whether the model supports per-credential expiry windows is the single most important capability to verify in writing before signing Clause 7.

Clause 8 (Window Sizing Rule). The window is sized to the task, not the person. A guest checking in for a three-night stay receives a window of length three nights plus a one-hour pre-arrival grace and a one-hour post-checkout tail; the total window is four nights. A contractor on a four-hour boiler service receives four hours plus a thirty-minute grace at each side. The window never exceeds the task by more than one hour at either side.

Usage note. Arbitrary window lengths are arbitrary policies. Where the lane is mobile-app credential, the window is set in the app; where the lane is keypad PIN, the window may need to be entered at the lock on the day (check the model’s published specification). Where the lane is mechanical key, the window is a custody window, not a credential window, governed by Clause 22.

Clause 9 (Hard Cutoff). A credential's valid-until instant is a hard cutoff, not a soft suggestion. At the cutoff, the credential fails to open the door. No issuer may "extend" an expired credential by text message; an extension requires a new issuance and a new Registry row, and the audit row is left untouched so the renewal is visible.

Usage note. A soft cutoff is a code that "might still work" because nobody disabled it. The clause forces every extension to be auditable. Whether the model automatically refuses to open the door after the cutoff or merely logs the attempt is a product-page fact that affects Part V.

Clause 10 (No Implicit Renewal). A temporary credential does not renew on its own. A guest who extends a booking receives a new credential, with a new valid-from and valid-until; the original is revoked at the moment of renewal. A contractor who runs late does not have their credential "automatically extended"; the original is revoked at the original cutoff, and a new credential is issued if the issuer agrees the task is incomplete.

Usage note. Splitting one stay into two credentials also splits the audit trail into two rows — exactly the granularity needed in a "the guest said they had permission to stay until Monday" dispute.

Clause 11 (Time-Zone Discipline). Every window is recorded in the property's local time, with the time zone named in the Registry header. Where the property uses an app-connected mobile credential (Lane 3, on supported models), the issuer confirms the app's time zone matches the property's at issuance; mismatches are corrected before the credential is sent to the recipient.

Usage note. Cross-time-zone credentials are a quietly common failure mode for short-stay rental properties. A guest arriving from a three-time-zone difference and a host who set the window "in good faith" both behave honestly; the lock does not.

Clause 12 (Anti-Stacking Rule). A single person holds at most one active temporary credential of a given Lane at any time. Multiple overlapping credentials for the same person and lane are prohibited; they cause confusion in audit and obscure which credential was used. The Registry rejects duplicate issuance; if a duplicate is discovered after the fact, the older credential is revoked and the revocation row is annotated.

Usage note. Stacking is what happens when a host wants to be sure the guest has a code and so sends two. The clause forces the host to choose.

Clause 13 (Pre-Arrival Grace Cap). A temporary credential may be issued with a pre-arrival grace of at most one hour before the formal valid-from instant. Longer grace windows are treated as standing access and routed to Clause 14. The grace window is logged separately from the formal window in the Registry so it can be audited.

Usage note. One hour absorbs a delayed flight, a slow taxi, a misjudged check-in time. Two hours is "the host wanted the guest to have a buffer" — and that conversation needs to happen out loud, in writing, and recorded.

Clause 14 (Standing Access Exception). A standing-access credential — a credential with a window longer than N days — is permitted only for the roles listed in the Standing Access Register and only with a written justification appended to the Registry row (a recurring vendor relationship, an emergency contact, an on-call agent). The default maximum validity is thirty days; re-issuance is required to extend. Standing-access credentials are reviewed quarterly under Part VI.

Usage note. This is the exception, not the default. Standing access is what happens to recurring cleaners, contracted maintenance crews, and on-call trades — people who need to come and go across windows the host cannot pre-schedule. The clause does not forbid them; it forces them into a register with an expiry date.

Door classDefault laneDefault window for a GuestDefault window for a ContractorDefault window for a Sub-renterDefault window for an InspectorStanding access permitted?
Class A — Tenant frontLane 1 PIN/code, with Lane 3 mobile-app on supported modelsstay length + 1 h each sidetask length + 30 min each sidesub-tenancy termwarrant windowonly on named Standing Access Register rows
Class B — Shared serviceLane 2 card/tag or Lane 3 mobile-app on supported modelsnot issued at Class Bper-shift windownot issued at Class Bwarrant windowonly on named Standing Access Register rows
Class C — Common entranceLane 3 mobile-app on supported models, with Lane 2 card/tag fallbackper-stay windowper-shift windowper-stay windowwarrant windowonly on named Standing Access Register rows

Usage note for the matrix. Each cell is a capture item, not an assertion. Whether a given Class A lock actually supports Lane 1 with per-credential expiry, or Lane 3 mobile-app issuance, is a product-page fact for the chosen model. Defaults are policy defaults — the hardware has to be chosen to support them.

Clauses 7 through 14 chain together into one issuance decision — roster check, window sizing, register routing, cutoff, renewal — and it is worth seeing the chain drawn out before moving to the pairing clauses. The diagram below follows a single credential from request to revocation under the Part II rules.

flowchart TD
    A["Issuance request · role category named in Population Registry"] --> B{"Issuer on the Issuer Roster?"}
    B -- "no" --> X["Refused · route to the Manager Issuer with authorisation document"]
    B -- "yes" --> C["Size the window to the task · Clause 8\ngrace capped at one hour each side · Clause 13"]
    C --> D{"Window exceeds the default bound?"}
    D -- "yes" --> E["Standing Access Register row\nwritten justification · Clause 14"]
    D -- "no" --> F["Issue credential · Registry row with\nvalid-from · valid-until · Clause 7"]
    E --> F
    F --> G{"Hard cutoff reached?"}
    G -- "task incomplete" --> H["No implicit renewal · Clause 10\nnew issuance · new Registry row"]
    H --> F
    G -- "task done" --> I["Credential fails at the lock · Clause 9\nrevocation row logged for Part VI audit"]

Part III — Contractor and Vendor Name-Tag Pairing Clauses

A temporary credential handed to a contractor is, by the time the door closes, in the hands of someone whose name the host may not know. These clauses bind the credential to a named individual whose presence can be checked at the door.

Clause 15 (Named-Individual Rule). A credential issued to a contractor or vendor is issued to a named individual, not to a firm. The Registry row records the individual's full name, the firm they work for, and the work-order reference. A credential addressed to "the plumber" is not valid; a credential addressed to "Mei Lin of Riverbend Heating, WO-2026-0411" is.

Usage note. The clause prevents the "send anyone" practice, where one firm credential is re-handed to whoever shows up. Whether the chosen lock supports a per-credential label is a product-page question.

Clause 16 (Name-Tag Pairing at the Door). Where the lock is at a door where staff are not present (most Class A and Class B doors), a contractor arriving at the door presents the work-order reference and a photo ID matching the Registry row. The issuer is contacted by phone before the door is opened; if contact fails, the door is not opened and the visit is logged as a failed entry attempt. Where staff are present (a Class B door at a staffed concierge), the staff member performs the visual match and the work-order confirmation before issuing a physical token (a sticker, a printed name-tag, a single-use card) that the contractor visibly carries during the visit.

Usage note. "Name-tag" means a visible pairing artifact — something a person on the property can glance at and confirm the credential-bearer is the named individual. The artifact can be a printed sticker, a single-use card, or a contractor's existing company ID.

Clause 17 (Substitution Rule). A contractor who arrives and is not the named individual on the credential is refused entry. The substitution is logged as a failed substitution attempt. A new Registry row is opened for the substitute only after the issuer has been contacted and has issued a new credential. Substitution does not happen at the door.

Usage note. The clause forces a conversation the contractor might prefer to avoid. A firm that says "any of us can come" needs to know that, under this policy, none of them can unless their name is on the row.

Clause 18 (Visitor Pair for Sub-Renters and Sub-Tenancy Workers). A sub-renter approved in writing receives a primary temporary credential under their own name. Workers engaged by the sub-renter (cleaners, petsitters, furniture movers) are issued secondary temporary credentials, each tied to the sub-renter's name in the Registry as the responsible party. The sub-renter is the Issuer of Record for those secondary credentials and accepts dispute-routing under Part V for any breach by a secondary.

Usage note. Sub-tenancy is the highest-risk temporary-access regime because two layers of person can each place a third layer of person at the door. The clause establishes clear lines of responsibility: the sub-renter is the governor of their sub-household's visitors, and the landlord can hold the sub-renter to account for what happens downstream.

Clause 19 (Vendor Day-Pass Token). Where a vendor attends repeatedly across multiple short windows (a parcel courier visiting six units in one morning, a franchisor reading meters across an estate), the vendor day-pass token is a single Lane 2 or Lane 3 credential valid for the named individual's full day, with a Registry row annotating the unit list the token is authorised for. The token fails at any unit not on the unit list. End-of-day revocation is mandatory.

Usage note. This is the standing-access exception (Clause 14) wearing a clip-on tie. The clause distinguishes the day-pass token from the blanket standing credential by binding the token to a unit list — the vendor can only use it where the issuer said they could.

Clause 20 (Escort Window Doctrine). Where a Class B door admits a contractor without a staff member present, the contractor's window is the escort window — the period during which the contractor is, in writing, the responsible occupant of the space they entered. During the escort window, no other person may enter the space without the contractor's knowledge, and the contractor may not extend the escort window by re-presenting their credential. At the end of the escort window, the credential is logged as returned and revoked; the contractor does not retain the credential overnight.

Usage note. "Escort" in this handbook is a temporal concept, not a person. The window is the escort; the contractor is alone inside the window; the lock records who entered and when.

Pairing artifactLane supportedVisible pairing at door?Pairing audit row?Substitution handlingSuitable for which role
Printed name-tag stickerLane 1, Lane 2, Lane 3, Lane 4yes — visually worn during visityes — sticker ID noted in Registryrefused at door; new Registry row requiredContractor, Vendor, Inspector
Single-use card (Lane 2)Lane 2 onlyyes — card visibly carried, surrendered at exityes — card ID and visit end-time notedrefused at door; new card issuedContractor, Vendor
Mobile-app credential under issuer's account (Lane 3)Lane 3 only, on supported modelspartial — phone screen shows holder's name if askedyes — app credential ID and timestamps in app logissuer revokes app credential and re-issues in own nameContractor on app-connected models
Mechanical key cut to a sub-custody keyway (Lane 4)Lane 4 onlypartial — physical possession is the pairingyes — Key Custody Register entrykey return is the substitution firewallStanding-access contractors, on-call agents

Usage note for the pairing artifact table. Each row is a capture item; the property chooses one artifact per role per door class, and the choice is recorded in the Door Register alongside the lane choice in Part I.

Part IV — End-of-Lease Closure and Surrender Clauses

A lease ends. So must every temporary credential issued under it. These clauses govern the surrender.

Clause 21 (Lease-End Credential Closure). At the lease-end instant stated in the tenancy agreement, every credential issued under that lease — Lane 1 PINs, Lane 2 cards, Lane 3 mobile-app credentials, Lane 4 mechanical keys — is revoked. Revocation is logged in the Registry with the row Revoked at lease end — Date Time and the underlying tenancy reference. Revocation is not a soft suggestion; the credential fails at the lock from the next moment forward.

Usage note. Whether the model supports atomic credential revocation — does deleting the tenant's user slot also delete their issued guests' sub-slots, or are those sub-slots separate? — is the second most important capability to verify in writing before signing this clause.

Clause 22 (Mechanical Key Return and Keyway Custody). Lane 4 mechanical keys issued under the lease are physically returned to the Issuer at lease-end walk-through, signed for in the Key Custody Register, and held under keyway control. A key not returned at walk-through is treated as a failed surrender; the cylinder is re-pinned at the landlord's discretion and the cost is documented. The keyway record (which cylinder is on which key) is preserved across re-pin cycles so the audit trail is unbroken.

Usage note. Mechanical keys are the credential that does not expire on its own. They are also the credential most often "handed to a friend" between lease end and cylinder re-pin. The clause makes the surrender a physical event, witnessed and signed for, with the cylinder re-pin as the enforcement teeth.

Clause 23 (Sub-Credential Sweep). Before lease-end walk-through, the Issuer sweeps the Registry for any secondary or standing-access credentials issued to persons associated with the outgoing tenant (their guests, their sub-renter's workers, their standing-access agents). Each is individually logged as revoked under the lease-end closure. Standing-access credentials that the incoming tenant has not re-authorised in writing are revoked unconditionally.

Usage note. Sub-credentials are the long tail. A tenant who leaves behind a working standing-access credential for the building's cleaner has, in effect, donated access to the next tenant. The sweep closes that loophole at the moment of handover, not at the moment of dispute.

Clause 24 (No Grace Period). A tenant does not hold a working credential after lease-end. Walk-through windows and key-return appointments are scheduled before lease-end, never after. A tenant who has not returned keys by lease-end is in failed surrender under Clause 22 and the cylinder re-pin clause attaches. A tenant who disputes the lease-end date does not keep their credential during the dispute; the dispute is governed by Part V and the credential is revoked.

Usage note. The grace period is the kindest possible default and the most dangerous. A tenant with a working credential during a dispute is a tenant who can re-enter the property the landlord is preparing for the next tenant. The clause's posture is harsh on purpose: the dispute is about access, not about the credential.

Clause 25 (Handover Pack). The handover pack transferred to the incoming tenant contains: (a) the Registry rows active at handover, (b) the Door Register and lane declarations, (c) the Issuer Roster, (d) the Key Custody Register rows relevant to the incoming tenant's doors, (e) the dispute log entries relevant to those doors (Part V), and (f) the audit confirmation under Part VI for the handover window. The handover pack is signed by outgoing Issuer, incoming Issuer and incoming tenant.

Usage note. The handover pack is the document of evidence for the next dispute. A tenant who arrives to find a code that "doesn't work" needs to know whether it was never issued, was issued to the previous tenant, was standing-access, or is a model capability that has failed. The pack answers each of those questions in one read.

Clause 26 (Warranty and Defect Window at Lease End). A credential issued under the lease and not used during the lease is not a warranty claim. A lock that fails to recognise a valid PIN during the lease is a defect under tenancy and the defect must be logged at the time of failure, not at lease end. The Registry's audit rows are the evidence base for a defect claim; a tenant who has not logged audit rows during the lease has, under this handbook, no defect claim to bring at lease end.

Usage note. This is the end-of-lease warranty clause the brief asked for. It rewards the tenant who audits during the tenancy and disciplines the tenant who does not — because the alternative is a tenant who, having never checked that the code worked, demands a fix at handover for a problem that is not a problem. Whether the chosen model supports audit-row read-out by the tenant (rather than only by the Issuer) is a product-page question.

StepActionOwnerEvidence producedDefault window after lease-endFailure mode
T-7 daysSchedule walk-through and key-return appointmentIssuerCalendar entry, tenant acknowledgementN/Amissed appointment escalates to T-3 reminder
T-3 daysSweep Registry for sub-credentials and standing-accessIssuerSweep log, list of rows to revokeN/Amissed sweep escalates to walk-through step
T-0 (lease-end)Walk-through, key surrender, RV inspectionIssuer + TenantSigned Key Custody Register, walk-through notecredential revoked at T-0failed surrender triggers cylinder re-pin
T-0 to T+24 hHandover pack assembledIssuerPack with Registry / Door Register / Issuer Roster / Key Custody / Dispute Logpack ready by T+24 hdelayed pack escalates to next-day SLA
T+24 hHandover pack transmitted to incoming tenantIssuerTenant countersignatureN/Aunsigned pack triggers Part VI audit

Usage note for the surrender table. "T-0" is the lease-end instant. The table is a policy timetable; whether the underlying lock operations (revocation at T-0, sweep at T-3) are achievable by the chosen model on the day is a product-page question. On supported models, check the model’s published specification.

Part V — Dispute Handling Clauses

The four recurring disputes in a rental property are predictable: the credential did not work, the contractor entered without escort, the old tenant still has a code, the guest denied entry to a legitimate party. These clauses route each.

Clause 27 (The Four Disputes). This handbook recognises exactly four dispute categories: (a) Failed Credential — a credential that did not open the door at the moment of legitimate use; (b) Unescorted Entry — a person who entered a Class B door without a logged-in escort window under Clause 20; (c) Credential Survival — a credential that worked after the tenancy or standing-access window had ended; (d) Refused Entry — a person authorised under a valid credential who was refused entry by staff or another tenant. Each dispute is logged in the Dispute Log within 24 hours of occurrence, with the underlying Registry rows and audit-log entries referenced.

Usage note. The four-category list is closed. New categories are added by amendment to this handbook, not by ad-hoc practice. A property that treats "the key fell in the pool" as a fifth dispute is treating the handbook as decoration.

Clause 28 (Failed Credential Routing). A Failed Credential dispute is routed as follows: the tenant or guest produces (i) the credential as issued, (ii) the Registry row, (iii) the time of attempted use. The Issuer reads the audit log (where the lock supports read-out — check the model’s published specification) for the relevant time window. The dispute resolves to one of three findings: credential valid but lock failed (defect under Clause 26, lock serviced), credential valid but recipient entered it incorrectly (no defect, recipient counselled), credential not valid (window had lapsed or row was revoked). The finding is logged in the Dispute Log and the audit trail.

Usage note. The clause forces "the code never worked" onto the audit trail instead of letting it be a one-sided complaint.

Clause 29 (Unescorted Entry Routing). An Unescorted Entry dispute is routed as follows: the tenant or staff member who observed the entry produces (i) the time of observation, (ii) the name of the person observed (if known), (iii) the contractor work-order reference if any. The Issuer reviews the Registry and the audit log for that time window. The dispute resolves to one of three findings: contractor within escort window (no breach, contractor's escort window recorded), contractor outside escort window with no extension (breach, contractor's standing access revoked and firm notified), person not on credential at all (breach under Clause 6, treated as forced entry, authorities contacted under the property's policy).

Usage note. The clause forces the resolution onto the Registry and the audit log instead of resolving by anecdote.

Clause 30 (Credential Survival Routing). A Credential Survival dispute is routed as follows: the tenant or staff member who discovered the surviving credential produces (i) the credential as discovered, (ii) the time of discovery, (iii) the door on which it was tested. The Issuer reviews the revocation log (where the lock supports it — check the model’s published specification) for the relevant credential ID. The dispute resolves to one of three findings: credential was revoked and the lock has a fault (defect, lock serviced), credential was revoked but the issuer failed to revoke a sub-credential (breach under Clause 23, sweep repeated and standing access revoked), credential was never revoked (breach under Clause 6, every active credential audited under Part VI).

Usage note. Credential Survival is the dispute that proves the value of Clause 23's T-3 sweep. A property that does not sweep will discover the surviving credential six weeks into the new tenancy — precisely when the dispute is hardest to resolve.

Clause 31 (Refused Entry Routing). A Refused Entry dispute is routed as follows: the person refused entry produces (i) the credential as held, (ii) the work-order reference or booking reference, (iii) the name of the refusing party. The Issuer contacts the refusing party within one business hour. The dispute resolves to one of three findings: refusing party misread the credential's authorisation (no breach, refusing party counselled), credential was valid but staff had been told to refuse all credentials for that person (procedural breach, refusing party's authority reviewed), credential was not in fact valid (no breach, original issuer's records reviewed). The finding is logged in the Dispute Log.

Usage note. The clause forces the resolution off the doorstep and onto the Dispute Log.

Dispute categoryFirst reviewerTime to first responseEvidence requiredResolution findingAuthority to bind the property
Failed CredentialIssuer4 business hoursRegistry row + time + audit log (where supported)valid-lock-failed / valid-recipient-error / not-validyes — for credential re-issuance
Unescorted EntryIssuer + landlord2 business hoursobservation note + audit log (where supported)within-window / outside-window / no-credentialyes — for contractor standing access
Credential SurvivalIssuer + landlord4 business hoursdiscovered credential + revocation log + audit logrevoked-but-fault / revoked-but-sub-credential-not / never-revokedyes — for credential sweep and lock service
Refused EntryIssuer + staff lead1 business hourheld credential + refusing party's namestaff-misread / procedural / not-validno — Refused Entry findings do not bind the property without landlord countersignature

Usage note for the dispute routing table. The "Authority to bind the property" column matters. A Failed Credential finding that says "lock failed" is an admission of defect and obliges the landlord to service. A Refused Entry finding is rarely an admission of anything by itself and therefore does not bind the landlord without a countersignature. This is the difference between a routing table and a ruling table.

Part VI — Audit, Breach and Change Control Clauses

The handbook has to outlive the tenant who wrote it.

Clause 32 (Quarterly Audit). Every Quarter, an audit is performed: every Registry row is reviewed against the lock's active credential list (where the lock supports read-out — check the model’s published specification); every active credential has a Registry row; every Registry row has an active credential or a revocation reason; every door class is consistent with the Door Register; every standing-access credential has been re-issued within its 30-day window. Audit findings are logged in the Audit Log and any breach is routed to Clause 33.

Usage note. The audit is the negative check: it verifies that what should not be, is not. The clause works only if the underlying lock supports credential read-out; this is the third major capability to verify in writing before signing.

Clause 33 (Breach Log). Every breach — every Clause 6 finding, every Clause 29 finding outside-window, every Clause 30 finding never-revoked — is logged in the Breach Log with: the date, the underlying Registry rows, the parties named, the resolution step taken, the time to resolution, and the recurrence flag (first, second, third or higher). A third-recurrence breach in any 12-month window triggers a handbook amendment under Clause 34.

Usage note. The recurrence flag is the early-warning system. A property that has its third Unescorted Entry breach in a year is not having a run of bad luck; it has a Clause 20 problem.

Clause 34 (Handbook Change Control). This handbook is amended only by written change request, seconded by landlord / property owner and reviewed by Issuer Roster. Amendments are numbered sequentially (Amendment 1, Amendment 2, …) and dated. Every amendment is transmitted to every current tenant within N days of signature. No oral amendment is valid; no retroactive amendment is valid.

Usage note. A handbook that can be amended by text message is a handbook in name only. The clause forces amendment into the document trail.

Part VII — Hardware Reconciliation

The clauses above lean on lock capabilities. None of those capabilities is assumed; each is a capture item to verify against the model’s published specification or in writing with the supplier before the clause is signed into a real property document. The SLK-9936S hotel-lock block is reproduced below once, as a granularity yardstick — what a finished spec block looks like, not as a portable specification. The 9936S is a hotel door lock and does not enter the residential rental regime; none of its numbers port to a rental front door. Where a rental property is choosing between keypad, RFID, mobile-app or mechanical-key models, each capability cell is a per-model question.

Capability this handbook leans onWhy the clause needs itProduct page questionWhat to ask the supplier if the page is silent
Per-credential expiry windowClauses 7, 8, 9, 10, 13, 14, 21Does this model support a per-credential start instant and end instant?"Show me in the admin UI where the validity window is set for a single PIN or card."
Atomic credential revocationClauses 12, 21, 23Deleting the tenant's user slot — does it also delete the issued sub-credentials?"Walk me through deleting a tenant's account and tell me what happens to the guest codes under it."
Audit log existence and capacityClauses 6, 28, 29, 30, 32Does the lock record events? What is the upper limit on records? How is the log read out?"How many events does the on-device log hold before it rolls over, and is the log downloadable?"
Mobile-app issuance lane (Lane 3)Clauses 5, 7, 11On supported models, check the model’s published specification. Which app lane does the model use — TTLock, Tuya, Doodle, or other?"Is issuance from the app done through TTLock, Tuya, Doodle, or a different stack? Confirm the lane for this exact SKU."
Mechanical override keywayClauses 3, 22Does the model include a mechanical key? Is the keyway a standard or proprietary cylinder?"What is the keyway — is it a standard profile I can re-pin at a local locksmith, or proprietary?"
Credential read-out by tenant vs only by IssuerClauses 26, 28, 32Can the tenant read their own audit log, or only the Issuer?"Show me the user-side view of the audit log for one of my tenants."
Door-thickness fitevery Class A and Class B installationWhat is the door-thickness range for this model?"Confirm the door-thickness range for the exact SKU; my doors are N mm."
Power behaviour and credentials retentionClauses 21, 28, 32On battery replacement, are active credentials retained?"Walk me through a battery swap. Are PINs, cards and app pairings retained?"

Usage note for the capability map. Each row is a question, not an answer. The table is the document the property takes to the supplier at quotation; the property does not sign a clause until each cell has been answered in writing. The first-party format ruler for the depth of a finished spec block is the product-page-documented SLK-9936S block:

SLK-9936S spec block — first-party format ruler (not portable to residential rentals). Door thickness 36–100 mm · RFID Mifare 1 @ 13.56 MHz · read distance 0–5 cm · read time < 0.25 s · power 4 × AA · battery operating cycles > 15,000 · audit/event records up to 1,000 · 5-pin cylinder · 3-point latch · stainless steel + alloy body · multiple finish options · mechanical emergency access · multilingual management software · standalone or centralized database modes · positioned for 1–5 star hotels.

This block is reproduced once for granularity comparison only. The 9936S is a hotel door lock; its numbers do not enter a residential rental decision. Where the rental property needs an audit-record capacity of 1,000 events, the question to ask the chosen residential model is "what is the on-device event-record capacity, and how is the log read out" — not "does the residential model match the 9936S numbers." Every per-model spec a rental property commits to is confirmed on the product page of that specific residential SKU.

Adoption Order

The handbook is adopted in five passes; each pass produces a written artefact:

PassWhat is writtenOwnerPass produces
1. Registry scaffoldPopulation Registry template, Door Register template, Issuer Roster, Lane declarationsIssuerempty-but-complete Registers
2. Door surveyevery door assigned to Class A, B, or C; every Class B door's lane declaredIssuer + landlordsigned Door Register
3. Window matrixevery role × door class pair assigned a default window per Clauses 7, 8Issuersigned Window Matrix
4. Pairing artefactsevery contractor and standing-access role assigned a pairing artefact per Clauses 15–20Issuersigned Pairing Register
5. Capability mapevery capability cell in Part VII answered against the chosen model(s)Issuer + landlordsigned Capability Map

Adoption order matters. A property that adopts the Capability Map before the Window Matrix is choosing hardware first and writing policy around the hardware; the policy will always be weaker than the hardware's limitations. A property that adopts the Window Matrix before the Capability Map is choosing policy first and discovering, at the capability step, what the chosen model can and cannot enforce.

Illustrative Scenario

Consider a 24-unit rental block, twelve long-tenancy and twelve short-stay, with one staffed concierge, two Class B service risers, one Class C common entrance, and a shared parcel room. The landlord has just taken over from a previous operator who left four open-ended "cleaner" codes and two unreturned mechanical keys. The new operator adopts this handbook.

Pass 1 produces an empty Population Registry. Pass 2 classifies the 24 tenant-front doors as Class A, the two service risers as Class B, the common entrance as Class C, and the parcel room as Class B. Pass 3 sets the matrix so long-tenancy guests receive Lane 1 PIN windows sized to the stay (Clauses 7–8), short-stay guests receive Lane 3 mobile-app windows on supported models with Lane 1 PIN fallback, contractors receive Lane 2 day-pass tokens with unit-list annotations (Clause 19), inspectors receive warrant-window windows in writing. Pass 4 assigns printed name-tag stickers to every contractor role (Clause 16), single-use cards to parcel couriers, and refuses substitution at the door (Clause 17). Pass 5 walks the Capability Map against the property's chosen keypad, RFID, mobile-app and mechanical-key models and finds that two of the four models do not support per-credential expiry windows — those two are not adopted at any Class A door.

In the first quarter after adoption three disputes arise: a Failed Credential (Clause 27a) resolved under Clause 28 as a valid-recipient-error finding; an Unescorted Entry (Clause 27b) resolved under Clause 29 as an outside-window finding with the contractor's standing access revoked under Clause 33; and a Credential Survival (Clause 27c) resolved under Clause 30 as a revoked-but-sub-credential-not finding with the T-3 sweep repeated. The fourth category — Refused Entry — does not arise. The Quarter 2 Audit Log confirms zero standing-access credentials outside the Standing Access Register. The Block now runs on a written policy, not on text messages.

This is an illustrative scenario, not a customer story, and the configuration choices it describes are one configuration that satisfies the handbook — not the only one. A property with a different mix of door classes, a different staffing posture, or a different lane availability will arrive at a different configuration that also satisfies the handbook.

Where This Handbook Stops

Three things this handbook does not do:

  • It does not specify which model to buy. The Capability Map in Part VII is the procurement worksheet the property fills in against the property's chosen models. The choice of model is downstream of the policy.
  • It does not cover the guest-side issuance workflow. That workflow lives in Smart Lock Guest Access for Rentals, which pairs with this handbook on the guest-credential side and refers back to it on the policy side.
  • It does not cover emergency access during the lease. Emergency access — lock failure, lockout, fire-service entry — is its own policy and lives in Smart Lock Emergency Access for Rentals, which pairs with this handbook on the crisis side and refers back to it on the credential-disclosure side.

For the broader credential-method comparison — temporary PIN codes versus IC cards versus fingerprint versus mechanical keyboxes on a per-stay turnover calendar — see Smart Locks for Short-Term Rentals. For the long-tenancy counterpart, where a credential has to survive a decade rather than a calendar, see Smart Locks for Long-Term Rentals.

Closing

A temporary-access policy is not a feature. It is the document the landlord, the tenant, the contractor and the inspector all reach for when the door does the wrong thing. The clauses above are written to be lifted into a property's house rules, with the bracketed fields substituted and the Capability Map answered against the property's chosen lock models. Every per-model capability cell is confirmed on the product page or in writing with the supplier before the clause is signed.

Request a quote to receive a capability map against your chosen lock models, or order samples to test the Clause 7 and Clause 21 capability questions against hardware before the policy is signed into your house rules.

Twój koszyk
Twoje doświadczenie na tej stronie zostanie poprawione dzięki zezwoleniu na pliki cookie Polityka plików cookie
Chat on WhatsApp