The VBS Volunteer Who Quits in July (and the Spreadsheet That Could Have Saved Her)

The woman who ran the craft station for three years straight sent her resignation by text message on a Tuesday in late July. No warning. Just a message that said she couldn't do it anymore and she was sorry. And here's the part that stuck with me: she wasn't burned out on kids. She was burned out on glue.

Specifically, on finding glue. And paper plates. And the pipe cleaners that were supposed to arrive with the VBS kit but didn't. She had spent every evening of VBS week driving to three different stores because the supply list and the actual box of materials never matched, and nobody had told her that was going to be her job on top of actually running the station for 45 kids.

That's not a faith problem. That's a logistics problem wearing a faith problem's clothes.

I've watched this exact thing play out at churches of wildly different sizes. A rural congregation running VBS for 30 kids off a single volunteer's kitchen table. A suburban program with 200 kids and a director who hadn't slept in four days. The scale changes. The failure point doesn't. It's almost always the gap between what the curriculum box promises and what actually shows up on Monday morning.

The curriculum isn't the problem. The handoff is.

Most VBS lesson plans are fine. Honestly. I've worked with enough of them to know that the actual teaching content, the stations, the daily themes, the memory verse structure, that stuff is usually solid. Publishers have been refining this for decades. The kids are going to have a good time if the adults can just get the materials into the right hands at the right time.

But vacation Bible school lesson plans almost never come with an operations layer. They tell you what to teach. They rarely tell you who's responsible for buying the 14 bags of cotton balls, when those cotton balls need to be in the building, and what the backup plan is when the shipment is late (and it will be late, roughly half the time, in my experience).

So the director fills that gap. Every time. And the directors who fill it badly lose volunteers like the craft station woman. The ones who fill it well build something a volunteer can actually walk into without a panic attack.

The difference between those two outcomes is usually one document. I'm not exaggerating.

What actually goes in the document

Here's what I've seen work, and I want to be honest that I've also seen it ignored by directors who were too deep in VBS week to look at their own plan. A document only works if someone owns it before the chaos starts.

• A per-station supply list with quantities, who's buying it, and the date it needs to be in the building. Not "construction paper." Say "6 packs of construction paper, assorted, purchased by June 1, stored in the closet off Room 4."
• Names.
• A single sentence next to each volunteer role describing what they are NOT responsible for, which sounds strange until you realize that the craft volunteer quitting over glue runs was entirely about a job she never agreed to absorbing silently until it broke her, and if someone had written "you are not responsible for sourcing missing supplies, text the coordinator" she might still be running that station today.
• A realistic time estimate per role, including setup and teardown, because volunteers who think they're committing to three hours and discover it's six will not come back next year.

That's it. That's the whole thing. It's not sophisticated. It fits on a few pages.

What makes it hard isn't the writing. It's the discipline to do it in May when VBS feels far away and you'd rather be doing literally anything else. I get it. I've put it off myself when I was coordinating a program, and I paid for it in frantic Wednesday-night supply runs that I could have prevented in April.

One caveat, and this matters: if you're running VBS for 15 kids with four volunteers who all know each other and have done it together for years, this level of documentation is probably overkill. Those small, tight programs run on relationships and nobody needs a spreadsheet to know who's bringing the snacks. The document starts earning its keep somewhere around the point where you have volunteers who don't all know each other, or a program big enough that no single person can hold every detail in their head.

I don't have a clean number for where that line is. I've seen 40-kid programs that needed heavy documentation because the volunteers rotated constantly, and 120-kid programs that ran smooth on institutional memory because the same twelve people had done it for a decade. It's less about headcount and more about how much of your operation lives in one person's brain. If the answer is "all of it," you're one bad week away from a July resignation text.

The craft station woman came back the next year, by the way. A different director rebuilt the whole volunteer structure over the winter, wrote the boring document, and assigned a single person to supply logistics. She told me the second year she never once left the building during VBS. That was the whole fix. Not inspiration. Not a better theme. A list with names on it.