What does Kmlog help a support worker do?
Kmlog records the distance, timing and GPS route of trips you choose to start. It can help an individual support worker organise travel between appointments and export a date-range mileage report. It is not a rostering system, an NDIS billing platform or an automatic decision about which kilometres can be claimed.
For a shift with a mix of work driving, private travel and public transport, manual start gives you control over which journeys become recorded trips. It also means you need to remember to start before driving and stop after arriving.
The design grew out of the developer's own frontline work. Read the story behind Kmlog's shift evidence and multi-stop records.
How support workers can record work mileage across a shift
A useful support-worker mileage tracker should fit the way you travel. In this fictional example, a worker uses a bus for part of the day, drives between appointments and uses the same car privately afterwards. The record keeps those situations distinct; the employer or service agreement determines which journeys are accepted.
| Journey | Recording choice | Review before sharing |
|---|---|---|
| Bus to the office | Do not start a car trip | Keep any separate travel evidence your employer needs |
| Office to appointment A | Start GPS before driving; stop after parking | Date, vehicle, locations, kilometres and work purpose |
| Appointment A to appointment B | Record a separate trip | Keep the timing and purpose of this leg identifiable |
| Private shopping after the shift | Leave work-trip recording stopped | Keep private travel separate from the submitted work record |
This is a selective work-trip workflow, not a complete business-use percentage logbook. If your chosen tax-record method requires all vehicle use or additional odometer records, keep those separately as required. Compare manual GPS, automatic detection and hardware tracking if remembering to start each drive is difficult.
A practical appointment-to-appointment workflow
- Before leaving: check that the journey belongs in your work records, open Kmlog and start recording while safely parked.
- During the drive: leave the active trip running. Background location permission allows recording with the screen locked; it does not start a new trip automatically.
- On arrival: park safely, then stop the trip. Check the distance, route and start and end locations.
- Label the record: use a short location name and a work purpose where the installed version supports it. Avoid health information and unnecessary personal details.
- At reporting time: choose the date range, review the included trips and export a PDF. Check the actual exported fields before sending it.
A temporary loss of mobile data does not stop local capture of an active trip. GPS quality can still vary, and address search, route matching and cloud sync need a connection when they run. Review gaps instead of assuming every record is complete.
Example: two appointments in one morning
This is an invented workflow example, not a customer story or an entitlement calculation. A worker drives from “Demo office” to “Demo appointment A”, then later from A to “Demo appointment B”. They record each drive separately so the timing and distance of each leg can be checked.
Our sample mileage report uses those two fictional journeys: 12.40 km and 8.60 km, totalling 21.00 km. It shows how the records appear in a PDF without publishing anyone's home address or client details.
If you make several stops during one recorded journey, Kmlog also supports adding stops to a completed trip within its recorded travel area. A stop label does not by itself classify the journey as payable travel.
Plan repeat visits with favourite destinations on iPhone
For a working round with several appointments, follow our multi-stop mileage tracking and navigation guide, from planning the destinations to sharing the completed record.
On iPhone 1.1.6 and later, Record & navigate lets you choose saved or new destinations, add planned stops and open a supported navigation app while Kmlog records the journey. For a familiar morning round, prepare the destinations while parked before starting the drive.
Tap the star beside a frequently used address to keep it as an on-device favourite. In 1.1.7, favourites appear first in the destination list and repeat visits to the same named address avoid duplicate history entries caused by small GPS differences.
A plan is separate from the travel record. Planned stops carry into trip review only when nearby recorded GPS points support them. Return to Kmlog to stop the trip after parking and check the actual route before preparing a report. See the release notes for platform availability.
Review a week of mileage before sharing
- Use Find trips to revisit the dates you worked and check each journey against your own appointment records.
- Check the selected vehicle and any optional odometer readings. Keep those readings separate from the GPS distance.
- Confirm the reporting dates and the mileage rate agreed with the recipient.
- On iPhone 1.1.6 or later, inspect the full-screen report preview, save a fixed copy to report history and share the PDF directly.
Use the mileage report example and field guide to check what is included in the exported file. If you correct a trip afterwards, generate a new report; the previously saved copy remains unchanged.
Support-worker mileage evidence: a checklist after each shift
- Identify the journey: check its date, start and end time, locations and selected vehicle against your roster.
- Explain the work purpose: use a concise description the reviewer can match to the shift without adding care notes or participant identifiers.
- Check the distance: inspect the GPS route and any gaps; do not treat a planned destination as proof that you travelled there.
- Check the amount: use the agreed rate and accepted kilometres. Keep reimbursement and participant-billing decisions separate.
- Inspect the attachment: open the generated image or PDF and confirm that its visible fields meet your provider's requirements.
After reviewing a completed journey, generate a trip summary image or a PDF report for the dates you need. Save the file on your phone or share it, then attach it to your provider's shift-note process where saved-file uploads are accepted. Review the report fields and sample PDF before submitting.
Kmlog's developer refined this workflow through several months of hands-on support work, including an organisation that used Connecteam for shift notes and mileage evidence. A generated image provided a consistent record to attach without repeatedly taking screenshots or photos of a screen.
Read the shift-evidence workflow and provider review considerations for details. This is a saved-file process, not an automatic Connecteam integration; upload options depend on your organisation's setup.
What can a support provider check in a mileage attachment?
A consistent report format gives a manager the same fields to review for each worker: journey dates and times, locations, distance, work purpose and the configured rate. Match those fields to the authorised roster and your travel policy, then query gaps or duplicate submissions before accepting a record.
A generated file can reduce repeated screenshots and make records easier to compare. It does not independently prove attendance, authorise a claim or replace your organisation's checks. Kmlog currently supports an individual worker's recording and file-sharing workflow; central team approvals and fleet management remain planned.
For a roster app such as Connecteam, save the image or PDF on your phone and attach it where your organisation accepts file uploads. Kmlog does not automatically send it to Connecteam. Tell us which mileage evidence your provider needs if your existing process requires a different field.
Keep client information out of shared reports
Use the minimum information the reviewer needs. A label such as “Appointment A” may be enough when your employer can match it to a separate authorised roster. Do not include diagnoses, participant numbers or care notes in a mileage record simply to explain a journey.
Before exporting, check both labels and addresses. A neutral label does not necessarily hide an underlying address in a report. Share the file only with the intended recipient through your usual approved channel.
NDIS mileage records: separate the evidence from the claim decision
Ask your employer or client which journeys they accept, which rate to use and what evidence they need. Keep mileage records separate from decisions about wages, reimbursement, participant charges or tax deductions. A rate entered into an app is a calculation input, not proof of an entitlement.
For NDIS-related work, check the current NDIS pricing arrangements and your service agreement rather than relying on a general mileage example. For employment conditions, consult Fair Work Ombudsman guidance or your employer. Kmlog does not determine those rules.
When is another workflow a better fit?
If you need every drive detected without tapping Start, compare apps with automatic detection. If you need central roster management, participant invoicing or team approvals, check a system that explicitly supports those functions. Kmlog's website portal and fleet tools remain planned, not current features.
Compare manual start, automatic detection and vehicle-linked hardware before choosing a recording routine.
Try it with your own work trips
Download Kmlog for Android on Google Play or for iPhone on the App Store. New users receive a 14-day free trial, followed by 10 free trip starts per month. Optional KmPro subscriptions offer unlimited trip recording; check current prices in your app store.
Explore the current features · Check release availability · Get help