On your own confirmed route, you can report that a customer is not at home, will be available later, wants to cancel or has an urgent appointment. You can also report when you will become unavailable. A planner can record the same events on a route. No reason or health information is requested.
For a customer who is available later, choose when they will be available again. For an employee, choose when their unavailability starts. Times follow the workspace time zone. Reporting an event does not reschedule, cancel or reassign an appointment and sends no customer message.
Skip this stop is a separate, explicit action. It marks the selected open, travelling or arrived stop as skipped. The appointment, hours and evidence remain. Reporting that the customer is not at home does not skip the stop. For a new visit after work has started or a stop has been skipped, the planner creates a separate calendar appointment.
Reporting exceptions and replanning require a connection. On an error, values remain on the open screen. Receipt is confirmed only when the response says so. This input is not an offline draft: closing or refreshing the screen may lose it. The existing limited offline status controls for a previously opened route stay the same.
The planner chooses a received event and requests a suggested allocation, or deliberately chooses an employee, times and optional cancellation for open work. A cancellation request does not cancel automatically. Urgency cannot override skills, availability or other hard limits.
Started and other protected work remains exactly as it was, with the same stop, employee, times and evidence. Open follow-up work after execution needs an explicit estimate at the last protected stop: its existing location, estimated availability and remaining work there. This is not a live GPS location. Missing information stays unknown; an empty estimate is not treated as zero.
Saving opens a proposal showing violations and unknown information. Applying always requires a human R2 signature and a current source. A changed route or day source requires reloading and checking again. The proposal sends no customer message. Customer emails go through a separate human R3 review.