Tell Rosterzen which on-call periods need covering, which roles or technical skills they need, who is available, and the working rules to follow. It builds a workable roster and shows you any gaps it cannot fill.
Free · No account needed
IT on-call roster · Example week
46 / 48
shifts covered
| Shift | Mon | Tue | Wed | Thu | Fri |
|---|---|---|---|---|---|
| Primary On-Call (18:00–08:00) | Priya | OPEN | Priya | Marcus | Priya |
| Secondary On-Call (18:00–08:00) | Marcus | Zoe | Marcus | Zoe | Marcus |
| Cloud Escalation | Nathan | Nathan | Rachel | Nathan | Rachel |
| Incident Lead | Rachel | Vikram | Rachel | OPEN | Vikram |
| Weekend / Holiday Backup | Kenji | Kenji | Zoe | Kenji | Zoe |
Built for operations in
When availability changes
Change an engineer's availability and Rosterzen rechecks primary and secondary coverage, technical eligibility, workload and recovery rules across the roster.
Before
Tuesday 18:00–08:00
Primary On-Call → Nathan
Change Event
Nathan spends most of the night handling a long-running production incident.
You ask Zoe to take the next primary on-call period immediately afterward.
Recovery rule broken
Zoe would start the next on-call period without the configured recovery time.
Next-day availability changes
Using Zoe here may make her unavailable for work already assigned the following day.
Another on-call gap
Moving Zoe from secondary coverage creates another on-call slot that still needs an eligible engineer.
How it works
Add the periods and roles to cover, add your engineers and rules, then generate the roster.
Coverage to fill
Set when primary, secondary or specialist coverage is required.
Configuration
On-Call Coverage
Engineers and rules
Add availability, technical eligibility, rotation limits and recovery rules.
Configuration
On-Call Team
Generate the roster
Rosterzen assigns eligible engineers and leaves anything it cannot cover open with a reason.
Configuration
On-Call Coverage Check
The result
If no eligible engineer can cover a period within your rules, Rosterzen leaves it open and tells you why.
IT on-call roster · Example week
| Shift Requirement | Mon | Tue | Wed | Thu | Fri |
|---|---|---|---|---|---|
| Primary On-Call (18:00–08:00) | Priya | Priya | Marcus | Priya | |
| Secondary On-Call (18:00–08:00) | Marcus | Zoe | Marcus | Zoe | Marcus |
| Cloud Escalation | Nathan | Nathan | Rachel | Nathan | Rachel |
| Incident Lead | Rachel | Vikram | Rachel | Vikram | |
| Weekend / Holiday Backup | Kenji | Kenji | Zoe | Kenji | Zoe |
When plans change
Update availability and regenerate. Rosterzen rechecks technical eligibility, rotation limits, recovery rules and required coverage.
Something changed
Nathan spends most of the night handling a long-running production incident.
Basic scheduler / spreadsheet
Rosterzen
Updated roster
46 / 48 shifts covered
Example scenario
This example shows primary and secondary coverage with technical eligibility, unavailable dates and recovery rules.
8
engineers
Real-world source scenario
2
on-call roles
Primary + secondary coverage
1 week
rotation
Common on-call handover period
FAQ
Yes. Model primary and secondary coverage as separate simultaneous requirements and define who is eligible for each.
Yes. Use rotation preferences or limits to reduce repeated assignment of the same people to unpopular periods.
Yes. One engineer can hold several technical skills, but they still count as one person for overlapping coverage.
Add the coverage to fill, engineer availability, technical eligibility and working rules. Preview a 7-day roster and any gaps with no account required.
Rosterzen