Travel time and km tracking for NDIS support workers

What goes missing

Records are kept per participant, but your day is one long trip. By the end of the week you remember who you saw and roughly when. You do not remember how long the drive from the second visit to the third took, or how far it was. That is the number you need when you write up travel.

We wrote about what to record for each trip in NDIS provider travel: logging travel time and km per participant.

What Tarry records

• Time on each site, from arrival to leaving.
• Travel time and kilometres for every drive between sites.
• Only the hours you schedule, so evenings and weekends are left alone.
• Gaps, marked on the timeline, if Android stops the app or a permission is missing.

Using it per participant

You do not have to start anything during the day. At the end of it, open the timeline and add a job to the visits and drives that belong together, one job per participant. A job takes a name, notes, tags and a billable flag. Use whatever reference your service agreement uses for the participant. Each job then totals its own time on site, travel time and kilometres.

Participant privacy

Tarry has no account and no server. Location is processed on your phone and stays there, unless you export a file and send it somewhere. The code is source available, so you can check that for yourself.

Source available on GitHub

What Tarry does not do

• It does not know NDIS rules or rates, and it does not decide what you can claim.
• It does not submit claims or connect to any NDIS system.
• It records only during your scheduled hours, so it will not fill in time outside them.
• It is on Android now. iPhone is coming.

If you invoice through Xero, the Xero travel lines calculator turns minutes and kilometres into invoice lines.

Questions