> For the complete documentation index, see [llms.txt](https://ynteq.gitbook.io/ynteq-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ynteq.gitbook.io/ynteq-docs/ynteq-features/managing-work-orders.md).
# Managing Work Orders
On this page, you manage your daily activities. With a single overview of all work orders, you can filter on the ones that are assigned to you and inspect the type, asset, due date and action. When executing, you open the pop-up menu you have all the information you need to get to work.
### Filters
In this overview it is possible to use filters to customize your view. The available filters are
* **Time Period,** within the work order overview it is possible to create an overview per day, week, month or year.
* **Status,** as work orders have different statusses (see ..) it is possible to filter on work orders with a specific status.
* **Priority,** work orders have four possible priorities (ranging from low to urgent).
* **Work type,** each work order can be marked as a certain type, Ynteq comes with a list of default types, but these can also be changed within the settings menu.
* **Owner,** (verschil tussen owner and assigned to)
In the overview the visible list can be ordered on every work order property. For status, priority and type it is possible to change it directly from the overview. To change other elements one needs to open & edit the work order. Please note that overdue work-orders will always remain visible, also if the due date is long in the past. These work orders can be removed by changing the status to cancelled or completed. Finally, work orders in bold are new (not-opened yet).
## Creating work orders
With the top right button it is possible to create a work order. The work order form pops up and asks the following information.
Every work order should be given a title, a due date (default is today), work type and priority. From the asset structure one can chose the right asset for the work order. Furthermore it is possible to give the work order an description and subtasks to provide more information for the person working on the task.
## Executing work orders
To execute a work-order, one simply click on the work-order in the overview to access the following menu.
Here all the information and optional files are visible. One can start/pause/complete a work-order with this simple interface. This allows for time-tracking of how much work is needed at the asset. Tip: Sometimes time-tracking is incorrect (for instance, when you forget to turn it off during a break). You can always edit the time when a work order is completed.
It is also possible to provide feedback here after completing the work order. Just mention what you did. Also, to build a more systematic history, you can use the tags functionality.
Furthermore it is possible to edit the work-order by hitting the editing button in the top right corner.
---
# 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://ynteq.gitbook.io/ynteq-docs/ynteq-features/managing-work-orders.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.