How to Evaluate a Volunteer Program After Its First Year

A lot of volunteer programs make it through their first year and then just... keep going. Which sounds fine, but it often means carrying forward all the things that didn't work alongside the things that did. Year two becomes a repeat of year one, and the coordinator who ran it is quietly exhausted from the same problems that plagued them in month three.

A first-year review doesn't have to be a formal evaluation process with a committee and a report. For most small nonprofits, it's more useful as a structured conversation you have with yourself and your key volunteers, followed by a few concrete decisions. The goal isn't to grade yourself. It's to make year two better than year one.

What to measure (and what not to over-index on)

There are obvious numbers to collect: total volunteers, total hours, shifts filled versus shifts you couldn't staff, volunteer retention rate (how many returned after their first shift), and any outcomes directly tied to your program's work.

These matter. But first-year numbers are almost always misleading in one direction or another. Programs often start strong because of launch energy, then dip before finding their steady state. Or they start slow because recruiting takes time, then finish the year with a full roster. A single year of data doesn't tell you whether you have a sustainable program. It tells you where you started.

What's more useful than comparing year-one numbers to some abstract standard is identifying trends within the year. Did retention improve as you refined your onboarding? Did no-shows spike around a particular time or shift type? Did certain volunteer roles attract people easily while others stayed chronically understaffed?

Those patterns are where the learning lives.

The questions worth asking

Before you dig into data, sit with a few honest questions:

What were you proud of? Name the specific moments or outcomes you felt good about. Not "we served the community" but "we filled every shift during the holiday rush and nobody panicked." The specifics tell you what actually worked.

What frustrated you most? Not the external things you couldn't control, but the friction inside your own program. If you spent a lot of time manually following up with volunteers who didn't confirm, that's a systems problem, not a people problem.

What did volunteers complain about? This is different from your frustrations. Volunteers experience your program differently than you do. The thing that felt fine to coordinate might have felt confusing to participate in.

What did you not do that you meant to? Every coordinator has a list. The volunteer recognition event that never happened. The welcome email sequence you kept meaning to set up. The debrief you planned to run after your big event. These aren't failures; they're information about what your actual capacity is.

Getting useful feedback from volunteers

Sending a survey is the obvious move, but surveys only work if you ask the right questions and make them short enough to complete.

Three questions that consistently produce useful responses:

1. "What was the most useful part of being a volunteer with us this year?"
2. "What was the most confusing or frustrating part?"
3. "Is there anything we could do differently that would make you more likely to volunteer again?"

Open-ended questions produce better insights than rating scales. A volunteer who gives you a four out of five tells you very little. A volunteer who says "I never knew what to do when the supplies ran out" tells you something you can fix.

Your volunteer satisfaction survey doesn't have to be comprehensive to be useful. Three good questions are better than twenty mediocre ones.

Reviewing your goals against reality

If you set goals at the start of the program, now is the time to look at them honestly. If you hit them, that's worth acknowledging. If you didn't, the question isn't "what went wrong" but "were the goals realistic, and what specifically got in the way?"

Many first-year programs set goals based on what they hoped for, not what the data suggested was achievable. That's okay. It's how you learn to set better goals for year two. Setting measurable program goals is a skill, and the first year gives you real baseline data to work from.

The operational systems question

Beyond outcomes, think about the systems that supported your program day-to-day. Were you spending more time on coordination tasks than on the actual work of the program? Were there manual processes you could automate?

Common first-year systems problems:

• Volunteer signups happening through a general email instead of a dedicated signup page
• No confirmation or reminder process, leading to no-shows
• Tracking hours in a spreadsheet that requires manual updates after every shift
• No way for volunteers to cancel a shift without calling or texting directly

These aren't catastrophic, but they compound. Every manual process you run takes time away from more valuable work, and it scales poorly as your program grows. The volunteer program documentation you create now will make it easier to hand things off, train new volunteers, and see what to systematize.

Three things to decide before year two starts

A first-year review is only useful if it produces decisions. Here are three worth making explicitly:

What are you going to stop doing? Every program accumulates practices that felt right at the time but don't actually serve the mission. A weekly all-staff update email nobody reads. A sign-in sheet process that creates double work. A volunteer role that was always understaffed because nobody wanted it. Name the things you're cutting.

What are you going to do differently? Pick one or two friction points to address before year two begins. Not everything, not a full process overhaul, just the things that caused the most pain. If no-shows were your biggest problem, invest in reminders and confirmation systems. If onboarding felt chaotic, write a cleaner checklist.

What are you going to track from the beginning? The most useful year-two data is the data you collect consistently from the start. If you didn't track volunteer retention rates in year one, decide now how you'll capture them in year two. If you didn't document the reasons volunteers left, add that to your exit conversation process.

The honest version

Some volunteer programs don't survive their first year. Others survive but shouldn't, because they're consuming more organizational energy than they're returning in impact. Part of a genuine first-year review is asking whether the program is worth continuing in its current form, and being willing to let the answer be "not quite."

That's not a failure. Adjusting a program's scope, focus, or structure after year one is a sign of organizational maturity, not defeat. The alternative is running a struggling program into year three and four out of inertia.

If you're not sure where you stand, a volunteer program audit can help you look at things more systematically. And if your program is dealing with data you've never quite made sense of, using volunteer data to make better decisions is worth reading before you plan your year-two approach.

Year one is an experiment. Year two is where you apply what you learned.