Frequently asked questions

The current pilot focuses on hospital teams, including doctors, nurses, allied health and administration. The rule library also includes examples for other workplaces. Contact us to check whether your team’s requirements are supported before entering staff data.

Start with your staff list, roles, FTE, shift times and staffing requirements. Add approved leave, individual requests and the rules your roster needs to follow. An anonymised example of your current roster is useful for a demo.

Try 2 roster periods for one group of up to 50 people within 60 days of the agreed start date. A 45-minute setup call is included. No card is required and the pilot does not automatically become a paid subscription. View the full offer and pricing calculator.

Yes. Each group has its own staff, shifts, settings and rosters. Site administrators manage hospital access. “My site rules” is shared across the hospital or business, and frequently used rules reflect use across the site.

Hard rules are required for a generated roster. Soft rules express preferences the solver tries to improve in priority order. You can require at least one education shift per week with a hard rule, then aim for two with a soft rule.

No. They are starting points with source references and settings to review. Check the applicable agreement, employee category and local arrangements. Some obligations require manual checks and cannot be established from roster assignments alone.

You choose the search time. A 20-minute search is a common starting point; complex rosters can need up to two hours. A longer search can improve a feasible result, but cannot resolve contradictory hard rules. You can leave the page and return while generation continues.

The solver does not silently discard hard rules. If it proves a conflict, RosterSolver shows a report to help you review the settings. A search can also end without finding a roster or proving that none exists.

Yes. Drafting opens in the editable view. Save changes to the same draft, or copy it to try another version. Manual edits are checked before publication, and any violations or incomplete checks must be reviewed and acknowledged.

No. Each generation starts with a copy of the shared defaults. Changes inside a generation affect that generation only; changes in Preparation apply to future generations. Published rosters retain their saved settings.

Yes. Open the CST rule in Rules and edit “Allowed deviation (percentage points)”. For example, a 25% target with an allowed deviation of 2.5 percentage points gives a 22.5%–27.5% band. Individual CST targets remain in People.

Staff see published rosters through their personal workspace. Generating, editing or finalising a draft does not publish it. An authorised administrator controls publication.

Staff with a linked roster profile can submit supported requests. Administrators review them for planning. Availability approval and your organisation’s HR paperwork are tracked separately; an approval in RosterSolver does not replace your HR process.

Yes. Each person can create a private subscription link for their published shifts. Updates appear when their calendar app refreshes. Keep the link private and revoke it if it is shared accidentally. A downloaded calendar file is a one-off copy.

Yes. Saved rosters can be exported as Excel or CSV. Site administrators can also export hospital data. Contact us if you need help exporting before your pilot or subscription ends.

The hosted service stores roster data on AWS in Sydney, and generation runs on an operator-managed computer in Australia. Email uses Google Workspace, which may process information overseas. See the Privacy Policy for details, including optional AI features and your access and correction options.