How to Write a Volunteer Position Agreement

There's a version of volunteer management where everyone understands exactly what they're signing up for, the organization knows what it can rely on, and nobody ends up frustrated because of a mismatch between expectations and reality. A volunteer position agreement won't get you all the way there on its own, but it helps.

This isn't about paperwork for its own sake. It's about the kind of clarity that prevents uncomfortable conversations six weeks in.

What's the difference between a position agreement and a waiver?

These two documents often get confused, and they serve completely different purposes.

A volunteer waiver (sometimes called a release of liability) is about legal protection. It documents that the volunteer understands any physical or safety risks involved in the role and releases the organization from liability in certain scenarios. Most nonprofit lawyers recommend one for any program involving physical activity, equipment, or interaction with vulnerable populations.

A volunteer position agreement is about the working relationship. It describes what the volunteer has agreed to do, what the organization has agreed to provide, and what the expectations are on both sides. It's less about legal protection and more about shared understanding.

You may need both. You may only need one. If you're running a food bank sorting program with minimal safety risk and very standard shifts, a waiver may be optional. If your volunteer role involves driving a vehicle or working with children, talk to a lawyer about what you need. The position agreement, though, is worth having almost regardless.

What to include in a volunteer position agreement

A useful agreement doesn't need to be long. One or two pages is plenty. It should cover:

The role and its scope. What is the volunteer actually doing? Be specific. "Helping with programs" is not a role description. "Assisting the lead coordinator with check-in at weekly food distribution shifts, every Saturday from 9am to noon" is.

The time commitment. How often? For how long? Is there an end date to the commitment, or is it open-ended? Spelling this out upfront prevents the awkward moment where a volunteer assumes they signed up for one event and you were counting on them for a year.

Training and onboarding requirements. If there's a required orientation, a safety training, or any certifications the volunteer needs before their first shift, note it here. This also gives you a clear record of what was completed.

What the organization provides. This part gets skipped sometimes, and it shouldn't. If you're providing supervision, materials, a point of contact for questions, or any form of acknowledgment (volunteer appreciation events, reference letters), say so. Volunteers who know what to expect from you are more likely to feel like partners rather than unpaid labor.

Confidentiality expectations. If volunteers will encounter private information about clients, participants, or organizational finances, note the expectation here. It doesn't need to be a formal NDA, just a clear statement that what they see in the course of their work stays within the organization.

How the relationship can end. This sounds formal, but it matters. Note that either party can end the arrangement, and briefly describe how you'd handle it (a conversation, some notice, returning any materials). If your volunteer policies include a process for releasing a volunteer from a role, referencing that here keeps everything consistent.

What you can skip

A few things that coordinators sometimes include but rarely need:

• Lengthy legal language. This is an agreement, not a contract. If you want a legally binding document, have a lawyer draft it. Otherwise, keep the language plain and human.
• Promises about future roles. Don't include language suggesting the volunteer is on a path to leadership or paid employment unless that's actually the program you're running.
• Performance metrics. An agreement isn't a performance review template. You can note general expectations, but leave specific evaluation criteria for a separate conversation.

The job description connection

A position agreement works best when it builds on a volunteer job description that already exists. If you've done the work of describing the role clearly for recruitment purposes, you've already got the foundation for an agreement. The job description tells people what the role is. The agreement documents that a specific person accepted it and understands what's expected.

Think of the two documents as different moments in the same relationship. The job description is the pitch. The agreement is the handshake.

When to have someone sign it

Timing matters. The worst time to hand someone an agreement is the minute they walk in the door for their first shift, when they're excited to help and may sign anything just to get started.

A better approach: send it as part of your onboarding sequence, after orientation and before the first shift. Give people a day or two to read it and ask questions. This is also a good moment to confirm that everything in the volunteer onboarding checklist has been covered.

If the agreement contains anything that might feel surprising, like a confidentiality requirement or a specific time commitment, flag it in a conversation before you send it. Written documents land differently when someone already understands what they're agreeing to.

How a position agreement connects to harder conversations later

One of the unexpected benefits of having a position agreement: it makes difficult conversations easier to have when they're needed.

If a volunteer consistently shows up late, or takes on tasks outside their defined role, or isn't completing what they signed up for, you now have something specific to refer back to. Not in a punitive way, but in a "here's what we both agreed to, let's talk about what's getting in the way" way.

This connects directly to setting expectations with first-time volunteers at the start of the relationship. The more clearly you communicate upfront, the less likely you are to need an uncomfortable conversation later. But when you do need one, having a shared reference point helps.

Where Volunteer Shift Manager fits

Volunteer Shift Manager doesn't generate position agreements, but it does handle the part that comes after: getting volunteers signed up for shifts, sending reminders, and tracking who showed up. If your onboarding process involves sending someone a position agreement before their first shift, you can reference the shift signup link as the next step once they've returned the agreement.

Keeping those two things connected (the paperwork and the scheduling) is the difference between a volunteer who shows up informed and one who shows up wondering what they agreed to.

Getting it done without overthinking it

A volunteer position agreement doesn't need to be a legal document. It needs to be a clear, honest description of what you're both agreeing to. One page, plain language, signed before the first shift. That's enough to prevent most of the expectation mismatches that cause friction later.

If you're using a generic template from the internet, spend five minutes customizing it for your specific role and organization. Generic documents communicate generic effort. A position agreement that actually describes the work sends a different message: we thought about this, and we're glad you're part of it.