A route you can explain
A courier returns from a rural drop-off to the restaurant zone while available for another order. Each line below describes an illustrative work leg, not a determination that a real trip is deductible. Keep the actual trip date, destination, purpose, and vehicle. The route details make it possible to separate customer travel from personal stops.
Compare the platform’s definition of reported miles with your own shift. Keep the acceptance history and shift times. A return toward a busy zone while available for orders has different facts from an off-duty trip home.
| From → to | Reason | Miles |
|---|---|---|
| Restaurant → customer | Active delivery | 6 |
| Customer → restaurant zone | Available for another order | 9 |
| Zone → restaurant | Next pickup | 3 |
The dollars, with the limits attached
The sample legs total 18 miles. At 76¢ per mile, the rate-based amount is $13.68. That amount is a possible expense calculation, not cash back. The same 18 eligible business miles before July 1 would use 72.5¢, giving $13.05. Confirm the vehicle and period before exporting because the 2026 business rate changes on July 1.
Neither a platform email nor a driveway-to-driveway total proves every mile is business. First and last drives can be commuting depending on the facts.
A practical logging routine
Let Automatic Tracking record the work drive, or start a trip when the work driving begins, and end it when work ends. Split personal errands and breaks involving private driving. Manual Entry can fill a documented missed segment; it is not a reason to apply a blanket extra-mile percentage.
A platform summary may use a different definition of miles than your tax log. Reconcile its trip data with the actual shift and where you were available for work.
A return drive after a remote delivery is fact-sensitive, especially if you have stopped accepting work. Preserve the app status and route before treating it as business mileage.
What to hand to the person reviewing it
For this return to service area record, retain the date, route, miles, and a specific assignment or activity reference. Compare the platform’s definition of reported miles with your own shift. A clear label helps organize the file, but the dated route and business reason carry the useful evidence.
Keep vehicle-level annual totals beside the return to service area trip list. Export the relevant dates as CSV for checking or PDF for reading. If a distance was corrected or reconstructed, preserve the reason and source rather than describing it as an untouched GPS measurement.
Close the log before the details disappear
Review this return to service area route while Restaurant → customer and Zone → restaurant are still familiar. Confirm that the 18-mile total belongs to the named vehicle, that every stop appears once, and that no private detour remains inside a work leg.
The first line, Restaurant → customer, is recorded as 6 miles for active delivery. The last line, Zone → restaurant, is 3 miles for next pickup. Those descriptions let a reviewer compare the route with the appointment, work order, delivery assignment, or receipt instead of accepting a rounded daily total.
At month end, compare the trip list with the calendar and the vehicle odometer. Investigate a missing day or duplicate before exporting. For this occupation, the most useful review question is specific: Neither a platform email nor a driveway-to-driveway total proves every mile is business. First and last drives can be commuting depending on the facts.
That check is more valuable than adding a generic “business” label to every drive.
If the illustrative 18-mile route happened twelve times, the mileage would total 216 miles. At the second-half business rate, the arithmetic would be $164.16. That is still a rate-based expense estimate, not tax savings, and it assumes every repeated route is separately eligible and supported.
Use a purpose that names the actual work, such as Return to service area, instead of “business trip.” Attach the client, property, assignment, or project reference used in this occupation. A reviewer should be able to understand why the vehicle moved without opening a private customer file or guessing from the destination.
Saved Places can reduce typing when Restaurant → customer or Zone → restaurant appears often. The saved label should suggest a purpose, not make the final decision. Review mixed-use locations every time, especially a supply store, bank, gym, brokerage, restaurant zone, or property that also receives personal visits.
Keep annual odometer readings for the vehicle even when the return to service area list looks complete. Trip rows explain business use; annual readings explain total use. If the same person switches between a pickup and family car, assign the route to the car that traveled it instead of moving miles later.
Export a small monthly CSV and read it before the year ends. Sort by date, vehicle, and return to service area. A PDF is useful for a human reviewer, while CSV makes duplicates and missing purposes easier to find. Keep both files with the underlying appointments, assignments, receipts, or work orders.
If return to service area happens only four times a year, a free worksheet may be enough. If it happens weekly, automatic GPS capture can reduce repetitive entry. The useful choice depends on the record habit you will maintain, not on treating a subscription as proof of a deduction.
Before filing or requesting reimbursement, read the report from the perspective of someone who did not drive the route. They should be able to connect return to service area, the named stops, the 18-mile subtotal, and the selected vehicle without relying on memory. If they cannot, add the missing factual label now.
Sources reviewed October 28, 2026: Applicable IRS guidance, 2026 rate adjustment.