A different reason to keep a clear mileage record
One of the people who collaborates with us and helps with internal testing is a practising nurse. Her work includes visiting clients in their homes to provide nursing care. That gave us a useful perspective alongside my own experience as a support worker.
In her particular working arrangement, she does not receive a per-kilometre reimbursement for these journeys. Instead, she needs clear records to discuss work-related car expenses with her accountant at tax time. Her main need is an understandable record of the journeys, not an allowance amount to submit after each shift.
That difference matters to me. A mileage app should be useful when someone needs supporting records for an accountant, as well as when someone needs evidence for an employer's reimbursement process.
The odometer includes the rest of life, too
Previously, she used a notebook and readings from her car's odometer. The difficult part was keeping the work journeys clear when the same car also carried her through ordinary life: commuting, shopping, outings and time with family.
The total distance on the car could not answer the question her accountant needed to review: which journeys were for work, and how much travel did those journeys involve? She or her accountant had to spend time piecing the information together.
With Kmlog, the routine is simpler. While parked, she can tap Start a trip, drive to the visit, then park and tap Stop trip. She reviews the places, timing, recorded GPS distance and vehicle before saving. A later journey can be recorded separately, so each leg stays understandable.
A drive after a visit might lead to another client, the hospital or home. Recording it preserves the details for review; it does not decide whether that leg is deductible. GPS also has limitations, so the completed record still needs checking.
The useful change was having individual journeys to review, instead of trying to reconstruct a working year from the car's total kilometres.
A financial-year report her accountant can review
When preparing records for her accountant, she can choose the relevant dates, review the included trips and generate a detailed Trip Report. For an Australian financial year, that usually means a period from 1 July to 30 June. She can then check and share the PDF, with supporting information her accountant needs.
The report brings the recorded journeys into a consistent format instead of leaving them scattered through notebook entries. Our sample mileage report shows the basic layout and explains which details to check before sharing.
There is an important boundary here. The ATO generally treats ordinary travel between home and a regular workplace as private; travel to other workplaces or client visits needs to be assessed against the relevant circumstances. Private shopping and family travel should not be included as work kilometres. The ATO also requires a work-related expense to be incurred personally and not reimbursed before it can be claimed. See its guidance for nurses and midwives.
A PDF of GPS trips is supporting evidence, rather than a complete tax calculation or an automatically valid tax logbook. Under the logbook method, additional requirements include a representative period of at least 12 continuous weeks, odometer records, journey purposes and expense evidence. Her accountant can advise which records and method fit her circumstances. The ATO employees' work-expenses guide explains the record requirements.
For the development thinking behind these reporting tools, read why I built reports into Kmlog.
Repeat visits should not mean choosing the address again
There is another routine that nursing visits and support work often share: returning to familiar places. In my own support work, I had regular clients I visited each week over a long period. That continuity helped me understand the people I supported and their needs.
The destinations were familiar, but the address suggested by a phone was not always the one I expected. A nearby GPS point might resolve to the neighbour's property or the opposite side of the street. Repeatedly correcting the same address added an unnecessary step.
That is why remembered places became part of Kmlog. When reviewing a trip, I can check the location, make an address correction within the supported area and give the place a recognisable label. Saving the labelled place lets Kmlog remember that address for later visits.
When a later trip endpoint is close enough to a saved place, Kmlog can prioritise that saved address and label over a fresh address lookup. The match is based on proximity, so I still check the result, especially when two regular destinations are close together. It helps reduce repeated address selection without changing the GPS distance already recorded.
Small savings add up across a multi-stop day
The useful places are not only clients' homes. They can include a hospital, a familiar activity venue, a regular appointment location or my own home. Saved places help with recognising completed journeys; favourite destinations on supported iPhone versions also make frequently used addresses easier to find when planning the next outing.
Across a day with several destinations, finding familiar addresses more easily means less repeated searching and correcting. It complements multi-stop recording and navigation: plan the visits, record the journey, then review the stops against the route that was actually captured.
A useful label does not need to contain a client's full name. Where practical, I use a non-identifying label such as Regular visit A, and keep clinical details and unnecessary personal information out of mileage records. Before sharing a report, check its addresses and labels and use the approved channel for the intended recipient.
The nurse's experience reinforced something I had learned in support work: a feature earns its place when it removes a repeated task from a real working day. Clear reports and remembered addresses do that in different ways, but they come from the same design priority.
This story draws on feedback from a practising nurse who collaborates with us and helps test Kmlog. Identifying details have been omitted. Features vary by platform and version; see the release notes for current availability.