I needed to understand more than the distance
As a support worker, I needed a practical way to keep track of my finances and the costs of doing the work. Driving was part of that picture. A completed trip told me how far I had travelled, but kilometres alone did not tell me how the mileage allowance compared with the cost of using my car.
That is one of the reasons I built the Report feature into Kmlog. I wanted to look back over a period and understand the journeys together, rather than work through them one at a time or build another spreadsheet after work.
In my first developer story, I wrote about making mileage evidence easier to prepare at the end of a shift. Reports grew from a related need: keeping the records useful for me as well as for the person reviewing them.
Keep the allowance and the estimated cost separate
In Kmlog, I can set a mileage allowance rate and a separate estimated vehicle cost per kilometre. The allowance represents the rate relevant to my arrangement. The cost rate is my own estimate of what driving costs me per kilometre.
Seeing those amounts separately gives me a clearer reference point. An allowance is money calculated for the journey; it is not automatically the amount left after the costs of using the car.
For example, imagine 100 km of recorded work travel with an allowance input of A$0.80/km and an estimated vehicle cost input of A$0.25/km. The calculated allowance would be A$80 and the estimated cost A$25. Comparing the two gives an estimated A$55 difference for that driving.
These are invented figures to explain the idea, not official rates. That difference is also not my total earnings or verified profit: it leaves out wages, tax, other work expenses and any difference between my estimate and actual vehicle costs. Kmlog keeps the allowance and cost amounts separate so I can make that comparison with the right context.
I wanted to know what the driving meant for my own costs, as well as how many kilometres I had travelled.
A report brings the selected trips and their calculated amounts together for the dates I choose. I still check the included journeys and the rates attached to them. The sample mileage report and worked calculation show how to read those separate totals.
A working week does not always happen in one car
I also wanted the app to fit people whose work and family life involve different vehicles. A worker might use one car for some shifts and another at other times. If every journey ends up in one undifferentiated list, it becomes harder to remember which car was used and which records belong together.
That is why multiple vehicle profiles and the vehicle selected for each trip matter to me. Choose the relevant car before recording and check it when reviewing the trip. Keeping that connection makes the later report easier to understand.
Where odometer records are useful, they need to stay with the right vehicle too. A car's cumulative odometer readings are separate from the GPS distance of a particular journey. Changing cars should not mix those two sets of readings.
Vehicle-scoped reports let me keep the selected records for one car together. They make it easier to review that vehicle's recorded work kilometres without treating every car I use as if it were the same one.
The app needs to fit different working patterns
Support work can involve casual shifts, and some workers also do other kinds of work between those shifts. I wanted Kmlog to make room for that reality. A useful record should still make sense when someone changes vehicles or uses the same car for more than one kind of work.
Separating vehicles helps with one part of that problem. It does not, by itself, separate employers or work purposes. When preparing a report, I still need to review the trip selection and make sure the journeys belong together for the intended recipient and period.
That distinction matters: a report can be well organised without deciding who should pay for a trip. My aim is to make the relevant records easier to collect and review, with the worker staying in control of what they share.
A report should help me finish the work
For me, Report is a way to turn individual journeys into an understandable overview: the period, selected trips, distances and configured allowance or cost amounts, with vehicle details where included.
I can review the output, save a copy for my own records and share an image or PDF when it is needed. On supported iPhone versions, the full-screen preview and saved report history make it easier to check a PDF before sending it and keep the copy I actually shared.
These features belong together because they answer a real working need: understanding my driving, keeping different vehicles clear and spending less time assembling records after a shift. That is the kind of practical value I want Kmlog to keep delivering. In the next story, a nurse's home visits bring another perspective on reports and remembered addresses.
This is my personal development story. Calculated amounts depend on the rates and trips included; they do not establish reimbursement entitlement or actual profit. Features and report fields vary by platform, version and selected options. See the release notes and current features for availability.