> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/user/guide/events-and-notifications/scheduling-and-dispatching.md). # Scheduling and dispatching Alert rules for fleet dispatch: route deviation, driving time limits, driver identification and absence, task performance, and work status changes. The **Scheduling and dispatching** section covers alert rules for fleet dispatch operations, including route deviation, driving and parking time limits, driver identification, task performance, and work status changes. * [**Deviation from the route**](/docs/user/guide/events-and-notifications/scheduling-and-dispatching/deviation-from-the-route.md): Notifies when a vehicle deviates from a predefined route, using route-type geofences. * [**Driver absence**](/docs/user/guide/events-and-notifications/scheduling-and-dispatching/driver-absence.md): Detects when a driver is absent from the seat while the vehicle is in operation, using AI-equipped cameras. * [**Driver change**](/docs/user/guide/events-and-notifications/scheduling-and-dispatching/driver-change.md): Tracks driver changes on shared vehicles by detecting when a new hardware key (iButton, RFID, or BLE) is used. * [**Driver identification**](/docs/user/guide/events-and-notifications/scheduling-and-dispatching/driver-identification.md): Tracks driver identification events via iButton, RFID, or facial recognition to confirm authorized drivers. * [**Driving time**](/docs/user/guide/events-and-notifications/scheduling-and-dispatching/driving-time.md): Alerts when a driver exceeds the allowed continuous driving time, with a configurable parking time to reset the timer. * [**Parking time**](/docs/user/guide/events-and-notifications/scheduling-and-dispatching/parking-time.md): Notifies when a vehicle remains parked beyond a configured time limit, and can be bound to geofences. * [**Task performance**](/docs/user/guide/events-and-notifications/scheduling-and-dispatching/task-performance.md): Sends notifications for field task events such as completion, delays, failures, arrivals, and form submissions. * [**Work status change**](/docs/user/guide/events-and-notifications/scheduling-and-dispatching/work-status-change.md): Notifies when a field employee updates their work status via the X-GPS Tracker app. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://navixy.com/docs/user/guide/events-and-notifications/scheduling-and-dispatching.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.