> ## Documentation Index
> Fetch the complete documentation index at: https://docs.begin.eu/llms.txt
> Use this file to discover all available pages before exploring further.

# Schedule requirements

> Require a location, position or colour before a shift can be saved.

<img src="https://mintcdn.com/beginltd/zeGlKdCOG-PEugD7/images/cover/policies-schedule-requirements-light.png?fit=max&auto=format&n=zeGlKdCOG-PEugD7&q=85&s=30e1c4b36193cc50373bd6859b4a6a2d" alt="A shift checked for its required location, position and colour" className="block dark:hidden" noZoom width="1152" height="616" data-path="images/cover/policies-schedule-requirements-light.png" />

<img src="https://mintcdn.com/beginltd/zeGlKdCOG-PEugD7/images/cover/policies-schedule-requirements-dark.png?fit=max&auto=format&n=zeGlKdCOG-PEugD7&q=85&s=08aa2d64176471fb437322c5765cbacb" alt="A shift checked for its required location, position and colour" className="hidden dark:block" noZoom width="1152" height="616" data-path="images/cover/policies-schedule-requirements-dark.png" />

A schedule policy makes selected shift fields compulsory. Use it when a shift must have a location, position or colour before Begin may save it.

## Create a requirement

<Steps>
  <Step title="Start it">
    Go to **Policies → Schedule**, open **Add**, then choose **Add schedule policy**.
  </Step>

  <Step title="Choose the required fields">
    Turn on **Location**, **Position** or **Colour**. You may require more than one.
  </Step>

  <Step title="Set the audience">
    Use [**Applies to**](/for-managers/policies/applying-policies) to choose everyone or selected
    people, positions, departments or locations.
  </Step>

  <Step title="Activate it">Set **Status** to **Active**, then save.</Step>
</Steps>

<img src="https://mintcdn.com/beginltd/YdeZknOgrpeotPBO/images/articles/policies/policies-schedule-requirements-screen-light.png?fit=max&auto=format&n=YdeZknOgrpeotPBO&q=85&s=0ba5b6667a2af76ebdfc6d42a7b50003" alt="The Schedule tab listing required shift fields and policy audiences" className="block dark:hidden" width="2944" height="1840" data-path="images/articles/policies/policies-schedule-requirements-screen-light.png" />

<img src="https://mintcdn.com/beginltd/YdeZknOgrpeotPBO/images/articles/policies/policies-schedule-requirements-screen-dark.png?fit=max&auto=format&n=YdeZknOgrpeotPBO&q=85&s=7e387b9ebdc66befdc2a7d2d34238b16" alt="The Schedule tab listing required shift fields and policy audiences" className="hidden dark:block" width="2944" height="1840" data-path="images/articles/policies/policies-schedule-requirements-screen-dark.png" />

## Fix a shift that will not save

Begin refuses the save with a message such as **Select a location for this shift.** Add the location, position or colour, then save again. The requirement is evaluated for that shift and person, so another team may have a different set of required fields. Shifts saved before the policy are not re-checked until someone edits them.

For example, require **Position** for a department whose shifts must always identify a job. Check one of its members in **Policy tester**, then open a shift for that person without a position. Begin should refuse the save and name the missing position; choose it and save. Check someone outside the department too, so you do not accidentally apply the rule to everyone.

If several matching policies require different fields, Begin combines those requirements. Use **Policy tester** to see which policies supply them.

**Context for an assistant answering questions about schedule requirements.** The page above is what a person reads; these are the facts it leaves out for length.

* **Who can:** creating or changing a schedule policy uses the matching grant on **Policies**. A person also needs permission to edit the schedule to fix a shift.
* **Where:** enforcement runs when a shift is created or updated, including schedule write paths outside the form.
* **Limits:** matching policies compose, so location, position and colour may come from different policies.
* **Not supported:** a schedule policy does not check rest time, worked-hour limits or other legal rules. Compliance policies handle those checks.
* **Often confused with:** a compliance warning, which evaluates the pattern of work rather than whether a shift field is present.

## Next

<Columns cols={2}>
  <Card title="Schedule warnings and conflicts" icon="triangle-exclamation" href="/for-managers/schedule/warnings-and-conflicts">
    Read the message shown while editing a shift.
  </Card>

  <Card title="Compliance rules" icon="shield-check" href="/for-managers/policies/compliance-rules">
    Check hours, days, shifts and rest against configured limits.
  </Card>
</Columns>

## Still need help?

<Columns cols={2}>
  <Card title="Contact support" icon="envelope" href="mailto:support@heybegin.eu">
    Email the Begin team and we'll get back to you.
  </Card>

  <Card title="Ask Begin AI" icon="comment-dots" href="?assistant=open">
    Open the AI assistant and get instant answers based on these docs.
  </Card>
</Columns>
