Question 1

Does the mobile app work offline?

Accepted Answer

A live connection is required. Mobile screens need a connection to your SkyRoster environment. Offline data access and background synchronisation are not supported. Plan for connectivity wherever staff need access to their assignments and requests.

Question 2

Can Data Manager import staff and roster spreadsheets?

Accepted Answer

Data Manager provides exports. It exports staff, unit, request, attendance, payroll-setting and calendar data within the user’s access permissions. It does not import a spreadsheet. Confirm initial migration and ongoing data-entry requirements with the implementation team.

Question 3

Does directory synchronisation handle employee departures?

Accepted Answer

Offboarding requires administration in SkyRoster. AD/LDAP synchronisation creates employee records and updates job numbers. It does not deactivate employees or synchronise later name and email changes. Include SkyRoster account updates and deactivation in your joiner, mover and leaver process.

Question 4

Are trainee and support pairings independently optimised?

Accepted Answer

Pairing is a manual planning step. Strategic trainee and support pairing is not independently optimised. Qualification eligibility, mutual exclusion and a configurable trainee cap support the pairing decision. Plan the pairings alongside the base roster and review the position allocation in tactical rostering.

Question 5

What solve time should we expect?

Accepted Answer

Performance depends on the roster and configuration. The search budget is configurable. There is no published production-scale benchmark linking headcount and rule complexity to a solve time. Evaluate representative demand, staff and rules using a time budget suitable for your workflow.

Question 6

Is shift-change history tamper-evident?

Accepted Answer

The current record is not tamper-evident. Concurrent publications can overwrite history, removing an employee from a roster can delete their history record, and some workflow changes use a generic reason. Use history to investigate recorded changes. Confirm retention, integrity and audit requirements separately during evaluation.

Question 7

Will separate solves produce the same roster?

Accepted Answer

Assignments and scores can differ between runs. The solver searches within a time budget and can find different results for the same demand, staff and configuration. It does not guarantee identical placements or scores. Review each result using applicable rule violations, unassigned shifts, preferences and operational judgement.

Review the fit for your operation.

Confirm service terms for your deployment.

Bring the right people into the review.

Review the technical fit

Check your requirements

Plan the rollout

Review your essential requirements.