> For the complete documentation index, see [llms.txt](https://docs.coreway.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coreway.com/coreway-hr/attendance-management/roster-management-upgraded.md).
# Roster Management (Upgraded)
* Roster Management meets the complex needs of multiple stores, various employee categories, and multiple shifts, allowing for daily, weekly, or monthly scheduling. It helps HR quickly generate schedules in bulk, while employees can view real-time schedules on the app, facilitating smooth internal communication.
* The setup sequence for Roster Management should be as follows:\
**Roster Setup > Employee Roster > Transfer Management**
* The new Roster Management supports:
1. **Team-Based Scheduling:** Schedule shifts based on employee classifications into different teams.
2. **Shift-Based Scheduling:** Assign shifts to employees and team members according to their shifts.
3. **Cycle-Based Scheduling:** Create schedules based on custom cycles, such as working four days followed by two days off.
4. **Multiple Shifts in One Day:** Allow for multiple shifts in a single day, ensuring that shift timings do not overlap.
5. **Quick Scheduling by Drawing Lines:** Quickly schedule shifts each day using a line-drawing method.
6. **Scheduling Compliance:** Monitor continuous scheduling, monthly rest limits, and provide risk warnings.
---
# 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://docs.coreway.com/coreway-hr/attendance-management/roster-management-upgraded.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.