> For the complete documentation index, see [llms.txt](https://docs.powerall.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.powerall.app/en/service/work-orders/work-types.md).

# Work types

In Powerall, as a user, you can define various hourly rates for the work performed on a [Work receipt activity](/en/service/work-orders/activities.md). This can be done using work types. On the work type, you record the following data:

* Description, which you see when you select the work type in the hours line
* A type, this determines whether it can be used for worked hours or for break time
* The [item](/en/parts/items.md), this determines the hourly rate on the hours line of the Work receipt activity
* The [order type](/en/configuration/order-types.md), this determines whether the hours are included in invoicing or not.
*

In practice, you can use work types for the following situations, for example:

* Using a different hourly rate for certain work, such as welding
* Using a different hourly rate for breaks
* Using a different hourly rate for an apprentice mechanic and an experienced mechanic

Powerall offers complete freedom in the number of work types you configure. This allows you to set up time registration perfectly to match the way your company works!


---

# 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://docs.powerall.app/en/service/work-orders/work-types.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.