Multi-stop mileage tracking and navigation for work

A workflow for a working day with several visits

A working journey can include several appointments, a community visit and a return to base. Kmlog brings destination planning, active trip recording and shareable evidence into that routine. Its development has been informed by the developer's hands-on experience working as a support worker and reviewing the paperwork involved in a shift.

On iPhone 1.1.6 and later, you can plan destinations and stops, then open a supported navigation app while Kmlog records the journey. Navigation gives directions; Kmlog's recorded GPS journey provides the trip record. A planned destination alone does not prove that you visited it.

Android and iPhone are both available. The planning and navigation workflow described here is for iPhone; features can differ by platform and installed version. Check the current release notes.

1. Plan multiple stops before driving

While parked, choose a saved destination or find a new address in Record & navigate. Add the planned stops for the journey and check that each address refers to the place you intend to visit. Select the appropriate vehicle and enter any optional odometer information your recording routine needs.

For repeat visits, iPhone 1.1.7 lets you star favourite destinations. Favourites appear first and are stored on the device, scoped to the signed-in account. Destination history also consolidates repeated entries with the same place name and address, so small GPS differences do not need to produce a long list of duplicates.

For example, a fictional working journey might run from Office to Address 1, then Community centre and Address 2. Decide whether those stops belong in one record before you start. If separate purposes, vehicles, rates or your employer's process require separate records, finish one trip and start the next at the relevant point.

2. Record the trip and open navigation

1. Check your planned destinations and start recording while parked.
2. Open a supported navigation app from the recording workflow. Kmlog continues recording the active trip in the background.
3. Keep the permissions needed for that active trip enabled. You can lock the screen; do not force-close Kmlog while it is recording.
4. When the journey is finished and you are safely parked, return to Kmlog and stop the trip.

This is a navigation handoff, rather than a promise of built-in turn-by-turn directions or automatic route optimisation. Check your selected navigation app for directions and current road conditions. Make changes to destinations when safely parked.

Kmlog can capture an active GPS trip locally during a temporary network interruption. Address search, cloud sync and road-matched displays still depend on connectivity. Review the completed record if a recording was interrupted or the phone could not obtain reliable GPS.

3. Review the actual journey, including changed plans

Review the recorded route, distance, timing and place labels after stopping. Planned stops can carry into review where nearby recorded GPS supports them. Check them against what actually happened: an appointment cancelled during the day should not become evidence of a visit simply because it was in the plan.

In the example, if you went from Office to Address 1 and then directly to Address 2, review the journey with that change in mind. Do not treat the unvisited Community centre as a completed stop. Correct a place label where necessary, but do not substitute a planned distance for the measured journey.

Keep the work purpose and any additional information your reviewer requires alongside the record. GPS kilometres and vehicle odometer readings describe different things. For a wider daily routine, see how to track work kilometres in Australia.

4. Share a clear trip image or mileage PDF

After reviewing a completed trip, generate a trip image to share or save on the phone. For several completed trips over a period, generate a date-range PDF and inspect its preview. Confirm which details your selected output includes before sending it.

A support worker whose provider requests a mileage attachment with a shift note can upload the generated file through the provider's normal process. For example, a workplace using Connecteam can accept an attachment if its configuration and policy allow it. This is a file-sharing workflow, rather than a direct Kmlog integration with Connecteam.

A consistent output format can make records easier to read and compare. The reviewer still needs to check the journey, required purpose and agreed rate. See the mileage report example and sharing checklist and the support-worker mileage guide.

Saved report history preserves the output created at that time. If you correct a trip later, generate a new report; the earlier saved copy does not change. Use the recipient's approved channel and check personal or client information before sharing.

Choose the recording method that fits your work

Destination planning does not turn Kmlog into an always-on automatic trip detector. You choose when to start and stop recording, which helps keep personal travel out of the work log. That also means remembering to start before the journey and stop afterwards.

If remembering those steps is the main difficulty, compare the trade-offs in our manual, automatic and hardware mileage tracking guide. An automatic detector may suit some drivers; others prefer controlling which journeys are captured.

Start with the current Kmlog workflow and features, then try a short journey and inspect the exported evidence before relying on it for your working day.

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