> For the complete documentation index, see [llms.txt](https://learn.withessential.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.withessential.com/field-operations/tasks/working-a-task-changing-its-status-and-saving-notes.md). # Working a task: changing its status and saving notes When you select a task, the full details open in the panel on the right. Toward the bottom, under Quick Actions, are the two controls you use to work the task. The Task Status dropdown lets you move the task through your workflow, for example from not started to in progress to done. The list of statuses is the set your business has configured for that kind of task, shown in their defined order. Below it is a Notes box, an internal scratchpad for this task where you can record context or what still needs doing. Some status changes can be automated. In Settings -> Work Management -> Tasks (Task Status Automations tab), your business can choose what status a task should move to when a related action happens, such as creating a visit, creating an invoice, resending to a contact, or marking an invoice paid. These notes stay with your team and are not the customer-facing description. Changing the status or editing the notes does not save on its own. A Save button sits at the bottom right, and it stays inactive until you actually change something; once you do, click Save to apply both the new status and the notes together. Cancel discards your changes and puts the status and notes back to what they were. Note that the property and customer notes shown higher up in the task header are separate records with their own small notes icon and Save, distinct from this task's own Notes box. > **Where to find it:** Open any task from the list. Its details fill the panel on the right, and near the bottom under Quick Actions you'll find a Task Status dropdown and a Notes box. ## Related guides * [How tasks are created and organized](/field-operations/tasks/how-tasks-are-created-and-organized.md) * [Quick Actions on a task: create a visit, invoice, or quote without leaving the task](/field-operations/tasks/quick-actions-on-a-task-create-a-visit-invoice-or-quote-without-leaving-the-task.md) * [Automate task statuses with Task Automations](/administration/settings/automate-task-statuses-with-task-automations.md) * [The Tasks inbox: folders, status filters, and search](/field-operations/tasks/the-tasks-inbox-folders-status-filters-and-search.md) * [What creates Deficiencies tasks](/field-operations/tasks/what-creates-deficiencies-tasks.md) * [What creates Invoices tasks](/field-operations/tasks/what-creates-invoices-tasks.md) --- # 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://learn.withessential.com/field-operations/tasks/working-a-task-changing-its-status-and-saving-notes.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.