Explore
HomeFeaturesSolutionsPricingDocsContact
Account
Start freeContact usLogin
Appearance

Workspace guide

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.

Back to docsBrowse features

Use this page 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.

Purpose

What this page is for

  • 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

Recommended workflow

  1. Begin with the default template, not an override.
  2. Set shift-by-shift role counts in the coverage matrix.
  3. Then review scheduler rules and fallback settings.
  4. Only switch to override mode when a single date needs special treatment.

Detailed guidance

How this page fits into the product

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 tips

What helps in real use

  • 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.

Common questions

Frequently asked questions

Why is the Active Days field visible in the matrix?

Because role activity influences how a row should behave for the selected date or template. It is there to explain availability, not just decorate the table.

Should I edit counts here or directly on the schedule page?

Edit counts here when the coverage pattern itself is changing. Edit the schedule page when you only need to adjust assignments for a week.