> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.12/investigate-and-respond-to-threats/day-to-day-tasks-in-cortex-xsoar/incident-management/work-plan.md).

# Work Plan

Monitor and manage incident playbook workflows in Cortex XSOAR 6.12.

The Work Plan is a visual representation of the running [playbook](/xsoar-6-administrator-guide/6.12/configure-cortex-xsoar/customize-and-configure-cortex-xsoar/playbooks/playbook-development.md) that is assigned to the incident. Playbooks enable you to automate many of your security processes, including, but not limited to handling your investigations and managing your tickets. Work Plans enable you to monitor and manage a Playbook work flow, and add new tasks to tailor the Playbook to a specific investigation.

When clicking the **Follow** checkbox you can see the Playbook executing in real-time.

In the Work Plan you can do the following:

* View [inputs and outputs](/xsoar-6-administrator-guide/6.12/configure-cortex-xsoar/customize-and-configure-cortex-xsoar/playbooks/playbook-inputs-and-outputs.md) of a playbook.
* View, create, and edit a [playbook task](/xsoar-6-administrator-guide/6.12/configure-cortex-xsoar/customize-and-configure-cortex-xsoar/playbooks/playbook-task-fields.md) for each required step.

  When you create a task, add a name, automation, and description. The name and description should be meaningful so that the task corresponds to the data that you are collecting.

  For each task you can do the following:

  Designate tasks as complete either manually or by running a script.

  Assign an owner for a task.

  Set a due date for the task.

  Add comments and completed notes, as required.
* Re-run the playbook, zoom in and out, and export to a PNG format.

The color coding and symbols in the Work Plan help you to easily troubleshoot errors or respond to manual steps. The following table displays the color codes and their meanings.

![incident-color-coding.png](https://4128117757-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9gZ0C5CI8Bl5Aulkp4dZ%2Fuploads%2Fgit-blob-393c82ef80b00fb8ab25e789485cdf64c97e65ad%2F7df1d820c24a1c6d435698f4cb02c0b09910fea5f59a5b6b75b9334e2c3a62d2.png?alt=media)


---

# 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://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.12/investigate-and-respond-to-threats/day-to-day-tasks-in-cortex-xsoar/incident-management/work-plan.md?ask=<question>&goal=<user_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.