Smart locks for apartment renovation projects are an occupied-cutover programme, not a hardware swap: a staged timeline that runs from notice templates

게시일: 9월 09, 2026

Smart Locks for Apartment Renovation Projects

Smart Locks for Apartment Renovation Projects

Smart locks for apartment renovation projects are an occupied-cutover programme, not a hardware swap: a staged timeline that runs from notice templates through weekend swap windows to a hard old-credential decommission date and a final master-key elimination step. The buildings in scope are occupied residential blocks — usually 1980s walk-ups, early-1990s mid-rises, and the rarer 2000s tower where a refurbishment finally justifies the lock upgrade. The work is conducted with tenants in residence, lease contracts in force, and a keying hierarchy that has been quietly compounding for decades. The programme's job is to retire that hierarchy honestly without locking anyone out, leaving anyone with a credential that no longer works on the door in front of them, or producing a compliance gap the next tenancy tribunal will name.

This article is the cutover programme. It is deliberately distinct from the install-side retrofit lens in Smart Lock Retrofit for Apartment Buildings — that article is about the physical decision of fitting a new lock to an existing door; this one is about the human and credential decision of fitting a new lock to an existing building while people still live there. It is also distinct from the after-handover operations playbook in Smart Locks for Apartment Operators, which takes the building on day one of the new locks and never looks back. The renovation timeline sits between pre-construction specification and steady-state operations; the buyer-guide to selection logic lives at Smart Locks for Apartment Buildings: Buyer Guide, and the new-build spec pack for a different kind of cutover lives at Smart Locks for New Apartment Construction. What follows assumes the lock has been selected, the renovation has been confirmed, and the team is asking a different question: how do we get from the keys in tenants' pockets today to the credentials we want in their pockets next quarter, without anyone losing access to their own home?

The illustrative scenario running through the article is the kind of building this article is really about: a 72-unit 1986-vintage walk-up, six storeys, two staircores, original master-keyed cylinders on every unit door, mid-life refurbishment covering risers, balconies, common-area finishes, and a lock replacement that has been deferred twice. Names are placeholder; the friction points are real.

Why a Refurbishment Lock Cutover Is Not a Hardware Event

A hardware swap is a half-day on each door. A renovation cutover is not. The doors carry years of mechanical-key compromise — a maintenance team with spare keys, contractors holding masters from previous works, former tenants named on an old cylinder log, an insurance position written against a keying hierarchy about to be retired.

Four forces make the cutover irreducible to an install:

The legacy key inventory is invisible until you ask. Every occupied block carries a shadow population: tenant copies, household spares with relatives, maintenance's labelled set, unreturned former-tenant keys, contractors' masters from prior works. None of these appear on lock spec sheets; the building learns about them when one turns up at the wrong door on the wrong day. The cutover must surface that population on paper before any hardware is touched.

Tenants have a relationship with the keys in their pocket. A nine-year tenant has a key on a hook, a key in a handbag, a key with their mother-in-law, a key lent to a house-sitter. Telling them the key is being replaced is a household interruption, not a procurement notice. The cutover designs that interruption so every copy is replaced inside the right window without the household hearing the change as a tenancy change.

The keying hierarchy outlives the project plan. Older blocks usually carry at least two masters and a sub-master in the wild — building master, maintenance master, sometimes an estate master. New cylinders are the visible half; retiring the masters honestly is the half that decides whether the cutover delivers what the refurbishment promised.

Notice, schedules and statutory windows vary by jurisdiction. Some require written notice before any lock change, or a specific notice period before keys are retired, or a documented override path the landlord retains across the cutover. The article names what must be confirmed with counsel; it does not assert the answers.

The shape of the work — about ten weeks end to end, six to ten occupied weekends of physical work, and a thirty-day settle-in after the last weekend — is what order-side conversations at our factory see most often. Shorter than ten weeks and the credential ledger is left with holes; longer than ten weeks and the operations team stops believing the cutover will finish.

The Cutover Stage Map

The ten weeks of the cutover are eight stage gates plus two settle-in windows. Each stage has an opening condition, an exit artefact, and one question the building has to be able to answer before the next stage begins. The table is the spine of the article; the sections that follow are one row of it.

