The Recap Nobody Plans For

Most lessons end at exactly the wrong moment. The teacher hits the last point, the clock is against them, someone's parent is already hovering in the doorway, and the whole thing just stops. No landing. The kids file out with a craft and a vague memory of a Bible story, and by Tuesday it's gone.

That gap between the end of a lesson and what a student actually retains is the part almost nobody designs for. And it's the part that decides whether any of the previous 30 minutes mattered.

Here's what the retention research keeps pointing at, and I'll be honest about where it's solid and where it isn't. The solid part: retrieval practice. The act of pulling information out of memory strengthens that memory far more than re-exposing someone to the same information. If you tell a kid the story of the prodigal son, and then five minutes later you tell it again, you've done almost nothing for retention. If you tell it once and then make them reconstruct it, out loud, in their own broken words, you've done something real. This is one of the most replicated findings in cognitive science. It's not a fad.

What this means for a 30-minute class of eight-year-olds is smaller and stranger than most curriculum makes it sound.

It means the review at the end isn't filler. It's the actual mechanism. The four minutes you always cut for time might be the four minutes doing the most work.

Most lesson plans treat review as decoration. A row of recap questions at the bottom of the page, the ones the teacher skips because the clock ran out. I've reviewed a lot of pre-built curriculum, and the pattern is almost universal: the front of the lesson is loaded with content, the back end tapers off into a limp closing prayer and a suggested activity. All the design energy went into delivery. None went into retrieval.

Which is backwards.

I worked with a teacher who ran a small midweek group, maybe ten kids, third and fourth grade. She was frustrated because they never remembered anything week to week. She'd re-teach the same concept three weeks running. When I actually watched her teach, the lesson was good. Genuinely engaging. But she ended every session by summarizing it herself. "So today we learned that God keeps his promises." Nice sentence. Did all the cognitive work for them. The kids just nodded.

We changed one thing. Instead of her summarizing, she made them do it. "Somebody tell me the story. Start at the beginning. What happened first?" Awkward at first. Long pauses. One kid got it wrong and another corrected him, which, by the way, is the corrected kid doing retrieval too. Within about three weeks the week-to-week recall was noticeably better. Not miraculous. Better. She stopped re-teaching from scratch.

I can't give you a clean percentage on that because I wasn't running a controlled study, I was watching one classroom. That's the honest version. But it lines up with everything the research says should happen, and I've seen the same shift in enough rooms to trust the direction if not the exact size.

The part I'm less sure about is spacing. The research says spaced retrieval, revisiting material across days or weeks, beats cramming it into one session. Totally true in a school setting where you see kids five days a week. In Sunday school you see them once a week if you're lucky, and attendance is spotty. A kid might miss two weeks in a row. So the neat spacing schedules from the lab don't map onto a ministry calendar cleanly, and anyone who tells you they do hasn't looked at an actual attendance sheet. I don't have a great answer for the spacing problem in a low-frequency, inconsistent-attendance environment. I've seen teachers try opening each week with a quick callback to the previous lesson, and that's probably the best available move, but it assumes the same kids were there. Often they weren't.

So the practical design principle is narrower than the research headline. It's not "space everything out perfectly." It's "build retrieval into the single session you're guaranteed to have, because that's the only thing you control."

Which changes how I think a lesson should be structured. Not front-loaded. Bookended. Content in the middle, a short retrieval hit near the start (whatever they remember from last time, even if it's fragments), and a real retrieval sequence at the end that is not the teacher talking. The end of the lesson should be the loudest part of the room, not the quietest.

This is also where I've watched a free lesson plan builder do something genuinely useful and something mildly annoying, so I'll be fair about both. The useful part: when you can generate the structure fast, you have time left over to build the recap questions, which is exactly the part teachers cut when they're prepping at 9pm on a Saturday. The annoying part: automated tools, ours included, still default to putting more energy into content generation than into retrieval design, because content is easy to generate and good retrieval questions are hard. A question like "what was the story about" is worthless. A question like "why did the older brother stay outside" forces reconstruction. The tool won't always know the difference. You have to.

One caveat before anyone rebuilds their whole approach. This matters most for content you actually want retained: the narrative, the core idea, the thing you'd want a kid to still know in a month. It matters a lot less for the parts of a Sunday morning that are about presence and relationship and just being a kid in a room with adults who show up. Not everything needs to be optimized for recall. A lot of ministry is not a memory task. If your class is mostly about the eight kids feeling known, retrieval practice is not your problem and you can ignore all of this.

But if you're teaching something you want to stick, and then you spend the last four minutes doing the remembering for them, you've built the whole lesson to leak out the bottom.

Stop summarizing. Make them do it. Badly, out loud, in the wrong order. That's the sound of it working.