> For the complete documentation index, see [llms.txt](https://help.agencydesk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.agencydesk.io/company-settings/rate-card/task-types.md).

# Task Types

Create and manage Task Types, including estimated times, rates, and default descriptions, to streamline team workflows and project planning.

{% stepper %}
{% step %}
Click the **+ New Task Type** button to start.
{% endstep %}

{% step %}
Add a descriptive **Task Type Name.**
{% endstep %}

{% step %}
Select the relevant **Assigned Department** for the Task you are creating.

{% hint style="info" %}
**Assigned Departments** are created in the **Departments** tab.
{% endhint %}
{% endstep %}

{% step %}
Edit the **Default Estimated Time** field for the Task.
{% endstep %}

{% step %}
Specify whether the task is **Billable** or **Non-Billable**.
{% endstep %}

{% step %}
Assign **Hourly Task Rates** for each Billing Tiers.
{% endstep %}

{% step %}
Write a **Default Description**, this can be as detailed as you'd like it to be. Task descriptions can be edited or customised when added to a Job.
{% endstep %}

{% step %}
Once all the fields have been edited with all the details, click on the **Save** button.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Some **Task** information, such as the pre-populated **Minimum Time Increment** and **Billing Tier** options can be edited or added in the **Finance** section of your Company Settings.
{% endhint %}


---

# 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.agencydesk.io/company-settings/rate-card/task-types.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.