> For the complete documentation index, see [llms.txt](https://www.opentimeclock.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.opentimeclock.com/docs/my-hours/request.md).
# Request
llows employees to submit various requests—such as time-off, schedule changes, or corrections—for manager approval.
This feature streamlines communication, helps track approvals, and ensures all requests are properly documented within the system.
1. **Request Tab** – Allows users to manage and track all requests, including PTO (Paid Time Off) and hour adjustments.
2. **Pending Requests / History Requests Tabs** –
* **Pending Requests:** Displays requests awaiting approval.
* **History Requests:** Shows all past and processed requests.
3. **Action Buttons** –
* **Request PTO:** Submit a paid time off request.
* **Request Hours Worked:** Request a correction for worked hours.
* **Delete Selected Item:** Remove a selected request from the list.
4. **Request List Section** – Displays detailed information about submitted requests, including date, hours, type, notes, and current status.
5. **Edit Option** – Allows users to modify a pending request before it is approved or denied by a manager.
---
# 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://www.opentimeclock.com/docs/my-hours/request.md?ask=&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.
