A dog walker needs a short, repeatable route through the property—not an owner account, a permanent PIN, or access to every camera. The safest setup gives one named person one time-limited entry method, proves the lock and alarm sequence at the actual walking hour, records arrival and exit, and removes access the same day the service ends.
This checklist is for recurring dog-walker visits in an occupied home. It focuses on the operating details that product pages rarely prove: code schedules, delayed arrivals, a walker entering while the alarm is armed, indoor camera privacy, a pet blocking the door, weak batteries, internet loss, and closeout. For a wider product-selection view, start with our smart locks for pet sitters guide.
Dog-walker access plan at a glance
| Control | Pass condition | Reject when |
|---|---|---|
| Identity | One named walker has a unique credential | Staff share an owner login or one permanent code |
| Schedule | The credential works only during the agreed visit window | It works overnight, on unused days, or after service ends |
| Door | Unlock, relock, latch state, and emergency entry are tested | The door can look closed while the bolt or latch is not seated |
| Alarm | The walker can follow one written arm and disarm route | A lock event is assumed to disarm the alarm without proof |
| Privacy | Only entry-route cameras and needed alerts are shared | The walker receives household-wide live view or recording access |
| Pet safety | The dog, lead, gate, and exit sequence have named checks | An app event is treated as proof that the dog is safely inside |
| Failure | There is a tested phone, battery, internet, and lockout route | The only backup depends on the same failed device or account |
| Closeout | Access is disabled, tested, and recorded after the final visit | Removal is assumed because the schedule or contract ended |
Start with the walking shift, not the lock app
Write the normal visit as a short sequence before creating any credential. Use real times and real doors. A useful record includes the earliest arrival, latest departure, entry door, alarm state on arrival, location of the dog and lead, any internal gate, camera policy, exit door, relock method, and the person who responds if something fails.
Keep the allowed window tight enough to flag an unusual visit but wide enough for normal delays. A 12:00 appointment might need access from 11:40 to 13:20, not exactly at noon and not all day. If the walker serves the home on Monday, Wednesday, and Friday, test that the credential fails on Tuesday. If the platform cannot schedule by day and time, use an owner-controlled activation routine and record when it is turned on and off.
Do not build the plan around an automation that no one can explain. The walker should have one written route that still makes sense if a phone notification is late.
Give every walker a named credential
Create a separate code or invitation for each person who may enter. Name the credential after the person, not the company. If a service sends a substitute, create a new short-lived credential for that substitute instead of sharing the regular walker’s code.
Never give the walker the owner’s smart-lock password, Apple ID, Google account, Amazon account, or full alarm administrator login. Shared accounts blur the event record and make offboarding harder. They may also expose household members, camera feeds, automations, billing, or recovery settings that are unrelated to the visit.
Record five fields for each credential:
- person and service company;
- door or lock it controls;
- allowed days and times;
- creation and expected removal dates; and
- owner responsible for the removal test.
Use our temporary access code checklist when creating and removing the credential, then add it to the household’s smart-lock code audit.
Separate lock access from alarm authority
An unlock event and an alarm disarm are different controls. Some systems can link them, but a feature label is not proof that the exact lock, hub, alarm mode, account role, and firmware behave as expected.
Choose one of three clear routes:
- Lock-only route: the alarm is already disarmed for the visit window and the walker controls only the door.
- Separate walker code: the walker has a limited alarm code and a separate lock code, with the sequence written down.
- Tested linked action: the named lock credential triggers the intended alarm change and the event log identifies the walker.
Test the exact arrival state. Arm the home as it would be before the visit. Let the walker use the real credential. Confirm entry delay, siren behavior, notifications, monitoring calls, and the event names. Repeat the test with the phone on mobile data rather than home Wi-Fi.
Do not give a service provider a master alarm code. A walker role should not be able to add users, change monitoring contacts, edit sensors, delete recordings, or change account recovery.
Prove the door closes with the dog beside it
A successful app command does not prove that a door is closed, latched, or safe. Test the door while holding the lead, carrying waste bags, and managing the dog. Look for a warped frame, stiff latch, springy weather seal, loose strike plate, or a bolt that can extend before the door is fully seated.
Run these physical checks:
- unlock from outside with the named credential;
- open the door while controlling the dog;
- close it without pulling the lead across the threshold;
- confirm the latch catches before the bolt extends;
- pull the door after locking; and
- confirm the door sensor and lock event agree.
If the dog can nose the door open, jump at the handle, reach a thumb turn, or block the sensor magnet, treat that as a failed test. Fix the physical door before relying on software.
Use arrival and exit evidence without turning the visit into surveillance
The owner needs enough evidence to know that the visit started and ended. The walker does not need access to every camera or room. A good minimum is a named unlock event, an entry-door state change, a named relock event, and an owner alert if the door remains open beyond a set limit.
If a camera covers the entry, tell the walker what it records, when it is active, who can view it, and how long clips are kept. Avoid cameras in private or changing areas. Do not place audio recording on by default; consent and recording rules vary by location.
Indoor cameras along the dog’s route need a separate decision. If they are not needed for property or animal safety, disable recording during the visit or exclude the route. If they are needed, keep the field of view narrow and the retention period short. Our home security camera privacy guide covers account access and footage retention, while the HomeKit camera privacy zones guide covers activity and recording boundaries.
Detect a missed exit instead of assuming one
The highest-risk event may be an incomplete closeout: the walker leaves, the dog remains near an open door, the lock command is sent, and no one checks the latch. Build an exception rule around evidence, not around a green app icon.
A simple owner response rule is:
- expect an unlock event inside the visit window;
- expect a door-open event soon after;
- expect a door-closed and relock event before the window ends;
- check for an open-door or unlocked state after a short grace period; and
- call the walker, then the local backup, if the state remains unresolved.
Do not automate emergency calls from one missing notification. App delivery can be delayed. The owner should verify the live state through a second signal, such as the door sensor, lock history, or a safe camera view.
Plan for substitutes and late visits
A substitute should never inherit the regular walker’s credentials. The owner should receive the substitute’s name and expected arrival before access is created. Make the credential expire after that single visit and confirm the old walker’s access remains unchanged.
If the walker is late, do not silently widen access for the rest of the day. Extend the window for a defined period, record the change, and restore the normal schedule after the visit. If repeated delays make the schedule unreliable, use an owner-controlled activation step with a backup contact rather than leaving a permanent code active.
Build a failure route that does not share the same weak point
List the failures that can happen at the door: walker phone dead, owner unreachable, lock batteries low, keypad unresponsive, hub offline, internet down, account signed out, door jammed, dog loose, or alarm sounding.
The backup route should not depend on the same failure. Examples include a mechanical key held in a sealed lockbox, exterior emergency-power contacts tested with the recommended battery, a local keypad code that works without internet, and a nearby person who can identify the walker and secure the dog.
Never hide a key under a mat or in an obvious garden object. If a lockbox is used, mount it securely, change its code after staff changes, and keep its location out of routine text threads.
Test the relevant guides before approving the route:
- smart-lock battery replacement and lockout prevention;
- smart-lock emergency power test;
- smart-lock lockout recovery; and
- home security internet outage test log.
Write a one-page dog-walker handoff
Keep the handoff short enough to use at the door. Include:
- entry address and permitted door;
- visit window and dates;
- how to use the named credential;
- alarm sequence and entry-delay time;
- dog location, lead location, gate rule, and approved route;
- camera and recording notice;
- door-closing and relock checks;
- owner and backup phone numbers;
- what to do if the dog is loose, the alarm sounds, or the lock fails; and
- final-visit access removal time.
Do not put an owner password, account recovery code, master PIN, or unprotected spare-key location in the handoff.
Run a 45-minute dog-walker access test
- Minutes 0–5: verify the walker name, credential scope, schedule, owner alert owner, and backup contact.
- Minutes 5–12: approach on mobile data, unlock the actual door, and confirm the event identifies the walker.
- Minutes 12–18: run the intended alarm sequence and verify entry delay, owner alerts, and monitoring behavior.
- Minutes 18–25: control the dog, open and close the door, check the latch and bolt, and compare lock and door-sensor state.
- Minutes 25–30: verify the camera notice, permitted views, privacy boundaries, and alert recipients.
- Minutes 30–35: disable Wi-Fi or remove internet temporarily and prove the local entry and owner response route.
- Minutes 35–40: simulate a failed keypad or dead phone and use the approved backup without sharing an owner account.
- Minutes 40–45: relock, verify the missed-exit rule, disable the credential, and prove it no longer works.
Dog-walker access scorecard
Score each item 0, 1, or 2. Zero means untested or failed, one means partly proved, and two means passed with evidence.
- named credential and owner;
- day-and-time schedule;
- entry door and physical latch;
- alarm arrival and exit route;
- dog and lead control at the threshold;
- camera notice and limited access;
- arrival and missed-exit alerts;
- phone, battery, internet, and lockout recovery;
- substitute and late-visit procedure; and
- credential removal and denial test.
A score below 16 out of 20 needs another test. Any zero for door security, dog control, account sharing, or credential removal blocks approval regardless of the total.
Do not approve the setup until these blockers are cleared
- The walker uses an owner account, permanent master code, or shared company PIN.
- The credential works outside agreed days and times.
- The physical door can remain unlatched while the app reports a lock action.
- No one has tested the alarm while it is in the real pre-visit state.
- The walker receives access to unrelated cameras, household members, or settings.
- The dog can reach the threshold before the walker has control of the lead.
- The only backup depends on the owner answering immediately.
- No one is assigned to investigate a missing exit or unlocked-door event.
- The final-visit removal test has no owner or deadline.
Close access after the final walk
Disable or delete the credential after the final confirmed visit. Then test it at the door or through the platform’s access simulator. Check the event history for any substitute, duplicate, or old code that should also be removed. Remove app invitations and camera shares separately; deleting a lock code does not necessarily revoke those permissions.
Record the removal time, person who performed it, denial-test result, any lockbox code change, and any incident that should change the next handoff. If something unusual happened, use the incident timeline worksheet while timestamps and messages are fresh.
Frequently asked questions
Should a dog walker have the owner’s smart-lock app login?
No. Use a named limited invitation or unique code. The owner login can expose household settings and makes it harder to identify who opened the door.
How long should a dog-walker code remain active?
Only for the agreed days and visit windows. Add a small buffer for normal travel delays, then disable the credential when the service ends.
Can unlocking the door disarm the alarm?
Some setups support a linked action, but test the exact lock, credential, hub, alarm mode, and account role. Do not assume a lock feature also controls the alarm.
Should indoor cameras record a dog walker?
Use only the coverage needed for safety or property security, disclose it, restrict access, and keep private areas out of view. Check local audio and video recording rules.
What if the dog walker arrives after the code window?
Extend access for a defined period, record the change, and restore the normal schedule afterward. Do not turn a late visit into permanent access.
How do I know the walker locked the door?
Look for both a named lock event and a closed-door state, then use a missed-exit rule if they do not arrive on time. A remote command alone does not prove the door latched.
