What happens to data when a tech leaves?

Technician turnover is one of the real risks in this business. When a route lived in one tech’s head or on their personal notes, their departure took the pool’s history with them. PoolPuma is built so that does not happen.

Every service visit is anchored to the body of water it happened at, not to a route run, a schedule, or the individual technician. That is the key design decision. It means each pool and spa carries a continuous service history, readings, chemicals used, notes, skip reasons, and proof photos, independent of who performed any single visit. A pool serviced by three different techs over two years still shows one unbroken record, because the history belongs to the asset, not the person.

So when a technician leaves, the company keeps everything. You disable that person’s login through user management, which stops their access, and the routes, visits, and history they touched remain intact under the account. The next tech who picks up those stops opens each pool and sees exactly how its chemistry has behaved and what was done last, so they are not starting blind.

Completed visits are also frozen at the time of service. When a stop was marked done, PoolPuma captured a snapshot, the photos, who completed it and when, the location, and the pool’s size that day, and later profile edits do not rewrite it. So a departing tech cannot quietly alter old records on the way out, and the history you rely on stays accurate.

The practical effect is continuity. Onboarding a replacement is faster because the knowledge is in the system, customer questions still get answered from the record, and the business owns its own operational memory rather than renting it from whoever happens to run the route this month.