> For the complete documentation index, see [llms.txt](https://interfacing.gitbook.io/interfacing-help-files/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://interfacing.gitbook.io/interfacing-help-files/quality-managers/task-management-application/creating-and-managing-tasks.md).
# Creating & Managing Tasks
## Workflow Overview
The **Task Management** application operates through a single, standardized workflow: the **Task Management** workflow. This workflow governs the full lifecycle of a task, from creation through closure.
IMAGE
***
## Interactive Tour
Explore the **Task Management** workflow and learn how each stage works, with key guidance and best practices along the way.
{% @howdygo/embed url="" %}
***
## Workflow Initiation
An task can be initiated through either of the following triggers.
{% tabs %}
{% tab title="Triggered by User" %}
A user may manually initiate a task when an activity requires formal assignment, execution, tracking, and review.
{% endtab %}
{% tab title="Triggered by Another Source" %}
At the [**Review & Plan Change Request**](/interfacing-help-files/end-users/change-request-application/navigating-the-change-request-management-workflow/review-and-plan-change-request.md) stage of the **Change Request Management** workflow, users may create tasks to support the implementation of the change.
{% hint style="info" %}
The task is assigned to an owner and reviewer and progresses through execution, review, and closure at the appropriate stage of the originating workflow.
{% endhint %}
{% endtab %}
{% endtabs %}
***
## Workflow Stages
This workflow is organized into **three key stages**, each with specific roles and responsibilities.
{% hint style="success" %}
For detailed instructions on any stage, click the corresponding button.
{% endhint %}
{% stepper %}
{% step %}
### Create New Task
> **Performed By:** Task Creator (e.g., Department Manager, Project Manager, Product Owner)
**Responsibilities:**
* Identify the need for a task.
* Provide the necessary details (e.g., name, priority, due date).
* Assign the appropriate owner and reviewer.
* Submit the task to initiate the workflow.
Create New Task
***
{% endstep %}
{% step %}
### Execute Task
> **Performed By:** Assigned Task Owner
**Responsibilities:**
* Accept or refuse the assigned task.
* Execute the required task activities.
* Document findings, outcomes, and supporting evidence.
* Submit the completed task for review.
Execute Task
***
{% endstep %}
{% step %}
### Manage Extension
This stage includes the **Extension Request Management** subprocess, which governs activities required to request, review, and apply additional time for task completion.
{% hint style="warning" %}
This stage is triggered only when additional time is requested to complete the task.
{% endhint %}
This workflow is organized into **two key stages**.
{% stepper %}
{% step %}
#### Request Extension for Task
> **Performed By:** Assigned Task Owner
**Responsibilities:**
* Initiate the extension request.
* Enter a proposed new due date and provide justification.
* Submit the request to initiate the workflow.
Request Extension
***
{% endstep %}
{% step %}
#### Approve or Reject Extension Request
> **Performed By:** Task Creator (e.g., Department Manager, Project Manager, Product Owner)
**Responsibilities:**
* Review the request and justification.
* Approve or reject the extension.
Approve or Reject Extension Request
***
{% endstep %}
{% endstepper %}
***
{% endstep %}
{% step %}
### Refuse Task
> **Performed By:** Task Creator (e.g., Department Manager, Project Manager, Product Owner)
**Responsibilities:**
* Review the refused task and associated feedback.
* Update task details as needed.
* Take appropriate action:
* Reassign the task
* Return the task to the existing owner
* Close the task without completion when further work is not required or feasible
Refuse Task
***
{% endstep %}
{% step %}
### Sign Off on Task
> **Performed By:** Assigned Task Reviewer
**Responsibilities:**
* Review the completed task, findings, and supporting evidence.
* Verify that the task was executed correctly and effectively.
* Assess whether the implemented task resolved or mitigated the identified issue.
* Identify any remaining risks, deficiencies, or follow-up needs.
* Approve the task to close the workflow or reject it for re-execution.
Sign Off on Task
***
{% endstep %}
{% endstepper %}
***
---
# 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://interfacing.gitbook.io/interfacing-help-files/quality-managers/task-management-application/creating-and-managing-tasks.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.