ProviderQMS

Rostering & service delivery

ShiftCare vs Brevity for NDIS providers

A staff-based licence or a client-based licence? Start with the work, then model the cost.

ProviderQMS editorial research · Sources checked 23 September 2026 · Review draft

The shortlist view

Shortlist ShiftCare when the brief centres on mobile workers and rostering. Investigate Brevity when several service lines need a shared operational system. That is an editorial starting point from their published scope, not a tested winner. The deciding demonstration is a completed support moving into the correct invoice and payroll workflow.

Based on vendor documentation, not hands-on testing. ProviderQMS sells document kits and a separate QMS product. No vendor enquiry collection or affiliate source links. Our method.

The choice behind the feature list

A roster is only the start of the buying decision. Your worker must find the right information, record the support and leave a useful handover. Your office then needs to reconcile delivery, funding and payment without repairing the same data in several places. Ask both vendors to show that complete sequence in the edition you would actually buy.

ShiftCare’s published scope puts rostering, mobile work and progress notes in view. Brevity describes a broader suite spanning client and employee management, scheduling and billing. Neither description establishes that your particular mixed-service workflow will be straightforward. Test the joins between tasks, not just the existence of a menu.

The buying differences to verify

The buying differences to verify
Decision ShiftCare Brevity
Licence basis Per user, with a published five-staff minimum; every login counts Published pricing uses clients; confirm the client definition, minimum and billing term
Claiming workflow Bulk uploads and direct NDIA claims sit on different plans Ask for the exact claim and remittance workflow in the proposed package
Implementation Scope training, migration and connected subscriptions Check the proposed tier: the pricing page shows setup fees on some tiers
Mixed service lines Demonstrate your required service types together Confirm which service modules are included and how records connect

These distinctions come from the linked vendor pages. Unlisted functionality remains a question, not a negative feature rating.

Give both vendors this same demo

Use a fictional participant and a rostered support. Change the worker shortly before the shift. Have the replacement find the current support instructions, record delivery and correct an inaccurate entry without losing its history. Ask the office user to create the invoice, identify a rejected claim and follow the correction through the finance system.

Measure the steps your team must repeat. Record the edition, any extra application and the person responsible for each handoff. If offline work matters, deliberately disconnect the demonstration device and ask the vendor to show recovery; do not assume a mobile app works offline.

Model the cost around your team

Create two scenarios using your expected staff logins and billable client count. Then repeat with realistic growth. A lower unit price does not identify the lower organisation cost when the units differ. Add setup, training time, integrations and any recurring messaging charges using the same GST basis.

Ask for a written explanation of inactive accounts, archived clients, administrator access and annual renewal. Put those assumptions into the two-year software cost tool. Do not enter a per-client price against your worker count.

Our decision rule

Advance the product that completes your essential workflow in the quoted edition, with a documented implementation owner and an affordable total commitment. If both pass, involve the staff who will use it daily in a repeat trial. If neither can demonstrate an essential step, keep the shortlist open rather than accepting a roadmap promise as a delivered feature.

Sources behind this comparison

Confirm current terms with the vendor. An unanswered question does not establish that a feature is absent.