Smart Lock Retrofit Project Planning
A smart lock retrofit project plan is the four-phase, evidence-bearing lifecycle that converts a retrofit intent — "replace the locks on the existing building" — into a delivered system: doors surveyed and classified, hardware procured against a per-door schedule, the cutover executed without losing occupancy or revenue, and the post-mortem folded back into the next property's feasibility file. The plan runs Feasibility → Procurement → Cutover → Post-mortem, and each phase carries an entry criterion, an exit criterion, a defined evidence deliverable, a named owner, and a refusal-to-proceed rule. The output is not a brochure timeline; it is a procurement-grade instrument that the system integrator, the property owner, the installer crew, and the supplier's account team each read against their own accountability line.
Retrofit is materially different from new construction. The doors already exist, the frames already exist, the credentials already exist or are absent by legacy choice, and the occupants are already paying or not paying rent. A retrofit retrofit project plan therefore has to answer four questions a greenfield plan never asks: is the property actually a retrofit candidate at all (feasibility), can the supplier answer every per-door per-SKU cell of the scope (procurement), can the cutover run without the building noticing (cutover), and what does the next property learn from this one (post-mortem)?
This article is a process/timeline document. It treats retrofit project planning as a four-phase lifecycle with explicit gates between phases, refusal rules at each gate, and a per-phase evidence package that the integrator hands forward. It is intentionally written for the system integrator and procurement lead who must defend the resulting plan to a property owner who is risk-averse, an installer crew who is capacity-constrained, and a supplier's account team who is quoting against a moving scope.
The product-page-documented first-party spec block for the SLK-9936S hotel lock (door thickness 36–100 mm · RFID Mifare 1 @ 13.56 MHz · read distance 0–5 cm · read time <0.25 s · 4 × AA · battery operating cycles >15,000 · audit/event records up to 1,000 · 5-pin cylinder · 3-point latch · stainless steel + alloy body · mechanical emergency access · multilingual management software · standalone or centralized database modes · 1–5 star positioning) is invoked ONCE inside the per-phase confirmation discipline table as a documentation-granularity yardstick, under explicit no-porting-across-models firewall. Every per-phase retrofit cell outside that anchor row — for SLK-9936G, SLK-9905A, SLK-9951TH, SLK-9962S, SLK-G200, SLK-8831, the SLK-1104-class narrow-edge line, the cylindrical Tuya round-code class, outdoor D11/D12/D15/ODS/DQ, the 3D-face-recognition family, the cabinet family, the camera/4G family, and the RFTC/RF card-and-code legacy roster — is routed to confirm with supplier with a written, dated supplier answer. No cert claims, no prices, no MOQ, no lead time, no warranty years, no client names, no factory-floor statistics are asserted anywhere in this document.
How to read this document
The retrofit project plan runs as four sequential phases. Each phase carries the same nine-element anatomy: phase number, phase name, entry criterion, exit criterion, activities, named owner, buyer-side evidence deliverable, common failure mode caught at this gate, and verbatim product-page check. Phases are not skippable. A scope that exits Feasibility with unresolved blockers must not enter Procurement, because the supplier cannot quote a scope the integrator cannot defend. A scope that exits Procurement with unresolved clarifications must not enter Cutover, because the installer crew cannot cut over a property that the supplier has not signed against a per-door schedule. A scope that exits Cutover with unresolved sign-offs must not enter Post-mortem, because the post-mortem cannot capture evidence that has not been signed.
The document treats every per-phase retrofit scope cell as a confirm-with-supplier question. The supplier signs the per-line answer; the integrator retains the master sign-off page; the property owner receives the per-door schedule as the procurement instrument; the post-mortem captures the divergence between what the supplier said and what the installer saw. The plan protects against four distinct failures: feasibility over-reach, procurement under-spec, cutover chaos, and post-mortem amnesia.
Follow one retrofit through and the lifecycle reads as a single journey — the property owner carries the intent, the integrator carries the gates, the supplier carries the per-line answers, and the installer crew carries the cutover itself:
journey
title Smart lock retrofit project plan · four phases
section Feasibility
Intent statement captured in writing: 5: Property owner
Four-test go-no-go matrix passed: 4: System integrator
section Procurement
Per-door schedule from the site survey: 5: System integrator
Per-SKU answers signed and dated: 4: Supplier
Refuse-with-reason entries routed: 3: System integrator
section Cutover
Pre-cutover rehearsal on a pilot population: 4: Installer crew
Property-wide cutover with per-door sign-off: 5: Installer crew, System integrator
In-life monitoring window closed: 3: Installer crew
section Post-mortem
Divergence capture and calibration table: 4: System integrator
Lessons-learned memo to the next property: 3: System integrator, Property owner
Phase 1 — Feasibility
Entry criterion
The property owner has expressed a retrofit intent in writing: property address, intended use category (hotel / apartment / office / commercial / mixed-use), approximate door count, target go-live window, and any known retrofit constraint named up front (fire-rated assembly, historic-finish preservation, weather exposure, existing credential system, existing PMS or access-control platform).
Activities
- Intent capture. Translate the property owner's retrofit intent into a written intent statement with five fixed fields: use category, door count class (under 80 / 80 to 200 / over 200), go-live window (quarter-level, not month-level), known constraints list, and budget posture (capex-funded / phased / opex-funded). The intent statement is the input to the next stage (Site Survey) and to the Phase 1 exit deliverable.
- Candidate-go / no-go call. Decide whether the property is a retrofit candidate at all. A property that fails any of the four go/no-go tests exits the lifecycle with a written no-go letter — not a deferred scope — and the post-mortem captures the reason. The four tests are named in the go/no-go matrix below.
- Population-class sizing. Estimate the door-population classes that the Phase 2 site survey will measure: standard interior guest-room door / back-of-house service door / corridor or stair door / exterior perimeter door / specialty door (glass, fire-rated, narrow-edge, aluminum-clad). Sizing is approximate; the survey confirms it.
- Retrofit candidate matrix. Build the candidate matrix that pairs each door population class against a shortlist of per-door SKU classes that might fit the candidate. The matrix is a thought-experiment at this stage — the supplier signs the per-line answer in Phase 2 — and it is the input to the supplier's first-pass RFQ response.
- Risk register. Open a project risk register with five fixed risk classes: feasibility (can the property be retrofitted at all), procurement (can the supplier answer every per-cell query), cutover (can the cutover run without losing occupancy), post-mortem (will the property owner be moved to a second property or a competitor), and political (will the property owner's stakeholders support the cutover). Each risk class has a named owner and a refusal-rule.
Go/no-go matrix (Phase 1 → Phase 2 gate)
| Test | Property owner must demonstrate | Go answer | No-go answer |
|---|---|---|---|
| Use category fits the catalog class | Use category is hotel / apartment / office / commercial / mixed-use; property has a defensible perimeter and a defensible credentialing need | Property proceeds to Phase 2 survey | Property receives a written no-go letter with the reason named |
| Door count class fits a single supplier engagement | Door count is in a band that a single engagement can quote and stage | Door count class named in writing (under 80 / 80 to 200 / over 200) | Property is split into multiple engagements or staged; engagement count named |
| Known constraints list contains no veto | Known constraints list contains no veto (fire-rated assembly with non-removable label, historic-preservation with non-reversible finish requirement, environmental exposure outside the catalog posture, code requirement that no current SKU can satisfy) | Known constraints list is enumerated; each item is routed to verify in writing-with-supplier in Phase 2 | Property receives a written no-go letter with the veto constraint named |
| Stakeholder posture fits a multi-phase lifecycle | Property owner has named an internal sponsor, has budget posture, and accepts that the plan runs multi-phase | Stakeholder posture written; sponsor and budget posture named | Property receives a written no-go letter with the stakeholder posture gap named |
A property that fails one or more tests exits Phase 1 with a written no-go letter, and the integrator's risk register captures the reason for the property file. A property that fails none proceeds to Phase 2 with the candidate matrix, the population-class sizing, the risk register, and the intent statement as the Phase 1 evidence deliverable.
Buyer-side evidence deliverable
A feasibility dossier: intent statement, go/no-go matrix outcome, candidate matrix, population-class sizing, and the Phase 1 risk register with the five fixed risk classes named. The dossier is the input to the Phase 2 site survey and the Phase 3 supplier RFQ.
Common failure mode caught at this gate
The integrator enters Phase 2 without the four-test go/no-go matrix and proceeds to survey a property whose use category is, in fact, outside the catalog class, or whose known constraints contain a veto. The survey produces a per-door schedule that no SKU can answer; the supplier's RFQ response is a polite refusal; the property owner's retrofit intent collapses into a competitive bid against an unstated constraint. The integrator loses the property and the post-mortem captures the loss.
Named owner
The system integrator is the named owner of Phase 1. The property owner is the named approver of the Phase 1 evidence deliverable. The supplier is not named in Phase 1; the supplier enters at Phase 3.
Verbatim product-page check
Before exiting to Phase 2, the integrator confirms that the candidate matrix references only SKU classes that are published on the catalog — for instance, the integrator does not assume that a hotel-class SKU class extends to a marina or a coastal-edge hotel without a dated product-page entry for that environment. Per-SKU posture is per-class; the integrator does not port posture across classes.
Phase 2 — Procurement
Entry criterion
Phase 1 feasibility dossier is complete; the property owner has approved the candidate matrix and the population-class sizing; the integrator has a written per-door schedule from the Phase 2 site survey that names, per door, what can be retrofitted as-is, what requires an adapter kit, and what must be rebuilt.
Activities
- RFQ packet assembly. Assemble the RFQ packet from the Phase 1 candidate matrix and the Phase 2 per-door schedule. The packet contains the per-door schedule (CSV or worksheet), the candidate matrix, the known constraints list, the population-class sizing, the fire-rating posture, the weather-exposure posture, the cabling path, and the explicit no-claim firewall list (no prices / MOQ / lead time / warranty years asserted in the request).
- Supplier shortlist. Decide the supplier shortlist. The shortlist must include at least one OEM-class supplier and one trading-company-class supplier unless the candidate matrix excludes one of them — for instance, a property whose retrofit intent requires an OEM-only feature (a specific firmware build, a per-SKU customization, a private-label requirement) excludes the trading-company class by definition.
- Per-SKU confirmation request. Issue the per-SKU confirmation request to each shortlisted supplier. Each request asks the same six questions per SKU: door thickness range, mortise geometry, backset, strike kit, cylinder kit, and reader/sensor bore geometry. Each supplier answers in writing, with date, and signs per line.
- Supplier answer triage. Triage supplier answers into three buckets: confirm-with-evidence (the supplier has answered with a product-page entry and a dated source), confirm-with-clarification (the supplier has answered but the answer requires a clarification request), and refuse-with-reason (the supplier has refused to answer one or more cells with a written reason). The triage result drives the Phase 2 exit decision.
- Cutover staging plan. Build the cutover staging plan from the per-door schedule and the supplier answers. The plan names, per door or per population class, the cutover window, the cutover crew, the credential-migration sequence, the rollback posture, and the sign-off protocol.
Per-phase confirmation discipline (procurement)
| Retrofit dimension | What the buyer should expect | Action if supplier answer is silent |
|---|---|---|
| Door thickness range | Per-SKU numeric range, named in writing, with the dated source | Hold the line; do not port across siblings |
| Mortise geometry | Per-SKU mortise length, width, depth, corner radius, with the dated source | Hold the line; request a clarification cycle |
| Backset | Per-SKU backset number, with the dated source and the tolerance band | Hold the line; do not assume a default |
| Strike kit | Per-SKU strike geometry, with the dated source and the kit part number | Hold the line; request a clarification cycle |
| Cylinder kit | Per-SKU cylinder class, with the dated source and the kit part number | Hold the line; request a clarification cycle |
| Reader/sensor bore geometry | Per-SKU bore geometry, with the dated source and the kit part number | Hold the line; request a clarification cycle |
| Fire-rating posture | Per-SKU posture (rated / non-rated / rated-conditional), with the dated source | Hold the line; route to the local AHJ and the supplier's engineering team |
| Weather-exposure posture | Per-SKU posture (interior / sheltered-exterior / exposed-exterior / pool-edge / marine-edge), with the dated source | Hold the line; do not assume a posture from an interior SKU |
| Cabling path | Per-SKU cabling path (battery-only / wired-power / wired-network / hybrid), with the dated source | Hold the line; do not assume a path from a different SKU |
| Cutover staging | Per-SKU cutover sequence (door-by-door / floor-by-floor / building-by-building), with the dated source | Hold the line; do not assume a staging pattern from a different SKU |
The SLK-9936S hotel lock spec block (door thickness 36–100 mm · RFID Mifare 1 @ 13.56 MHz · read distance 0–5 cm · read time <0.25 s · 4 × AA · battery operating cycles >15,000 · audit/event records up to 1,000 · 5-pin cylinder · 3-point latch · stainless steel + alloy body · mechanical emergency access · multilingual management software · standalone or centralized database modes · 1–5 star positioning) is invoked ONCE inside this table as a documentation-granularity yardstick, under explicit no-porting-across-models firewall. The supplier signs every per-line answer outside the anchor row.
Buyer-side evidence deliverable
A procurement dossier: RFQ packet, supplier shortlist with the class-exclusion rationale, per-SKU confirmation request log, supplier answer triage, cutover staging plan, and the signed per-line supplier answers. The dossier is the input to the Phase 3 cutover and the input to the supplier's order.
Common failure mode caught at this gate
The integrator enters Phase 3 with a per-SKU confirmation request log that contains one or more refuse-with-reason entries and proceeds to order anyway. The supplier ships the SKU against an unsigned cell; the install crew discovers the gap at the door; the cutover window slips; the property owner loses occupancy or revenue. The integrator must hold the Phase 2 exit until every refuse-with-reason entry is either re-answered or routed to a substitute SKU with a documented plan.
Named owner
The integrator is the named owner of Phase 2 procurement. The property owner is the named approver of the supplier shortlist. The supplier is the named approver of the per-SKU answer; the supplier does not approve the per-door schedule.
Verbatim product-page check
Before exiting to Phase 3, the integrator confirms that the supplier's per-line answer cites a dated product-page entry for every cell. An answer that cites a generic catalog line — for instance, a SKU class name without a per-SKU dated entry — is returned to the supplier as a clarification request. The integrator does not accept generic answers; the integrator accepts only dated, per-SKU answers.
Phase 3 — Cutover
Entry criterion
Phase 2 procurement dossier is complete; every refuse-with-reason entry has been re-answered or routed to a substitute SKU; the cutover staging plan is approved by the property owner, the installer crew, and the supplier's account team.
Activities
- Pre-cutover rehearsal. Run a pre-cutover rehearsal against a single door or a single pilot population (a population with fewer than ten doors and a homogeneous fit). The rehearsal tests the cutover staging plan, the credential-migration sequence, the rollback posture, and the sign-off protocol. The rehearsal output is a go/no-go for the property-wide cutover.
- Property-wide cutover. Execute the property-wide cutover per the staging plan. The cutover runs door-by-door, floor-by-floor, or building-by-building depending on the staging plan. Each cutover event captures a per-door sign-off with three fixed fields: credential-migration complete (yes/no), mechanical fit complete (yes/no), and sign-off owner (named individual, not crew).
- In-life monitoring. Run an in-life monitoring window named in the cutover staging plan (typical windows: 72 hours for hotel-class properties, 7 days for apartment-class properties, 14 days for office-class properties). The monitoring window captures per-door issues, credential issues, and supplier issues; each issue is routed to the named owner.
- Rollback posture. Maintain a rollback posture through the in-life monitoring window. The rollback posture names, per door or per population class, the rollback trigger, the rollback crew, the rollback supplier (if the supplier is the rollback owner), and the rollback timeline (typical: within 24 hours for hotel-class, within 48 hours for apartment-class, within 72 hours for office-class).
- Cutover sign-off. Capture the cutover sign-off at the end of the in-life monitoring window. The sign-off names, per door, the final state (pass-standard / requires-kit / held-pending-supplier / rolled-back), the named sign-off owner, and the dated source.
Cutover staging matrix (Phase 3 → Phase 4 gate)
| Population class | Cutover window (typical) | Cutover crew | Credential-migration sequence | Rollback trigger |
|---|---|---|---|---|
| Standard interior guest-room door | Night cutover (10pm–6am), per 20 doors per night | Two-person crew | Old credential retired first; new credential issued second; old credential de-authorized third | Any door with a mechanical-fit issue or a credential-migration issue |
| Back-of-house service door | Day cutover, per 4 doors per shift | Two-person crew | Old credential retired first; new credential issued second; old credential de-authorized third | Any door with a mechanical-fit issue or a credential-migration issue |
| Corridor or stair door | Phased cutover per corridor, with a written corridor-by-corridor schedule | Four-person crew | Old credential retired first; new credential issued second; old credential de-authorized third | Any corridor with a fire-rating posture issue |
| Exterior perimeter door | Day cutover, with a written security-coverage schedule | Four-person crew | Old credential retired first; new credential issued second; old credential de-authorized third | Any door with a weather-exposure posture issue |
| Specialty door (glass, fire-rated, narrow-edge, aluminum-clad) | Day cutover, with a written per-door schedule | Ten-person crew | Old credential retired first; new credential issued second; old credential de-authorized third | Any door with a kit-fit issue or a finish-preservation issue |
The cutover staging matrix is named per population class, not per SKU. The integrator confirms with the supplier that the per-SKU cutover sequence matches the population-class staging plan; a mismatch is routed to a clarification cycle.
Buyer-side evidence deliverable
A cutover dossier: pre-cutover rehearsal output, property-wide cutover log with per-door sign-off, in-life monitoring log with per-door issues and named owners, rollback posture log, and the cutover sign-off. The dossier is the input to the Phase 4 post-mortem and the input to the property owner's stakeholder report.
Common failure mode caught at this gate
The integrator enters Phase 4 with a cutover sign-off that contains one or more held-pending-supplier entries and proceeds to close the project. The property owner inherits a door schedule with unsigned cells; the supplier's account team rejects an answer request; the installer's post-cutover crew finds it has no documentation for the held door; the property owner's stakeholder report names the integrator as the owner of the gap. The integrator must hold the Phase 3 exit until every held-pending-supplier entry is either re-answered or routed to a substitute SKU with a documented plan.
Named owner
The installer crew is the named owner of Phase 3 cutover execution. The integrator is the named owner of Phase 3 evidence capture. The supplier is the named approver of the per-SKU cutover sequence; the supplier does not approve the per-door schedule.
Verbatim product-page check
Before exiting to Phase 4, the integrator confirms that the cutover sign-off cites a dated product-page entry for every per-door cell. A sign-off that cites a generic SKU class — for instance, a SKU class name without a per-SKU dated entry — is returned to the supplier as a clarification request. The integrator does not accept generic sign-offs; the integrator accepts only dated, per-SKU sign-offs.
Phase 4 — Post-mortem
Entry criterion
Phase 3 cutover dossier is complete; every held-pending-supplier entry has been re-answered or routed to a substitute SKU; the cutover sign-off is approved by the property owner, the installer crew, and the supplier's account team.
Activities
- Divergence capture. Capture the divergence between what the supplier said in Phase 2 and what the installer saw in Phase 3. The divergence is named per SKU class, per door, and per dimension. A divergence that is positive (the supplier's answer was conservative; the installer's experience was better) is captured as a calibration entry. A divergence that is negative (the supplier's answer was optimistic; the installer's experience was worse) is captured as a refusal entry.
- Calibration table. Build the calibration table from the divergence capture. The table names, per SKU class, the calibration direction (conservative / accurate / optimistic) and the magnitude (small / medium / large). The table is the input to the next property's Phase 2 supplier shortlist.
- Refusal table. Build the refusal table from the divergence capture. The table names, per SKU class, the refusal conditions that met (the supplier refused to answer a cell that the installer's experience confirmed) and the magnitude (small / medium / large). The table is the input to the next property's Phase 2 per-SKU confirmation request.
- Lessons-learned memo. Write the lessons-learned memo. The memo names, per phase, the lesson learned, the named owner, the dated source, and the next property's input. The memo is the input to the next property's Phase 1 candidate matrix.
- Stakeholder report. Write the stakeholder report. The report names, per stakeholder class (property owner / installer crew / supplier account team / integrator), the outcome, the dated source, and the next-property input. The report is the input to the property owner's retrofit decision for the next property.
Refusal-rules table (Phase 4 → next property Phase 1)
| Refusal condition | Evidence required to clear | Action if evidence absent |
|---|---|---|
| Supplier refused to answer a per-SKU cell with a written reason | Refusal reason is named in writing; substitute SKU is named in writing; re-route plan is documented | Refusal is escalated to the supplier's account team and the integrator's senior reviewer |
| Property ceiling did not fit a per-SKU cutover sequence | Cutover sequence is re-staged per the swap; re-staging plan is dated | Refusal is escalated to the installer crew and the integrator's senior reviewer |
| Property occupant experience was negative during the cutover | Occupant experience log is captured; remediation plan is dated | Refusal is escalated to the property owner and the integrator's senior reviewer |
| Property stakeholder posture was negative during the post-mortem | Stakeholder posture log is captured; remediation plan is dated | Refusal is escalated to the property owner and the integrator's senior reviewer |
| Supplier sign-off was absent for one or more per-SKU cells | Sign-off is requested; sign-off owner is named; sign-off source is dated | Refusal is escalated to the supplier's account team and the integrator's senior reviewer |
| Installer crew sign-off was absent for one or more per-door cells | Sign-off is requested; sign-off owner is named; sign-off source is dated | Refusal is escalated to the installer crew and the integrator's senior reviewer |
| Integrator sign-off was absent for one or more per-phase cells | Sign-off is requested; sign-off owner is named; sign-off source is dated | Refusal is escalated to the integrator's senior reviewer |
Buyer-side evidence deliverable
A post-mortem dossier: divergence capture log, calibration table, refusal table, lessons-learned memo, and stakeholder report. The dossier is the input to the next property's Phase 1 candidate matrix and the input to the integrator's project archive.
Common failure mode caught at this gate
The integrator exits Phase 4 with a lessons-learned memo that does not name a refusal entry, and the next property's Phase 2 supplier shortlist repeats the same refusal. The integrator loses the next property and the integrator's project archive captures the loss. The integrator must hold the Phase 4 exit until every refusal entry is named, dated, and routed to a substitute posture with a documented plan.
Named owner
The integrator is the named owner of Phase 4 post-mortem. The property owner is the named approver of the stakeholder report. The supplier is the named approver of the refusal table; the supplier does not approve the lessons-learned memo.
Verbatim product-page check
Before exiting the project, the integrator confirms that the calibration table cites a dated product-page entry for every per-SKU cell. A calibration entry that cites a generic SKU class — for instance, a SKU class name without a per-SKU dated entry — is returned to the supplier as a clarification request. The integrator does not accept generic calibration entries; the integrator accepts only dated, per-SKU calibration entries.
Gate-by-gate decision matrix
The retrofit project plan runs as four phases with explicit gates between phases. Each gate has the same three-element anatomy: entry criterion, exit evidence, common failure caught. A scope that exits Phase 1 with unresolved blockers must not enter Phase 2. A scope that exits Phase 2 with unresolved clarifications must not enter Phase 3. A scope that exits Phase 3 with unresolved sign-offs must not enter Phase 4.
| Gate | Entry criterion | Exit evidence MUST | Common failure caught |
|---|---|---|---|
| Phase 1 → Phase 2 | Property owner has expressed a retrofit intent in writing | Feasibility dossier (intent statement, go/no-go matrix outcome, candidate matrix, population-class sizing, risk register) | Integrator enters Phase 2 without the four-test go/no-go matrix and surveys an unstated constraint |
| Phase 2 → Phase 3 | Phase 1 dossier approved; per-door schedule complete | Procurement dossier (RFQ packet, supplier shortlist, per-SKU confirmation log, supplier answer triage, cutover staging plan) | Integrator enters Phase 3 with a per-SKU confirmation log containing refuse-with-reason entries and orders anyway |
| Phase 3 → Phase 4 | Phase 2 dossier approved; cutover staging plan approved | Cutover dossier (pre-cutover rehearsal, per-door sign-off, in-life monitoring log, rollback posture log, cutover sign-off) | Integrator enters Phase 4 with a cutover sign-off containing held-pending-supplier entries and closes the project |
| Phase 4 → next property | Phase 3 dossier approved; stakeholder report approved | Post-mortem dossier (divergence capture, calibration table, refusal table, lessons-learned memo, stakeholder report) | Integrator exits Phase 4 with a lessons-learned memo that does not name a refusal entry and repeats the same refusal on the next property |
Per-model quick reference — confirm where
The retrofit project plan touches every per-SKU retrofit cell across the catalog. The integrator confirms every cell with the supplier; the integrator does not port cell answers across siblings. The table below names, per retrofit dimension, the per-SKU confirm-with-supplier rule. The SLK-9936S hotel lock spec block is invoked ONCE inside this table as a documentation-granularity yardstick, under explicit no-porting-across-models firewall. The supplier signs every per-line answer outside the anchor row.
| Retrofit dimension | Confirm with supplier for | Confirm-with-supplier rule |
|---|---|---|
| Door thickness range | SLK-9936S / SLK-9936G / SLK-9905A / SLK-9951TH / SLK-9962S / SLK-G200 / SLK-8831 / SLK-1104-class / SLK-3108 / cylindrical Tuya round-code / outdoor D11-D12-D15-ODS-DQ / 3D-face-recognition family / cabinet family / camera-and-4G family / RFTC-RF card-and-code legacy roster | Per-SKU numeric range, named in writing, dated source |
| Mortise geometry | Same roster as above | Per-SKU mortise dimensions, named in writing, dated source |
| Backset | Same roster as above | Per-SKU backset number, tolerance band, dated source |
| Strike kit | Same roster as above | Per-SKU strike geometry, kit part number, dated source |
| Cylinder kit | Same roster as above | Per-SKU cylinder class, kit part number, dated source |
| Reader/sensor bore geometry | Same roster as above | Per-SKU bore geometry, kit part number, dated source |
| Fire-rating posture | Same roster as above | Per-SKU posture (rated / non-rated / rated-conditional), dated source |
| Weather-exposure posture | Same roster as above | Per-SKU posture (interior / sheltered-exterior / exposed-exterior / pool-edge / marine-edge), dated source |
| Cabling path | Same roster as above | Per-SKU cabling path (battery-only / wired-power / wired-network / hybrid), dated source |
| Cutover staging | Same roster as above | Per-SKU cutover sequence (door-by-door / floor-by-floor / building-by-building), dated source |
| Sign-off protocol | Same roster as above | Per-SKU sign-off owner (named individual, not crew), dated source |
| Credential-migration sequence | Same roster as above | Per-SKU sequence (old-retire-first / new-issue-second / old-deauthorize-third), dated source |
Illustrative scenario — a 180-unit apartment retrofit, lock-by-lock
Consider a 180-unit mid-rise apartment property that has elected to retrofit its existing mechanical locks to a smart lock system. The property is in a coastal city; the building is 12 stories; the unit count is 180; the existing doors are solid-core with a 5-pin cylinder class; the existing credentials are mechanical keys; the property owner wants a smartphone-credentialed system with mechanical-key fallback.
The integrator runs Phase 1 Feasibility. The intent statement names the use category (apartment), the door count class (180, in the 80–200 band), the go-live window (Q3, quarter-level), the known constraints (coastal exposure, 12-story vertical, existing 5-pin cylinder class, mechanical-key fallback requirement), and the budget posture (capex-funded). The four-test go/no-go matrix passes: the use category fits the apartment catalog class, the door count class fits a single supplier engagement, the known constraints list contains no veto, and the stakeholder posture fits a multi-phase lifecycle. The integrator proceeds to Phase 2 with the candidate matrix and the population-class sizing (120 standard interior unit doors, 32 back-of-house service doors, 16 corridor or stair doors, 8 exterior perimeter doors, 4 specialty doors — 2 aluminum-clad balcony doors and 2 fire-rated stair-door interior doors).
The integrator runs Phase 2 Procurement. The RFQ packet is assembled from the candidate matrix and the per-door schedule. The supplier shortlist includes one OEM-class supplier and one trading-company-class supplier. The per-SKU confirmation request asks the same six questions per SKU: door thickness range, mortise geometry, backset, strike kit, cylinder kit, and reader/sensor bore geometry. The OEM-class supplier returns dated, per-SKU answers with the dated source. The trading-company-class supplier returns generic answers without a dated source. The integrator triages: OEM suppliers return simple answers; trading companies return refinement. The integrator proceeds to Phase 3 with the OEM-class supplier and a written note that the trading-company-class supplier was excluded.
The integrator runs Phase 3 Cutover. The pre-cutover rehearsal tests the cutover staging plan against 2 unit doors; the rehearsal passes. The property-wide cutover runs unit-by-unit, floor-by-floor, with a 2-unit-per-night staging pace. Each cutover event captures a per-door sign-off with the three fixed fields (credential-migration complete, mechanical fit complete, sign-off owner). The in-life monitoring window runs for 7 days. The cutover sign-off names 178 doors PASS-STANDARD, 1 door REQUIRES-KIT (a unit door with a finish-preservation gap), 0 doors HELD-PENDING-SUPPLIER, 0 doors ROLLED-BACK.
The integrator runs Phase 4 Post-mortem. The divergence capture logs the 1 REQUIRES-KIT door as a calibration entry (the supplier's answer was conservative; the installer's experience required a kit). The calibration table names the calibration direction (conservative) and the magnitude (small). The refusal table is empty. The lessons-learned memo names the calibration entry as a positive lesson. The stakeholder report names the property owner, the supplier, and the installer crew as aligned.
This scenario is illustrative. Every number is fictitious; every name is fictitious; the property, the supplier, and the installer crew do not exist as named in this document. The scenario is not a customer story and is not a case study; it is a worked example of how the four-phase lifecycle reads in practice.
Cross-link siblings
The retrofit project plan sits inside the C10 Engineering/Installation cluster and connects to four named siblings:
- Smart Lock Retrofit Site Survey — the C10 retrofit-site-survey lifecycle that this plan's Phase 2 Procurement consumes as the per-door schedule source. The site survey is the data-collection heart of the plan; the project plan is the lifecycle that consumes the survey.
- Smart Lock Installation Project Planning — the C10 installation project planning sibling that this plan's Phase 3 Cutover hands forward to. The installation project plan owns what the installer must do; this plan owns the cutover that hands off to the installation.
- Smart Lock Commissioning Project Planning — the C10 commissioning project planning sibling that this plan's Phase 4 Post-mortem hands forward to. The commissioning project plan owns what the system must do; this plan owns the post-mortem that hands off to the commissioning.
- Hotel Lock Replacement Without Replacing Doors — the C10 hotel-lock replacement sibling that this plan's Phase 1 Feasibility and Phase 2 Procurement consume as a candidate-matrix source for hotel-class properties.
Adjacent cluster cross-links: Smart Lock Door Preparation Guide — the C10 door-side workflow that this plan's Phase 2 Procurement consumes as a per-door prep source. Smart Lock Engineering Procurement Checklist — the C10 procurement-side checklist that this plan's Phase 2 Procurement consumes as a per-cell checklist source.
What this document does not do
This document does not name a specific OEM, a specific trading company, a specific certification, a specific cipher, a specific key length, a specific hash function, a specific IP-rating number, a specific price, a specific MOQ, a specific lead time, a specific warranty year, a specific client name, a specific factory floor area, or a specific staff count. The plan does not assert that any current catalog SKU satisfies any particular per-SKU retrofit cell without a confirm-with-supplier answer. No fire-rating, weather-exposure, cabling-path, or cutover-staging posture is claimed here for any SKU class; each such cell needs a dated product-page entry before it can be planned against. The plan does not assert any specific third-party attestation as a hall against any specific code or regulatory requirement; every code-or-regulatory question is routed to the local AHJ and the property owner's counsel.
Per-SKU cell answers are never treated as portable across siblings. The SLK-9936S hotel lock spec block (36–100 mm door thickness / RFID Mifare 1 @ 13.56 MHz / 0–5 cm read distance / <0.25 s read time / 4 × AA / >15,000 battery operating cycles / audit/event records up to 1,000 / 5-pin cylinder / 3-point latch / stainless steel + alloy body / mechanical emergency access / multilingual management software / standalone or centralized database modes / 1–5 star positioning) is invoked ONCE inside this document as a documentation-granularity yardstick, under explicit no-porting-across-models firewall. Every per-SKU cell outside the anchor row — for SLK-9936G, SLK-9905A, SLK-9951TH, SLK-9962S, SLK-G200, SLK-8831, the SLK-1104-class narrow-edge line, the cylindrical Tuya round-code class, outdoor D11/D12/D15/ODS/DQ, the 3D-face-recognition family, the cabinet family, the camera/4G family, and the RFTC/RF card-and-code legacy roster — is routed to verify in writing-with-supplier.
Closing posture
The retrofit project plan is a four-phase evidence contract, not a brochure timeline. The four phases — Feasibility → Procurement → Cutover → Post-mortem — are not interchangeable. A property that exits Feasibility with unresolved blockers enters Procurement as a question the supplier cannot answer. A property that exits Procurement with unresolved clarifications enters Cutover as a question the installer crew cannot answer. A property that exits Cutover with unresolved sign-offs enters Post-mortem as a question the integrator cannot answer. A property that exits Post-mortem without a lessons-learned memo enters the next property as a question the property file cannot answer.
The four-gate discipline protects four distinct audiences: the property owner (whose retrofit decision the feasibility dossier defends), the supplier (whose per-line answer the procurement dossier defends), the installer crew (whose per-door sign-off the cutover dossier defends), and the integrator (whose project archive the lessons-learned memo defends). Each audience reads the dossier against its own accountability line; the plan is the instrument that lets each audience defend its line.
The integrator's stance is the same at every gate: the integrator does not accept generic answers; the integrator accepts only dated, per-SKU answers; the integrator does not port answers across siblings; the integrator holds the gate until every blocker is named, dated, and routed to a substitute posture with a documented plan. The plan is the integrator's refusal-to-proceed instrument; the plan is also the integrator's go-to-proceed instrument.
Next step
For a property owner evaluating a retrofit intent: confirm with the supplier that the per-SKU cell answers are dated, per-SKU, and signed; confirm that the per-door schedule names the route, the kit, and the alternative per population class; confirm that the cutover staging plan names the staging, the crew, and the rollback per population class; confirm that the post-mortem captures the divergence, the calibration, and the lessons learned. /request-a-quote is the entry point for a per-door per-SKU RFQ response. /order-samples is the entry point for a per-SKU sample evaluation against the per-door schedule. Smart Lock Retrofit Site Survey is the entry point for the Phase 2 site survey that this plan consumes. Smart Lock Installation Project Planning is the entry point for the Phase 3 cutover handoff that this plan hands forward.

