Maintenance access for rentals as a work-order workflow: door zoning, per-trade windowed credentials, four audit-log questions and a refusal ladder.

Publisert tidligere: jun 30, 2025

Smart Lock Maintenance Access for Rentals

Smart Lock Maintenance Access for Rentals

A working transcript, not a feature pitch. What follows is a real-shape conversation between a head cleaner for a small rental operation — she manages the cleaning crew, the scheduled trade visits, the in-and-out between tenancies — and an application engineer at a smart-lock factory. The setting is an office; the subject is how to issue trade access to a unit, a corridor, or a plant door without handing the building over.

The reason this conversation exists in writing: most product pages describe the lock. Almost none describe how a manager reconciles "I need the plumber in flat 4B at 14:00" with "the tenant upstairs is on the couch and their storage closet is not a service area" and "next Tuesday's gas inspection needs a paper trail that survives the regulator asking." The head cleaner's questions are the questions a buyer faces; the engineer's answers are framed against a 79-model catalog that includes a hotel line (24 hotel locks), a fingerprint line (37 models), a keypad line (18 models), an RFID line (9 models), an outdoor line (10 models), a face line (6 models), a cabinet line (6 models), a glass line (3 models), and a camera/4G line (3 models). Locks read as a vertical. Maintenance access is described as a workflow. They meet rarely enough that the buyer-facing translation matters.

The scheduled branch, answered before the first exchange

Direct answer, before the dialogue does the work. Smart lock maintenance access for rentals is the practice of issuing per-trade, per-door, per-window credentials to a contractor or cleaning crew — typically a time-bounded PIN, a card enrolled for the work order, or a fingerprint enrolled for the recurring crew — so that the door opens only for the named scope, the named window, and the named reason, while tenant-only zones (private storage, bedroom, in-unit safe) stay on a different credential the trade never sees. On models with audit logging — check the model’s published specification — each entry produces a record that names who, when, which door; the buffer depth and the export path are per-model facts you verify before you rely on the paper trail. Sibling documents own adjacent territory: content 320 governs the plant-room side of maintenance access for residential buildings (riser/boiler/electrical); content 326 governs the broader access-management policy for rental portfolios (who holds what credential, when, on which schedule); content 333 governs the emergency branch of rental access (when the credential chain breaks and the trade must enter now). This document is the scheduled, non-emergency, on-a-known-work-order branch.

FieldEntry
Applies toRental units during scheduled maintenance, common-area service corridors, plant rooms shared with residential floors, contractor escort windows on a single building
Does NOT apply toPlant-room standing access (see content 320); broad rental access-management policy (see content 326); emergency-only access with no work order (see content 333); short-term rental per-stay turnover (see content 308)
Document ownerHead cleaner / facilities lead / junior property manager under explicit supervision
Review cadencePer work order (entry/exit) + monthly reconciliation; per-incident log review
Hardware scopeBattery-powered smart locks from a 79-model catalog; no field wiring assumed; mix of keypad, card, fingerprint, and app/Bluetooth lanes

How the transcript is built: questions carry the structure, annotations carry the verification

One word in the form factor itself: this article is an annotated dialogue. The questions carry the structure. The annotations between exchanges name what is really being asked and how to verify the answer on a product page or in a work-order template before the buyer commits. The head cleaner speaks as the buyer's voice; the engineer speaks as the factory's voice. Both voices are honest about the limits of what a lock can do, and about the parts that have to be a building policy, not a hardware feature.

Setting up the room

The cleaner runs a 96-unit rental block on a rolling schedule. Two of her days a week are trade days — Tuesday and Thursday — when plumbers, gas inspectors, painters, and a single carpenter come through on pre-booked windows. Her standing problem: tenants do not want strangers in the flat. The standing temptation: hand the tradesperson a master key for the day and trust the trade. She does not trust the trade. She has spent ten years not trusting the trade, and her insurer and her local authority have asked, separately and jointly, to see who opened which door when. Her software is a spreadsheet and a key cabinet. Her upgrade question: can a smart lock give her per-trade, per-window, per-door access that she can revoke the moment the job is done — without buying an enterprise platform she does not need?

The engineer sits across. He sells the lock, not the platform. His first sentence is the one most lock sellers skip, and he will not skip it.

