> For the complete documentation index, see [llms.txt](https://docs.we360.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.we360.ai/how-to-and-best-practices/mastering-time-and-attendance/shift-rotations.md).

# Shift Rotations

Manage rotating shift schedules, employee rosters, and late-arrival alerts with We360.ai attendance management and time tracking.

For organizations with rotating shift patterns (e.g., morning/afternoon/night shifts), We360.ai allows you to create multiple shift templates and assign employees dynamically.

## Configuration Steps

{% stepper %}
{% step %}

#### Create Multiple Shift Templates

In **Settings → Workplace → Shifts**, define each rotation (e.g., "Morning Shift: 7am–3pm", "Afternoon Shift: 3pm–11pm"). Include working days and break allowances.
{% endstep %}

{% step %}

#### Assign Rotations to Teams

Assign the appropriate shift to each team. For teams that rotate on a schedule, manually update the team's active shift at the start of each rotation cycle.
{% endstep %}

{% step %}

#### Configure Late-Comer Alerts

Navigate to **Settings → Emails & Alerts** and enable late arrival notifications. Set a grace period (e.g., 10 minutes) after which a manager is automatically notified if an employee has not clocked in.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
If an employee is on a shift that rotates at midnight, switch on **Cross-day Working Time** in **Settings → Workplace** so the working day is not split across two calendar dates. See [Reporting on Shifts That Cross Midnight](/how-to-and-best-practices/mastering-time-and-attendance/reporting-on-shifts-that-cross-midnight.md).
{% endhint %}


---

# 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.we360.ai/how-to-and-best-practices/mastering-time-and-attendance/shift-rotations.md?ask=<question>&goal=<user_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.