The events chair said she’d book the venue by Friday. It’s Monday. No venue. You text her. She responds with “sorry, it’s been a crazy week. I’ll do it tomorrow.” Tomorrow comes. Nothing. You text again. She doesn’t respond for two days. You book the venue yourself at 11 PM on Wednesday because the event is in three weeks and you’re out of time.
Next month, you ask for volunteers for the fundraiser. She raises her hand again. You smile, nod, and quietly plan to do her tasks yourself. Because holding her accountable felt harder than just doing the work.
This is the accountability problem in every volunteer organization. Nobody’s getting paid. Nobody signed a contract. The only tool you have is goodwill, and using goodwill to enforce deadlines feels like punishing someone for donating their time.
So accountability doesn’t happen. Deadlines slide. Commitments evaporate. The same reliable people do everything. The unreliable ones keep volunteering and keep not following through. And the reliable ones burn out.
Why Accountability Feels Wrong (and Why It Isn’t)
Holding volunteers accountable feels like being a boss in a place where nobody asked for a boss. Your members are doing this for free. Who are you to demand results?
Here’s the reframe: accountability isn’t punishment. It’s respect.
When you don’t hold someone accountable for a commitment, you’re saying their contribution doesn’t matter. If the events chair books the venue or doesn’t book the venue and nothing changes, the message is clear: what you do doesn’t actually affect anything. That’s not freeing. It’s demoralizing.
The organizations that retain the best volunteers aren’t the ones with the loosest standards. They’re the ones where commitments mean something. Where saying “I’ll handle the flyer by Thursday” matters because someone’s counting on it. That sense of being counted on is what makes volunteering feel meaningful instead of optional.
Volunteer burnout doesn’t come from too much accountability. It comes from too little. When nobody’s held accountable, the reliable people absorb all the dropped balls. That’s what burns them out.
Start Before the Commitment: Set Clear Expectations
Most accountability failures aren’t failures of follow-through. They’re failures of setup. The person didn’t do the task because the task was never clearly defined.
“Can you help with the picnic?” isn’t a commitment. It’s a vague intention. What part of the picnic? By when? What does “done” look like?
“Can you order the paper goods for the picnic by June 5? We need plates, cups, and napkins for about 60 people. Budget is $50. Here’s the membership card for reimbursement.” That’s a commitment. It has a deliverable, a deadline, a scope, and a resource. The person can say yes to something specific or say no to something specific. Both answers are useful.
Every task you assign should answer four questions: What exactly needs to happen? By when? What resources do you have? Who do you tell when it’s done?
The Three-Strike Framework (Without Calling It That)
You don’t need a formal disciplinary process. You need a pattern of escalation that feels natural.
First time someone doesn’t deliver: assume good faith. Life happened. Send a casual check-in. “Hey, just wanted to follow up on the venue booking. Everything okay?” No judgment. No frustration. Just a question. Most of the time, this is enough. They apologize, they do it, done.
Second time: a direct conversation. Not by text. By phone or in person. “I noticed the last two tasks didn’t get done on time. Is there something going on, or is this a bad time to be taking on extra? No shame either way. I just want to make sure we’re setting you up to succeed.”
This conversation gives them an exit ramp. Maybe they overcommitted. Maybe they have family stuff. Maybe they just don’t want to do this particular type of work. Giving them the chance to say “actually, can someone else take this?” is a kindness, not a criticism.
Third time: reassign quietly. Don’t make a public announcement. Don’t call them out at a meeting. Just stop assigning them tasks that have deadlines. Keep them involved socially. Let them show up to events, participate in discussions, enjoy the community. But don’t put them on the critical path.
Some people are great community members and terrible task completers. That’s fine. Not everyone has to be a worker bee. But the organization needs to know who it can rely on and plan accordingly.
How to Follow Up Without Micromanaging
There’s a line between accountability and hovering. Checking in every day on a task due in two weeks is micromanaging. Never checking in until the deadline passes is negligence. The middle ground is one check-in at the halfway point.
Task assigned on Monday, due Friday? Check in Wednesday. “How’s the venue booking going? Need anything from me?” That’s it. Brief. Helpful. It signals that you’re paying attention without standing over their shoulder.
For longer projects, check in weekly. Same format. “Quick update on the newsletter? Anything blocking you?” If they say they’re on track, trust them. If they say they need help, provide it. If they don’t respond, that’s data.
The check-in removes obstacles, not catches failures. Often the person who’s behind isn’t lazy. They’re stuck. They don’t know who to call. They can’t find the login. They don’t have the budget number. A quick check-in surfaces these blockers before the deadline passes.
Accountability for Board Members
Board accountability is trickier because board members are peers, not subordinates. You can’t “manage” a fellow volunteer. But you can create structures that make accountability the default.
Written role descriptions. Before someone joins the board, give them a one-page document that lists their responsibilities, time commitment, and meeting attendance expectations. “The treasurer is expected to attend at least 9 of 12 monthly meetings, present a financial summary at each meeting, and reconcile accounts within one week of each month’s end.” If someone can’t commit to that, better to know before they join than after they’ve gone silent for three months.
Meeting attendance policies. Your bylaws probably already have one. Enforce it. “A board member who misses three consecutive meetings without notification may be removed by majority vote.” This provision exists for a reason. Use it when needed. It’s not personal. It’s governance. When board members go silent, the attendance policy gives you a framework for the conversation.
Quarterly self-assessments. Once a quarter, each board member answers three questions: What did I accomplish this quarter? What do I plan to do next quarter? Do I need anything from the rest of the board? Share the answers with the full board. The transparency itself creates accountability. Nobody wants to write “accomplished nothing” three quarters in a row.
Accountability for General Members
General members have fewer formal commitments, but there are still expectations worth enforcing.
Dues. If someone hasn’t paid, follow up. Twice. Then apply whatever policy your bylaws specify (usually suspension of voting rights, access to events, or membership itself). This isn’t harsh. It’s fair. The members who do pay are subsidizing the ones who don’t. Free digital tools can automate these reminders so you don’t have to be the bad guy. Payment methods matter here too. Some members don’t pay because the process is inconvenient, not because they don’t want to.
Event commitments. If someone RSVPs yes and doesn’t show up, that’s a data point. If they do it three times, stop planning around their RSVP. This isn’t punitive. It’s practical. When you’re ordering food for 40 and only 28 show up, the 12 no-shows cost the organization money.
Volunteer commitments. If someone signs up for a volunteer task and doesn’t complete it, follow up with the casual check-in (first time) or direct conversation (second time). But also look at the pattern. If the same people keep dropping tasks, stop assigning them tasks and find episodic volunteers who’ll complete a specific, bounded commitment.
The Hardest Part: Being Consistent
Accountability only works if it applies to everyone. The founding member who’s been around since 2008 doesn’t get a pass on paying dues. The president’s best friend doesn’t get to skip meetings without consequence. The moment accountability becomes selective, it becomes resentment.
This is genuinely hard. These are your friends. Your community. The person you’re holding accountable might have hosted your family for dinner last week. But selective accountability poisons an organization faster than no accountability at all, because it signals that rules exist for some people and not others.
Apply the same standards evenly, use the same gentle escalation with everyone, and separate the personal relationship from the organizational role. You can love someone and still say: “We need the report by Friday.”
What Happens When You Get This Right
Organizations with clear, consistent accountability have fewer burned-out leaders, more reliable volunteers, and less drama at board meetings. Not because they’re strict. Because expectations are clear. People know what they’re signing up for, they know someone’s counting on them, and they know that their contribution matters enough to track.
That’s not being a dictator. That’s building a community where showing up actually means something.
Clear expectations need clear data. Somiti tracks who’s paid, who’s volunteered, and who’s committed to what, so accountability is based on facts, not feelings.