> For the complete documentation index, see [llms.txt](https://help.aphex.co/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aphex.co/docs/planner/features/delay-reasons.md).

# Delay Reasons

{% hint style="info" %}
**Who can use this feature?**

Admins can create custom Delay Reasons. Admins, Task Owners and Assignees can add Delay Reasons to Progress Updates.
{% endhint %}

Delay Reasons give context to delayed tasks, allowing the team to explain why their task didn't progress as expected from a dropdown. Every project starts with a default list of Delay Reasons, but Project Admins can edit and add custom Delay Reasons at any time.

## Create Custom Delay Reasons&#x20;

***

Creating Delay Reasons lets you build a reusable library of Delay Reasons to add when adding a delay to Tasks.

<figure><img src="https://2273109354-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLu0mYklsCTm7XQm3ZGqv%2Fuploads%2FVYaOeeB9PWlHFZJ1KCma%2FDelay%20Reason%20-%20Create%20(2).svg?alt=media&amp;token=07126ce9-9b26-49e4-803a-4ad50dc07303" alt=""><figcaption></figcaption></figure>

#### Creating a new Delay Reason:

* Open the Delay Reasons page, then click <img src="https://2273109354-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLu0mYklsCTm7XQm3ZGqv%2Fuploads%2FKHdUZEGF8Mz4VX4fSZWf%2FGroup%201.svg?alt=media&amp;token=da17ec8b-2297-46a5-a239-e286fec6cdb5" alt="" data-size="line">
* Create your custom Delay Reason by entering a name and selecting a category

<details>

<summary>Delay Categories </summary>

Each delay reason needs to belong to one of the following categories:

| Delay Categories         |
| ------------------------ |
| Delay Categories         |
| Environmental            |
| Inadequate Planning      |
| Insufficient Resources   |
| Prior Work               |
| Quality                  |
| Safety                   |
| Scope Change             |
| Submittals and Approvals |

</details>

## Filter by Delay Reason

***

Once Delays have been logged, you can filter any View to show Tasks impacted by specific Delay Reasons - or simply highlight all Tasks that have recieved any Delay at all.

<figure><img src="https://2273109354-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLu0mYklsCTm7XQm3ZGqv%2Fuploads%2Fnkvt8SgpNOD1Ls5uX5sw%2FFilted%20by%20delay%20reason%20(1).svg?alt=media&amp;token=bcc2c555-0287-4b35-9010-79ec4f25b1af" alt=""><figcaption></figcaption></figure>

#### Filter by Delay Reason:

* Click <img src="https://2273109354-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLu0mYklsCTm7XQm3ZGqv%2Fuploads%2F1uSzhSb5aSNnZd5vTaGB%2FFilter%20Button.svg?alt=media&amp;token=8ddd7f1c-0296-4af2-bdeb-d08d56fc56b6" alt="" data-size="line"> and <img src="https://2273109354-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLu0mYklsCTm7XQm3ZGqv%2Fuploads%2FbVv9qtyepRHQfkVwypud%2FText%20Buttons%20(2).svg?alt=media&amp;token=fce29edb-8b74-4d75-bfa0-d8ad7292c94b" alt="" data-size="line">
* Select `Delay Reason` in the first dropdown
* Select from `Is`, `Is Not`, `Is Empty` and `Is Not Empty` in the second dropdown
* Select your desired Delay Reason in the third dropdown

See also: create & share <a href="/docs/planner/features/view-controls.md" class="button secondary">Views</a>

<details>

<summary>Filter Breakdown</summary>

| Filter       | Operator                                           | Value        |
| ------------ | -------------------------------------------------- | ------------ |
| Delay Reason | <p>Is <br>Is Not <br>Is Empty <br>Is Not Empty</p> | Multi-select |

</details>

## Report on Delays

***

As the team starts to record delays against Tasks, all updates (including Delays, On Track & Improvement events) can be traced back to the responsible Task Owner or Subcontractor. This makes it easy to understand how all parties are performing across the project.

<figure><img src="https://2273109354-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLu0mYklsCTm7XQm3ZGqv%2Fuploads%2FhlZYh6YynLfVoW7h4Qp7%2FProduction%20Control.svg?alt=media&amp;token=195885c4-f1fc-4ebf-b8a8-b00c70282ba7" alt=""><figcaption></figcaption></figure>

#### Power BI

User Power BI to build custom reporting on delays and performance, based on data in your weekly Published Versions. Aphex provides free templates as a starting point but everything can be customised to suit your project reporting requirements.

#### Aphex Insight

Utilise Aphex Insight to track Delay Concentration by Delay Reason. See trends and drill down into specific Tasks to identify which Delay Reason has the highest delay concentration.

See also: <a href="/docs/integrations-and-api/power-bi/getting-started-with-power-bi-reporting.md" class="button secondary">Connect to Power BI</a>


---

# 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.aphex.co/docs/planner/features/delay-reasons.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.
