VisitsTracker › NDIS
Evidence for every support hour
Support workers do not tap anything. Time at a participant’s address is recorded on its own, travel between addresses is measured, and the hours you record have something behind them when a question is asked months later.
No card needed. Set up in an afternoon.
What you get
Delivered hours, measured at the address
Support hours record themselves
Time inside the boundary at the address becomes a visit with the time in and the time out. Nobody is reconstructing a shift from memory at the end of a long day.
Travel is measured, not estimated
The day’s distance comes from readings we trust at the rate you set, one claim per worker per day. A day under half a kilometre creates no claim rather than a wrong one.
Late and missed shifts are visible
A shift that did not start inside its window raises an alert the same day, and coverage lists the addresses nobody reached.
Evidence per shift
A PDF with the map of the day, every reading and what we made of it, the photos, the signatures and every edit. Each day carries a fingerprint so a reader can check nothing was changed after the fact.
Faked positions never count
Readings from mock-location tools are marked and excluded from hours and travel, while staying visible in the record and in anything you send out. Nothing is quietly dropped.
Lone worker cover for community shifts
Gone-quiet alerts when a phone stops reporting after clock-in, and an SOS that emails everyone who can see that worker with a responder link that needs no account.
Workers see the same record
Exactly what is held about them, counted rather than summarised, and exportable by them at any time. Casual teams accept this far better when it is visible to them too.
A separate regional system
Australia and New Zealand run as their own regional system, apart from the others, and your workspace’s data stays in it. You choose how long raw location is kept, and can suspend deletion while a matter is open.
What this is not
This is evidence for delivered hours and travel. It does not price supports against the NDIS Price Guide, does not create or submit bulk payment claims to the NDIA, and is not a plan management or rostering system. It sits alongside whatever you claim from and answers what that system assumes: that the shift happened, at the address, for the length recorded.
Straight answers
Questions people ask
Does it submit claims to the NDIA?
No. It produces the record behind a claim: where the support was delivered, when it started and ended, the travel involved, and evidence that none of it was altered afterwards. Claiming stays in the system you already use.
How is a support shift verified?
By time spent inside the boundary at the participant’s address, from readings we trust, with arrival and departure recorded. Nobody scans or taps anything.
How is travel worked out?
From the day’s trusted readings at the rate you set, one claim per worker per day. Readings flagged as faked are excluded, so a faked position cannot inflate travel.
Where is the data held?
Australia and New Zealand run as one regional system, separate from the UK, South Africa and India, and a workspace’s data stays in the region it was created in. You set the retention period for raw location.
Will casual support workers accept it?
They take it much better when they can see it. Collection is limited to the hours you set and refused outside them at the server, and the app shows each worker exactly what is held about them, which they can export themselves whenever they like.
Also part of VisitsTracker
The rest of the product
Try it on one van for a week.
Put it on one phone, run a normal week, and see what comes out the other end.