A rental smart lock is not ready for the next resident when one keypad code has merely been changed. Turnover must remove old accounts, phones, codes, keys, automations, camera access, alarm permissions, and recovery paths; verify door fit and batteries; test failures; and hand control to the correct owner and resident.
Smart-lock turnover at a glance
| Area | Pass condition | Common failure |
|---|---|---|
| Ownership | The lawful owner or manager controls the lock and recovery | A former resident or installer remains primary owner |
| Credentials | Old codes, phone keys, cards, fingerprints, and shares all fail | Only the visible keypad code was changed |
| Mechanical access | Keys are accounted for and rekeying follows the property plan | An unknown physical key still works |
| Door fit | The bolt moves freely with the door open and closed | The motor strains against a misaligned strike |
| Integrations | Alarm, camera, voice, and automation access match the new tenancy | A departing resident keeps indirect access through another app |
| Handover | The new resident receives named access, privacy terms, support, and tests | Everyone shares an undocumented master code |
1. Confirm authority and the turnover boundary
Identify the property owner, manager, outgoing resident, incoming resident, installer, cleaner, contractor, and any short-term guest roles. Follow the lease, local access and rekeying rules, fire and egress requirements, privacy law, and building policy. Do not delete evidence, lock out a lawful occupant, or change access before the authorized turnover time.
2. Freeze changes and export the record
Before removing access, record the lock brand, model, firmware, serial, account owner, administrators, users, codes, keys, credentials, hub or bridge, battery type, integrations, automations, warranty, and support case. Export access history only when lawful and necessary. Keep sensitive codes and movement records out of shared maintenance notes.
3. Audit every form of access
| Credential | Turnover action | Acceptance test |
|---|---|---|
| Owner/admin account | Transfer or confirm lawful ownership and recovery | Old owner cannot administer after handover |
| Phone key / app share | Remove user, device, home membership, and trusted session | Old phone cannot unlock locally or remotely |
| Keypad code | Delete named resident, guest, cleaner, and contractor codes | Each removed code fails; new named code works |
| Fingerprint / card / watch / wallet key | Remove from lock and linked platform | Removed credential fails at the door |
| Mechanical key | Count, recover, rekey, or replace under the property plan | Only authorized keys work |
| Voice / automation | Remove linked accounts, routines, and broad household roles | Former users cannot unlock or disarm indirectly |
4. Remove access from every connected platform
Check the lock app, Apple Home, Google Home, Alexa, alarm app, property-management platform, camera app, hub or bridge, router, password manager, mobile wallet, installer portal, and any short-term rental service. Removing a keypad code does not remove an Apple, Google, Amazon, manufacturer, or alarm-system role.
5. Rekey or account for the mechanical path
A retrofit smart lock may leave the existing cylinder and keys unchanged. Decide whether the cylinder must be rekeyed, replaced, or documented. Count owner, resident, cleaner, contractor, mailbox, garage, gate, common-entry, and emergency keys. Never disable required emergency egress or building access.
6. Inspect the door before testing electronics
Check slab, frame, hinges, strike, deadbolt, latch, weather stripping, handle, glazing, inside release, and fire-door requirements. Extend and retract the bolt by hand with the door open, then closed without pushing, pulling, lifting, or slamming. Correct alignment before recalibrating the motor.
7. Replace or verify batteries
Use the maker-approved battery type and replacement process. Record installation date and expected review date. Test low-battery warnings, emergency power, mechanical entry, and battery removal behavior without creating a lockout. Do not mix old and new cells unless the manufacturer explicitly allows it.
8. Reset only when the ownership plan requires it
A factory reset can remove users, history, calibration, integrations, and recovery, but it can also create downtime or erase evidence. Confirm authorization, export needed records, keep a mechanical key on the secure side, and document the exact reset and recommissioning steps. A reset is not a substitute for verifying every linked account.
9. Create named access for the new resident
Give each resident a named account or code with minimum permissions. Avoid one shared master code. Set guest, cleaner, contractor, and maintenance access with clear schedules and expiry. Explain who can view access history, manage users, unlock remotely, connect voice assistants, or link the lock to an alarm.
10. Test door state, auto-lock, and history
Verify locked, unlocked, open, closed, ajar, jammed, low-battery, invalid-code, and offline states where supported. Test auto-lock with the door closed and deliberately ajar. Confirm the app cannot report a secure doorway merely because the bolt extended into empty space. Check named-user and timestamp accuracy.
11. Audit alarm, camera, and automation behavior
Test whether unlocking disarms an alarm, starts a camera routine, turns on lights, changes a thermostat, or sends a notification. Define which credentials may trigger each action. Remove old residents from alarm and camera roles. Treat unlock-to-disarm as high risk and verify forced entry remains visible.
12. Run one-failure-at-a-time tests
| Failure | Safe test | Record |
|---|---|---|
| Internet down | Disconnect WAN while keeping local power | Local access, remote control, alerts, history, recovery |
| Hub or bridge down | Power off the named dependency | Direct access, integrations, fault timing, restoration |
| Phone unavailable | Lock away the owner phone | Key, keypad, resident access, support path |
| Battery unavailable | Use the maker-approved test | Warning, emergency power, key path, replacement |
| Account recovery | Verify without changing ownership | Email, MFA, trusted device, support identity checks |
Use the smart-lock acceptance test and battery/outage checklist for commissioning details.
13. Complete the handover
Give the new resident the physical keys, named credentials, owner or resident role, privacy explanation, emergency entry method, battery type, support details, fault procedure, test results, and next review date. Remove installer and temporary turnover access while all parties can verify the result. Store the record with the security-system documentation checklist.
14. Schedule post-move checks
Repeat door fit, access, battery, and history tests after 24 hours, after one week, after weather changes, and after any firmware, router, hub, account, resident, cleaner, or contractor change. Review codes and members at least quarterly and at every turnover.
Where Abode fits
For an Abode property, verify the exact lock integration, Abode app users, alarm permissions, CUE automations, camera access, event history, monitoring contacts, and outage behavior. Compare the Abode Lock, Smart Security Kit, and current Abode plans.
FAQ
Is changing the keypad code enough between tenants?
No. Audit owner and member accounts, phone keys, fingerprints, cards, wallet keys, mechanical keys, alarm roles, cameras, voice assistants, and automations.
Should a smart lock be factory-reset at every turnover?
Only when authorized and appropriate for the ownership plan. Export needed records, preserve emergency access, and verify every linked account either way.
Who should own the smart-lock account?
The lawful property arrangement should define ownership. Residents should receive named minimum access and clear privacy and recovery terms.
How do I prove an old resident no longer has access?
Test every removed code, phone, card, biometric, key, platform role, and indirect automation after revocation.