What's really being asked / verify by. The buyer's question is not "which lock do you sell?" It is "what does the lock do that my key cabinet cannot, and what does it do that I have to keep doing the old way?" The second question is the harder one. A smart lock changes issuance cost and audit visibility; it does not change who decides what scope a contractor is allowed to enter. That decision is a building policy, and the lock can either enforce it (by being told which credential opens which door and when) or expose it (by being silent and printing the same ring of yellow 2021 master keys the building was running before).

The engineer's first move is not a product name. It is a four-zone classification, drawn on the room's whiteboard.

Exchange 1 — Classify every door before you classify any lock

Cleaner: "I'll start with the easy one. The unit door is a tenant's home. I have to get in for inspections. I don't want to ask the tenant to be home, because that costs me a tenant visit. What's the smallest credential change I can make that still proves who came in?"

Engineer: "Smallest is dangerous. Let's classify first. There are four zones in a rental block that a maintenance workflow has to think about separately, and one of them — the unit door during a work order — is the zone every shortcut fails on. The four are: tenant-only inside the unit, the unit door itself during a scheduled window, the shared service spaces between units (corridor linen closets, refuse rooms, bike stores, the lobby plant), and the building plant (riser, boiler, electrical room). Today, your key cabinet gives every trade a key that opens all four. The audit trail on your printer shows the same line five times. The lock has to change one of those at a time, not all four."

What's really being asked / verify by. A work-order-driven lock spec is not "tenant locks the door; the trade has a key." It is "for the duration of this work order, the unit door accepts a credential the trade holds, and rejects every other credential; the tenant's daily credential is paused, not deleted; the inside-the-unit doors the tenant keeps private (their storage closet, a private safe-room if the building has one, a shared stair that loops past the kitchen) stay on the tenant's lane alone." That is three policies, not one. Confirm before any purchase that the model you are shortlisting supports a temporary PIN or a time-bounded credential — check the model’s published specification — and that "temporary" means it expires by itself, not "you have to remember to delete it."

ZoneWhat it isWhose credential, normallyWhat changes for a work orderAudit-log expectation
Tenant-only inside unitBedroom, walk-in closet, private storage, in-unit safeTenant daily credentialNothing. Trade never gets a credential that works here.None expected; lock is not present, or is present and locked-out from trade lane
Unit door during windowThe flat's main door, on the day and hour of the work orderTenant daily credential (paused)Trade lane receives a windowed credential. Tenant lane is suspended, not erased, for the same door only.On models with audit logging — check the model’s published specification — every open is recorded with credential ID + timestamp
Shared service spacesLinen closet, refuse room, bike store, lobby plant, mail roomBuilding staff credentialTrade lane works the same as building staff lane for that window, then expires.On models with audit logging — check the model’s published specification
Building plantRiser, boiler, electrical room, sub-meter vaultSpecialist named credential onlyTrade receives named credential scoped to one door class, never blanketOn models with audit logging — check the model’s published specification; records retained per local regulatory regime

What's really being asked / verify by. Three per-model facts govern the four-zone table above: (1) does the model accept a temporary PIN that expires by itself, and what is the maximum window it accepts; (2) what is the maximum number of distinct credentials the model holds simultaneously — fingerprint templates, PIN codes, cards, app accounts, mechanical-key overrides — because the four zones must fit on the same lock without the trade's windowed PIN clobbering the tenant's daily PIN; (3) what is the audit-record capacity, what gets recorded, and how records are read out — those three are not the same number, and all three are per-model. Check the model’s published specification before you commit.

Cleaner: "So the lock has to know about the zone classification, but the lock does not enforce it. I enforce it with what I enrol into the lock."

Engineer: "Yes. And that is the part no brochure will tell you. The lock is a faithful executor of whatever list of credentials you give it. The classification is yours."

Confirm by: A four-zone rule sheet, dated, signed off by the cleaner and the supervisor, attached to the work-order template. If the rule sheet does not exist, the lock is just a more expensive key cabinet. The rule sheet is the actual product.

Exchange 2 — What trade access actually needs (and what it does not)

Cleaner: "Tuesday is plumber day. He has three calls on the block — a leaking tank in 4B, a stop-tap replacement in 7C, a stack valve in the basement riser. He arrives at 09:00, finishes at 14:00. I want him in three doors, not the building. How do I say that in a lock?"

