VBS Isn't a Teaching Event. It's a Forgetting Event.

Most of what a kid learns at Vacation Bible School is gone by the following Tuesday. Not because the week was bad. Because it was designed, without anyone meaning to, to be forgotten.

That sounds harsh. I'll stand by it anyway. When you compress five lessons, four craft stations, a snack theme, a memory verse, and a nightly worship set into a single frantic week, you've built something that produces an incredible experience and almost no retention. Those are not the same outcome. We treat them like they are.

A memorable week and a learned truth are two different design goals, and most VBS plans optimize hard for the first one while assuming the second comes free.

It doesn't come free. Here's the problem from a learning design angle. Retention is a function of spacing and retrieval. Spacing means the gap between encounters with the same idea. Retrieval means being asked to pull the idea back out of your own head, not just hear it again. VBS violates both principles on purpose. Everything happens in one dense block (that's the whole appeal for working parents), and the week is so packed that kids are almost never asked to recall yesterday's point. They're too busy making the next foam visor.

I spent five years building curriculum for church and non-profit programs before this job, and I watched a decent-sized suburban church run a genuinely excellent VBS one summer. Great energy. Kids loved it. Volunteers nailed it. Then someone on staff did something almost nobody does: they asked the kids three weeks later what the theme had been. Most couldn't name it. These were engaged, happy kids who'd had a wonderful week. The experience landed. The content evaporated.

If you can't retrieve it a week later, you didn't learn it. You attended it.

So when people ask me for VBS curriculum ideas, my honest answer is usually not about the theme or the games. It's about building two or three deliberate retrieval moments into a week that's actively fighting against them.

The one design move that actually survives the week

Here's the change I've seen work, and it costs nothing. At the start of each day, before the new lesson, spend ninety seconds asking kids to tell you yesterday's point. Not you reminding them. Them telling you. A volunteer with a microphone, a couple of quick answers from the floor, done.

That's it. That's the whole intervention. It feels too small to matter, which is exactly why nobody does it. But that ninety seconds is a retrieval event, and retrieval is what moves something from "I heard that" to "I know that." You're taking a week built for forgetting and inserting the one mechanism memory actually runs on.

The cognitive science behind this (the testing effect, if you want to go read about it) is about as settled as anything in learning research gets. The catch is that it only works if the kid does the pulling. A review slide where the leader reads yesterday's verse out loud does almost nothing. The kid has to generate the answer. That distinction gets lost constantly, and it's the difference between review that works and review that's theater.

Why the crafts aren't the problem

I want to be careful here because the easy conclusion is "cut the fun stuff and teach harder." That's wrong, and it's the kind of advice that gets written by people who've never watched a seven-year-old at 10:45 on day three.

The crafts, the games, the songs, the snacks: those are doing real work. They're managing cognitive load. A kid can't absorb concept after concept for three hours straight, and the physical breaks are what let the brain reset. The problem isn't that VBS has too much fun. The problem is that the fun and the content run on parallel tracks that never touch.

• Tie the craft to the point.
• When the memory verse is about God providing, and the craft is a random foam cross with no connection to that idea, you've spent twenty minutes of prime attention on something that reinforces nothing. Make the craft the retrieval. Have them build the thing that represents today's truth and explain it back to a volunteer when they're done. Now the craft is doing double duty, and you haven't added a single minute to the schedule.

That second bullet is the whole ballgame, honestly.

I'll be upfront about what I don't know. I don't have clean data on how much VBS retention actually matters in the long run. A kid might forget the specific theme and still walk away with a real sense that church is a place where people are glad to see them, and maybe that's the more important outcome. I genuinely don't know how to weigh those against each other. Possibly the warm memory is worth more than the recalled verse. But if a church is going to spend hundreds of volunteer hours and a real chunk of its annual budget on five days of teaching, it's at least worth asking whether the teaching part is designed to stick or just designed to happen.

Most VBS plans I've seen are designed to happen. Beautifully. Loudly. And then gone by Tuesday.