Why Your Child Forgets Last Week's Coding Lesson

Last updated: September 2026

When a child forgets last week's coding lesson, the usual explanation is that they were not paying attention or the material was too hard. In my experience across 200+ students, it is almost never either. The concept was understood at the time, and then nothing existed to hold it in place for the six days before the next lesson.

That distinction matters because the two problems have completely different fixes. A child who did not understand needs re-teaching. A child who understood and lost it needs a reference and a recall habit, which takes about ten minutes to set up.

Key Takeaways

A concept can be taught well, verified correct at the end of a session, and still be gone a week later.
The cause is usually the gap between lessons, not the lesson itself.
Re-teaching from scratch is the expensive fix and it does not stop the same loss happening again.
The cheap fix is a one-page reference the child keeps, plus three minutes of recall at the start of each session.
Watch for the same concept being explained more than twice. That is the signal something structural is wrong.

The case that made this obvious

In August I reviewed three consecutive Scratch sessions with a beginner, age 8, and one concept kept reappearing: the coordinate system, the x and y values that decide where a character sits on screen.

Session one: it came up because the child noticed the numbers changing on his own and asked about them. The explanation he got was muddled.

Session two: he was asked whether he knew what the x and y axes were. He said no. Nothing from the previous week had survived. It was taught again, properly this time, and at the end of the session he was tested and explained both axes correctly in his own words.

Session three: he stated it backwards, and later in the same hour asked outright what one of the terms even meant.

That middle session is the important one. The teaching was good and the child demonstrably had it, because he was checked. It still did not survive seven days. So the problem was not comprehension and it was not the explanation.

He had nothing to look at between lessons. No notes, no sheet, nothing pinned anywhere. The only place that concept existed was his memory, and a week is a long time in an 8-year-old's week.

Three teachings of one idea consumed somewhere between fifteen and twenty minutes of lesson time, and it still was not solid.

Why re-teaching feels productive and is not

Re-teaching is the natural response and it is the reason this can continue for months without anyone noticing.

It feels like a good session. The tutor explains, the child follows, everyone leaves satisfied. The lesson looked exactly like teaching. What it actually did was rebuild something that had already been built once, using time that was supposed to go on new material.

The tell is repetition across sessions rather than within one. Explaining something twice in a lesson is normal and healthy. Explaining the same thing from zero in three separate lessons is a structural signal, and the correct response is to change the system rather than to explain more clearly.

One parent of a 10-year-old starting with Scratch told me what mattered to her was having the right path mapped out, and a tutor who taught with a purpose. Taught with a purpose is the operative phrase. A lesson spent rebuilding last month's material has no purpose left in it.

Recall is not the same as review

The single cheapest change is how a session opens.

Most lessons start with a recap: the adult restates what was covered last time. That is review, and it is close to useless for retention, because the child sits and listens while someone else does the remembering.

Recall is the opposite. You ask, and they retrieve. "Before we touch anything, tell me what x and y do." Then you wait.

The difference is not stylistic. Being made to retrieve something strengthens the memory in a way that hearing it again does not, which is the well-documented testing effect, and spacing those retrievals out over days rather than massing them into one session strengthens it further through the spacing effect.

The practical value is also diagnostic. Three minutes of asking tells you whether you need to spend fifteen minutes rebuilding. If it is there, you move on and keep the time. If it is not, you have found out at minute three instead of minute forty, when it surfaces as confusion in the middle of something harder.

Session opening	What the child does	Time cost	Retention value
Adult recaps last week	Listens	5 minutes	Very low
Adult re-teaches from zero	Follows along	15 minutes	Low, and it recurs
Adult asks, child retrieves	Remembers	3 minutes	High
Nothing, straight into new work	Nothing	0 minutes	The gap surfaces later, worse

Give them something to consult

The second fix is a reference the child physically keeps.

It does not need to be elaborate. One page. The concept, in their words where possible, with a small picture or example. For the child above it would have been a coordinate grid with the centre marked zero, an arrow labelled left and right for x, and an arrow labelled up and down for y. That is the entire artefact and it would have saved most of twenty minutes.

What makes it work is ownership. A sheet the tutor keeps is a lesson plan. A sheet the child keeps, adds to, and can find on a Tuesday afternoon is a reference. Let them write on it.

Scratch's own tutorial cards and ideas pages work well as a supplement, and the Scratch Foundation learning library has more. But they are generic, and a page in a child's own handwriting about the specific thing that confused them beats a polished generic one most of the time.

If your child is at the stage where these concepts are landing for the first time, what your child actually learns in Scratch sets out the sequence they will meet them in.

What parents can do between lessons

You do not need to understand the code. Three things help and none of them require you to know Scratch or Python.

Ask one question, once, midweek. Not a quiz. "What was the thing you learned last week?" If they cannot answer at all, that is worth telling the tutor before the next session rather than letting it be discovered live.

Ask them to show you rather than tell you. Opening the project and pointing at the screen is easier for a child than describing it, and it produces better recall. A child who cannot explain a concept can often demonstrate it, and demonstrating it reinforces it.

Protect the reference sheet. If it goes in a drawer, it does not exist. Somewhere visible near where they work is enough.

What does not help is more lessons. If a concept is not surviving the week, adding a second weekly session gives you two sessions that both leak. Fix the leak first. The same applies to longer lessons, which tend to add fatigue rather than retention.

Three Ways Kids Look Like They're Learning to Code on the difference between apparent progress and the real thing.
Scratch for 8-Year-Olds: What Your Child Actually Learns for the concept sequence this applies to.
How to Teach Your Child Python at Home including the explain-it-back check for testing understanding.

Frequently Asked Questions

Is it normal for a child to forget a coding concept between lessons? Yes, and it is the single most common pattern I see. A week is long at 8 or 10 years old, and unless something carries the concept across the gap it will often be gone. Forgetting is not evidence that a child is unsuited to coding.

How do I know if my child understood the lesson or just followed along? Ask them to explain one specific thing rather than the project as a whole. A child who followed along can tell you what the program does. A child who understood can tell you why a particular line or block is where it is.

Should I make my child practise coding between lessons? Open-ended building beats drills. The most effective homework I set is "make something impressive before next time," which regularly produces more independent learning than a structured exercise does. Ten minutes of their own project beats thirty minutes of assigned repetition.

How many times should a tutor need to explain the same thing? Twice inside one lesson is normal. Three times across three separate lessons means the system is wrong, not the child. At that point the answer is a reference and a recall habit, not another explanation.

My child remembers Scratch but forgets Python. Why? Scratch shows its structure visually, so the blocks themselves act as a reminder every time they open a project. Python hides that structure in text and whitespace, so there is nothing on screen to jog the memory. Children moving between the two often need written notes for the first time.

Does this mean my child needs more lessons? Usually the opposite. If material is leaking between sessions, more sessions leak more. Fix retention first, then consider frequency.

The Bottom Line

A child forgetting last week's lesson is a systems problem far more often than an ability problem. The concept was understood, nothing held it, and a week passed.

Give them one page they keep, open each session by asking rather than telling, and watch for any concept that gets explained a third time. Those three habits cost almost nothing and they recover more lesson time than any change to how the material is explained.

I teach kids ages 8 to 16 online, 1-on-1, and building the retention habits is as much of the job as teaching the code. Book a free Discovery Call.