A route you can explain
A Flex driver leaves the pickup station for a long delivery block with multiple stops. 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.
Save the block assignment, route date, and when work ended. A long block may exceed the platform’s displayed active distance because of actual road routing. Reconcile those differences instead of automatically adding a percentage.
| From → to | Reason | Miles |
|---|---|---|
| Station → delivery cluster | Assigned package block | 42 |
| Cluster → final delivery | Complete route | 31 |
| Final delivery → work zone | Available repositioning | 21 |
The dollars, with the limits attached
The sample legs total 94 miles. At 76¢ per mile, the rate-based amount is $71.44. That amount is a possible expense calculation, not cash back. The same 94 eligible business miles before July 1 would use 72.5¢, giving $68.15. Read the current source guidance as well as the example because a similar route can receive different treatment.
Station travel and the drive home require their own commuting analysis. Do not assume every first or last mile qualifies solely because the work is app-based.
A practical logging routine
Record the active work drive and inspect the ending point. If a phone interruption occurs, verify that the recovered trip covers the route. Use supporting block details for any missing segment and keep the vehicle name consistent. Keep the underlying trip detail because a calculated amount cannot establish why the drive occurred.
A delivery block can include the station, dozens of stops, and a return toward a service area. Preserve block assignments and actual odometer or GPS miles.
A platform’s displayed route length may differ from road miles. Reconcile rather than automatically adding a percentage.
What to hand to the person reviewing it
For this delivery block record, retain the date, route, miles, and a specific assignment or activity reference. Save the block assignment, route date, and when work ended. Check the date, route, purpose, vehicle, and source record together before using the result. Keep the underlying trip detail because a calculated amount cannot establish why the drive occurred.
Keep vehicle-level annual totals beside the delivery block 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 delivery block route while Station → delivery cluster and Final delivery → work zone are still familiar. Confirm that the 94-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, Station → delivery cluster, is recorded as 42 miles for assigned package block. The last line, Final delivery → work zone, is 21 miles for available repositioning. 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: Station travel and the drive home require their own commuting analysis. Do not assume every first or last mile qualifies solely because the work is app-based.
That check is more valuable than adding a generic “business” label to every drive.
If the illustrative 94-mile route happened twelve times, the mileage would total 1128 miles. At the second-half business rate, the arithmetic would be $857.28. 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 Delivery block, 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 Station → delivery cluster or Final delivery → work zone 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 delivery block 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 delivery block. 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 delivery block 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 delivery block, the named stops, the 94-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.