Offline mode

Pool equipment lives behind houses, and cell signal often does not. The tech side of PoolChecker Pro is built to shrug that off.

What works with no signal

Once a tech has opened their route with coverage (the morning driveway check is enough), the day is stored on the phone. From there, with zero bars they can still:

• Open stops and see gate codes, sticky notes, and checklists.
• Complete checklist items, enter chemistry readings, and write or dictate notes.
• Take photos and record videos.
• Complete the stop.

Everything queues on the device with an offline banner showing what is pending.

What happens when signal returns

The queue replays automatically, oldest first. Chemistry and service entries save with the time they were recorded, not the time they synced, so history stays truthful.

How conflicts are settled

If the office changed something while a tech was offline, the rules are boring on purpose:

• Chemistry and service records: the most recent edit wins. In practice these rarely collide, because only the tech at the pool is writing them.
• Routes and customer or pool details: the server's version wins, since dispatch changes from the office are authoritative.
• A genuinely ambiguous conflict is never silently discarded; it is flagged for a human to resolve. Losing field data is the one unforgivable failure, so the design never does it.

What needs signal

Anything that talks to the outside world in real time: sending an on-my-way text, navigation itself, and the customer report send. Those fire when connectivity returns or the tech taps them again.

Two habits that make offline seamless

1. Open the app before leaving the house. That caches the day. A tech who first opens the app in a dead zone starts with nothing.
2. Do not force-close the app mid-day. The queue lives happily in the background; killing the app just delays the sync.