> For the complete documentation index, see [llms.txt](https://knowledgebase.flaik.com/flaik-knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.flaik.com/flaik-knowledge-base/for-sups-managers/availability/creating-your-group/creating-your-group-1.md).
# Commitment Rules
Create a group to define all the ways your staff interact with Availability.
### **Setting up minimum commitments (Irregular schedule)**
Next step is to specify the minimum commitment that you need your staff to commit too.
**Regular Schedule:** For your regular schedule, this will be the 4 or 5 days that you want them to commit to as a full time staff member.
**Irregular Schedule:** For an irregular schedule, this will be the minimum number of days that you want them to commit to across the entire season. As an example, this could be 30, 60, or 90 days. Only once an instructor has selected sufficient days to meet this minimum commitment will they be able to submit their availability calendar.
### **Advanced Rules**
The minimum commitment is a basic way of getting staff to commit to the bare minimum number of days. You can also use advanced rules to start driving behavior to help meet your supply/demand needs.
Advanced rules let you create certain combinations of days that your instructors must select in order to be able to submit their calendar. In the example below, we've created two advanced rules.
Rule 1: ***Exactly 5 Happy Go Fun Days*** - In order for instructors meet this criteria, they must select exactly 5 Happy Go Fun Days in order to be able to move forward. If they don't select exactly 5 Happy Go Fun Days they won't be able to submit their calendar.
Rule 2: ***Minimum 7 Peak Days*** - In order for instructors to meet this criteria, they must select a minimum of 7 Peak Days. If they don't select a minimum of 7 Peak Days, they won't be able to submit their calendar.
In this example, instructors must select a minimum of 30 days that includes Exactly 5 Happy Go Fun Days and a Minimum of 7 Peak Days in order to submit their availability. If they don't meet this criteria, they will be unable to submit.
### **Notes**
* The rule type of 'Maximum' prevents instructors from selecting additional days beyond the set amount. Instructors that want to make themselves available for extra days will not be able to submit their availability.
* If an Availability Group has a status of 'Warning' it means that based on the numbers of days left in the season, instructors in this group will be unable to meet the requirements of the group if they attempted to fill out their availability response (eg they must work 3 holiday days but all the holiday days are in the past, or they must work at least 17 days but there are less than 17 days left in the season)
### **Explanation for staff**
After you've setup your minimum commitment and advanced rules, you can provide additional guidance to your instructors to help them get through completing their calendar. The more complex your rules, the more guidance you will need to provide.
Once you've added in your explanation, click **Next** to start setting up automated notifications.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://knowledgebase.flaik.com/flaik-knowledge-base/for-sups-managers/availability/creating-your-group/creating-your-group-1.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.
