Nonprofit Volunteer Policies: What You Actually Need (and What You Can Skip)

Most small nonprofits I've worked with have one of two problems with policies. Either they have nothing written down and are quietly hoping nothing bad happens, or they downloaded a 40-page volunteer handbook template from somewhere and now no one reads or signs it. Both are bad outcomes for the same reason: the policies aren't doing the job they're supposed to do.

Volunteer policies exist to protect three things: the people doing the work, the people being served, and the organization. That's it. If a policy isn't clearly serving one of those, it doesn't need to exist. This guide walks through the ones that earn their place and the ones you can skip.

What volunteer policies are actually for

Before deciding what to write, get clear on the job. A good volunteer policy does one of four things:

1. Sets safety expectations so volunteers don't get hurt and don't accidentally hurt others.
2. Defines the boundary between what a volunteer is and isn't responsible for.
3. Protects sensitive information about the people you serve.
4. Gives you a clear way to act when something goes wrong.

Anything else is filler. The longer your handbook, the less likely anyone reads it, including you when you actually need to refer to it.

The five policies most small nonprofits do need

These are the ones worth the effort. You can usually fit all of them in a single short document.

1. A waiver and release of liability

If volunteers do anything physical, drive on your behalf, work with children, work with food, or are on property you don't own, you want a signed waiver. It doesn't make you immune to lawsuits, but it documents that the volunteer understood the risk and chose to participate anyway.

Keep it short. A page is enough. State what activity they're consenting to, acknowledge that volunteering carries some inherent risk, and have them sign and date it. If you're not sure what to include, your state's nonprofit association probably has a free template, or the Council of Nonprofits has guidance.

2. A code of conduct

This is the document you'll actually use most often, and most nonprofits don't have one. It should say plainly: how volunteers are expected to treat staff, each other, and the people you serve. What language and behaviour aren't tolerated. What happens if someone violates it.

Three paragraphs is enough. The point is to give yourself something to point to when a volunteer isn't working out, not to anticipate every possible scenario.

3. A confidentiality agreement (if you serve sensitive populations)

If your volunteers will see client names, medical info, addresses, immigration status, or anything that could harm someone if it leaked, you need a signed agreement. One paragraph saying "I will not share what I see or hear here outside of the organization, including on social media" covers most of it.

This is non-negotiable for healthcare, domestic violence, immigration, and youth-serving orgs. For a community garden, probably not necessary.

4. A photo and likeness release

If you ever post volunteer photos on social media or in newsletters, get this signed at intake. It's a checkbox on the same form as the waiver. Two sentences. Including a way for someone to opt out specifically.

This one is small but matters. Some volunteers don't want to be photographed for personal safety reasons (custody situations, leaving an abusive relationship, immigration status, etc.). Asking the question respects that.

5. A clear "what to do if something goes wrong" reference

Not really a policy in the legal sense, but it functions like one. A single page that tells a volunteer:

• Who to call if there's a medical emergency
• Who to call if a participant gets aggressive or unsafe
• Who to call if they witness something concerning involving a child or vulnerable adult
• Who to call if they get injured or feel unsafe

If you've ever had a volunteer freeze up because they didn't know what to do, you understand why this is worth writing down. Put it on a laminated card and stick it wherever your volunteers actually are.

Policies you can usually skip

These come up in templates a lot. Most small orgs don't need them.

• Dress code policies. Just tell volunteers what to wear in the shift description. Codifying it in a separate document is overkill.
• Cell phone use policies. Same thing. If you don't want phones out during shifts, say so when you onboard the person.
• Punctuality and attendance policies. Putting "be on time" in writing doesn't make anyone more punctual. What helps is reminders that get answered and a culture where the coordinator notices when someone's reliable.
• Lengthy harassment and discrimination policies copied from corporate HR templates. Your code of conduct should cover this in plain language. A 12-page HR document creates the illusion of protection without doing much.
• Drug and alcohol policies for roles where it isn't relevant. If a volunteer is sorting clothes at a thrift store, you don't need a policy. If they're driving a van of seniors to medical appointments, you do.

The principle: write policies for the actual risks of the actual work. Don't write policies for theoretical risks you copied from someone else's program.

How to write a policy that people will actually read

Three rules. They're more important than the legal nuance.

Use the words people use. "Volunteer" not "service-engaged community participant." "Quit" not "voluntarily terminate engagement." The more it sounds like a contract, the more it gets skimmed.

Put the action up front. A confidentiality policy should start with "Don't share what you see here outside the organization." Then explain. Most people stop reading after the second sentence anyway, so make those count.

Keep it on one page. If your full volunteer policy doc is more than two or three pages, you've written too much. The signal you're sending isn't thoroughness, it's distrust. People notice.

When to ask a lawyer

You don't need an attorney to write a code of conduct or a confidentiality clause. You probably do if you're:

• Working with children, where state laws vary on background checks and reporting requirements
• Operating in healthcare or any HIPAA-adjacent space
• Bringing volunteers across state lines or internationally
• Coordinating a large surge of volunteers during a disaster, where liability questions get unusual

For most everything else, your state's nonprofit association has templates and free guidance. Use them as a starting point, then strip out everything that doesn't apply to your work.

Where Volunteer Shift Manager fits

We don't generate volunteer policy documents. What we do is make it easier to actually use them once you've written them, by giving you a place to attach a waiver to the signup flow so a volunteer reads and accepts it before they can claim a shift, and to track who's signed what.

If you've ever had to dig through a filing cabinet to find a waiver signed in 2022, that part of the problem is solvable. The harder part, writing policies that fit your work and not somebody else's template, is on you.

The honest take

A good volunteer policy is one that someone can read in three minutes, sign with understanding, and refer back to if something goes wrong. Most nonprofits have either no policies or policies that are too long and too generic to be useful. The middle path, a short clear document that covers the real risks of the real work, is what you're aiming for. It protects everyone involved without making volunteering feel like signing up for jury duty.