How do pool techs log service visits with photos?

Logging a visit happens at the stop. The technician opens the body of water on their route run, records the readings and chemicals used, adds any notes, and attaches photos of the work. On a route with signal it uploads immediately; in a dead zone it queues on the device and syncs later, so the technician never has to stop to fight the connection.

Photos are part of the proof, not a loose attachment. When a stop is completed, PoolPuma captures the device time and the GPS location along with the completion photos, and it checks the visit against a company-level proof policy. That policy is where an owner or manager sets the standard: a minimum number of photos, whether location is required, whether readings are required, and whether a skip needs a note. A manager can override the policy for a specific visit, but the override is recorded with a reason, so exceptions are visible rather than silent.

When the stop is marked done, PoolPuma freezes a snapshot onto that day’s record: the completion photos, who completed the visit and when, the captured location, and the body of water’s size at the time of service. Later edits to the pool’s profile do not rewrite that finished record, so the proof from a past visit stays exactly as it was captured.

The payoff is downstream. When a customer disputes whether a pool was serviced, or a chargeback question comes up, the office has time-stamped, located photos tied to the specific body of water, without calling the technician to reconstruct the day. Skipped stops carry their reason too, so a missed pool reads as a documented decision rather than a gap.