StageWindowOpening conditionExit artefactQuestion it answers for the building
S1 — Legacy credential auditT-12 to T-8 weeksRenovation scope locks the lock-replacement lineInventory of every credential in the wild: tenant keys, landlord master, maintenance master, contractor set, former-tenant set, override keys; decommission date proposed per populationWhat is "the wild" we are retiring?
S2 — Cutover plan draftT-8 to T-6 weeksLegacy inventory complete; new-lock shortlist approved by operationsWritten cutover plan: weekend windows, pilot scope, refusal protocol, rollback path, master-key retirement dateHow do we run the cutover without an incident?
S3 — Notice templates approvedT-6 to T-4 weeksCutover plan signed; counsel consulted on notice wording and statutory periodsNotice templates approved for four audiences (tenants, on-site staff, contractors, owners' corporation); refusal-register and complaint paths publishedWhat will every audience be told, by whom, when?
S4 — Notice issuedT-4 to T-2 weeksTemplates approved; install schedule agreed per weekendFirst notice delivered to every audience; second reminder scheduled; refusal register openedHas everyone been told in time to plan around the weekend?
S5 — Pilot weekend swapT-2 to T-1 weeksNotices acknowledged; pilot scope signed (two units, one staircore, one common door)Pilot report signed by operations and refurbishment lead; lessons captured; per-wave plan updatedDoes the chosen swap pattern actually work on a real weekend?
S6 — Rollout weekend wavesT-1 week to T+0 weeksPilot signed; per-wave plan published; standby installer rota confirmedEach weekend wave installs on its doors; per-wave handover log signed; per-wave credential change log openedAre we still on the cutover plan, wave by wave?
S7 — Old-credential decommissionT+7 to T+14 days after each waveWave handover log signed; legacy-credential inventory page updatedCutover date met for that wave's doors; legacy credential is dead on its door by the documented date and timeHas the old credential actually stopped working?
S8 — Master-key eliminationT+14 days after final waveAll unit and common-door waves complete; master-key inventory confirmedPhysical master-key surrender, recorded destruction, mechanical-key cylinder re-pin/replace decision signed, post-cutover auditIs the legacy keying hierarchy retired, on paper and on the door?
Settle-in — Issue and anomaly windowT+15 to T+30 daysMaster-key elimination signed; per-door audit completeAnomaly log closed or escalated; credential ledger reconciled with tenant roster; refurbishment lock cutover report signedDid the new credential ledger match the people on the lease?

Each stage is one or two weeks of calendar time and produces one artefact the next stage cannot start without. Skipping a stage costs more time than it saves.

S1 — Legacy Credential Audit (T-12 to T-8 Weeks)

The first stage is not about new locks. It is about the credentials the new locks replace, because every credential the cutover ignores today surfaces on day six. The audit is paper-first; the doors are not touched yet.

The audit has five non-negotiable columns: Population (current tenant, former tenant, landlord staff, maintenance contractor, refurbishment contractor, owners' corporation, on-call emergency holder); Credential class (mechanical key, master key, sub-master, PIN, card or fob, fingerprint template, app account, override key); Quantity in the wild (conservative estimate — logs that say "3 copies" usually mean 4 to 6); Holder of record (name on file); Proposed decommission date (the cutover date).

PopulationCredential classQuantity in the wildHolder of recordProposed decommission
Current tenantMechanical unit-door key (per-tenant)One per unit + 0–3 spare copies held by householdLeaseholder on fileCutover date of the relevant weekend wave
Former tenantMechanical unit-door key (unreturned)Estimate from un-returned-key logLast known address on fileCutover date of the relevant weekend wave (cylinder re-pin executed)
Maintenance contractorMechanical master or grand masterPer contractor contract; one set minimumMaintenance leadSurrender on S8 day + documented destruction
Landlord/agentBuilding master + common-door sub-mastersPer key-issuing log; conservatively 4–8 sets over a building's lifeLandlord or managing agentSurrender on S8 day + documented destruction
Refurbishment contractorMechanical master or grand master issued for the worksPer contract; at least one set per contractor on the projectRefurbishment project leadSurrender on contract-end + documented destruction
Owners' corporation / strataCommon-area master(s)Per key-issuing logBuilding committee secretarySurrender on S8 day + documented destruction
On-call emergency holderOverride key or master held by named individualPer emergency protocol; usually one set held off-siteNamed holder in protocolSurrender on protocol-renewal date
App/Bluetooth adminApp account with admin role on the (legacy) doorOne per previous admin; sometimes inherited from prior vendorPrior admin contactRevoked on first day of cutover

Three audit rules, practical not procedural:

Quantities are conservative estimates. A log that says "3 copies" usually means 4 to 6 in the wild. The decommission date is set against the conservative figure; a door with five copies the building only knows about three of is a door whose decommission date has to allow for the unknown copies.

The audit ends with a decommission date per credential, not a strategy per door. The audit sets a date per credential so the cutover plan can build a calendar; the plan enforces that date on the door.

The audit is the only stage where the building learns about the shadow population. Once the weekend waves begin, the shadow surfaces as angry calls ("my key stopped working and I never got a notice"). Every shadow credential caught at audit is an angry call avoided at swap. The cost of audit rigour is money spent on a ledger; the cost of audit slack is a tenant whose key no longer opens their own door on a Sunday afternoon.

S2 — Cutover Plan Draft (T-8 to T-6 Weeks)

The cutover plan is the document operations, the refurbishment lead, the contractor, and the residents' notice all read from. It is not the supplier's quote or the renovation's lock schedule; it is a one-off paper that ties weekend work to the audit's decommission dates.

The plan has eight short sections, each a translation of the audit, lock shortlist, and construction calendar into a per-weekend question:

Weekend window design. Every physical intervention fits a weekend — Saturday morning to Sunday evening — with a hard rule: every door is operable on Monday morning. A weekend that leaves a tenant locked out Monday is a roll-back, not a weekend. The plan names the windows, doors in scope per window, the Saturday-night standby rota, and the rollback procedure if a door fails to commission.

Per-wave door list. Waves of 8 to 14 units plus 1 to 3 common doors — the size one team can finish by Sunday afternoon with the building's other trades still running. The list names every door, every credential class, and the audit reference for the credential dying on that door's weekend.

Pilot scope. First weekend: two units and one common door, run on the rollout plan but observed and reported. The pilot tests the cutover pattern under occupied conditions; the report feeds S5.

Tenant refusal protocol. Some tenants will not be home, refuse access, or refuse the new credential. The non-negotiable rule: the building's access is preserved through the upgrade; refusal does not prevent the swap. The plan specifies what the operator does — defer the door, issue a temporary credential, escalate — and how the refusal is recorded.

Mechanical-override decision. Replace outright (no legacy keys exist) or re-pin (cheaper, but the unknown-copy risk the audit named). For a known master-keyed history, replace is the default. Override-key class and availability are confirmed with the supplier before pilot sign-off; override-key behaviour is a per-model question — check the model’s published specification.

Old-credential decommission date. Per wave: the exact date and time the legacy credential stops opening the door. Mechanical keys: cylinder replaced or re-pinned. PINs and cards: lock re-initialised, legacy codes cleared.

Master-key retirement date. A single date, at least 14 days after the final wave's decommission date, on which every legacy master is surrendered, recorded as destroyed, and the cylinder's master-key profile removed. The retirement date is the building's published position on what "no longer a master-keyed building" means.

Rollback path. If a wave fails — pilot hardware fails a commissioning test, the standby rota proves insufficient, a class of door does not fit — the wave is rolled back, doors revert to legacy credentials, and the next wave is delayed. The rollback path is a written procedure because the building does not have time to write one during a failure.

Each plan section closes when its "done" artefact is signed: the window design when the calendar with named on-call rota is published; the per-wave list when every door and its audit reference are posted; the pilot scope when pass/fail criteria are signed; the refusal protocol when scenarios are mapped to operator actions; the override decision when the memo is signed; the decommission date when the per-wave schedule names the date and time per credential; the master-key retirement date when the surrender, destruction, and cylinder-replacement plan is filed; the rollback path when the named procedures and authority are committed to writing.

S3 — Notice Templates Approved (T-6 to T-4 Weeks)

The notices are the part the operations team under-invests in and the tenants over-respond to. A notice that reads like a procurement email is rewritten three times in the first rollout weekend; a notice that reads like a tenant letter does the cutover's communications work before the first door is touched.

Four audiences, four templates, one approval flow. The templates are written for the audience's information needs, not for supplier branding.

AudienceChannelTiming relative to cutoverToneLengthOne job it must do
Tenants of recordDoor-dropped letter, post to lease address of record, building notice board, management app pushFirst notice T-4 weeks; second reminder T-1 week; day-of card T-0 (handed to the installer to leave on the new door if no contact)Plain, dated, signed by a named building contact, with a phone number that rings a personOne A4 side or screen equivalent — honest but readableTell tenants what is changing, what is not, what they need to do, who to ask, and what happens if they refuse
On-site staff (concierge, caretaker, building manager)Briefing meeting + written SOP + per-shift handover noteBriefing T-6 weeks; per-shift handover from T-4 weeksOperational; written as instructions not policy summaryUnder one screen per topicTell staff what to say when a tenant asks, when a tenant refuses, and when a credential does not work
Contractors (refurbishment contractor plus sub-trades)Contract instruction + site induction update + per-day whiteboard at the site officeUpdate T-6 weeks; daily from T-4 weeksSite-management language; short imperative sentencesOne page per trade; one whiteboard entry per shiftTell contractors the legacy master is being retired on a specific date and any new copy must come from the approved cutover path
Owners' corporation / building committeeFormal agenda item at a committee meeting + written minutes of the decisionT-8 to T-6 weeks (ahead of tenant notice)Formal; references the cutover plan as appendixUsually 2–4 pagesGive the committee the date they will be asked to approve the master-key retirement, with the cutover plan attached

The tenant letter is the one the operations team rewrites the most. The version that ships has five jobs and none of them is selling the lock:

  • What is changing. The door's lock is being replaced. Plain language, not "the credential system is being upgraded."
  • What is not changing. The tenancy, the rent, the deposit, the use of the home.
  • What they need to do. Be home in the agreed window, decide which household members take which credentials, bring identification for any new credential with a name attached.
  • Who to ask. A named person, a phone number, an email, an after-hours path for emergencies — the building's contact, not the supplier's customer service.
  • What happens if they refuse. The operator's refusal policy, stated honestly. Refusal is documented; the door is still upgraded; the legacy credential still retires on the cutover date the audit set.

Three drafting rules keep the templates from drifting into supplier language. The supplier's name does not appear in the tenant letter's byline — the supplier is a contractor, not the face of the change. The notice does not describe the technology ("smart lock", "electronic credential", "IoT-enabled device"); it describes the experience ("a new lock, new keys, a new way to open the door"). The notice is dated, version-numbered, and signed by name.

S4 — Notice Issued (T-4 to T-2 Weeks)

The notice stage looks like clock-watching and is actually a credibility exercise. The notice's job in these two weeks is to land on the tenant's actual life — on the kitchen counter, in the household's notice pile — and stay visible enough that the tenant remembers it on Saturday morning.

Four practical rules govern the issue:

Every channel is used. Door-drop, post to the lease address of record, building notice board, and management app push (if the building has one). Redundancy is not duplication; one channel fails on every block, and the tenant who misses the notice is the tenant who misses the swap. The record kept is which channels were used, on which date, for which unit.

A reminder is built in. At T-1 week, a shorter second notice — door-hanger or doormat card — recaps the weekend window and the contact number. It is not the full notice; it is the version the tenant reads at the door the day before.

Refusal and acknowledgement are tracked. Tenants who return a signed acknowledgement, call to verify in writing, or refuse are recorded against the unit. Units with no contact by T-1 week move to the S2 refusal protocol: the door is still in the wave, the installer still arrives, the legacy credential still retires on the cutover date; tenant participation may be deferred, the door is not.

The master-key retirement is not a tenant conversation. A separate formal communication from landlord or managing agent to the master-key holders handles surrender and destruction. The tenant letter does not mention it; the committee communication, contractor instruction, and staff briefing do. The master-key conversation is a custody conversation, not a tenant conversation.

The seven issuing actions run in this order across the timeline: owners' corporation formal notice at T-8 weeks (committee minute with cutover plan attached); contractor instruction reissued at T-6 weeks and refreshed daily from T-4 (site induction register); staff briefing at T-6 weeks and refreshed per shift from T-4 (briefing register + handover book entry); first tenant notice drop at T-4 weeks (per-unit delivery log signed by dropper); second tenant reminder at T-1 week (per-unit drop log); day-of card at T-0 (installer's per-door log); master-key surrender at T+14 days post-final-wave (surrender receipt + destruction certificate). Each action has a named owner, a channel, and a date; the cutover plan's S4 artefact is the consolidated log showing all seven complete.

S5 — Pilot Weekend Swap (T-2 to T-1 Weeks)

The pilot is the cutover's first test under occupied conditions. It runs on the same plan as the rollout; the only difference is the report is signed before the next wave begins. The pilot answers four questions before the cutover commits to a six-weekend run.

Does the chosen hardware actually fit the doors the audit said it would? Sample bench fit is not door fit. The pilot puts the sample-on-the-jamb against the real doors and the report records per-door deviation in fit, finish, latch tension, strike alignment, and the closing force the building's fire-rated assemblies will tolerate.

Do the tenant communications actually land? The pilot runs the same templates on a smaller audience; the report documents which tenants acknowledged, refused, could not be reached, and what the building did about each.

Does the decommission behaviour match the audit? The pilot verifies that the old credential stops opening the new door on the cutover date and time the plan named — not earlier (tenant not on the new system locked out on Friday) and not later (legacy credential's grace period extended accidentally).

Does the Saturday-night standby rota actually work? The pilot runs the rota; the report records call response time, who answered, what the fix was, and how long the door was out of service. The rollout's standby rota is built from what the pilot report says.

Pilot questionEvidence requiredPass criterionFail action
Hardware fit on real doorsPer-door deviation log across two units and one common doorAll deviations within product-page tolerance (check the model’s published specification)Re-spec the next wave's hardware class
Tenant communicationsPer-tenant acknowledgement log within 48 hours of first notice100% of tenants acknowledged or refused in writing, or refusal protocol triggeredReissue notice; extend the next wave's notice window
Decommission behaviourTime-stamped lock audit showing legacy credential fails on cutover date/timeCutover happened at the planned date and time, not beforeRe-issue cutover date; rebuild tenant acknowledgment
Saturday-night standby rotaPer-call log with response time, fix, downtimeFirst response under two hours; door returned to service same shiftRebuild standby rota; add a named second responder

A pilot that passes goes into rollout. A pilot that fails on any one of the four questions triggers a rollback to S2, not a retry. The cost of retrying the pilot is two more weeks of cutover calendar; the cost of skipping the rollback is a six-weekend rollout that fails the same way the pilot did. The pilot is the building's veto opportunity, and it is used.

S6 — Rollout Weekend Waves (T-1 Week to T+0 Weeks)

The rollout is six to ten weekend waves, each a small-scale version of the pilot. Each wave installs its doors, produces a per-wave handover log, opens its credential change log, and is followed seven to fourteen days later by S7's decommission step. S6 is wave mechanics, not per-wave decisions; those were made in S2.

The wave-day protocol fits one weekend and is the same every weekend:

Saturday morning, doors 1 to N: Installer arrives with the per-wave door list, new hardware, credential enrolment tool, and the wave's per-tenant credential cards. Installer reviews the list against the actual doors; deviation from the survey is logged. Legacy lock removed, new lock fitted, commissioning test run (open, lock, unlock, code-enrol where applicable, mechanical-override test, app-pairing where applicable), per-door commissioning time recorded.

Saturday afternoon, doors 1 to N: Tenant encounter. Installer meets tenant in the agreed window, issues the new credential, walks through it (mechanical key, PIN, card, fingerprint, app — depends on the lock), captures the tenant's signature on the per-door credential-issued log, records any issue preventing issuance (refusal, absence, technical fault).

Saturday late afternoon: Installer closes the wave's per-door log. Doors not completed — refused, absent, technical fault — move to the per-wave exception list with a written status. The exception list is the next weekday morning's priority.

Sunday morning: Installer returns for any Saturday-evening standby calls (battery fault, latch not aligning under temperature change, tenant arrived home after the installer had left). Same protocol as Saturday afternoon.

Sunday afternoon: Installer closes the wave. The wave handover log is signed by the installer, the building manager or shift supervisor, and the per-wave supervisor. The handover is the artefact S7 cannot start without.

Wave-day activityOwnerTime budgetDocument produced
Pre-wave door-list reviewInstaller + building manager30 min, before any door is touchedPer-wave readiness memo signed by both
Per-door installationInstaller45–90 min per door (door class and lock class dependent — check the model’s published specification)Per-door commissioning log line
Tenant encounter + credential issueInstaller, witnessed by building manager15–30 min per householdPer-door credential-issued log, tenant signature
Exception handlingInstaller + standby rotaSaturday afternoon through Sunday morningPer-wave exception list with status
Wave handover sign-offInstaller, building manager, per-wave supervisorSunday afternoonWave handover log, three signatures, versioned per wave

The wave's size is what one team can finish by Sunday afternoon with the building's other trades running. A wave that overruns is a wave that over-scoped its list; the next wave is shortened, not the Sunday extended.

S7 — Old-Credential Decommission (T+7 to T+14 Days After Each Wave)

The decommission stage is the cutover's hinge — it retires the legacy credential on the door, and on the day it is missed, the cutover has technically failed even if the building does not know it yet. Every wave has its own decommission date; the dates are set in S2's plan and enforced here.

Decommission behaviour is per credential class, and the cutover plan specifies the behaviour per class. Mechanical keys: cylinder replaced (new cylinder, new key blank, legacy key no longer fits) or re-pinned (existing cylinder reconfigured). Replace is the default for buildings with a master-keyed history; re-pin is acceptable for buildings with no documented master and a fully-returned-key log. Mechanical master and sub-master keys: retired by cylinder replacement at the master-pinning level, or by removing the master-pin from every lock in the wave. The audit's master-key inventory is the input; the S2 cylinder re-pin/replace decision memo is the gate. PIN codes: the lock is re-initialised, legacy code cleared, new code(s) issued under the tenant or staff credential-issued log. Cards or fobs: lock re-initialised, legacy card de-authorised, new cards issued under the same log. Fingerprint templates: lock re-initialised, legacy template cleared, new templates enrolled. Biometric re-enrol posture (what is captured, stored, deleted) is governed by the building's biometric-data policy; the cutover plan names that policy as a precondition and the supplier's role as the enrolment tool, not the policy author. App accounts: legacy admin revoked, new admin issued under the staff credential-issued log, tenant accounts re-paired under the new lock's Bluetooth pairing and named on the lease.

Credential classDecommission behaviourDocumented inOwnerVerification
Mechanical unit keyCylinder replace or re-pin; legacy key blank no longer fitsWave handover log + per-door commissioning logInstaller + building managerTry legacy key in new cylinder on T+7 day; no entry
Mechanical master / sub-masterMaster-pin removed or cylinder replaced to remove master-key profileCylinder-replace memo from S2 + master-key surrender logLandlord / managing agentMaster-key surrender receipt; destruction certificate on T+14 day
Legacy PIN codeCode cleared in lock re-initialisationPer-door credential-issued logBuilding managerTry legacy code in new lock on T+7 day; access denied
Legacy card / fobCard de-authorised in lock re-initialisationPer-door credential-issued logBuilding managerTap legacy card on T+7 day; no entry
Legacy fingerprint templateTemplate cleared in lock re-initialisationPer-door credential-issued log + biometric-policy referenceBuilding managerPresent legacy finger on T+7 day; access denied
Legacy app accountAdmin account revoked; tenant account re-pairedApp-account log + per-door credential-issued logBuilding managerTry legacy admin login on T+7 day; credentials rejected

The verification step is the part the cutover plan names and the operations team under-runs. Verification is the day, normally T+7, when the standby rota tries the legacy credential against the new door and records whether it works. A legacy credential that still works on T+7 is one whose decommission step missed a behaviour. The wave's exception list is reopened, the door is re-commissioned, the next wave's protocol updated.

S8 — Master-Key Elimination (T+14 Days After Final Wave)

S8 is the cutover's last credibility step. It is the day the building stops being a master-keyed building, on paper and on the door. Until S8, the keying hierarchy is alive in some form — even with new unit-door cylinders, the common-area masters and the maintenance master represent a single point of unauthorised access if not retired. S8 retires them honestly.

S8 has four steps in this order:

Step 1 — Surrender. Every named holder of every master key identified in S1's audit appears, in person or by signed courier, with the key(s) named on the surrender log. The key-issuing log, the master-key inventory, and the tenant-leak checks are the inputs; the surrender log is the output. A key that does not appear on surrender day is a key whose holder the building still needs to contact; the legacy cylinder stays in service until the key is surrendered or the cylinder is replaced out of master-profile.

Step 2 — Recorded destruction. Each surrendered key is destroyed in the presence of a witness — the building manager or the landlord's representative, depending on the agreement. Destruction is documented on a destruction certificate naming the holder, the key identifier, the date, the method (industrial shear, cutting torch), both witness signatures, and a photograph attached. The certificate is the document the building's insurance position and the next tenancy-tribunal defence both rely on.

Step 3 — Cylinder-level profile removal. Every previously-master-keyed cylinder is either replaced outright (new cylinder has no master-key profile), or re-pinned to a profile with no master (master-pinning removed, sub-master becomes a single-key cylinder). Whether the replacement cylinder supports a master-key profile at all and how it is disabled is a per-model documentation question the cutover plan is not allowed to gloss.

Step 4 — Audit and announcement. A post-cutover audit walks every common-area door and verifies the cylinder's master-key profile is removed; an audit memo is signed by the building manager and the landlord; the owners' corporation or committee is formally notified that the building's keying hierarchy has been retired, with the memo as attachment.

S8 stepInputOutputTime budgetOwner
1. SurrenderMaster-key inventory from S1; key-issuing logSurrender log signed per holderOne morningLandlord / managing agent
2. Recorded destructionSurrender log + named witnessDestruction certificate per key with photographSame morning, immediately after surrenderWitness (building manager or landlord's representative)
3. Cylinder-level profile removalPer-door cylinder list; new-lock product page (check the model’s published specification)Re-pinned or replaced cylinders, per-door commissioning logTwo to five working days, depending on door countRefurbishment locks contractor
4. Audit and announcementPer-door audit; audit memo; committee minuteAudit memo signed; committee formal notificationHalf a day to walk common doors; same day for memo and notificationBuilding manager + landlord

S8's four steps fit one working week for a small block, two for a larger one. Surrender and destruction occupy one morning in the landlord's office; cylinder-level profile removal is the locks contractor's two-to-five-day pass; the audit walk on common doors is half a day followed by the committee notification the same day. The week is not negotiable for length; what is negotiable is which common doors are walked first. The audit starts at the highest-traffic common doors and finishes at the lowest; the order is the order the rest of the building will read.

Two rules govern S8 and they are non-negotiable. First, a master key that does not appear on the surrender day is treated as a still-in-wild credential; the affected cylinder stays in service at the previous profile until the key is surrendered or the cylinder is replaced out of master-profile. The building does not pass S8 with an unaccounted master key. Second, the destruction certificate is a building document, not a supplier document; the supplier is not the witness unless the building's policy explicitly makes them so. Insurance and tribunal position belong to the building.

Settle-In — Issue and Anomaly Window (T+15 to T+30 Days)

The settle-in window is the cutover's warranty period: the four weeks after S8 in which the new credential ledger meets the people on the lease, and the small percentage of small problems surface as named, fixable items rather than ambient grumbling. The window's closing artefact is a cutover report signed by operations, the landlord, and where managed, the management company.

Issue classIndicatorOwnerResolution window
Credential issue at handoverTenant reports inability to use the new credential on the first independent attemptInstaller standby rota + building managerSame-day, with a maximum 24-hour delay if parts are needed
Cross-tenant credential confusionTenant reports a credential that appears to work on a neighbouring doorBuilding manager + lock supplierSame-week; door-by-door commissioning audit
Master-key retirement push-backFormer holder requests the master backLandlord / managing agentSame-week; written answer referencing the surrender log
Audit anomalyMismatch between per-door log and per-tenant credential issuanceBuilding managerSame-week; audit-driven re-visit

The window closes when three things happen at once: every issue class closed or escalated to the asset owner for a documented reason; the credential ledger reconciled with the tenant roster (every tenant who should hold a credential does; no credential held by a person not on the lease); the cutover report signed. A cutover report unsigned at thirty days is a cutover with unresolved issues; the building does not declare the renovation lock line complete until the report is signed.

Risk Register

The cutover has failure modes the literature does not name because the literature talks about the install, not the occupied human situation. The risk register below names the eight the cutover plan must price, not as probability estimates but as design constraints.

All eight are the things that have happened in real occupied cutovers; they are risks because the literature is silent on them, not because they are unlikely.

RiskWhat it looks like in an occupied blockMitigation in the cutover plan
R1 — Audit undercounts shadow credentialsA key the building does not know about is still in the wild at decommissionConservative-quantity rule in S1; verification step in S7
R2 — Tenant notice never reaches the householdA unit's first notice is door-dropped after the tenant has already left for the weekendMulti-channel rule in S4 (door-drop, post, board, app push, day-of card)
R3 — Pilot passes on friendly doors but fails on awkward onesThe pilot weekend's two units happen to be the simplest doors in the wave; the rest of the wave is harderMid-spectrum pilot selection in S5 (not the easiest, not the hardest)
R4 — Saturday-night standby rota is unstaffedA door fails on Saturday evening and the standby contact does not answerTwo-named rota, one primary and one secondary, with a two-hour response time window in S2
R5 — Credential crossover between wavesA tenant in wave 1 mistakenly receives a credential intended for wave 2 (or vice versa)Per-wave credential ledger with date/time of issue, signed by the issuing installer
R6 — Master-key surrender fails to surface all keysA holder of a master is on the audit inventory but does not appear on surrender dayCylinder stays in service at previous profile until the key is accounted for, in S8's step-1 rule
R7 — Decommission verification skippedS7's T+7 verification is forgotten, so a legacy credential still works past its cutover dateVerification step owned by name in the wave handover log, not in a separate document
R8 — Cutover report unsigned at 30 daysThe settle-in window closes without an audit sign-off because the issues have not closedPer-issue escalation to the asset owner with documented reason; no declaration of cutover completion without the report

None of these risks is exotic. All eight are real occupied-cutover lessons; they are risks because the literature is silent on them, not because they are unlikely.

What This Programme Does Not Solve

The cutover is the credential and human half of the renovation lock line. It is not the install half, the warranty half, or the dispute half. Three questions are explicitly out of scope and each is the natural handoff to a sibling article.

Hardware choice. What the new lock physically is, what its credential lanes are, what its admin-role structure supports, what its door-fit envelope looks like — these are the buyer-guide questions and the developer spec pack questions, not the cutover questions. The buyer guide at Smart Locks for Apartment Buildings: Buyer Guide is the start; the retrofit-install lens at Smart Lock Retrofit for Apartment Buildings is the install companion; the developer pack at Smart Locks for New Apartment Construction is the new-build sibling. The cutover assumes the lock has been chosen; it does not re-litigate the choice.

Daily operations after handover. What the operations team does on day one of the new fleet — move-in credential ceremonies, contractor window management, weekly audits, battery rotation — is the playbook at Smart Locks for Apartment Operators. The cutover ends when the playbook takes over; the first four weeks of the playbook are the same weeks as the settle-in window, and the playbook is the document the operations team will refer to for the questions the cutover does not answer.

Legal posture, biometric consent and statutory notice periods. What jurisdiction the building is in, what the local notice rules require, what the biometric-consent posture must be, what the master-key destruction rules require for the building's insurance position — these are counsel questions, not catalog questions. The cutover plan names what must be confirmed with counsel; it does not assert the answers. The cutover touches occupied property under existing tenancies, so the counsel handoff carries double force.

The remaining unknown — what the building should do if the refurbishment's lock line is shipped but the operations playbook is not yet in place — has a clear answer: hold the cutover to the next playbook start date, and run the cutover as a deferred plan, not a partial start. A cutover without an operations playbook becomes a notice-and-panic operation within thirty days.

A Pre-Quote Capture Sheet for the Cutover

The catalogue constraints do not change for a cutover; what changes is which per-model detail the cutover must surface at the supplier stage. The pre-quote capture sheet is the cutover-specific minimum; every blank is a fact confirmed on the relevant product page at quote time, not asserted by the supplier's brochure.

Capture askWhat it means for the cutoverWhere it lands in the plan
Per-credential class decommission behaviour (replace, re-pin, re-init)Decides whether S7's verification step is buildable for each credential classS2 cutover plan; S7 wave handover
Master-key profile availability on the new cylinderDecides whether S8's profile-removal step is a software disable or a cylinder replaceS2 cylinder-replace memo; S8 step 3
Mechanical override key class and key-availabilityDecides the standby rota's response timeS2 weekend window design; S6 wave-day standby
Credential capacity per lane (PIN, card, fingerprint, app)Decides whether the new credential ledger can hold the per-tenant rosterS6 credential issued log; S7 credential verification
Admin-role structure (admin / sub-admin / housekeeping / user)Decides whether the operations team can run a per-role credential ledgerS7 admin-account revocation; S8 staff credential
Event-record depth and retrieval pathDecides whether the per-door log is auditable after handoverS7 decommission verification; settle-in audit
App/Bluetooth platform lane (TTLock / Tuya / Doodle — check the model’s published specification)Decides whether the operations team can issue remote credential changes during the cutoverS6 tenant encounter; S7 app-account revocation
Battery type and operating life under the cutover's use patternDecides whether the spare-battery rota can sustain the wave daysS6 standby rota; settle-in anomaly window
Door-fit envelope against the building's actual doors (thickness, backset, bore, mortise)Decides whether the cutover's sample-on-the-jamb is realisticS5 pilot weekend fit log
Ingress / exposure class for common-area and riser-door locksDecides whether the cutover's common-area doors can stay at the same exposure ratingS5 pilot common-door log; S8 audit

The capture sheet is for the supplier conversation, not the cutover plan. Every blank becomes either a confirmed per-model line on the product page, a question to take to the supplier at quote time, or an explicit entry in the cutover plan's exception register.

Closing — The Programme Is the Unit

A renovation lock line is a programme, not an installation. The hardware choice is one input; the operational cadence is another; the cutover is what connects them. A cutover that is not staged — that treats the renovation lock line as a weekend of installs — leaves the building with a credential ledger that does not match the people on the lease, a master-key inventory one master key short of being honestly retired, and a tenant population whose first encounter with the new door is a complaint.

The stages — audit, plan, notice, pilot, waves, decommission, master-key elimination, settle-in — are eight decisions and two windows. Each has an exit artefact the next stage cannot start without. The artefacts are the building's evidence trail; the cutover report is its public face; the per-tenant credential-issued log is its daily proof. A building that runs this programme honestly finishes its refurbishment with a credential ledger it can defend and a keying hierarchy retired on paper and on the door.

The cutover is the unit of work the renovation leads with when the lock line is confirmed. When the brief is to replace locks across an occupied apartment block as part of a refurbishment, the answer is rarely a lock model. The answer is a ten-week programme with eight stage gates; the programme starts with the audit and ends with the cutover report.

For a starting conversation about a specific block — door count, vintage, keying hierarchy, common-area scope, refurbishment calendar — the next step is a quote brief that lists the buildings, the doors per class, and the legacy credential inventory from S1. Send that to the supplier through the request-a-quote path at Request a quote; a sample-set against the per-wave door list can be ordered in parallel through Order samples. The supplier's role at this stage is verified in writing the per-model behaviour the cutover plan needs and to surface the small percentage of small incompatibilities the audit cannot.

장바구니
쿠키를 허용하면 이 사이트에서의 이용 경험이 개선됩니다. 쿠키 정책
Chat on WhatsApp