> For the complete documentation index, see [llms.txt](https://help.tillit.cloud/tillit/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tillit.cloud/tillit/knowledge-base/setting-up-tillit/events/event-type.md).

# Event Type

### Overview

One can use Events in TilliT to trigger activities. There are 5 categories of Events:

* Equipment
* Order
* Activity
* Shift
* Custom

Apart from Custom, all these events come pre-configured in TilliT for you to use as you see fit.

### Creating a new **Event Type**

Navigation: **Settings > Configuration > Event Type > Create**

You will be presented with a pop-up.

<figure><img src="/files/efALObSDuqj3Htuo7W9i" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/HCE7IHc6R7vzR7O3AWea" alt=""><figcaption></figcaption></figure>

### **Fields**

| Name              | Description                                             |
| ----------------- | ------------------------------------------------------- |
| **Name \***       | name of the event.                                      |
| **Closing Event** | select an event that, when started, closes this event.  |
| **Subtitle**      | a description of the event                              |
| **Priority \***   | the numerical priority of the event                     |
| **Display Order** | the order in which the event is shown throughout the UI |
| **System Event**  | tie your custom event to a TilliT system event.         |

Click the ***Save and close*** button to finalise.

{% hint style="info" %}
This event is now available as a trigger for activities and closing events.
{% endhint %}

## Downtime Types

TilliT includes the following built-in downtime types that can be used when raising equipment events:

| Downtime Type   | Description                                                                     |
| --------------- | ------------------------------------------------------------------------------- |
| **UNPLANNED**   | Unplanned equipment downtime not attributable to a specific cause.              |
| **BREAKDOWN**   | Equipment breakdown events, tracked separately from general unplanned downtime. |
| **PLANNED**     | Scheduled downtime such as maintenance windows.                                 |
| **UNAVAILABLE** | Periods where the asset is not available, such as shift breaks.                 |

BREAKDOWN is a distinct downtime type that allows breakdown events to be reported and analysed separately from UNPLANNED downtime.


---

# 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://help.tillit.cloud/tillit/knowledge-base/setting-up-tillit/events/event-type.md?ask=<question>&goal=<endgoal>
```

`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.