> 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-6182441.md).

# Time Schedule

Creation of the relevant time schedules. Samples:

* Day Shift
* Evening Shift
* Night Shift

A Time Schedule can now be copied from another Calculation Id.

| Topic                              |
| ---------------------------------- |
| [Calculation ID](#field-1)         |
| [Time Schedule](#field-2)          |
| [Description](#field-6)            |
| [Hide](#field-9)                   |
| [Trigger](#field-20)               |
| [Advanced break offset](#field-21) |
| [Activity (Trigger)](#field-120)   |

## See also

[Update Recurring Time Schedules](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/update-recurring-time-schedules.md)\
[Multi create Time Schedule Calendar](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/multi-create-time-schedule-calendar.md)\
[Q\&A (Holiday holidays)](https://docs.dynalogic.com/birds-jobmanager-product-overview/troubleshooting-and-known-issues/q-and-a-holiday-holidays.md)

## Reference

| Topic                                                                                                                                                                |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Time Schedule Shifts](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/time-schedule-shifts-6182443.md)     |
| [Time Schedule Lines](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/time-schedule-lines-6182445.md)       |
| [Time Schedule Calendar](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/time-schedule-calendar-6182447.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.

</details>

<details>

<summary>Description</summary>

Description of the record.

</details>

<details>

<summary>Hide</summary>

Field on Time Schedule to hide the Time Schedule from pick lists.

</details>

<details>

<summary>Trigger</summary>

If the employee has to change the *Time Schedule* at the time of registration, a trigger can be inserted here.

E.g. Travel schedule

</details>

<details>

<summary>Advanced break offset</summary>

Must be marked if the Time schedule is with fixed breaks and **time from sign in** in Format.

The parameter is used to calculate overtime/flex when one or more breaks are dropped.

</details>

<details>

<summary>Activity (Trigger)</summary>

Select if a change to another Schedule type is desired. E.g. Overtime, Flex, no pay etc.

</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-6182441.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.
