> 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/task-performance.md). # Task performance Receive notifications for field task events: task completion, delays, failures, arrivals, and form submissions. Applies to tasks assigned to field employees. ## Overview The Task performance rule is designed to help companies track and manage the progress and completion of tasks assigned to field employees. Whether you're overseeing a large remote workforce or a smaller team, this rule ensures you stay informed about critical task-related events, such as task completion, delays, failures, and form submissions. ![](https://2096203889-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F446mKak1zDrGv70ahuYZ%2Fuploads%2Fgit-blob-212b91c5af2d091b47864a6496e90d1ee4178544%2Fimage-20240808-235145.png?alt=media) The Navixy platform provides timely notifications via SMS, email, push notifications, or directly within the web user interface. By using this functionality, businesses can maintain control over the task completion process, leading to improved efficiency and decision-making. ## Rule settings ### Task events and statuses In the rule settings, specify the task statuses and events for which you want to receive notifications. You can choose from options such as task completion, delays, failures, arrivals, and form submissions. By selecting the relevant options, companies can stay informed about key developments in their field operations, helping to minimize disruptions and ensure smooth task execution. For common settings, see [Rules and alerts](/docs/user/guide/events-and-notifications.md). ## System operation details * The **Task performance** alert is triggered every time a task-related event occurs, with no reset timer, meaning the alert notifies you immediately with each event. This differs from other rules on the Navixy platform that have reset timers to limit notification frequency. * This rule is cloud-processed and is not dependent on specific hardware, allowing it to be applied to multiple GPS devices simultaneously. This flexibility enables users to manage several GPS devices within a single rule efficiently. --- # 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/task-performance.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.