A route you can explain
A DJ drives to a venue walkthrough, loads equipment and returns for a Saturday event. 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.
Use an event identifier across walkthroughs, pickups, load-in, and load-out. The event may produce several dates of travel. Weekend timing does not make a real work drive personal, and an event label does not make a family trip business.
| From → to | Reason | Miles |
|---|---|---|
| Warehouse → venue | Saturday event load-in | 12 |
| Venue → supplier | Collect missing event cable | 5 |
| Supplier → venue | Return for setup | 10 |
The dollars, with the limits attached
The sample legs total 27 miles. At 76¢ per mile, the rate-based amount is $20.52. That amount is a possible expense calculation, not cash back. The same 27 eligible business miles before July 1 would use 72.5¢, giving $19.57. Confirm the vehicle and period before exporting because the 2026 business rate changes on July 1.
A combined personal and event trip needs separation. Do not claim every mile of a weekend away because one stop was a venue visit.
A practical logging routine
Save recurring venues and keep the event name in the trip purpose. Review late-night end times and any personal stops after load-out. Retain the event contract or call sheet beside the route records. Preserve the source record and any correction note so another person can follow the calculation later.
A venue walkthrough on Thursday and load-in on Saturday are separate drives for the same event. Use an event name to connect them.
Late-night mileage is not personal merely because it happened on a weekend, but the trip still needs a business purpose.
What to hand to the person reviewing it
For this venue load-in record, retain the date, route, miles, and a specific assignment or activity reference. Use an event identifier across walkthroughs, pickups, load-in, and load-out. Keep the underlying trip detail because a calculated amount cannot establish why the drive occurred. Review the actual workday and separate commuting or personal stops before saving the final report.
Keep vehicle-level annual totals beside the venue load-in 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 venue load-in route while Warehouse → venue and Supplier → venue are still familiar. Confirm that the 27-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, Warehouse → venue, is recorded as 12 miles for saturday event load-in. The last line, Supplier → venue, is 10 miles for return for setup. 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: A combined personal and event trip needs separation. Do not claim every mile of a weekend away because one stop was a venue visit.
That check is more valuable than adding a generic “business” label to every drive.
If the illustrative 27-mile route happened twelve times, the mileage would total 324 miles. At the second-half business rate, the arithmetic would be $246.24. 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 Venue load-in, 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 Warehouse → venue or Supplier → venue 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 venue load-in 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 venue load-in. 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 venue load-in 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 venue load-in, the named stops, the 27-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.