Prepare a Volunteer Travel and Expense Policy for a Community Event

The short answer

A volunteer travel and expense policy is a short written agreement that tells volunteers which costs the event may cover, what needs approval before money is spent, what records to keep, how and when to submit a claim, and who reviews and pays it. Your job as an organizer is usually to draft the proposal. Your board, committee or sponsoring organization approves each provision and sets the effective date. Until that approval exists, nothing in the draft promises anyone a reimbursement.

This guide covers that drafting task for amateur tournaments and community events. It gives you a policy outline, a decision table for each expense category, a submission workflow and a worked example. Limits, rates and payment methods are left blank on purpose. Those are decisions for your organization, not defaults.

What a complete policy covers

Published templates follow a similar structure. ExpenseIn's volunteer travel and expense policy template is one example. It is organized around an introduction and booking procedures, expense categories and exclusions, reporting and documentation, unclaimed expenses, and policy updates with acknowledgment. The outline below builds on that structure and adds the review and payment roles a volunteer-run event needs spelled out.

• 1. Scope and contacts: which events, roles and dates the policy applies to, and who volunteers ask about it.
• 2. Booking and authorization: which costs must be approved in advance, who can approve them, and whether anyone books travel on volunteers' behalf.
• 3. Included and excluded categories: what the event may cover and what it will not.
• 4. Submission route and deadline: where claims go, in what form, and by when.
• 5. Missing records, unclaimed expenses and exceptions: what happens if a receipt is lost, a claim arrives late, or a cost falls outside the listed categories.
• 6. Review and payment responsibilities: who checks claims, who decides the accepted amount, and who records payment.
• 7. Version history and acknowledgment: the current version, its effective date, and how volunteers confirm they have read it.

Each of these items is an organizational decision. The draft should propose an answer for each one and mark it clearly for approval. Leaving an item unaddressed and hoping it never comes up is the thing to avoid.

Decide each expense category with a decision table

Go through every category you expect volunteers to raise, one row at a time. Typical candidates for an event are personal vehicle mileage, parking, tolls, public transit or rideshare, meals during long shifts, overnight lodging for out-of-town officials, and supplies bought on the event's behalf. Your event may need fewer or different rows. Fill in a row only after someone has thought through the circumstances. Leave a cell marked "to be decided" rather than guessing.

Proposed category	Circumstances considered	Advance authorization needed?	Proposed limit or calculation basis	Supporting records	Reviewer	Decision authority
Personal vehicle mileage	Volunteers driving to the venue or between sites	To be decided	To be decided by the organization	Trip date, start and end points, distance, purpose	Volunteer lead	Treasurer or committee
Parking and tolls	Venue parking, toll roads on approved trips	To be decided	Actual documented cost, or another basis the organization sets	Receipt or payment record	Volunteer lead	Treasurer or committee
Supplies bought for the event	Last-minute purchases such as scorecards, tape, first-aid restocking	Yes, proposed	To be decided	Itemized receipt and approval reference	Event coordinator	Treasurer or committee
Lodging	Officials or key volunteers traveling from out of town	Yes, proposed	To be decided	Booking confirmation and receipt	Event coordinator	Committee

The rows above only show how to fill in the table. They are not recommended limits or rules. The reviewer and decision-authority columns matter as much as the amounts. Volunteers need to know who says yes before they spend, and who says yes afterward. Where possible, the person who approves a claim should not be the person who receives the money.

Write the exclusions as explicitly as the inclusions. If the event will not cover something volunteers commonly assume it will, put that in the excluded list, so nobody finds out after paying. Fines, personal upgrades or a companion's travel are possible examples, depending on what your organization decides.

Set out the submission workflow

Describe the claim process as a sequence of steps, each with a named owner. A volunteer should be able to follow it without asking anyone.

• 1. Before spending, the volunteer obtains any advance approval the policy requires and keeps the approval reference, such as a message, form number or written note.
• 2. After the expense, the volunteer submits the date, purpose, amount, currency, category, supporting record and approval reference.
• 3. The reviewer checks the claim against the approved policy: is the category included, are the records present, and was advance approval obtained where required?
• 4. The decision-maker records the accepted amount and the reason, including the reason for any reduction or refusal.
• 5. The finance owner records payment status under whatever payment arrangements the organization has confirmed.

State the submission route and deadline in the policy itself. The route might be a shared form, a paper envelope at the scorer's table, or a message to the treasurer. A single route makes claims easier to track than several informal ones. A deadline lets the treasurer close the event's books.

Worked example: adding up a claim

This is a hypothetical example. Suppose the approved policy reimburses actual documented travel costs. A volunteer submits two records, one for 12 currency units and one for 8, so the submitted total is 20. That figure is only what was claimed. The reviewer still checks each record against the policy, and the decision-maker records the accepted amount. The arithmetic creates no entitlement.

Claim: Volunteer A, registration desk, tournament day 1
  Record 1   parking            12
  Record 2   transit fare        8
  ---------------------------------
  Submitted total               20
  Approval reference            [from step 1]
  Accepted amount               [recorded by decision-maker]
  Reason                        [recorded by decision-maker]
  Payment status                [recorded by finance owner]

Missing records, unclaimed expenses and exceptions

These cases cause most disputes, so the draft should propose a specific treatment for each one:

• Missing records: whether a signed explanation can substitute for a lost receipt, and up to what point.
• Unclaimed expenses: what happens to costs not submitted by the deadline, and whether volunteers can choose not to claim.
• Exceptions: who can approve a cost outside the listed categories, and how that decision is recorded so it does not quietly become precedent.

Tax treatment of volunteer reimbursements and unreimbursed volunteer costs, along with any record-keeping obligations attached to them, depends on your organization's status and the applicable rules. Have the treasurer or your accountant confirm these points before the policy is approved, because they can affect how you set the calculation basis and what records you require.

Get it approved and acknowledged

Bring the outline, the completed decision table and the workflow to whoever governs the event's money. Ask them to approve each provision individually rather than the document as a whole, and record the effective date and version number. Then share the approved policy with volunteers when they sign up, not on event day. Ask each volunteer for a simple acknowledgment that they have read it. When the policy changes, update the version history and collect acknowledgments again from anyone the change affects.