We've covered onboarding (clear roles beat vague vibes) and delegation (let go of the wheel on small stuff). But there's a phase after that nobody preps you for: month 4-6, when volunteers who were reliable start quietly fading.

Chapter 3 gets into this, but here's the pattern I see most: it's rarely the volunteer burning out first. It's the lead.

When the person running the team gets stretched thin, the small things that made volunteers feel valued disappear first — the shoutout in chat, the quick "how'd that go for you" check-in, the heads-up before a schedule change. Volunteers don't leave because the work got harder. They leave because the relationship got thinner.

What's actually kept people around, from what's worked in this community:

• Rotate the recognition, not just the tasks. If the same 2-3 people get thanked every time, everyone else assumes their work doesn't register.

• Ask before you assume someone's out. A volunteer who goes quiet for two weeks isn't always quitting — sometimes they're waiting to be asked back in.

• Protect your own bandwidth like it's a team resource. If you're too burned out to notice engagement dipping, nobody else is watching for it either.

• Re-recruit your best people every few months. A quick "here's what's next, and here's why I want you specifically on it" conversation resets commitment better than any thank-you message.

So — for the teams you're running or have run: when did you first notice a volunteer disengaging, and what actually got them to stay (or what did you wish you'd done differently)?

Every guide tells new team leads to "delegate more." Cool advice. Zero instructions.

Six months into running a volunteer crew, I finally figured out why my early attempts at delegating kept backfiring — I'd hand off a task, then check in so often the volunteer felt like they hadn't actually been trusted with anything. They'd disengage within two weeks.

Here's what changed once I stopped hovering:

• Delegate the outcome, not the steps. Tell them what "done" looks like, not how to get there. Micromanaging the process is what makes people feel like a pair of hands instead of a teammate.

• Set one check-in, not five. Pick a single point (e.g., 48 hours before an event) to review progress. Constant pings signal you don't trust them.

• Let small things break. If a volunteer's approach isn't how you'd do it but it still gets the job done, let it ride. Perfection on your terms isn't the goal — reliability is.

• Match the task to the person, not the org chart. The person who's great at logistics shouldn't be running icebreakers just because there's a slot to fill.

The teams that scale past 10-15 volunteers are the ones where the lead has actually let go of the wheel on the small stuff. The ones that stay small are usually still run by someone who "just delegates" but rechecks everything anyway.

If you're leading a team right now — where's your delegation actually breaking down? Is it trust, unclear outcomes, or just not having the right person for the task?

Ran a community event last year with 40 signed-up volunteers. By week 3, only 11 showed up. Not because people didn't care — they signed up, after all — but because of one mistake I see almost every new organizer make:

No one told them exactly what to do.

"Help out at the event" is not a role. It's a vibe. And vibes don't survive contact with a Saturday morning when someone would rather sleep in.

What actually fixed it for us the second time around:

• Name the role, not the vibe. "Check-in table lead" beats "help with registration." Specific roles create ownership; vague asks create optional participation.

• Give a first task within 48 hours of signup. Momentum dies in the gap between "yes I'll help" and actually doing something. Close that gap fast.

• One person, one point of contact. Volunteers ghost committees. They don't ghost people who know their name.

• Say thank you in public, not just private. A callout in your group chat does more for retention than a nice DM ever will.

None of this is groundbreaking. It's just easy to skip when you're busy planning the actual event. But the teams that stick around aren't the ones with the best cause — they're the ones with the clearest structure.

Curious if others here have found different levers that moved the needle on volunteer retention. What worked for your team?