For community and in-home supports
A community team is a workforce you cannot see. Almost every operational question you have is about the gaps between supports: who is where, how they got there, and who is paying for the trip.
If this is your week
Workers clock in and out on their phone and the location comes with it. Somewhere unexpected gets flagged for a person to look at rather than blocking the shift — because a worker parked around the corner is a question, not a locked door.
The trip between supports is captured with the shift rather than remembered afterwards, and priced against the rate that actually applies to it instead of one flat figure used everywhere.
Participant transport gets booked, rostered and billed as its own thing. An hour of driving does not quietly disappear into the support that came after it.
A support that runs with nobody else present opens a lone-worker session, and a session nobody closes raises attention on its own — rather than being noticed the following morning.
Why this one matters here
Travel is captured at the shift and flows into the timesheet, the billable and the pay run down the same path as the support itself. Because nothing is submitted separately, nothing has to be reconciled separately — which is the whole reason travel is the line item most providers give up on.
Most providers are more than one of these, which is exactly why it is one system and not four.
Build a week that already passes the award
Read about it →What the breach costs, before you publish
Read about it →From clock-in to payslip without retyping
Read about it →Bulk claims that match their own remittance
Read about it →Notes tied to the goal they were for
Read about it →Clocks that run whether or not anyone remembers
Read about it →Authorisation that expires on its own
Read about it →Evidence that accumulates instead of being assembled
Read about it →