A smart lock is only as controlled as its current user list. Audit every code, app account, key, automation, and recovery path after a guest stay, contractor visit, roommate change, move, lost phone, or household staffing change. The goal is not to delete everything. It is to know who can enter, through which door, during which hours, and how that access will be removed.
Smart-lock access audit at a glance
| Access type | Verify | Action |
|---|---|---|
| Owner/admin account | Named owner, recovery email/phone, MFA, current devices | Remove shared admin logins and stale devices |
| Permanent household code | One named person per code | Replace shared codes with individual codes |
| Guest code | Purpose, start/end time, door scope | Expire after the visit |
| Contractor or cleaner | Scheduled window and work order | Use temporary access; revoke after handover |
| Former resident or employee | Codes, app membership, keys, automations | Remove in a written offboarding sequence |
| Physical key or key box | Holder, copies, storage, return status | Rekey if custody is uncertain |
1. Export or record the current access list
Before changing anything, capture the lock name, door, owner account, admins, members, codes, schedules, linked home platform, bridge or hub, physical keys, and recovery method. Use names such as “Pat — dog walker” instead of “Guest 3.” If the lock cannot label codes, maintain a protected code register that records purpose and expiry without exposing the code itself.
2. Separate admin, household, and temporary access
- Admin: can change users, settings, integrations, and recovery. Keep this group small.
- Household: regular entry without system administration.
- Temporary: guests, cleaners, trades, carers, pet sitters, and deliveries with a defined window.
- Emergency: a tested fallback for an authorized contact, stored and reviewed separately.
Do not reuse an alarm master code as a lock code. Do not give contractors the owner account merely because temporary access is inconvenient.
3. Check every code against a person and purpose
For each code, answer five questions: Who uses it? Which door opens? When should it work? When was it last needed? Who owns revocation? Delete unknown codes only after confirming they are not tied to an emergency plan, accessibility need, property manager, or service agreement.
4. Audit schedules and door scope
A cleaner may need Tuesday access to the side door, not permanent access to every exterior lock. A short-term guest may need entry for a weekend, not until someone remembers to delete the code. Test scheduled access at the beginning, during, and after the permitted window. Confirm the lock uses the correct time zone after daylight-saving, router, hub, or firmware changes.
5. Remove access in the right order
- Preserve any access history required for a dispute, incident, or handover.
- Confirm the person no longer needs legitimate entry.
- Remove the app member and lock code.
- Remove Apple Home, Google Home, Alexa, alarm, camera, garage, and property-management access separately.
- Collect physical keys, fobs, remotes, and key-box details.
- Test the removed code and account at the door.
- Record who completed the offboarding and when.
6. Review event history without over-trusting it
Named code events can help confirm normal access, but a log is not perfect proof of identity. Codes can be shared, doors can be left open, manual keys may not appear, clocks can drift, and offline locks may sync late. Use the log to investigate exceptions, then confirm with the people involved and other lawful evidence.
7. Test batteries, connectivity, and local entry
Run the smart-lock battery and outage checklist. Verify the physical key or approved backup, low-battery warning, keypad, app, bridge, hub, Wi-Fi, local operation, and behavior during internet and power failures. Access control is incomplete if the household cannot enter when the owner’s phone or cloud service is unavailable.
8. Coordinate the lock with the alarm
Decide whether unlocking should disarm the alarm and whether that automation is safe for every user. A temporary lock code should not silently grant permanent alarm, camera, or admin access. Test the door sensor, entry delay, siren, notifications, and monitoring process with the provider’s approved test mode.
9. Protect privacy and recovery
Use individual accounts, strong unique passwords, multi-factor authentication where supported, current recovery details, and named household roles. Review the guest-access guide and installer-access checklist when access also reaches cameras, alarm settings, or network equipment.
10. Set an audit cadence
Review access quarterly and immediately after a resident, employee, cleaner, contractor, carer, guest, property manager, phone, hub, or lock changes. A useful audit ends with zero unknown codes, a named owner for each active credential, a tested fallback, and a date for the next review.
Where Abode fits
For a sensor-led system around smart-lock access, compare the Abode Smart Security Kit, the current Abode plans, and the Abode Lock. Verify current lock fit, code roles, supported integrations, automations, event history, backup entry, and monitoring behavior for the exact setup before buying.
FAQ
How often should smart-lock codes be audited?
Quarterly is a useful baseline, with an immediate audit after any resident, guest, contractor, cleaner, carer, employee, phone, account, hub, or lock change.
Should every person have a separate code?
Yes where the lock supports it. Named codes make access easier to revoke and exceptions easier to investigate without changing every household member’s credential.
Is deleting a lock code enough when someone leaves?
No. Remove app membership, home-platform access, alarm and camera roles, garage access, physical keys, fobs, remotes, and recovery access separately, then test the removed credential.
Can a smart-lock event log prove who entered?
Not by itself. Codes can be shared, clocks can drift, and physical keys or open doors may bypass the recorded event. Treat logs as one source of evidence.
Turn the code audit into a tested access-control loop
A list of active codes is only the start. A useful audit connects each credential to a person, a door, an approved time window, a fallback, and a removal test. That turns the spreadsheet or app screen into an operating control the household can check after a guest stay, contractor visit, move, lost phone, or account change.
Use one row per person and access path. Record the lock name, door, credential type, owner, purpose, start date, expiry or review date, backup entry method, linked platforms, and the person responsible for removal. If the same person has a keypad code, app membership, physical key, voice-assistant access, garage remote, and alarm role, list them separately. Removing one route does not remove the others.
| Audit field | What to record | Pass condition |
|---|---|---|
| Identity | Named person, owner, and reason for access | No shared or unexplained credential remains |
| Door scope | Exact lock and physical entrance | The credential opens only the intended route |
| Time scope | Start, end, recurring schedule, and time zone | Access works only during the approved window |
| Linked systems | App, alarm, camera, garage, Apple Home, Alexa, Google Home, or property platform | Every linked role has a named owner and separate removal step |
| Fallback | Mechanical key or other owner-controlled entry path | The household can enter during a phone, account, battery, or network failure |
| Evidence | Creation, use, denial, removal, and retest record | The owner can show what was tested and when |
Link the audit to the physical fallback
A code review can look complete while the backup key is missing, mislabeled, held by the wrong person, or unable to turn a stiff cylinder. Run the smart-lock mechanical-key backup checklist for every exterior lock. Confirm the exact key, storage owner, retrieval path, cylinder operation, and handoff record. Do not put a key location, safe code, or recovery secret in a broadly shared audit file.
Link the audit to door state and auto-lock behavior
Removing an old code does not help if the door regularly stays unlatched or the bolt cannot travel cleanly. Use the smart-lock auto-lock checklist to test open-door behavior, close detection, delay, manual override, guest entry, alignment, and failure alerts. Run the test with the door open and closed. A successful app command with a rubbing bolt is not a pass.
Link the audit to documentation ownership
Record the installed model, serial number, door, battery type, app owner, second verified owner, support route, warranty record, and reset instructions in the home-security system documentation checklist. Keep recovery details in an owner-controlled location. The access audit should point to the record, not duplicate passwords, recovery codes, or sensitive key locations.
Link offboarding to account and data removal
When a resident, contractor, cleaner, carer, property manager, or owner account leaves, follow the account deletion and data export checklist. Preserve the records the household lawfully needs, transfer ownership first, remove the person from every connected platform, revoke sessions, rotate exposed shared secrets, and test a denied attempt. Do not factory-reset the lock before confirming that another verified owner can manage it.
Run a 45-minute smart-lock access audit test
- Minutes 0–8: Export or photograph the current code, user, key, app, and platform lists without exposing them in a shared channel.
- Minutes 8–15: Match every credential to a named person, door, purpose, owner, and review or expiry date. Flag anything unknown.
- Minutes 15–22: Test one resident credential and one temporary credential during the intended time window. Confirm the correct door and linked alarm behavior.
- Minutes 22–28: Test the approved physical fallback and closed-door bolt travel. Check low-battery and offline instructions without creating an unsafe lockout.
- Minutes 28–35: Remove a disposable test credential from the lock and every linked platform. Revoke the test app session where supported.
- Minutes 35–40: Try the removed credential at the door and from the app. A denial is the pass condition; record any delayed sync or surviving route.
- Minutes 40–45: Record failures, owners, deadlines, and the next audit date. Keep the live system in its normal state and confirm the household still has two owner-controlled recovery paths.
The final record should show zero unknown codes, one owner for every active route, a tested denial for removed access, a working physical fallback, and a dated repair list. If a credential cannot be explained or removed safely, disable it only after confirming another owner and entry path. Treat unexplained administrator access as an account-security incident, not a paperwork problem.