The Review Step Everyone Skips (And Why Your Lessons Leak)

A kid can recite the entire story of David and Goliath on Sunday and have no idea what you're talking about the following week. Not because the lesson was bad. Because nobody built in the one thing that actually moves information from "heard it once" to "can use it later."

Retrieval. The deliberate act of making someone pull information back out of their own head, without the answer sitting in front of them.

Most lesson structures I see do the opposite. They present, they reinforce, they review by re-reading. The teacher summarizes at the end ("so today we learned that God gives us courage"), everyone nods, and the lesson feels complete. It isn't. A summary you hand to a student is a summary they didn't generate. And the research on this is about as settled as learning science gets: information you retrieve is remembered far better than information you simply re-read. The effect shows up in classrooms, in labs, in medical training. It's not fragile.

Here's the frustrating part. Teachers already sort of know this. They just design it out of their lessons because retrieval feels slower and messier than telling.

Why re-reading feels like learning (and isn't)

When a student re-reads a verse or hears you recap the story, their brain registers familiarity. Familiarity feels like knowing. It's a lie, basically. The student recognizes the material, mistakes that recognition for mastery, and moves on. Then Wednesday comes and the whole thing has evaporated.

I watched this play out with a volunteer who taught a sharp group of fourth graders. She ran a beautiful lesson on the Good Samaritan. Discussion, a craft, a recap slide. The next week she opened by asking who the story was about and got maybe two hands, both hesitant. She assumed the kids weren't paying attention the first time. They were. The lesson just never asked them to retrieve anything, so nothing stuck in a usable form.

Contrast that with how this works in a well-built homeschool Bible curriculum, where the parent is often teaching the same kid across weeks and can actually see what leaks out. Those parents figure out fast that asking "what happened last time?" before starting anything new is worth more than any recap they could deliver themselves. They stumble into retrieval practice because they have the feedback loop to notice what doesn't carry over. Most Sunday school teachers don't, because they see a kid for 30 minutes and then hand them off.

What this actually looks like on a Sunday morning

You don't need a system. You need to stop answering your own questions.

The cheapest version: start the lesson with retrieval instead of ending with it. Before you introduce anything new, ask the class to tell you what they remember from last week. Wait through the silence (it will be uncomfortable, maybe eight full seconds, let it sit). The struggle to recall is the part that does the work. If you jump in and rescue them after two seconds, you've killed the entire mechanism.

A few concrete ways to build it in without blowing up your prep time:

• Ask, don't tell.
• Replace your end-of-lesson summary with three questions the students have to answer from memory, no Bible open, no slide up. You'll find out immediately what actually landed, which is uncomfortable, which is exactly why it's useful.
• Space it out. If you taught something two weeks ago, bring it back today in a single question. The gap between exposures is doing something: retrieving information after you've started to forget it strengthens the memory far more than retrieving it while it's still fresh. This is the part most teachers get wrong, because they think reviewing right away is more effective when the opposite is closer to true.

Here's my honest caveat. I don't know the exact spacing that works best for an eight-year-old in a church context, and anyone who gives you a precise number is guessing. The lab studies use college students and controlled intervals. A Sunday school room is not a lab. What I'm confident about is the direction: retrieval beats re-reading, and spaced retrieval beats massed retrieval. The specific timing is something you'll have to feel out with your own class.

There's also a cost nobody mentions. Retrieval makes a lesson feel worse in the moment. Kids sit there blank. The room goes quiet. You, the teacher, feel like it's falling apart, because telling them the answer would feel smoother and more competent. That discomfort is the single biggest reason teachers abandon this, and it's why the slickest-looking lessons are often the ones that retain the least. A lesson that feels effortful to the student is frequently working harder than one that feels polished.

From the design side, this is the decision I'd fight for over almost any other. Not a better craft, not a flashier object lesson, not more content crammed into 30 minutes. Just: make the kid pull it back out before you give it to them. If you only change one thing about how you structure a lesson this fall, cut your closing summary and open next week by making them reconstruct it from memory.

It'll feel like it bombed. Check again the following week.