Engineer: "Three doors, three windows, three credential types if you want the audit trail to be readable. You say it as: a PIN good for 09:00–14:00 on door 4B only; a PIN good for 10:00–12:00 on door 7C only; a PIN good for 11:00–11:30 on door basement-riser only. On the standalone keypad models in our catalog, that is what 'temporary PIN with time window' means. Whether a specific keypad model supports a PIN with a window — and the maximum window it accepts — is per-product-page."

What's really being asked / verify by. "Multiple windows, one user, one door" is a credential-design question. It is not the same question as "one window, many users, one door" — which is the cleaning-crew question. It is not the same question as "one user, one window, many doors" — which is the all-day access question. Buyers sometimes treat these as the same. The lock treats them differently. The PIN table that holds the windows has to be sized for the busiest day in the rotation, not for the average. Confirm the per-lock credential capacity — the maximum number of distinct temporary PINs the lock can hold simultaneously — on the product page before you commit. Confirm whether "expired" means the PIN stops opening the door or whether the lock deletes the slot (freeing capacity for the next PIN); both behaviors exist and they differ between models.

Cleaner: "And if I want the auditor to see the difference between the plumber and the gas inspector on the same door?"

Engineer: "Then the credential must be distinct per trade, even if the window overlaps. The lock cannot infer 'plumber' from the act of opening a door. If you enrol one PIN per trade, the audit log says who; if you enrol one PIN per trade-per-door, the audit log says who and where; if you enrol one PIN per trade-per-door-per-day, the audit log says who and where and on which work order. The third is the one your regulator wants to see. The cost of that detail is the cost of three PIN slots per trade per day, and your busiest day is the sizing case."

Trade personaTypical windowDoors they touchCredential shape (recommended)Window discipline
Plumber09:00–14:00Unit 4B, basement riser (rare)One PIN per door per dayHard end at 14:00; PIN expires by itself
Gas inspector10:00–11:30Unit 7C only (one flat per visit)One PIN per door per visit; rotates per visitHard end at 11:30; PIN expires by itself
Painter08:00–17:00 across two daysUnit 2A onlyOne PIN valid for two consecutive day-windowsHard end at 17:00 day 2; trade lane expires
Electrician13:00–15:00Corridor service panel + 3F consumer unitTwo PINs (corridor + unit)Hard end at 15:00; corridor PIN expires; unit PIN expires
Cleaner (recurring)Monday and Thursday, 09:30–13:0012 unit doors across the rotationOne PIN per cleaner (not per day)Weekly expiry; renewed on Monday morning
Carpet fitter08:00–16:00 day onlyUnit 9DOne PIN, weekend windowExpires Friday at 18:00
Appliance delivery12:00–13:00 (single 60-min slot)Lobby + unit door onlyOne PIN, 60-minute windowHard end; slot booked in advance

What's really being asked / verify by. Six per-model facts carry the table above. (1) Maximum PIN length and minimum PIN length — both must be acceptable for a casual user typing under stress. (2) PIN reuse rule — most models forbid reusing the same PIN within the last N slots; confirm whether that N suits a per-day rotation. (3) Maximum number of distinct PINs the lock holds simultaneously — the sizing case. (4) Behaviour at expiry — door denies, slot remains, or slot auto-deletes. (5) Master-admin relationship — does the master code keep working while the temporary PIN is active. (6) Lockout on failed attempts — most models throttle after a number of wrong PINs; confirm whether the trade's first try from a stopped clock triggers that throttle. All six are per-model; all six are on the product page.

Cleaner: "And the master code? If the master code is the same across the block, I have the same problem I have today — one key, every door."

Engineer: "Then the master code is not the same across the block. One master per door, kept in a sealed envelope in the supervisor's safe, used only when the lock refuses every other credential. That is the mechanical fallback doctrine and it is not a feature, it is a design rule. The product page for the model you shortlist will say what the mechanical fallback is — most models in our catalog include a mechanical-key cylinder; some do not. Confirm mechanical fallback design on the product page before you rely on the override."

Exchange 3 — Audit logs: framed as the four questions the product page never gets asked at

Cleaner: "You keep saying 'check the model’s published specification.' Give me the four questions I should be asking, because right now I have no idea what to look for."

Engineer: "Four questions, in order. The first decides whether the rest of the conversation is worth having."

What's really being asked / verify by. Audit logging on a rental maintenance workflow is not a single feature. It is four independent capabilities, each of which may be present or absent on the specific model you shortlist. None of them can be inherited from a category description. All four must be answered on the product page before you commit. The four are recorded below as the table that anchors the rest of the article.

