> 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/shift-rules.md).
# Shift Rules
It lets administrators set rules for employee shifts, such as start and end times, grace periods, and automatic clock-in/out adjustments, ensuring consistent scheduling and accurate time tracking.
1. **Add Shift** – Create a new shift rule with custom start/end times, lunch breaks, and restrictions.
2. **Shift List** – Shows all the available shift rules you’ve created for easy selection and editing.
3. **Shift Name** – Enter or edit the name of the shift rule for easy identification.
4. **Shift Start** – Set the time employees are scheduled to begin their shift.
5. **Shift End** – Set the time employees are scheduled to end their shift.
6. **Lunch (Minutes)** – Define the duration of the lunch break for this shift.
7. **Differential** – Assign a pay differential (e.g., night shift) if applicable, or select “No Differential Pay.”
8. **Clock In Rules** – Configure how early employees can clock in and how time is recorded.
9. **Lunch Rules** – Configure policies around lunch breaks, such as automatic deductions or timing.
10. **Clock Out Rules** – Set rules for clock-out behavior, such as preventing early or late clock-outs.
11. **Delete This Rule** – Permanently remove the selected shift rule.
12. **Duplicate This Shift** – Copy the selected shift rule to quickly create a similar one.
13. **Clock-in Before/After Settings** – Restrict when employees can clock in or automatically adjust recorded times.
14. **Prevent Shift Start Exceeding Hours** – Block starting a shift if it will exceed a specified number of paid hours per day or week.
---
# 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/shift-rules.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.
