> 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-requests.md).
# Managing Requests
Operators are the eyes and ears in the factory. The Ynteq CMMS makes it very easy for them to collect their input in “work order requests”. The head of the maintenance team will then evaluate the work requests and turn them in work-orders or decline them with feedback.
## Creating Work Requests
To create a work request you click the button in the top right corner of the screen to access the following form.
A new work request needs a title and has to be connected to the correct asset. Furthermore it is possible to provide more information with a description or an image. The contact details are deafult to be your own, since you will be informed with the decision of the follow-up.
## Reviewing Work Requests
In the overview of all incoming work request bold request will mean they have not been opened yet. To review a work request you click on the specific work request from the list.
Now there are to options, either to decline the work request or to turn it into a work order. For both options there is the required field to provide a reason, since the requester will be informed on the follow-up.
When accepting a work request, hence turning it into a work order, the due date can be set (default is today). Furthermore you have to give the right information for the work type and priority. Via this route it is also possible to give a detailed description and create subtasks.
---
# 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-requests.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.