The Fifth Day of VBS Is Where Retention Goes to Die

Nobody remembers what they learned on Wednesday of VBS week. Not the kids. Not the volunteers. Usually not even the person who wrote the lesson.

That's not a knock on VBS. It's just what happens when you compress five days of teaching into a format designed around energy, snacks, and a decibel level that would concern OSHA. The whole thing is built to feel unforgettable. And the feeling is real. But feeling and retention are different systems in the brain, and most vacation Bible school lesson plans are optimized for the first one at the expense of the second.

Here's the thing I keep running into when I look at how VBS is structured from a learning design angle.

A week of intense, high-arousal experiences produces vivid memory of the experience and almost no memory of the content.

Kids will remember the foam party. They'll remember the giant inflatable. They'll remember Pastor Greg getting a pie in the face on Friday. Ask them three weeks later what the Thursday Bible point was and you'll get a blank stare, maybe a shrug, occasionally a confident wrong answer. I've watched this play out across churches of wildly different sizes, and the pattern doesn't care whether you spent $400 on curriculum or built it yourself.

The reason is boring and well-documented. It's called the spacing effect, and it's one of the most replicated findings in cognitive science. Learning that gets distributed across time, with gaps in between, sticks dramatically better than learning crammed into a concentrated block. VBS is the crammed block. Five days, back to back, then nothing. It's the single worst possible schedule for durable memory, and we've somehow made it the flagship educational event of the church calendar.

If you want kids to remember the content, the design problem isn't the week itself. It's what happens in the four weeks after it.

Most VBS planning stops at Friday. The volunteers are exhausted, the director is running on coffee and adrenaline, and the last thing anyone wants to think about is a follow-up. I get it. I've watched ministry teams collapse into a heap on Saturday morning and consider the whole thing a win because nobody got lost and the fire marshal didn't show up. Fair enough. Survival counts.

But if retention is actually a goal (and I'd gently ask whether it is, because sometimes VBS is really an outreach and community event wearing a curriculum costume, which is fine, just be honest about it), then the design has to extend past the week.

What that looks like in practice is smaller than you'd think. One church I worked with sent home a single index card each day with one question on it, tied to that day's story. Not a packet. Not a workbook. A card. Parents were told to ask the question at dinner sometime in the next week. That's a crude version of spaced retrieval, and retrieval practice (the act of pulling information out of memory rather than reviewing it) is the second most powerful lever we have after spacing.

Did it work? Honestly, I don't have clean data on it. The director thought so. A few parents mentioned kids bringing up the stories weeks later. But I'm not going to pretend a stack of index cards is a controlled study. What I can say with confidence is that the underlying mechanism is sound, and it costs almost nothing to try. That's a rare combination in curriculum, where the expensive thing and the effective thing usually aren't the same thing.

The deeper issue is that VBS content is often designed to be forgotten. The Bible points get simplified into a five-word slogan repeated with hand motions. Which, fine, hand motions plus repetition does help encoding. But a slogan is not a concept. "God is with you" chanted forty times encodes the phrase, not the theological idea behind it, and kids are perfectly capable of reciting a phrase they don't understand. I've heard eight-year-olds nail the daily catchphrase and then completely fail to connect it to the actual story it came from.

Repetition builds fluency with the words. It doesn't build understanding of the meaning. Those are separate outcomes and they require separate design choices.

So what would I actually change if I were rebuilding vacation Bible school lesson plans from the learning side?

I'd cut the number of Bible points in half. Five stories in five days is too much surface area for durable memory in a high-distraction environment. Three, taught deeper, with deliberate callbacks between them, would outperform five taught in isolation. Fewer things, more connections. That's not a VBS principle, that's just how memory consolidation works.

I'd build one retrieval moment into every single day, and I don't mean a review video. I mean kids actually generating an answer, out loud or on paper, before you tell them anything. The generation effect says that struggling to produce an answer, even a wrong one, before seeing the correct answer produces better retention than just being shown the correct answer cleanly. It feels less smooth. It works better. Most curriculum avoids it because smooth sells.

And I'd stop pretending the week is the deliverable. The week is the encoding event. The retention happens, or doesn't, in the spaced follow-up that almost nobody plans.

I want to be careful here, because I'm skeptical of my own advice when it's this tidy. There's a real argument that VBS was never supposed to be about content retention at all, that its actual function is relational and communal, getting kids into the building and giving them a warm association with church. If that's the goal, then everything I just said is beside the point, and optimizing for memory would be optimizing for the wrong thing. I don't think that's fully true. But I don't think it's fully false either.

What I'm fairly sure of is this: if a church spends months preparing VBS and tells itself the kids are learning the Bible, it should at least know that under the current design, most of that learning evaporates by August. Whether that matters depends on what you thought you were building. Just don't confuse the volume for the memory. They're not the same thing, and they never were.