A pool-service visit should not require broad access to the home. The safest plan gives a verified worker the smallest physical route needed for the scheduled job, keeps alarm and Apple Home authority separate, records useful arrival and departure events, and closes any temporary access as soon as the work ends.
This checklist is for recurring or one-time residential pool service: water testing, chemical treatment, filter work, cleaning, equipment inspection, and a planned repair. It is not a guide to pool operation, chemical handling, electrical work, child safety, drowning prevention, emergency response, or building-code compliance. Follow the pool professional, equipment maker, property rules, and local requirements for those jobs.
Start with a yard-only access boundary
Write the permitted route before choosing a code, camera, lock, or automation. A typical route is street or driveway to one exterior gate, then gate to pool equipment and pool deck, then back out through the same gate. The default boundary excludes the house, garage, bedrooms, offices, medicine, keys, alarm controls, network equipment, and unrelated outbuildings.
| Area or action | Default | Exception that needs approval | Proof after the visit |
|---|---|---|---|
| Driveway or front path | Transit only | Planned parking or equipment unloading | Arrival and departure times |
| Side or rear gate | One named route | Alternate gate after a documented obstruction | Gate closed and secured |
| Pool deck and equipment | Scheduled service work | Repair scope approved by the owner | Job note, photo, or service record |
| House or garage | No access | Owner present and grants a specific one-time task | Door closed, alarm state restored, access removed |
| Alarm controls | No credential | Only when the route crosses a protected interior zone | Test event and immediate credential closeout |
| Apple Home | No membership | Rare, named, time-limited need approved by the owner | User removed and automations reviewed |
A yard-only plan reduces the number of systems that can fail. It also gives the homeowner and service company a clear answer when the normal gate is blocked, a pet is loose, weather changes, equipment appears damaged, or someone asks for access beyond the written job.
Build one pool-service access sheet
Keep the operating record short enough to use on every visit. Record the service company, scheduled date and window, named worker or dispatch contact, work order, permitted gate, areas allowed, areas excluded, whether anyone will be home, pet and child constraints, access method, expected notifications, camera boundaries, alarm boundary, and the person who closes the visit.
Do not put reusable alarm codes, master lock codes, Wi-Fi passwords, Apple Account details, or hidden-key locations in a general calendar note or text thread. The sheet should identify the approved method without turning the record into a credential vault.
Verify the company, visit, and worker
Confirm the appointment through a known company channel, not only an unexpected message from a new number. Match the service window, address, work order, vehicle or worker details when provided, and the job that was approved. If the company rotates workers, use a company-controlled access process or a fresh named code for the visit instead of one permanent code shared by every crew member.
- Call or message the company using the contact already on the account when the visit changes unexpectedly.
- Do not unlock a gate because a person can name the homeowner, pool brand, or service company.
- Pause the visit when the worker, work order, requested route, or timing does not match the access sheet.
- Keep billing approval separate from permission to enter an excluded area.
Choose the lowest-authority access method
Use the first method that safely supports the job. The normal order is owner present; supervised remote gate release with live confirmation; a named temporary gate or door code with a narrow schedule; then a managed physical key with a custody record. Do not add the worker to Apple Home merely to solve an exterior gate problem.
| Method | Good fit | Main control | Closeout |
|---|---|---|---|
| Owner present | First visit, repair, or changed route | Direct identity and scope check | Inspect and relock |
| Supervised remote release | Known worker during a short window | Verify first, open once, confirm gate state | Confirm secure state |
| Named temporary code | Recurring visits with compatible hardware | Unique name, limited days and hours | Disable or delete after the final visit |
| Managed physical key | Gate hardware without supported electronic control | Numbered key and signed custody | Return, reconcile, or rekey after loss |
| Apple Home membership | Only a documented Home-control job | Named person, least authority, review date | Remove and verify loss of access |
The temporary access-code removal checklist covers the final deletion and retest. If a code must remain for recurring service, review it on a fixed date, keep it unique to that company or worker, and remove it when the contract, worker, or route changes.
Keep Apple Home and alarm authority separate
An Apple Home invite can expose controls beyond one gate, depending on the home, user permissions, accessories, and software version. Alarm disarm authority can expose protected interior zones. Neither should be the default credential for a worker who only needs the yard and pool equipment.
If a rare job truly requires Apple Home control, document the exact accessory, user, time window, and reason. Review every visible lock, garage door, camera, automation, and scene from the invited account before the visit. After removal, test that the account can no longer control the home. Use the HomeKit guest-access checklist for that separate process.
If the route crosses an alarmed interior door, make a separate decision: owner present, scheduled bypass allowed by the system and property rules, or a named alarm user with the smallest permitted authority. Never place a master alarm code in a lock-code note. The security-app permission audit helps document who can receive alerts, view cameras, use location, and change related phone settings.
Test the gate, lock, and contact sensor as one route
A code is not a complete access plan. Test the physical gate from both sides, including latch alignment, self-closing behavior, weather movement, and any pool barrier requirement that applies to the property. If a contact sensor is present, confirm that the closed state means the gate is physically latched, not merely close enough for the sensor.
- Open the gate using the exact approved method.
- Confirm the expected lock, gate, or contact event appears.
- Walk the full permitted route without entering an excluded area.
- Close the gate from the worker side and check the latch by hand.
- Confirm the app or panel returns to the correct closed state.
- Repeat with the phone unavailable and the approved fallback method.
Use the open-zone troubleshooting guide when the gate shows open after physical closure, clears intermittently, or is routinely bypassed. A misaligned sensor can make an automation look correct while the barrier remains unsecured.
Design alerts for action, not noise
Decide which events need an immediate check and which belong in the visit record. A useful set may include gate opened outside the service window, gate left open beyond the tested working interval, excluded exterior door opened, alarm state changed, camera unavailable, or the expected departure event missing.
| Event | First check | Owner action | Escalation |
|---|---|---|---|
| Early or unknown arrival | Verify with the company | Keep access closed | Follow the property incident plan |
| Gate left open | Contact the worker | Ask for physical closure and proof | Send an authorized local person if needed |
| Excluded door opened | Check people, alarm, and camera context | Protect occupants and follow the response plan | Use emergency services only for a real emergency |
| Expected event missing | Check device and network state | Do not assume the visit did not occur | Use the service record and physical inspection |
| Camera offline | Check power, network, and privacy settings | Use non-camera evidence | Repair before relying on it again |
The alert-escalation plan can assign the first checker, backup contact, response time, and safe action for each event. Avoid automations that unlock another door, disarm the alarm, or open a garage merely because a worker arrived.
Set camera boundaries before the first visit
Cameras should support the access route and property incident plan without turning the visit into unnecessary worker surveillance. Aim at the gate, approach, or equipment area that needs evidence. Exclude neighboring property, indoor windows, changing areas, and unrelated private spaces where possible. Tell the service company about recording as required by local rules and the service agreement.
Test daylight, glare from water, night reflections, foliage, rain, and movement around equipment. A bright pool surface or wet lens can hide the event that matters. Confirm the timestamp, event label, retention path, export method, and who can view footage. The security-camera privacy guide covers placement and account boundaries, while the HomeKit camera evidence-export checklist covers retrieval before an incident.
Plan for pets, children, weather, and equipment hazards
Access automation cannot decide whether the yard is safe to enter. Record whether pets may be outside, whether children or guests are present, who controls the gate during the visit, and what conditions cancel entry. Do not remotely release a gate when a pet could escape, a child is unsupervised near the pool, severe weather creates risk, or the worker reports an electrical, structural, chemical, or equipment hazard.
- Keep pet containment independent from a phone notification.
- Never use a security automation as a substitute for pool barriers or adult supervision.
- Give the worker a known contact for unexpected access or safety conditions.
- Stop the visit when the approved route is flooded, blocked, damaged, or unsafe.
- Require qualified help for work outside the original service scope.
Prepare battery, network, phone, and account fallbacks
Test failures before the service window. A worker should not become stranded inside the yard because a gate battery, phone, internet path, cloud service, hub, or account fails. The fallback must preserve required barrier behavior and should not expose a hidden master code or untracked key.
| Failure | Expected behavior | Approved fallback | Proof after recovery |
|---|---|---|---|
| Gate or lock battery low | Warning appears before failure | Replace battery or use documented emergency method | Normal lock and latch retested |
| Internet unavailable | Known local functions continue or stop | Owner present or managed physical route | Queued events and state checked |
| Owner phone unavailable | Visit does not depend on one device | Named backup owner or preapproved code | Authority record reviewed |
| Worker code fails | No repeated guessing or shared master code | Verify identity, then issue a fresh narrow method | Failed code disabled |
| Account compromise suspected | Access pauses | Use physical control and account recovery plan | Sessions, users, and credentials reviewed |
Use the smart-lock battery and lockout checklist for power planning, the internet-outage test log for network behavior, and the HomeKit account-recovery guide for owner access and trusted-device failures.
Use this visit runbook
- Before the window: verify the company, worker or dispatch contact, job, route, weather, pets, children, and access method.
- At arrival: match the expected visit before releasing access or allowing the named code window to begin.
- During work: keep access limited to the approved yard and equipment areas. Treat any scope change as a new approval.
- At departure: require the gate to close and latch, then check the expected sensor, lock, or camera event.
- After the visit: close one-time access, review unusual events, and record any equipment, gate, or account issue.
- At contract end: remove the worker and company credentials, recover keys, review automations, and run a denied-access test.
Close access and record exceptions
A completed cleaning or treatment is not the end of the security job. Confirm the gate is physically secure, excluded doors remain closed, alarm state is correct, temporary access is disabled, and no new Apple Home user, automation, trusted device, or shared code remains. Record deviations such as a different worker, alternate gate, code failure, camera outage, pet issue, weather cancellation, or gate that would not latch.
If an incident occurred, preserve facts without editing the record into a preferred story. Note timestamps, people, device state, notifications, service messages, photos or exports, actions taken, and the final physical state. The incident timeline worksheet provides a neutral format.
Run a 60-minute acceptance test before the first service visit
- Minutes 0–10: review the company, work order, yard-only boundary, pets, children, weather rules, and backup contacts.
- Minutes 10–20: use the exact access method, walk the permitted route, and confirm excluded doors stay closed.
- Minutes 20–30: close and latch the gate, then verify lock, contact, notification, and camera events.
- Minutes 30–40: test one wrong-time attempt and confirm it does not create broader access.
- Minutes 40–50: stage phone unavailable, internet unavailable, and low-battery decisions without defeating the barrier.
- Minutes 50–60: remove the temporary method, test denied access, review logs, and sign the access sheet.
Do not approve the plan until these blockers are cleared
- The service company, worker, appointment, or work order cannot be verified.
- The worker asks for house, garage, Apple Home, or alarm access that the written job does not need.
- The gate does not close and latch reliably from the worker side.
- The app reports closed while the physical gate remains unsecured.
- A permanent shared code or hidden master credential is the only available method.
- Pets, children, weather, or a site hazard make remote entry unsafe.
- The access path depends on one phone, one account, or an untested internet connection.
- Cameras record excluded private areas or cannot produce the evidence the plan assumes.
- No named person owns departure confirmation and credential closeout.
Frequently asked questions
Should a pool-service worker be added to Apple Home?
Usually no. A worker who only needs an exterior gate and pool equipment should receive a narrower physical access method. Add an Apple Home user only when a documented task needs Home control, and remove that access after the task.
Is one permanent gate code acceptable for a recurring company?
A unique company code is better than a household master code, but it still needs a schedule, owner, review date, event test, and removal rule. A named worker code provides better attribution when the hardware and company process support it.
Can a camera confirm that the pool gate is secure?
A camera can add context, but it does not replace a physical latch check or reliable contact state. Glare, weather, angle, delay, and network failure can hide or delay the event.
What happens when the worker changes?
Verify the change through the service company, remove or disable the old worker’s access, create the smallest new method if needed, and test it before the next unattended visit.
