The VBS Debrief Nobody Runs (And Why Your Volunteers Quit in October)

The last kid gets picked up on Friday afternoon. The decorations come down over the weekend, or they don't and they sit in the fellowship hall until Labor Day. Everybody's exhausted. Everybody says "that was great" and "see you next year."

And then nobody writes anything down.

That's the failure I saw more times than I can count during my eight years running children's ministry, and it's the one that quietly costs you volunteers. Not the chaos of VBS week itself. The silence after it.

Here's what actually happens. You run a huge week. Fifty kids, twenty-some volunteers, a schedule held together by adrenaline and a shared Google Doc that stopped being accurate on Tuesday. You survive it. Then you close the file, mentally, and you don't open it again until you're staring down next June wondering why the registration station was such a mess and why three of your best crew leaders suddenly "aren't sure about their schedule this summer."

They're not sure because nobody ever asked them how it went. Because the week ended and they never heard about it again until you needed them to say yes to another round of it.

In my experience, the debrief is the single cheapest retention tool in children's ministry and almost nobody does it. It costs you forty-five minutes and a willingness to hear things you'd rather not hear. That's the whole price.

I'm not talking about a survey. Please, not another survey. Volunteers who just gave you a week of their lives are not going to fill out a ten-question form with a satisfaction scale. They'll ignore it, and then you'll conclude "nobody had feedback" when the truth is you asked in a format nobody answers.

---

What works is a real conversation, scheduled within about ten days of the last day, while it's fresh but the exhaustion has worn off enough that people can think straight. I learned to book it before VBS even started. Put it on the calendar in May. "VBS wrap-up, Thursday June 18th, 7pm, pizza, one hour, done by 8." When you schedule it after the fact, it never happens, because by then everyone's brain has moved on to school starting.

And you keep it small and specific. Not "how did everyone feel about VBS." That gets you a room of nice people saying nice things. You ask the questions that surface the operational stuff:

• Where did you personally get stuck?
• What's the one thing that, if we fixed it, would make you say yes faster next year?
• What did you spend time on that a better system could've handled for you?

That last one is the money question. Because most of your VBS curriculum ideas and station plans probably worked fine. What didn't work was the logistics wrapped around them. The crew leader who never got a printed rotation schedule and spent the week guessing. The snack volunteer who found out about the kid with a peanut allergy on day three, from the kid. The registration table that had a forty-minute line on Monday because two people were doing a four-person job.

None of that is a curriculum problem. All of it is an operations problem, and all of it is fixable, and none of it gets fixed if you never write it down while the memory is sharp.

So here's the part that actually matters: you take notes during that conversation, and the notes become next year's prep document. Not a vague "improve registration" note. A specific one. "Registration needs four volunteers Monday, two the rest of the week. Pre-print name tags Friday before. Assign one person just to allergies and medical forms." That level.

I kept a running document I called the VBS carryover file. Ugly name, saved me every single year. By the third summer it had turned into something genuinely useful: a list of exactly what broke, who caught it, and what we changed. When a new director eventually took over that ministry, I heard that file was the only reason the first week under new leadership didn't fall apart. Because the institutional knowledge wasn't locked in one exhausted person's head. It was on paper.

And I'll be honest about the limit here, because I've watched this go sideways too. A debrief only works if you actually change something based on it. If your volunteers tell you the same thing two years running and nothing moves, you've now trained them that giving feedback is pointless, which is worse than never asking. I've seen a director run a beautiful wrap-up meeting, take great notes, and then do the exact same broken registration setup the next year because the notes lived in a document she never reopened. The debrief isn't the win. Acting on it is. The conversation is just how you find out what to act on.

One more caveat, since I know somebody's thinking it. If you run a tiny VBS, twelve kids and four volunteers who are all your close friends, you probably don't need a formal sit-down. You already know what broke because you all lived it three feet apart from each other. This is for the mid-size and up programs, the ones where the director genuinely does not see everything that happened at the snack station or the craft table or the check-in desk. Once you cross about fifteen volunteers, no single person has the full picture anymore. That's the threshold where you have to go collect it on purpose.

The thing I wish somebody had told me in year one is that your volunteers decide whether they're coming back long before you send the ask. They decide during that week, based on whether they felt set up to succeed or set up to scramble. And they confirm it in the weeks after, based on whether anyone seemed to care how it went for them.

A forty-five minute conversation with pizza tells them somebody cared. It's not a magic fix. But it's the difference between building next year's team from people who already trust the process and building it from scratch every June because your good ones quietly drifted off in October and you never knew why.