Volunteer Mileage: Rates, Reimbursements, and Records

Published charity rates are often lower than business standard mileage rates. Volunteers who casually multiply all miles by a business rate can overstate value on personal returns or on internal reports. Staff traveling for the organization may be on a different policy entirely—employer reimbursement versus volunteer in-kind contribution.

Ask early: Does your nonprofit reimburse at a set cents-per-mile? Do volunteers track miles for their own records at a charity rate? Are grant budgets expecting a specific rate assumption? Write the answer into your program’s one-page mileage policy.

Use MileLedger’s nonprofit-oriented calculator to model reimbursements for planning—then confirm the figure your board, grant officer, or tax advisor actually wants you to use.

For reimbursements and grant documentation, collect date, miles, purpose (event setup, meal delivery, site visit, supply run), volunteer name, and program or grant code when relevant. Boards and grant officers care about consistency more than fancy software—as long as the log is complete and repeatable.

Purpose should name the activity, not just “volunteering.” “Deliver weekend meals — Route B” or “Setup — spring fundraiser” is auditable. “Helping out” is not.

If multiple volunteers share a vehicle, record who drove and whose miles are being claimed or reimbursed. Shared trips without names create duplicate claims and awkward audits.

Keep staff business travel in a separate categorization from volunteer in-kind miles when both appear in the same organization. Mixed records confuse audits, Form reporting conversations, and grant reports that only want volunteer contributions.

Use clear labels or categories: Staff — program travel, Volunteer — in-kind mileage, Personal — do not report. Train new coordinators on the labels once; enforce them every month.

When a staff member also volunteers on weekends, log those trips under the volunteer category with the volunteer purpose—not under their weekday staff travel account.

Pick a monthly cutoff (for example, the last Friday). Ask volunteers to confirm uncategorized trips before that date. Export the month’s volunteer miles by program. Spot-check three random trips for purpose quality.

Reimburse on a published schedule if you pay cents-per-mile. Delayed reimbursements encourage people to stop logging. Predictable process keeps participation high.

Store exports where the next coordinator can find them: shared drive, fiscal year folder, grant name in the filename. Institutional memory matters when staff turn over mid-grant.

Grant officers often want totals by program period, not a single undifferentiated number. Tag trips with program or grant codes as you go so you are not sorting a year’s worth of “misc volunteer” lines in a panic.

For boards, a one-page summary helps: miles by program, estimated value at the board-approved rate, number of active drivers, and a note that figures are estimates pending advisor or auditor review.

Volunteers who deduct charity mileage on personal returns should get clear copies of their own logs—not a combined org export that includes everyone. Privacy and clarity both improve when each person receives their slice.

Publish which rate and which categories you use. Capture date, miles, purpose, name, and program code. Separate staff travel from volunteer miles. Confirm trips monthly. Export by program for grants. Share individual logs with volunteers who need them for personal records.

Model reimbursements with the free nonprofit tools on this site, then keep the living log in MileLedger so reporting is an export—not a reconstruction from calendars and text threads.