RECURRING AVAILABILITY / EXCEPTIONS / ROTA
Use recurring availability without pretending every week is the same.
A regular pattern saves time, but it is not a promise that lasts forever. Give the pattern a date range, then keep holidays, exams, appointments and one-off changes visible.
A four-step recurring-availability method
Collect the normal weekly pattern for each person and role.
Start with the pattern people can usually work, not with an assumption that it never changes.
Record the date range for which that pattern is valid.
A date range prevents an old availability answer becoming a permanent hidden rule.
Add exceptions such as holidays, exams, appointments and one-off requests.
Exceptions are often the reason a recurring rota becomes wrong.
Review the resulting coverage before publishing each week’s rota.
Recalculate the affected periods before sending the schedule to the team.
Keep patterns separate from hard constraints
Use the availability template to collect regular and blocked times, then check the result with the coverage calculator. A preference should not silently override a required role or unavailable period.
Useful for student, part-time and seasonal teams
Recurring patterns help when people work the same days most weeks, but school terms, second jobs and seasonal changes still need a review loop.
Student scheduling → · Part-time scheduling → · Seasonal scheduling →
Make the weekly review lighter
Shift Helper is being designed to keep recurring availability, exceptions, coverage and the published rota connected for small teams.
See the availability workflow → · Small-team scheduling → · Join early access →