> 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/cortex-xsoar-8-on-prem/8.5/investigate-and-respond-to-threats/incidents-and-indicators-investigation/investigate-an-incident/use-the-work-plan-in-an-investigation.md).
# Use the Work Plan in an investigation
The Work Plan is a visual representation of the running playbook assigned to the incident. Playbooks enable you to automate many security processes, such as managing your investigations and handling tickets. Work Plans enable you to monitor and manage a playbook workflow, and add new tasks to tailor the playbook to a specific investigation.
In an investigation, when you open the **Work Plan** tab, you can see the playbook, the playbook name, and navigation tools.
By default, the **Follow** checkbox is checked, which allows you to see the playbook executing in real-time. The playbook moves when a task is completed.
In the Work Plan you can do the following:
| Action | Description |
| --------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Change the default playbook | On the left-hand side of the window, select the playbook you want to run.
When changing the playbook, all completed tasks are removed and the new playbook will run. If you select playbooks several times you can view the history of which playbooks ran.
|
| Rerun the playbook | When changing the playbook, select the current playbook to run again. |
| View inputs and outputs | View the inputs and outputs of each task that has run. You can't view inputs and outputs of any task that hasn't run. |
| Manage tasks | View, create, and edit a playbook task. For each task, you can do the following:
- Designate tasks as complete either manually or by running a script.
- Assign an owner
- Set a due date
- Add comments and completed notes, as required.
You can manage these tasks in the CLI by using the /task command. For more information about tasks, see Incident Tasks.
|
| Export to a PNG | Export the Work plan to a PNG format for easy analysis. |
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 playbook tasks and icons in the Work Plan.
{% hint style="info" %}
### Important
A playbook will not continue its execution path if a prior task has failed; you must resolve the failed task before subsequent tasks can run.
{% endhint %}
Playbook tasks and icons in the Work Plan
| Task | Description |
| ----------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|  | Standard automated task
The arrow and lightning bolt indicate a standard automated task. This task does not require any analyst intervention. They turn green automatically if they are successful.
|
|  | Standard manual task
The arrow indicates a standard manual task. These tasks are used where usually it's not possible to automate them. You can add comments, assign them to an owner, and set a due date.
You need to complete it before the Work Plan can continue.
|
|  | Conditional task
The diamond indicates a conditional task, which is either an automated conditional task (with the lightning bolt) or a manual conditional task. These tasks are used as decision trees in your work plan.
|
|  | Data collection task
The speech bubble indicates a data-collection task. This task prompts you to respond to multi-questions.
|
|  | Active task
The gear icon indicates an active task.
|
|  | Completed task
The green check mark indicates a completed task.
|
|  | Overdue task
The clock icon indicates the task is overdue.
|
|  | Pending manual task
The orange user icon indicates that the playbook is pending action. The task requires you to open it and manually mark it as complete.
|
|  | Failed task
The red warning icon indicates that the automation failed to complete as expected and requires manual inspection and troubleshooting. Contact your Cortex XSOAR administrator.
|
|  | Skipped missing content
The skipped task due to missing content, such as a missing integration.
|
|  | Sub-playbook task
The workflow icon indicates that the task is a playbook nested within the parent playbook. You can view that playbook by opening the task and selecting Open sub-playbook.
|
### **Add ad-hoc tasks to a Work Plan as part of your investigation**
As part of your incident investigation, within the Work Plan you can create tasks for a specific iteration of a playbook. The task type can be an automation or another playbook. For example, within a manual task, you might need to enrich some data and run an investigation playbook.
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.
1. In the Work Plan, go to the task where you want to add and click the + sign at the bottom right-hand corner of the task.
The ad-hoc task is added after the task on which you clicked.
2. Select the task type.
* Standard: Runs a single automation.
* Playbook: Runs a playbook to enhance the investigation.
The playbook functions as any playbook would and requires you to define the inputs and outputs, as well as any other details.
3. Click **Save**.
4. To run the Work Plan again, click the **Run again** icon.
Example 28.
For a phishing investigation, after the initial playbook run parses the email and extracts email addresses, as part of the manual investigation, you could use the **Email Address Enrichment - Generic v2.1** playbook as an ad-hoc playbook task to get more information about these email addresses.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://cortex-docs.paloaltonetworks.com/cortex-xsoar-8-on-prem/8.5/investigate-and-respond-to-threats/incidents-and-indicators-investigation/investigate-an-incident/use-the-work-plan-in-an-investigation.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.