A typical evaluation ends up comparing a scheduling engine against one vendor, a leave and swap workflow against an HR system's bolt-on, and a payroll export against whatever an integrator built by hand last time. None of those specialist tools has an answer for the questions the other two get asked. Below is every module, grouped by what it actually does rather than by our org chart, with the mechanism written out in full for the three that carry the roster itself.
Platform
One system, not a shelf of point solutions
Most rostering software on the market is one of the modules below, sold as the whole product, with the rest stitched together from spreadsheets, a separate leave portal and a consultant's payroll export script. SkyRoster is one system: one employee record, one rule engine, one login, from strategic rostering through to the mobile app a controller checks before a shift.
The system
The whole product on one screen
Click any block to see what it does and where it connects.
One operational day, sliced into 96 quarter-hour slots, the grain the platform actually plans against.
Plan the month
The demand and the rules, settled before anyone works a single shift.
Run the day
What happens once the roster is live and reality does not cooperate.
People and competency
Who is allowed to do what, and who gets to change that.
Time, pay and evidence
What the roster actually cost, and the record that proves it.
Plan the month · 01
Strategic rostering
Builds and publishes the month ahead: an optimisation engine allocates every shift against your demand and your configured rules, then shows exactly which rule placed each one.
89 strategic constraint classes, wired across up to 8 roster configurations, team or individual staffing, with or without a rotation pattern, working or preventive duty.
Open the Strategic rostering pageverifiedCompiled counts & rule catalogue, compiled on 12 September 2026
Explore each capability
Plan the month
The demand and the rules, settled before anyone works a single shift.
Strategic rostering
Build the month against demand, solve it against your own rules, publish it through a version-aware gate.
Sector planning
Sectors, positions and a quarter-hour demand model: where the roster's demand numbers actually come from.
Leave and duty
Requests and approvals checked against the same rules the roster runs on, not a separate ledger.
Run the day
What happens once the roster is live and reality does not cooperate.
Tactical rostering
Turn a published shift into a working position, interval by interval, for the day in progress.
Shift swaps
Every swap checked against a documented eligibility gate before either side can approve it.
Mobile app
The controller's own view of today: their position, their requests, nothing else collected.
People and competency
Who is allowed to do what, and who gets to change that.
Competency
Licences and ratings on a calendar the roster engine reads directly, not a spreadsheet kept beside it.
Staff records
One employee record. Payroll, mobile and the roster all read from the same one.
Configuration
Units, rules and roles, set by your own administrator, not filed as a change request to us.
Time, pay and evidence
What the roster actually cost, and the record that proves it.
Attendance
Clock-ins and timesheets, reconciled against what the published roster actually asked for.
Payroll export
Overtime, allowances and close-of-month, shaped for the payroll system you already run.
Reporting
What the roster actually did, not just what it was built to do.
Integrations
Directory sync, single sign-on, and the systems already sitting in your organisation.
Audit & History
A central change log, history on individual records, and search and filters to investigate recorded changes.
Read this first
Start with the three that carry the roster
Strategic rostering, tactical rostering and sector planning are the modules that decide who works when and who stands where. They get the deepest treatment on this site: the mechanism, the vocabulary, and what each one deliberately does not do. The other pages describe each capability and its scope. Confirm the tools and records available for Audit & History in your written offer.
If you would rather start from what the product does not do than from what it does, that page exists too: /platform/limits.
Bring us a month that went wrong.
A working session is 45 minutes with your own roster on screen, not a canned demo. Bring a pattern that fought you and we will walk through what the engine would have done with it.