The VBS Debrief Nobody Runs (And Why Your Volunteers Won't Come Back)

The Friday after VBS ends, everyone goes home and collapses. That's the pattern. The stage gets torn down Saturday morning by whoever shows up, the leftover snacks get dumped in the church kitchen fridge where they'll live until October, and the director sends a group text that says something like "YOU ALL WERE AMAZING, GO SLEEP." Then nothing. No meeting. No notes. No record of what actually happened.

And next February, when it's time to plan again, everyone starts from scratch. Every single time.

I ran VBS as a children's ministry director for eight years, and for the first three of those years I did exactly what I just described. Big emotional thank-you. Total shutdown. Then I'd spend the next spring trying to remember why the second-grade room was always chaos and whether we actually ran out of craft glue on Wednesday or if I just imagined that. (We ran out. We always ran out. I never wrote it down.)

Here's the operational reality that curriculum companies don't sell you on: the week itself is not the hard part. The hard part is that VBS is the single biggest volunteer mobilization most churches attempt all year, and almost nobody captures anything from it. All that data, all those observations about which stations worked and which volunteers thrived and which age group needed more help, just evaporates by Sunday.

So let me tell you what I finally started doing, because it changed my volunteer retention more than any recruitment pitch ever did.

I ran a debrief. A real one. Not the parking-lot "good job everybody" version.

The first year I tried it, I scheduled it for the Tuesday after VBS ended. Big mistake. People were fried and half of them didn't show. So the next year I moved it to the Thursday of VBS week itself, during the last 20 minutes, while everyone was still in the building and still had the week fresh. That worked. Not because people had more energy (they had less), but because the observations were still specific. Nobody was reconstructing a blurry memory. They could tell me exactly what happened at the craft table on Monday because it had happened that same week.

What I asked was simple. Three questions. What ran out. What you'd change. Who you'd want to work with again.

That third question surprised me the first time. I added it almost as an afterthought, thinking it was a nice team-bonding thing. It turned out to be the most valuable data I collected all year. Because when you're building next year's volunteer teams, knowing that your teen helper Marcus was incredible with the kindergarteners and that two of your adult leaders genuinely could not stand working the same station, that is gold. That's the difference between a team that clicks and a team that quietly falls apart by Wednesday.

I kept all of it in one document. Nothing fancy. A shared doc titled with the year, broken down by station and age group, with a running notes section. The running-out list. The volunteer pairing notes. The "this VBS curriculum ideas packet promised a 15-minute rotation but it took 25 and blew up our whole schedule" list. Every year that document got a little longer and a little more useful, and every year my planning in the spring got a little less like starting over.

Something I got wrong, and I want to be honest about it: I assumed the volunteers who complained the most were the ones least likely to come back. Wrong. Backwards, actually. The volunteers who gave me detailed, specific, kind of relentless feedback were almost always the ones who returned. The ones who said "everything was great!" and left fast were the ones I never saw again. Engagement looks like critique, not compliments. Took me years to understand that.

The pushback I always hear on this: people don't have time. It's the end of an exhausting week. Asking for a debrief feels like piling on.

Fair. I don't have a clean answer for churches running VBS with a skeleton crew of five overworked people, because in that situation, honestly, the debrief might genuinely be too much and you're better off with the director just jotting notes solo on Friday morning while it's fresh. This works best when you've got enough volunteers that the debrief is a shared ten minutes, not another task dumped on the one exhausted person.

But for most mid-size programs, the 20-minute debrief is the cheapest volunteer retention tool you own. Volunteers who feel like their observations went somewhere come back. Volunteers who feel like they poured out a week of their life into a black hole don't. It's not complicated, but it is completely counterintuitive to how most churches run the end of a big week, which is: applaud, disperse, forget.

The part that still bugs me is how much institutional knowledge churches lose to volunteer turnover simply because nobody wrote anything down. A church can run VBS for fifteen years and be no better at it in year fifteen than year three, because the person who figured out the check-in flow left, and the person who knew which rooms flooded when it rained moved to another state, and none of it lived anywhere except in their heads.

Write it down. Thursday afternoon, three questions, one document. Then next spring, before you buy a single new thing, open that document first.

That leftover snack fridge, though. That one I never solved.