Skip to content
SkyRosterBook a discovery call

For your team · Roster planners

Plan from demand to published roster.

Build assignments around the coverage your unit needs, using staff availability, qualifications and configured rules. Review the result, make adjustments and manage publication in the same workspace.

Staffing demand

Define coverage before assigning people.

Give each shift a staffing range, by day and qualification. SkyRoster turns the minimum into required slots and the maximum into room for extra coverage.

Sequence requirements

Set the staffing range for each shift type across the cycle.

Weekly requirements

Give weekdays and weekends the coverage they each need.

Pattern requirements

Build demand around a reusable pattern, such as four days on, four off.

Use Position View to review demand and add, remove or mark slots as required. Explore strategic rostering →

Roster generation

Optimise the roster and retain manual control.

Run the optimiser against your rules and priorities. Assign a shift manually when needed, then lock it to preserve that decision in the next run.

Repeated solves can produce different assignments and scores. Review the result of each run against your requirements. Trainee and instructor pairing remains a manual, instructor-led step. How the rostering engine works →

Review

Review before you publish.

See the effect of your latest changes without moving an assignment. Check Solution highlights supported rule violations, affected staff and shifts still needing cover.

The check applies your configured thresholds. It does not establish that those thresholds satisfy your operational or regulatory obligations. Review Check Solution and its scope →

Publication

Choose how each revision is published.

Override

Correct the current version in place.

Minor

Publish a routine update with the next version number.

Major

Publish a larger revision at the next multiple-of-ten version. Your unit can require head-of-unit approval.

Published shifts retain previous states with timestamps and, where recorded, change reasons. Some approval types use a generic reason. Shift history supports operational review; it is not a tamper-evident record of every action.

Scope an evaluation around your roster cycle.

Use a 20-minute discovery call to describe your demand, roster cycle and planning challenges. We’ll use that context to shape a tailored demo or evaluation.