DoorDash, Uber & Lyft Driver Daily Shift Mileage Log Template (2026 PDF/CSV)

The current sample reads Vehicle: Delivery sedan; Apps worked: DoorDash + Uber Eats; Shift start odometer: 28430; Shift end odometer: 28534. Replace every sample value before printing. A correct trip table under the wrong vehicle or claim period creates a report that looks finished but cannot be reconciled.

Edit your worksheet

Replace the sample context and rows with records from your own vehicle, assignment, property, patient route, or claim period. Review every line before printing because the form calculates what you enter and does not verify the underlying event. A clear label helps organize the file, but the dated route and business reason carry the useful evidence.

Business: 72.5¢ Jan–Jun and 76¢ Jul–Dec. Context fields appear in the printout and CSV. The form does not save or upload your entries.

Print preview

The preview exposes missing headers, the wrong vehicle, and rate-period mistakes before they reach a reimbursement request or tax file. Compare it with the original trip rows and supporting records, then download both readable and editable copies. Preserve the source record and any correction note so another person can follow the calculation later.

Get Milevaro: 14 days free

Keep the shift boundary and the route

Start and end odometer readings give the shift’s total distance. They do not prove that every mile was business. Itemize or explain personal breaks and first or last drives separately. This editable trip form can describe shift legs; it does not infer deductible miles from app names.

Details this worksheet keeps visible
FieldIllustrative value
VehicleDelivery sedan
Apps workedDoorDash + Uber Eats
Shift start odometer28430
Shift end odometer28534

Fill it in and review the result

Reconcile the 104-mile illustrative odometer change with the full shift record, not just the two sample rows. Keep app availability and delivery history. A platform report can measure active miles differently from the car’s actual work route. Confirm the vehicle and period before exporting because the 2026 business rate changes on July 1.

Editable sample trips
DateFromToPurposeMiles
2026-10-08Restaurant zoneRural customerActive delivery6
2026-10-08Rural customerRestaurant zoneAvailable repositioning9

Read the output with its limits

The shift odometer readings are supporting context. The tool totals the itemized rows, not the difference between those readings. Add the full supported shift detail before treating the preview as a complete shift report. Preserve the source record and any correction note so another person can follow the calculation later.

Check the header before the trip rows

This worksheet keeps Vehicle, Apps worked, Shift start odometer, Shift end odometer in the report context. Those fields answer a different question from the mileage total: they identify which vehicle, person, property, assignment, period, or evidence set the rows belong to. Review them whenever the sheet is copied for a new month or client.

The current sample reads Vehicle: Delivery sedan; Apps worked: DoorDash + Uber Eats; Shift start odometer: 28430; Shift end odometer: 28534. Replace every sample value before printing. A correct trip table under the wrong vehicle or claim period creates a report that looks finished but cannot be reconciled.

If one file covers several properties, projects, or vehicles, either split it or identify the correct context on every affected row.

The distinguishing field for this form is shift odometer. Keep its supporting source outside the browser because the generator does not save entries. Download the CSV for checking and print the PDF for reading; open both files once before relying on them at tax time.

Audit the sample like a real report

The editable example contains 2 trip rows totaling 15 miles. The first row runs from Restaurant zone to Rural customer for active delivery. The last runs from Rural customer to Restaurant zone for available repositioning. Each row needs its own date and purpose even when both belong to one project.

For this shift odometer worksheet, check that no row is duplicated, no personal detour remains inside a work distance, and no date falls outside the labeled period. A valid June 30 business row uses 72.5¢; a July 1 row uses 76¢. Other mileage categories use their own rates.

This page starts with a driver works a lunch delivery shift across two apps. Treat that as an illustration, not a record of your drive. Replace it with observed or supportable details. If a route was added later from a calendar or map, mark the reconstruction and retain the appointment, invoice, receipt, or service record used to rebuild it.

Print one test page before building a full report. Confirm that shift odometer is visible, long purposes wrap, and no table column is cut off. A browser PDF can use a different paper size or margin than the office printer, so inspect the saved file rather than assuming the on-screen preview guarantees the final layout.