Audit-log question (on the product page, before quoting)What to askAcceptable answer shapeWhat to refuse
Q1. Does it record?"Does this model record an event each time a credential opens the door — any credential, including a time-bounded temporary PIN, including a master-code use?""Yes, every successful open is recorded; the lock's published capacity is N events.""We can tell you after install." / "We can connect it to a phone app." (the app is a transport, not the lock's record)
Q2. What is the buffer?"What is the maximum number of events the lock holds before the oldest event is overwritten?"A number, in the product specifications."It depends on traffic." / silence
Q3. What is the read-out path?"How are the records read out — phone app, dedicated PC software, a USB cable, an RFID card the manager brings to the door?"A named, documented method with the path from the lock to a file the manager owns."It just appears." / "We can show you on a video."
Q4. What is the record shape?"Does each record include a credential identifier (so the manager can tell plumber from inspector), a timestamp, a door identifier (so the manager can tell 4B from 7C)?"Yes to all three."Just dates." / "We don't say."

What's really being asked / verify by. The four questions above are independent. A lock can answer "yes" to Q1, "yes" to Q2 with a number, "no" to Q3 (no documented export path), and "no" to Q4 (records exist but are not credential-attributed). Each yes/no combination is a real product in the market. None of them is a "smart lock"; each is a smart lock with a specific audit posture. The product page is the only place this is written down. If the product page is silent, the answer is no.

Cleaner: "If the answer to Q1 is 'yes' and Q2 is '200', how do I know whether 200 is enough?"

Engineer: "You take your busiest day of trades, multiply by the number of working days you expect between reads, and you make sure the buffer is larger than that number. If your busiest day is twelve trade entries, and you read the log weekly, you need at least eighty-four slots. Most models buffer more. The point is not the buffer; the point is the cadence. The cadence you can run is the cadence the buffer permits."

What's really being asked / verify by. Buffer arithmetic is a property of the workflow, not of the lock. The lock commits a maximum; the workflow commits a cadence. Where the lock's maximum is smaller than the workflow's cadence, the oldest record is overwritten before the manager reads it. That is silent data loss. It is the failure mode that the audit log was supposed to prevent. Check the model’s published specification what the maximum is; run your arithmetic against your busiest week.

Cleaner: "And the hotel lock you sell — the 9936S — its product page says 'audit/event records up to 1,000.' That number is huge. Why isn't that the universal answer?"

Engineer: "That number belongs to that one hotel model. It is a hotel RFID lock. It does not enter a rental maintenance workflow. The number is large because the hotel's line of work is twenty-five nightly events per door for a hundred doors over a week, and the buffer is sized for the hotel's read cadence, with the management software pulling records nightly. The number is not portable. It tells you nothing about what a keypad model designed for residential doors holds. The number tells you, instead, what a finished spec block looks like — it has a number, it is in the published specifications, it is paired with a software path for read-out. That is the format you are looking for on the residential model you are actually buying. The number itself, leave it on the hotel lock's page."

What's really being asked / verify by. The 9936S spec block is invoked once, here, as a format ruler. It looks like this in the published specifications: 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. None of those numbers — door thickness, frequency, range, time, battery count, cycle count, record count, cylinder, latch, body, finish, software, positioning — is portable to a residential maintenance door. The block is a writing standard: it shows what a complete datasheet looks like. It does not show what a residential maintenance lock does. Confirm the residential model's actual specifications on the residential model's product page.

Cleaner: "So I take Q1 through Q4 to the product page for the model I am shortlisting, I write down the answers, and I treat silence as 'no.'"

Engineer: "Yes. And you date the page. Specs move; a record dated when you evaluated the model is the one that matters when the regulator asks."

Exchange 4 — The per-job temporary credential, end to end

Cleaner: "Walk me through one work order, end to end. Plumber in 4B on Tuesday 09:00–14:00. I want it from the moment the work order lands on my desk to the moment I tear up the page on Friday."

Engineer: "Six steps. Each has a paper output. The paper is what survives the regulator's visit; the lock is what survives the tenant's memory."

What's really being asked / verify by. "Per-job credential, end to end" is a workflow, not a hardware feature. The lock's job is steps 2–4. The building's job is steps 1, 5, and 6. The workflow is owned jointly. The lock has to be capable of steps 2–4; the building has to be willing to do steps 1, 5, and 6.

StepWho owns itWhat happensPaper output
1. Work order receivedCleaner's officeScope, door(s), window, trade name, contact, tenant notification logWork-order sheet, dated, with tenant signature or refusal noted
2. Credential issuedCleaner (or supervisor)A time-bounded PIN (or card, or fingerprint slot) enrolled into the named door for the named windowCredential register entry: door ID, trade name, window start, window end, credential ID
3. Trade entersTradeEnters PIN at the door; door admitsNone at the door; the lock's own memory records the entry (on models with audit logging — check the model’s published specification)
4. Trade exits and reportsTrade + cleanerTrade confirms completion; cleaner marks window closedTime-stamped completion note on the work-order sheet
5. Credential expiresThe lockThe PIN stops opening the door automatically at the window endNone — the lock enforces it; the cleaner does not have to remember
6. ReconciliationCleaner (Friday morning)Pulls the lock's memory; checks every recorded open against the work-order sheetReconciliation log, dated, signed

What's really being asked / verify by. Step 5 is the single most underrated feature in the conversation. A PIN that you have to remember to delete is a PIN you will forget to delete. The lock expiring the PIN on its own is what makes the workflow survivable. Check the model’s published specification that the model you shortlist supports a PIN whose expiry is set at issuance, not at deletion. If the model requires deletion-as-step, the workflow becomes "remember to delete" — which is the failure mode the lock was supposed to replace.

Cleaner: "And if the plumber is late, or early?"

Early: Half an hour late: the PIN is still valid; door admits. Two hours late: the PIN has expired; door denies. The cleaner trades at the door on the phone, not at the lock. The lock has done its job.

Cleaner: "And if the plumber comes back the next morning because the part did not arrive?"

Engineer: "Then you issue a new credential for a new window. The previous credential has already expired; the lock does not know it was the same person; you do not need it to. The new credential is a new work order; the work order is a new line in the credential register."

What's really being asked / verify by. "Re-issue on next-day work order" is the second-most underrated. It is what stops a permit where the cleaner "remembers" the previous PIN and re-uses it. The habit is a credential that lasts one work order; the rule is one work order, one credential.

Exchange 5 — Tenant-only zones: what stays private, and how the lock enforces it

Cleaner: "The tenant upstairs keeps a folding bike in a closet off the kitchen, and the landlord next door stores a folder of insurance papers in a drawer in the same flat. The plumber does not see either of those doors. How do I tell the lock that?"

Engineer: "Two ways, and they differ in what they cost the tenant."

What's really being asked / verify by. "Tenant-only zone" inside a rental unit is a category problem. The tenant's storage closet, the tenant's safe-room, the landlord's insurance drawer — three different relationships, three different lock postures. The lock on the unit door cannot distinguish them. The lock on the inside door can.

Tenant-only zoneWhat is privateWhose lockWhose credentialTrade sees it?
In-unit storage closetTenant's bike, suitcases, hobby kitA separate lock on the closet door, not on the unit doorTenant's daily credential only; never trade laneNo — the trade lane works the unit door only
In-unit safe-room (where present)Tenant's valuablesA separate lock on the safe-room doorTenant's daily credential + masterNo — the trade's windowed PIN does not open the safe-room door
Landlord storage drawerLease paperwork, spare keys, regulatory filesA separate lock on the drawer (or the drawer is outside the unit, e.g., the management office)Building staff credentialNo — the trade is not on the building-staff lane
Shared corridor linenMops, sheets, cleaning chemicalsA separate lock on the corridor closetBuilding staff + cleaner onlySometimes — confirm scope per work order

What's really being asked / verify by. The trade's windowed PIN is a credential that works one door (the unit door) for one window. It does not propagate to the storage closet or the safe-room because those are different locks on different credential lanes. The unit door's lock is the only lock the trade's PIN touches. If the inside-the-unit door is the same lock as the unit door (which is true of single-point locks on some interior doors), then the storage closet needs a separate physical lock — a cabinet lock, a small cam lock, an interior latch with its own key — and that is a hardware decision the building makes, not a credential one. The catalog includes a cabinet line of 6 models designed for exactly this kind of inside-the-unit interior lock. Confirm fit and mounting on the product page.

Cleaner: "So if I have to buy a second lock for the storage closet, I am adding hardware, not saving it."

Engineer: "You are. The saving is in the policy: the tenant knows the closet is theirs, the trade knows the closet is not theirs, and the auditor can verify it on the work-order sheet. The lock is the cheapest part of that conversation. The rule sheet is the expensive part."

Confirm by. A dated tenant-only zone register, kept with the work-order template. One row per unit. Three columns: inside-the-unit private lock (yes/no, what kind), trade-lane access (yes/no, which window), reason. The register is what survives the regulator's visit. The lock survives the tenant's memory. Both are needed.

Exchange 6 — The tenant-notification policy: when, what, how

Cleaner: "When do I have to tell the tenant the trade is coming?"

Engineer: "Tell them before the credential is issued, not after. Three times in writing, with the work-order ID visible."

What's really being asked / verify by. "Tenant notification" is a building policy and a regulatory regime. The lock has no opinion on it. The policy has three timing columns. What changes by regime is the minimum notice, the form of notice (written, in-person, recorded), and the consequence of refusal. None of those is a lock feature.

Notification stepWhenFormWhat it saysWho signs
Advance noticeAt least 48 hours before window opens (longer where local regime requires)Written, posted to door + emailed/texted to tenant's contact channelWork-order ID, trade name, scope, window, contact for refusalCleaner; copy filed
Same-day reminderMorning of the windowTexted or emailedTrade ETA, tenant option to be present, contact lineCleaner; copy filed
Post-visit noteWithin 24 hours of window closingPosted to door + emailedTrade name, time entered, time exited, what was done, any damage notedTenant or tenant's representative; copy filed

What's really being asked / verify by. Notification timing is regime-dependent. The local authority, the tenancy agreement, and the insurer's published standard together fix the minimum notice; the building policy can be stricter than any of them but not laxer. Confirm with the building's counsel and the tenancy agreement what the minimum is. The lock does not enforce notification. The lock's audit log is the receipt that the work happened, not that the tenant was told.

Cleaner: "And if the tenant refuses?"

Engineer: "Then the window does not open. The credential is not issued. The work order is rescheduled or escalated to the landlord's right of entry per the tenancy agreement. The lock does not enter a tenant's flat against the tenant's refusal. That is the building policy, not a hardware feature, and it pre-dates the smart lock by a hundred years."

Confirm by. The tenancy agreement, the insurer's terms, the local regime. The lock is silent on this question because the question is not a lock question. It is a tenancy question.

Exchange 7 — Boundary cases: scheduled maintenance, recurring crews, and the third-shift call-out

Cleaner: "Three more shapes I run into. The recurring cleaner who comes every Monday and Thursday. The quarterly fire-alarm test. The 23:00 emergency call-out because the tenant in 6A smells gas. What does the lock do differently for each?"

Engineer: "Three different credential shapes. The lock has to support all three."

Work shapeTradeWindowCredential shapeWhy
Recurring cleanerNamed person, fixed crewMonday 09:30–13:00, Thursday 09:30–13:00One PIN per cleaner, valid Monday + Thursday, expires on the Sunday after the rotation; renewed each quarterSame person every week, but the credential rotates so a leak (lost phone, copied PIN) self-expires
Quarterly testSpecialist contractorTuesday 08:00–16:00, once per quarterOne PIN per door, valid for the day-window, expires at 16:00; no rotation between quartersSame trade, infrequent, but the credential is still per-visit (not a standing one) so the auditor sees this quarter's visit
23:00 emergencyOn-call gas engineerUnknown duration, arrived on the nightEither a pre-arranged "emergency lane" PIN (issued at the start of the contract, valid 22:00–06:00 daily, expires after 90 days) OR a one-shot PIN issued by phone to the engineer at the doorSpeed matters; the credential is the one that admits in the dark without a key handover

What's really being asked / verify by. Three shapes, three credential rules. The recurring cleaner is the only one where the same person holds the same credential for more than a day. The quarterly test is the only one where the credential is per-visit but the visit is months in the future. The 23:00 emergency is the only one where the credential has to be issuable by phone, not at the lock. All three are per-model facts — check the model’s published specification whether the model supports the credential shape, what the maximum window is, and whether the PIN can be issued from an app (where "confirm app connectivity on the product page" applies, because app/Bluetooth lanes are model-specific in the catalog).

Important routing note. The 23:00 emergency lane belongs to a sibling document. Content 333 governs the emergency-access branch of rental access — when the credential chain breaks and the trade must enter now. What this article covers is the scheduled, non-emergency, work-order-driven branch. The boundary between the two is the work order: if a work order exists, you are here; if no work order exists and entry is forced, you are in 333. The same lock can serve both branches. The workflow is the difference.

Exchange 8 — The supervisor's standing question: what do I do when the lock refuses

flowchart TD
    A["22:30 on a Friday:\nthe lock refuses every credential"] --> B{"1 · Is the PIN current?\nwork-order window still open?"}
    B -- "expired" --> B1["Issue a new PIN\nfor the new window"]
    B -- "current" --> C{"2 · Is the PIN\nfor this door?"}
    C -- "wrong door" --> C1["Walk the desk\nto the correct door"]
    C -- "right door" --> D{"3 · Is the lock powered?\nbatteries in date · warning on?"}
    D -- "battery flat" --> D1["Replace batteries"]
    D -- "power ok" --> E{"4 · Does the master code\nopen the door?"}
    E -- "yes" --> F["Door admits\nmark it on the work-order sheet"]
    E -- "no" --> G{"5 · Mechanical override\nkey in the sealed envelope?"}
    G -- "yes" --> H["Door admits\noverride use logged on the WO sheet"]
    G -- "no" --> I["Vendor support:\nlock failure, not workflow failure"]

Cleaner: "Last question, and it is the one I get at 22:30 on a Friday. The lock refuses every credential. The plumber is at the door. The tenant is in the lobby. What do I do?"

Engineer: "Three answers, in order, before you reach for the override."

What's really being asked / verify by. "Lock refuses every credential" is a real failure mode. The right answer is not "use the master code" — it is three diagnostic checks, in order, each taking less than a minute. The master code is the fourth step, after the diagnosis. The fifth step is the mechanical override.

StepWhat to checkTimeIf yesIf no
1. Is the PIN current?Is the work-order window still open? Has the PIN expired?30 secondsContinueIssue a new PIN for the new window
2. Is the PIN on this door?Did the cleaner issue the PIN for 4B when the plumber is at 7C?30 secondsIssue the correct PINWalk the desk to the correct door
3. Is the lock powered?Are the batteries in their date? Is the low-battery warning on?60 secondsReplace batteriesContinue
4. Use the master codeDoes the master code open the door for the named supervisor?30 secondsDoor admits; mark on work-order sheetContinue
5. Mechanical overrideDoes the mechanical key open the lock? Is the key in the sealed envelope in the safe?60 secondsDoor admits; mechanical key use logged on work-order sheetVendor support: this is a lock failure, not a workflow failure

What's really being asked / verify by. The five-step ladder above is the rule that protects the building from the moment the lock refuses. Each step is less than a minute. Each step has a paper output. The paper is the work-order sheet, dated, signed, with the failure mode named. Check the model’s published specification what the lock's behaviour is at low battery, at master-code use, and at mechanical-override use. Check the model’s published specification what the lock's "low battery" warning is and how many openings remain after the warning.

Crucial scope rule. Mechanical override is the named fallback on most models in our catalog, including the hotel line (mechanical emergency access is a published feature on SLK-9936S). It is not a portable feature to every residential model. Confirm mechanical fallback design on the product page for the specific residential model you shortlist. The override design is a procurement decision, not a feature discovery at 22:30 on a Friday.

The realistic scenario — consider a 96-unit rental block with a Tuesday trade day

Consider a 96-unit rental block with a Tuesday trade day. A head cleaner runs the rotation. Tuesday is plumber + gas-inspector day. The block has four staircases and a basement riser. The cleaning crew is two people on Monday and Thursday. The carpet fitter arrives on the first Friday of every month for one unit. The gas engineer has a 23:00 emergency lane that expires every 90 days.

The Tuesday cycle runs like this. By Monday evening, the cleaner has the week's work orders in a folder — three plumber calls, one gas inspection, one quarterly fire-alarm test. She writes the work-order sheet for each. By Tuesday 08:30, she is at the office issuing PINs. Three PINs for the plumber (one per door, each windowed). One PIN for the gas inspector (one door, windowed). One PIN for the fire-alarm tester (corridor + riser, windowed). The PINs are enrolled in the locks. The lock's own memory records the entries as the trades arrive. The cleaner does not have to be at every door.

By Tuesday 14:00, all windows are closed. The PINs have expired on their own. The cleaner's Friday morning reconciliation pulls the lock memories (on models with audit logging — check the model’s published specification), reconciles every recorded open against the work-order sheet, signs the reconciliation log, and files it. The tenant upstairs is not aware a trade came through unless the work-order sheet names a scope that touched their unit. The regulator, who arrives on a date of their choosing, sees a paper trail that names a date, a door, a trade, a window, a credential ID.

That is what a 79-model catalog looks like when it is treated as a workflow. The hardware is the small part. The rule sheet is the large part. The lock is the enforcer. The cleaner is the issuer. The work-order sheet is the receipt. The product page is where you confirm the lock is capable of enforcing the rule.

What's really being asked / verify by. A work-order-driven lock spec on a 96-unit block is not a hardware story; it is a workflow story. The lock is capable if its capability is verified on the product page. The rule sheet is the rest. Check the model’s published specification what the model you shortlist supports. Then write the rule sheet. Then issue the first PIN. Then run the first Tuesday.

What this article does not solve, and where it routes

This article covers the scheduled, non-emergency, work-order-driven branch of trade access on a rental block. It is not the whole of access management. It is not the whole of maintenance access. It is the scheduled branch. The boundaries are explicit.

QuestionWhere it goes
The riser / boiler / electrical / sub-meter room — what lock posture, what credential posture?See content 320 — Smart Locks for Apartment Maintenance Rooms. That document governs plant-room standing access on residential buildings. The trade lane described in this article intersects plant rooms at the basement riser; the plant-room policies are in 320.
The broader rental access-management policy — who holds what credential, when, on which schedule, with what hierarchy?See content 326 — Smart Lock Access Management for Rentals. That document governs the access policy as a whole. This article governs the maintenance sub-policy; 326 governs the policy it sits inside.
The 23:00 emergency — when the credential chain breaks and the trade must enter now?See content 333 — Smart Lock Emergency Access for Rentals. That document governs the emergency branch with no work order. This article governs the scheduled branch; 333 governs the unscheduled.
The per-stay turnover — the four-credential arena for short-term rentals?See content 308 — Smart Locks for Short-Term Rentals. That document governs the per-stay credential arena (PIN, IC card, fingerprint, keybox). This article is rental-residential, not per-stay; the credential shapes differ.
The model choice — which lock, on which door, with which credential?Confirm on each product page before quoting. Per-model facts (door-fit range, credential capacity, audit-record capacity, temporary-PIN support, mechanical fallback design, app/Bluetooth connectivity) are not portable.

The five-link routing above is a contract with the buyer. Maintenance access on a rental is not one article; it is a small cluster. This article owns the scheduled branch. The siblings own the plant-room branch, the access-policy branch, the emergency branch, and the per-stay branch. Confirm per-model facts on each product page; the rule sheet is the rest.

Closing the dialogue, opening the work-order sheet

Cleaner: "I came in asking which lock to buy. I am leaving with a rule sheet, a credential register, a tenant-only zone register, a notification policy, a five-step refusal ladder, and a four-question product-page interrogation."

Engineer: "You are. The lock is on the order form. The rule sheet is on the office wall. The cheap one to write down is the rule sheet. The expensive one to write down is the rule sheet."

Confirm by. Four questions per model, on the product page, before quoting. One rule sheet per building. One credential register per work order. One tenant-only zone register per unit. One notification policy per tenancy. One five-step refusal ladder per supervisor. One reconciliation log per week. None of these is on the lock's product page. All of them are on the building's policy.

For a sample order built to your rule sheet — one lock per door, with the credential capacities you actually need on the lock that touches your busiest Tuesday — open /order-samples and tell the factory the rule sheet. For a quote that turns the rule sheet into a door schedule, open /request-a-quote and send the door schedule. For a catalogue of the 79 models in scope and the 18 keypad / 9 RFID / 24 hotel / 37 fingerprint / 10 outdoor models you can shortlist from, open /request-catalog and ask for the residential rental maintenance kit. For a deeper read on the plant-room branch, see smart locks for apartment maintenance rooms. For the broader access policy, see smart lock access management for rentals. For the emergency branch, see smart lock emergency access for rentals.

The lock is the easy half. The rule sheet is the part that survives the regulator's visit. The rule sheet is what you write next.

Handlekurven din
Din opplevelse på dette nettstedet forbedres ved å tillate informasjonskapsler. Informasjonskapselpolicy
Chat on WhatsApp