Volunteer program policies: five principles to build them on

Why start with principles, not a template

A downloaded template hands you pages and pages written for someone else's program, and you spend a week deleting the parts that don't fit. Principles are the five decisions underneath those pages. Make them first, and each policy turns into a short answer to one question: what does our principle say about this?

They help on the hard days too. The next time a “could the volunteers just…” email lands on your desk, “that isn't what our program is for” is a lot easier to say when it's already in writing.

1. Know who the program serves

Start with the people the work is for, then the work volunteers do for them. “Our volunteers sort and pack food for families who use our pantry” is a principle. “Volunteers help wherever they're needed” is how scope creep starts.

Next, list the roles you have, one line each, with the program each belongs to. When a new ask comes in, like covering the front desk or helping at the gala, check it against the list. If it fits, add a role with a short job description. If it doesn't, you already have your answer, and does this fit our mission? can help with the close calls.

2. Make the promise go both ways

Volunteers give their time. You give them a clear job, a heads-up before every shift, someone to ask and an easy way to step back. In return, you can ask them to show up when they said they would, tell you early when they can't, and follow the few rules that keep people safe.

Put both halves on one page, and only promise what you'll really do. A monthly check-in call you never get around to does more harm than no promise at all.

3. Put safety before speed

You can skip a lot when you're starting out. Not this. It's also the principle that most needs a local check. Think about three groups: the people you serve (especially children or vulnerable adults), the work itself (lifting, driving, kitchens, tools) and the volunteers (minors, health, getting home after a late shift).

For each risk, decide what a volunteer needs before they start: training, a skill or license, a signed waiver, a background check, or a second adult in the room. Then write it into the role, not into a separate binder nobody opens. Your insurer, and your state's rules for minors and background checks, will shape the details, so ask before you finalize. Our nonprofit insurance guide covers the questions to bring.

One more rule worth writing down: collect only the personal details a role needs. A date of birth or an emergency contact can wait until someone is on your team. It doesn't belong on a public sign-up form.

4. Make recognition part of the job

People stay where they feel seen, and that takes a habit more than a budget. Thank people on the day, by name, for something specific. Keep an honest record of the hours they give, because volunteers love seeing what their time adds up to, and so do your board and funders.

Then watch for the quiet ones. When Maria, a Saturday regular, hasn't been in since July, a short “We miss you, is everything okay?” often does more than an appreciation dinner. For the bigger moments, here are volunteer appreciation ideas that cost little or nothing.

5. Write down your no's

Every program needs a few written no's. No to roles that should be paid jobs. No to work outside your mission. No to an overbooked shift, with a waitlist instead of a crowded room. And no to a volunteer who isn't the right fit, said kindly and early, with another way to help if you have one.

Scope creep wins when the no lives only in the coordinator's head. On paper, it isn't you turning someone down. It's how the program works.

Turn the five principles into a one-page policy

Here's the whole thing on one page. Fill in the brackets, cut what you don't need, and have your director or board read it once before it goes out. Add a handbook later, for the practical things like where to park and what to wear.

Review it once a year, and again after anything goes wrong. Ask two or three of your regulars what's missing; they'll know.

How Ember Volunteers runs these, day to day

A policy sticks when the daily work follows it without anyone having to remember. Here's how Ember Volunteers handles each principle:

• Who it serves. Every shift belongs to a program. When you post a shift, Ember suggests the best times and how many volunteers are free then, counting only the ones with the skills the program lists.
• What volunteers can expect. Anyone can sign up for a shift from your one link with just a name and an email, and a confirmation email follows with the details. Your first 25 public sign-ups need nothing more from you, and confirming your EIN raises the limit. Each program emails volunteers a reminder 3 days before their shift, and you can add 2 weeks, 1 week or 1 day before.
• Safety. The public sign-up form never asks for a date of birth or guardian details. Ask for those yourself, privately, once someone is on your team.
• Recognition. Hours record when you check volunteers in, and volunteers with an Ember login can see every hour they've given in their own portal. Ember marks a volunteer Lapsing once it's been over two months since you last saw them, and the ones with nothing booked show up in a short weekly note to owners, admins and program staff.
• Saying no. When a shift is full, people on your public page can join its waitlist. Nobody moves up on their own, so you decide who fills an open spot.

Which of the five could you write down before the week is out?

The Ember tool for this

Ember Volunteers

Volunteers sign themselves up from one link, get a reminder before their shift, and their hours record when you check them in. You see who's gone quiet while there's still time to call. Free if your budget is under $50K a year.