The Recap Problem: Why Your Students Forget Last Week's Lesson

Ask a room of eight-year-olds what they learned last Sunday and watch what happens. Blank faces. Maybe one kid remembers there was a snack. Maybe another remembers a puppet. Almost nobody remembers the actual point of the lesson, which was, let's say, that Joseph forgave his brothers.

This drives teachers crazy, and I understand why. You spent Tuesday night prepping. You told the story well. The kids were engaged in the moment. And seven days later it's gone like it never happened.

Here's the part most people get wrong: the kids didn't fail. The lesson design did.

Memory doesn't work the way curriculum publishers seem to assume it works. There's this quiet assumption baked into almost every lesson plan I've ever reviewed, which is that if a student understands something clearly in the moment, they'll retain it. That's just not true. Understanding and retention are two different systems. You can nail the first and completely whiff the second.

The research on this has been sitting around for over a century. Hermann Ebbinghaus mapped the forgetting curve in the 1880s, and the shape of it is brutal: most of what we learn drops off sharply within the first day or two unless something pulls it back. What pulls it back is retrieval. Not re-reading. Not re-hearing. Actually digging the information back out of your own head.

Which brings me to the thing almost every Sunday school lesson skips.

The five minutes nobody plans for

Look at how a typical lesson opens. There's usually a "welcome" or an icebreaker, then straight into the new story. The previous week gets, at best, a one-line callback from the teacher: "Last week we talked about Joseph and his coat, remember?" And the kids nod, because kids nod, and then you move on.

That callback does almost nothing for retention. You said it. They didn't retrieve it. Those are not the same event in the brain.

What actually works is embarrassingly simple and almost nobody does it consistently. You open with a low-stakes retrieval task. Not a quiz, not a test, nothing that feels like school. You ask them to tell YOU what happened last week before you say a word. "Somebody catch me up. What was going on with Joseph and his brothers?" Then you shut up and let them struggle for a second.

That struggle is the whole point. The effort of pulling it back is what strengthens the memory. In learning design we call it the retrieval effect, and it's one of the few findings in cognitive science robust enough that I'll actually stake a claim on it. It holds up across ages, subjects, and settings. I'd bet on it in a room of eight-year-olds and a room of retirees in an adult Sunday school class, and I've watched it work in both.

Here's what I can't tell you cleanly, and I want to be honest about it: I don't know the exact right dosage. Two minutes? Five? Does it matter if one kid does all the retrieving while the others coast? Probably, yeah, but I've seen mixed results on how much that hurts the quiet kids, and anyone who tells you they've got the precise formula is selling something.

What this means for how you actually plan

Most teachers I work with are pulling material from three or four places, stitching a lesson together on a Thursday night. Some of it is paid curriculum, some of it is free church curriculum they found online, some of it is stuff they've done for years. And almost none of those sources build in a retrieval step, because retrieval doesn't photograph well in a sample lesson. It looks like empty space on the page.

So you have to add it yourself. A few things worth knowing before you do:

• Put it at the front, not the end.
• The temptation is to "review" at the close of class, but end-of-lesson review is mostly re-exposure, and re-exposure is the weakest form of practice there is. The retrieval belongs at the start of the NEXT session, spaced a week out, because the forgetting has already started and that's exactly when pulling it back does the most good. This is the piece that trips people up, because it feels backward to open a lesson by talking about a different lesson.
• Keep it verbal and low-pressure.
• Write down one specific question in advance, not "review last week," because a vague reminder to review will get skipped every single time you're running behind, which is every single time.

There's a version of this I'll caution against. If your class roster churns a lot, if you've got different kids every week, front-loaded retrieval mostly falls apart, because half the room wasn't there for the thing you're asking them to retrieve. In that situation you're better off building tiny retrieval moments inside a single lesson, asking them to recall the beginning of a story before you tell the end of it. Not as powerful. But it fits the room you actually have.

I'll admit the thing I keep circling back to is how little of this shows up in the materials teachers are handed. It's not that publishers don't know. It's that a retrieval prompt is invisible on a glossy page, and glossy pages sell curriculum. A five-minute stretch of kids fumbling to remember Joseph doesn't look like much. It's just the part that determines whether any of it sticks.