Edit Requirements
Edit Requirements is the rule layer behind weekly planning. It defines how many people are required for each role, on each shift, and how the scheduler should behave when generating or filling a week.
Use this guide when you need to
- Set required staffing counts by shift and role.
- Tune scheduler rules like max consecutive days, fallback roles, and fairness lookback.
- Use date overrides only when one date must differ from the normal template.
Jump to section
Purpose
Describe the coverage the week is expected to satisfy
- Create the default coverage matrix for a group.
- Define scheduler behavior that affects autofill and weekly generation.
- Support special dates through overrides without destroying the baseline template.
Workflow
Build the baseline before tuning Auto-fill behavior
- Begin with the default template, not an override.
- Set shift-by-shift role counts in the coverage matrix.
- Then review scheduler rules and fallback settings.
- Only switch to override mode when a single date needs special treatment.
Requirement or assignment?
Change the requirement only when the expected coverage changed
A requirement says what should normally exist. An assignment says who is covering it this week. Keeping those concepts separate is one of the most important habits in a rules-based scheduling workflow.
- Permanent staffing expectation changed → edit requirements.
- One person needs to move this week → edit the schedule.
- Holiday or special-event exception → use a date override.
Guidance
Requirements are the contract between operations and the scheduler
The requirement matrix should state what must be covered; scheduler settings then decide how aggressively RoleSchedule searches for a workable assignment.
Coverage matrix first, rules second
A common mistake is treating rules as the main setup task when coverage counts are still vague. The scheduler can only behave intelligently if the matrix itself is clear. Start with role counts by shift and use rules to refine behavior afterward.
How active days affect the matrix
The matrix reflects role activity. If a role is configured for weekdays only, its availability and coverage meaning on weekends will differ. This is why the Active Days column matters: it explains why a role may be unavailable or behave differently for a date.
When to use a date override
Use an override when one specific date needs a different shape from the default template, such as a holiday, special event, or temporary surge. Do not rewrite the base template if the change is truly local to one date.
Why this page matters so much to weekly scheduling
If the group schedule feels broken, the requirements page is often the first structural page to inspect. The grid may be where you notice a gap, but the requirements page explains what the system thinks the group is actually supposed to cover.
Practical notes
Requirement edits that keep automation predictable
- Treat the coverage matrix as the operational truth for required staffing.
- Use override mode sparingly so the base template stays understandable.
- If the matrix feels crowded, review whether shifts and roles are still structured well.
Questions
Questions about turning coverage needs into scheduling rules
How required counts, date exceptions, and assignments interact with the scheduling engine.
Can I require different staffing levels on different days?
Yes. Requirements define the expected coverage pattern and can be adjusted when different dates or operating periods need different staffing. Date-specific overrides are a better fit for exceptional days than permanently changing the normal weekly model.
What is the difference between a requirement and an assignment?
A requirement says what coverage should exist; an assignment says who is actually filling it. Keeping those separate lets Auto-fill search for people against a clear operational need and lets schedulers change one week without accidentally rewriting the normal staffing model.
Do requirements affect Auto-fill?
Yes. Requirements are one of the primary inputs Auto-fill uses to determine which roles still need coverage. If the required counts are wrong, the generated schedule may be logically consistent but operationally wrong.
What should I do when one day needs unusual coverage?
Use a date-specific override or a week-level adjustment when the exception is temporary. Change the baseline requirement only when the normal recurring expectation has actually changed.