> For the complete documentation index, see [llms.txt](https://docs.dynalogic.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/time-schedule-shifts-6182443.md).

# Time Schedule Shifts

It is possible to specify multiple shifts in a time schedule. The clock-in registration is used to determine the correct shift.

*Shifts are named 1, 2, 3...*

If there are several *shifts* on the time schedule, *shift* on the employee card must be empty.

| Topic                                              |
| -------------------------------------------------- |
| [Calculation ID](#field-1)                         |
| [Time Schedule](#field-2)                          |
| [Weekday](#field-4)                                |
| [Shift](#field-6)                                  |
| [From Time](#field-7)                              |
| [To Time](#field-8)                                |
| [Weekday](#field-9)                                |
| [Weekday](#field-10)                               |
| [Adjust Time Schedule to registrations](#field-11) |

## See also

## Reference

[Time Schedule](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/time-schedule-6182441.md)\
[Time Schedule Lines](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/time-schedule-lines-6182445.md)\
[Schedule Type](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/schedule-type-6182421.md)

\
\\

<details>

<summary>Calculation ID</summary>

Related Calculation ID.

</details>

<details>

<summary>Time Schedule</summary>

Enter Time Schedule No.

**Related topics**

* [Time Schedule](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/time-schedule-6182441.md)

</details>

<details>

<summary>Weekday</summary>

Day of the week.

</details>

<details>

<summary>Shift</summary>

Selecting the shift. For example:

* 1 for Day shift
* 2 for Evening shift
* 3 for Night shift

</details>

<details>

<summary>From Time</summary>

Time from where the line starts.

</details>

<details>

<summary>To Time</summary>

Time to where the line ends.

</details>

<details>

<summary>Weekday</summary>

Weekday (related to From Time).

</details>

<details>

<summary>Weekday</summary>

Weekday (related to Time To).

</details>

<details>

<summary>Adjust Time Schedule to registrations</summary>

The field is used to change a fixed schedule to a *floating* schedule.

The offset is calculated from the first [schedule type](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/schedule-type-6182421.md) line of the time schedule.

Marking means that everything from the 1st schedule type line is shifted from the new *clock-in* registration applied to the schedule, so that the entire schedule is *staggered*.

</details>


---

# 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.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/time-schedule-shifts-6182443.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.
