Updated August 2026.
A temporary smart-lock code should answer four questions: who can use it, which door it controls, when it works, and who proves it no longer works. This checklist covers the full path from approval to removal. It is designed for cleaners, dog walkers, contractors, carers, short-term guests, deliveries, and emergency access.
Smart-lock apps, alarm integrations, user limits, code schedules, event history, remote access, plans, and supported hubs change. Confirm the exact model and current maker instructions before using a code for a live property. Keep a mechanical key or another owner-controlled recovery route.
Create one access record before creating the code
| Field | Required record | Failure to avoid |
|---|---|---|
| Person | Real name, role, contact, approver, and identity check | Generic “cleaner” or “guest” codes shared by several people |
| Door | Exact building, entrance, lock, keypad, door sensor, and fallback key | A code works at more doors than the visit requires |
| Window | Start date, end date, days, hours, time zone, and late-arrival rule | A one-hour visit becomes permanent access |
| Permissions | Unlock, lock, app control, history, remote use, alarm, cameras, and garage access | Lock access quietly grants unrelated system access |
| Owner | Person who creates, tests, monitors, removes, and closes the record | Everyone assumes somebody else removed the code |
Use one named code per person
Do not reuse the household PIN or hand a contractor an owner account. Create a unique code for one person and purpose. Avoid birthdays, addresses, repeated digits, phone-number fragments, and codes used on another property. Do not send the code in the same message as the property address and alarm instructions.
If the lock supports schedules, use the narrowest window that still allows a normal arrival delay. Record the time zone and daylight-saving behavior for second homes and remote managers. If schedules are unavailable, create the code immediately before the visit and assign a named person to remove it immediately after.
Separate lock access from alarm and camera access
| System | Question | Independent removal check |
|---|---|---|
| Smart lock | Can the person unlock locally, remotely, or both? | Old PIN, fingerprint, app session, voice route, and invitation all fail |
| Alarm | Does a lock event arm, disarm, delay, or silence anything? | Retired alarm PIN and user fail without changing owner access |
| Apple Home or another platform | Was the person added as a resident, guest, or app user? | Home invitation, scenes, automations, and shared devices are reviewed separately |
| Cameras and doorbell | Can the person view live video, recordings, or notifications? | Camera share and saved session fail on the person’s device |
| Garage, gate, or building entry | Does the route need another credential? | Every remote, code, app, badge, and intercom record is retired |
For Apple Home households, use the HomeKit guest-access checklist and member-removal checklist. A lock code can remain active after a Home guest is removed, and a vendor account can remain signed in after the code is deleted.
Test the code at the physical door
- Stand outside with the door closed, latched, and aligned. Keep an owner and recovery key available.
- Enter one wrong code and confirm the lock rejects it without exposing useful account or code details.
- Enter the temporary code during the approved window. Record unlock response, door-sensor state, event name, time, notifications, and any alarm effect.
- Lock the door from outside. Pull and push the door to prove the bolt and latch are physically engaged.
- Try the code before and after the approved window. Confirm both attempts fail.
- Check the event on a second administrator’s phone. The record should identify the right person or code, door, action, and time where the product supports it.
Plan for low battery, poor alignment, and outages
A valid code does not help if the keypad has no power, the bolt binds, the bridge is offline, or the app owner cannot be reached. Record battery type, warning behavior, replacement date, keypad lighting, cold-weather limits, door alignment, Wi-Fi or radio path, bridge, internet dependency, and mechanical entry.
Run a controlled test with internet disconnected. If the product supports local keypad operation, prove the temporary code works or fails as expected without internet. Then restore service and check queued events, clocks, schedules, stale state, and notifications. Never discover the offline behavior during a real visit.
Use entry events without exposing private spaces
An exterior camera can verify an approach, but access does not automatically justify indoor camera access. Record each lawful view, recording rule, retention period, shared user, and disclosure. Keep cameras out of bedrooms, bathrooms, and other private spaces. Use a direct door sensor to confirm opening and closing rather than treating camera classification as a door state.
The smart-lock security checklist covers physical fit, account control, integrations, and outage tests. The lockout-recovery checklist covers failed batteries, phones, networks, and ownership recovery.
Remove the code and prove removal
- Remove or expire the named code in the lock system.
- Remove the person’s lock-app account, fingerprint, remote session, voice permission, and shared-home access where applicable.
- Remove separate alarm users, camera shares, garage accounts, gate codes, intercom records, Wi-Fi access, and saved tablets.
- At the physical keypad, enter the retired code during its old allowed window. It must fail.
- Enter an owner code and use the mechanical key to prove authorized recovery still works.
- Check history and notifications. Record the failed retired-code test and the successful owner test.
- Close the record with removal time, tester, evidence, exceptions, and next audit date.
Recurring-worker audit
For cleaners, carers, dog walkers, and property staff, review access monthly. Match every active code to a real person and current job. Remove generic, duplicate, dormant, and former-worker codes. Test the busiest entrance, the second administrator, the recovery key, and the outage path. Review household changes after a move, separation, lost phone, changed contractor, or ownership transfer.
Abode lock and sensor planning
For an Abode setup, compare the current Abode Lock, Mini Door/Window Sensor, Smart Security Kit, and plans. Verify the exact lock, keypad, user and code limits, schedules, remote access, event history, hub requirements, alarm behavior, integrations, service state, and mechanical fit before purchase.
FAQ
Should every visitor use the same smart-lock code?
No. Give each person a named code with the smallest useful time window. A shared code hides who used the door and makes removal harder.
When should a temporary smart-lock code be removed?
Set an end time when the code is created, then verify that it fails after the visit. Also remove linked app users, alarm users, camera shares, and garage access separately.
Does deleting a code from an app prove the door is secure?
No. Test the retired code at the physical keypad, check the event history, confirm the door closes and latches, and keep a mechanical recovery route.
Can a smart-lock code disarm a security system?
That depends on the exact lock, alarm, integration, user, automation, and service. Keep unlock and disarm as separate jobs unless the documented setup and a controlled test prove the intended behavior.
