> For the complete documentation index, see [llms.txt](https://help.paintscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.paintscout.com/support/operations/tasks/introduction-to-tasks.md). # Introduction to Tasks Overview of the tasks page including categories, filtering, sorting, and managing follow-ups linked to deals. Tasks in PaintScout are to-do items linked to [deals](/support/operations/deals/introduction-to-deals.md) that help you track sales follow-ups, production handoffs, and other job-related actions. Each task automatically connects to the related [contact](/support/contacts-and-companies/contacts-and-companies/how-to-create-a-new-contact.md) and [company](/support/contacts-and-companies/contacts-and-companies/how-to-create-a-new-company.md). For repeat workflows, use [Checklists](/support/operations/tasks/checklists.md). Checklists let you apply a reusable set of tasks to a deal in one step. {% hint style="danger" %} **Important:** this feature requires the paid **Operations add-on.** {% endhint %} *** ## The Tasks Page The Tasks page gives you a clear overview of everything you and your team need to get done.

{% hint style="warning" %} Tasks from Checklists will **not** appear on the Tasks page unless they have a due date. {% endhint %} *** ## Task Categories * **Upcoming:** This tab includes all future scheduled tasks. They only appear here when they have a due date. * **Overdue:** Tasks that are past their due date. These are highlighted in **red** for visibility. * **Completed:** Tasks that have been finished. Completed tasks appear with a **strikethrough**. * **All:** A combined view of every task, regardless of status. *** ## Filtering and Sorting * **Filter by User:** Focus on tasks assigned to specific team members.

* **Sort Tasks:** Organize by due date and time, user or more to prioritize work. * Click the **Column Sorter** icon to select which categories you'd like to filter by

*** ## Managing Tasks Each task has a **"..." (More)** menu with quick actions:

* **Edit Task:** Update details like due date, description, or assignment. * **View Deal:** Jump directly to the linked Deal for full context. * **Delete Task:** Remove a task that’s no longer needed. *** ## When to Use Checklists Use a checklist when the same set of tasks repeats across deals. This works well for sales handoffs, production kickoff, and closeout steps, or as a list of "to-dos". Add a checklist on the deal's **Tasks** tab. Tasks are assigned and dated automatically based on your checklist settings. [Learn how to use Checklists](/support/operations/tasks/checklists.md). ## Related articles


Create a Task	Create tasks in PaintScout to track reminders and follow-ups linked to deals, contacts, and companies.	Create a Task
Managing Tasks	Manage your task workflow in PaintScout — create, edit, complete, and delete tasks linked to deals for organized follow-ups and reminders.	Managing Tasks

--- # 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://help.paintscout.com/support/operations/tasks/introduction-to-tasks.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.