Use consistent units. This template expects miles, and its 15-mile sample is not a place to enter kilometers, reimbursement dollars, or odometer readings. Put start and end odometers only in labeled context fields. Converting or mixing units silently makes the rate calculation impossible to verify.

In this shift odometer file, keep the first sample date, 2026-10-08, separate from the last, 2026-10-08. Dates decide the 2026 rate period. Do not assign July’s 76¢ to a June row because the report was printed later, or divide an annual total without dated evidence.

Give each trip in the keep the shift boundary and the route one primary purpose another person can understand. “Meeting” is weaker than a review tied to a project. “Supplies” is weaker than replacement valve for rental A. The report can stay concise without exposing information the receiver does not need.

Reconcile the CSV with the printout. The downloadable rows should preserve shift odometer, dates, routes, purposes, and distances. Open the CSV in a spreadsheet and make sure dates and decimals were not automatically reformatted. Keep the untouched download before adding formulas, colors, or manual totals.

For shift odometer, a signature records approval only after an authorized person signs, and a vehicle header is useful only after correct readings are entered. Treat every blank, default, and sample value as unfinished. The generator cannot know whether a plausible value belongs to the scenario: A driver works a lunch delivery shift across two apps

If this shift odometer report combines clients, properties, vehicles, or activities, preserve the allocation in a field or purpose. One annual total is difficult to divide later. Monthly files make corrections easier, while a year-end keep the shift boundary and the route summary can be rebuilt from reviewed exports.

Save support for a driver works a lunch delivery shift across two apps with a repeatable name, such as 2026-10 vehicle project mileage. Keep Social Security numbers, bank logins, full patient names, and unnecessary home addresses out of a broadly shared PDF. Store any private cross-reference for shift odometer in a controlled location.

Review the deduction or reimbursement method separately from this shift odometer template. Standard mileage, actual expenses, an accountable plan, Schedule E, medical mileage, and charitable service do not use one rule. The form organizes keep the shift boundary and the route inputs; cited IRS material and a qualified professional address eligibility.

Finish by asking whether the scenario still matches the rows: A driver works a lunch delivery shift across two apps If the work changed, update the context and purposes before reuse. Copying last month’s completed sheet is efficient only when every inherited value is reviewed; otherwise it produces a polished record for the wrong activity.

Sources reviewed October 28, 2026: Record rules, 2026 rate adjustment.

Questions people ask

These answers summarize the calculation, source records, and practical limits for this exact topic. Read them before treating the worked example as a finished tax record, reimbursement claim, or product decision. The report should let a bookkeeper trace each subtotal back to a dated and understandable trip.

What is special about this template?

Start and end odometer readings give the shift’s total distance. They do not prove that every mile was business. Itemize or explain personal breaks and first or last drives separately. This editable trip form can describe shift legs; it does not infer deductible miles from app names.

Which fields should I check first?

Reconcile the 104-mile illustrative odometer change with the full shift record, not just the two sample rows. Keep app availability and delivery history. A platform report can measure active miles differently from the car’s actual work route.

Does it create an Excel workbook?

The download is CSV, which Excel and Google Sheets can open. It is not an XLSX workbook and it does not preserve spreadsheet formulas.

What does this form not establish?

Do not add a standard missing-mile percentage or automatically claim every driveway-to-driveway mile.

Keep the next drive in your log

Milevaro records your drives automatically, or with one tap, and can reduce repeated address entry for frequent work drives. Review the purpose, vehicle, and distance before exporting because a tracking tool does not determine tax treatment. Review the actual workday and separate commuting or personal stops before saving the final report.

Try every feature free for 14 days with no card or account required for local use. Then the Free plan keeps 30 trips a month, or Milevaro Pro is $89.99/year or $8.99/month for unlimited trips.

Get the app

Milevaro reports are records of trips logged by the user. They are not IRS-certified (the IRS does not certify software) and do not guarantee a tax deduction. A deduction lowers taxable income; it is not direct cash back. The estimated deduction is business miles multiplied by a user-set rate and is an estimate, not tax advice. Consult a qualified tax professional.