Skips, rainouts, and time off

Plans meet weather, locked gates, and sick days. Each situation has a tool, and each tool has different side effects.

One stop: Skip & Reschedule

On the stop screen (or from the route), Skip & Reschedule moves a single visit to tomorrow or to the pool's next regular service day. The original stop is marked skipped, the new one is created, both days' totals update, and you can optionally text the customer about the change (consent permitting; it falls back to email).

Use it for locked gates, a dog in the yard, or "customer asked to push a day". The skipped stop stays visible in the day's history, so you can always answer "why did we not service this pool on Tuesday".

The whole day: End Route

Ending a route that still has open stops opens a decision screen: for each remaining stop, pick reschedule to next service day (optionally notifying the customer) or plain skip. Nothing silently disappears; you decide per pool. This is the rainout tool: three taps and the washed-out afternoon is rebooked properly.

A person: Time Off

Approved time off (on the Team page's Time Off tab) does two things automatically: removes the tech's routes inside the leave window, and re-plans those pools onto adjacent days or other techs where possible. Pools that could not be absorbed are surfaced for manual placement rather than silently dropped, so check the routes for the leave window after approving.

This connects to pay: approved PTO hours flow into timesheets as paid, non-overtime hours (see Timesheets, overtime, and pay).

What customers experience

Every reschedule path can send a schedule-change message, controlled by the toggle in Settings, Notification Preferences. If you keep it on, a rainout day becomes thirty seconds of work AND every affected customer knows before they notice the missed visit. That message is most of the perceived professionalism.

What does NOT exist

There is no undo for route changes. A skipped stop can be re-added by scheduling a visit, but the original ordering of a day is not recoverable, which is why the calendar drag (move, not destroy) beats re-optimizing when you just need to shuffle.