> 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/product-q3/settings/schedules.md).
# Schedules
The Schedules feature in TimeClockFree allows you to create, edit, and manage employee work schedules.
It helps assign shifts, set work hours, and ensure coverage while tracking attendance against planned schedules.
1. **User List** – Displays all employees or users in your account so you can view or assign schedules.
2. **Weekly Columns (Monday–Sunday)** – Shows each day of the week where you can assign or view shift schedules for employees.
3. **Scheduled Shifts** – Displays the specific shift assigned (e.g., “Days 8AM–5PM”) to the employee for each day.
4. **Edit Button** – Allows you to edit the employee’s schedule for the selected week or day.
---
# 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/product-q3/settings/schedules.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.
