Prepare a scenario before the sales call
Use invented names and a simple week with two workers, a manager and three supports. Include one change, one absence and one correction. State what your service needs without uploading a real participant roster or asking the salesperson to infer it.
Separate the roster from a support-funding or pricing decision. Software configuration must reflect your actual arrangements; a successful calendar demonstration does not establish that a support is funded or a claim is valid.
Follow the shift from start to finish
| Demo step | Ask the vendor to show |
|---|---|
| Create | How the intended manager schedules a support and sees a conflicting assignment. |
| Change | How the time or worker is changed and who can see the latest version. |
| Communicate | How the worker learns about the change and what happens if they do not respond. |
| Deliver | How the worker records what actually occurred and corrects an error. |
| Reconcile | How actual delivery is compared with the roster before the relevant downstream output. |
| Retrieve | How an authorised reviewer finds the shift record, changes and related evidence later. |
Add any essential service-specific scenario. Record “not demonstrated” when time runs out; do not turn it into a claim that the product lacks the feature.
Check SIL-specific assumptions separately
A shared living roster may involve several participants, support ratios and individual arrangements. Ask the vendor to demonstrate your fictional configuration and explain where staffing coverage and participant invoicing are represented. Have the appropriate person validate the assumptions.
Use our SIL roster-of-care guide for the operational review task. Do not treat a generic software demo as approval of a funding arrangement.
Include workers and the person who handles exceptions
Have the intended worker try the phone workflow and the manager handle a change. Check readable text, keyboard access where relevant, save feedback and the difference between draft and completed work. If connectivity is unreliable, ask what can be done offline and how conflicts are resolved when service returns.
Fictional failure to investigate: the manager changes Thursday’s start time, but a worker’s open phone screen still shows the old time. Ask what refresh, notification or acknowledgement protects the handover. Record the actual behaviour and any operational control needed.
Compare the complete operating arrangement
Check payroll, accounting, invoicing and export dependencies on the exact plan quoted. An integration label does not establish which fields, direction or timing are supported. Ask for a demonstration of the specific handoff you need.
Browse source-linked product starting points, then use the cost calculator. If the roster is sound but quality follow-up needs attention, consider the separate ProviderQMS quality workspace against that task. It is not represented as a roster replacement in this guide.
Rostering demonstration brief
Use business requirements and internal references only. Entries stay in this page and are lost when you leave or reload. Print or download your brief before leaving.
Source: https://ndiscompliant.com.au/marketplace/ndis-rostering-software-demo/ · 3 October 2026
Sources and editorial approach
Source pages checked 3 October 2026. Linked official guidance and vendor statements are identified separately from our suggested evaluation methods. Examples are fictional. Research and drafting used AI assistance; this guide does not claim practitioner approval or independent vendor testing.