What Parents Get After Every Coding Session

Last updated: August 2026

After every coding session you get a written progress report and a full transcript of the lesson. Not on request, not weekly, not a summary at the end of a package. After each session, covering what your child learned, what clicked, and what is coming next. You can also opt into a monthly meeting to go through progress properly.

The reason this exists as a product rather than a courtesy is simple. You cannot assess your child's code, so without a record you are judging a technical subject entirely by whether your child seems cheerful afterwards. That is not enough information to spend money on for a year.

Key Takeaways

• A written report and a full session transcript arrive after every session, automatically.
• Parents can additionally opt into a monthly progress meeting.
• A transcript beats a dashboard because it is evidence rather than a summary of someone's opinion.
• Reporting that only happens on request stops happening around week four.
• The reason it matters: children can appear engaged while retaining very little, and you cannot see that from outside.

Table of Contents

• What Actually Arrives
• Why a Transcript, Not a Dashboard
• Why This Matters More Than It Sounds
• The Monthly Meeting
• What to Ask Any Tutor About Reporting
• What We Do Not Do
• Frequently Asked Questions
• The Bottom Line

What Actually Arrives

Three things, in plain terms.

A written progress report, after every session. What was taught, what your child understood, where they struggled, and what the next session covers. Short enough to read in a minute.

A full transcript of the session. The actual conversation, in plain text. Not a summary. If you want to know how a concept was explained, or what your child said when they got stuck, it is there. It is a Markdown file, which means it opens in anything and belongs to you rather than living behind someone's login.

A monthly progress meeting, if you want one. Optional, and some families never take it up. Others use it as the moment to raise scheduling, redirect the projects, or ask whether the pace is right.

None of it is billed separately. Preparation, reports, and message replies are not counted against your hours.

Why a Transcript, Not a Dashboard

Several platforms compete on a parent dashboard: a login where you see modules completed and a progress bar. Dashboards look impressive and mostly measure attendance.

A transcript is a different kind of object. A dashboard tells you a module was completed. A transcript lets you see that your child was asked to predict what the code would print before running it, said "I don't know" four times, and then got it. That is what learning actually looks like, and no progress bar represents it. Being asked to retrieve an answer rather than recognise one is the mechanism cognitive scientists call retrieval practice, and a transcript is the only record that shows whether it happened.

It also means you can check the teaching, not just the outcome. If you ever wonder whether an hour was well spent, you can read the hour. Very few parents do this more than once or twice, but the fact that they can changes what kind of hour gets delivered.

The same principle runs through how we teach in the first place. Showing something beats describing it, whether that is a tutor demonstrating a technique or a student handing the AI a screenshot instead of a paragraph. A transcript is that principle applied to reporting.

A parent of a son learning Python described the part that tends to matter most in practice:

"Michael is a great teacher that takes you from 0 to the top. He explains clearly and creates great challenges that help tremendously. He is also helpful and responsive." Tahir, parent of a son learning Python

Responsive is not a teaching quality, it is an operational one, and parents notice it more than any curriculum feature.

Why This Matters More Than It Sounds

Here is the uncomfortable finding that makes reporting a product rather than a nicety.

I tracked fourteen one-on-one sessions across three students this July and found three separate ways a child can look like they are learning while you have no evidence they are: the child who watches without ever building, the child who agrees with everything so agreement carries no information, and the child who can make the code work but cannot explain any of it. All three students were motivated and enjoying the lessons. Two had significant gaps that ran for weeks. The full write-up is in three ways kids look like they're learning to code.

Every one of those was caught by close attention over several sessions. None of them would have been visible to a parent asking "how was your lesson?" and getting "good."

That is what the report is for. It is not a marketing artefact, it is the mechanism by which you find out that your child has been quietly lost for three weeks, while there is still time to change something.

The Monthly Meeting

The written record answers "what happened." The monthly meeting answers "is this still the right plan."

Typical things that come up: the project has stopped interesting them and we should switch, they are ready to move from Scratch to Python earlier than expected, school has got heavier and once a fortnight would work better, or a sibling wants to join. These are all decisions, and decisions are better made in a conversation than in a report.

It is genuinely optional. Some families read the reports and never need the call. The offer stands either way.

What to Ask Any Tutor About Reporting

Whether or not you work with us, this is the question that separates providers fastest.

Ask: "What do I receive after a session?"

A provider genuinely tracking your child answers instantly and specifically, because the answer is a thing that already exists. A provider who is not goes vague, and the vagueness usually takes the form of putting the work back on you: whenever you want an update, just ask.

That answer is a soft no. Reporting that depends on the parent remembering to chase it stops happening by about week four, which is exactly when you would most want to know whether the first month worked.

Two follow-ups worth asking: is it after every session or periodically, and does anything outside the lesson get billed to my hours.

What We Do Not Do

No live dashboard. You get documents, not a login. I would rather send you the actual record than build a progress bar.

No graded assessments. We do not test children and rank them. The report describes what happened, including when it did not go well. If you want an independent yardstick, your child's published Scratch projects or their code on their own machine are better evidence than any score we could invent.

No editing out the bad sessions. If a lesson ran long on the wrong thing, the report says so. I hold that standard in public too, not just in reports, and I write up my own sessions that went badly as readily as the ones that went well.

Frequently Asked Questions

How often do I get a progress report? After every session. It covers what was taught, what your child understood, where they struggled, and what is next. You also receive a full transcript of the session.

What is in the transcript? The actual conversation from the lesson, in text. Not a summary. You can see how a concept was explained and what your child said when they got stuck.

Can I talk to the tutor about progress directly? Yes. You can opt into a monthly progress meeting, and you can message between sessions. Neither is billed against your lesson hours.

Do you provide session recordings? Recordings and transcription are available, along with an analysis of what your child learned and what comes next. Ask and it will be set up.

What if the report says my child is struggling? Then it has done its job. Struggling early is normal and fixable. The problem is not a child who struggles, it is a parent who finds out in month four.

Is reporting included in the price? Yes. Reports, preparation, and message replies are not counted against your hours. Pricing is on the pricing page.

Related Articles

• Three Ways Kids Look Like They're Learning to Code, the research this reporting exists to catch.
• How to Choose the Right Coding Tutor for Your Child, where reporting sits among the questions to ask before booking.
• What 30 Sessions of 1-on-1 Coding Actually Look Like for a Kid, progress viewed across a whole package.

The Bottom Line

You cannot judge a coding lesson by whether your child seemed happy afterwards, and you should not have to. A written report and a full transcript after every session mean you can see what was taught and what landed, without needing to read code. If a provider cannot tell you what arrives after a session, they are not tracking your child closely enough to tell you anything useful later.

Want to see what one of these reports actually looks like? Book a free Discovery Call and I will walk you through a real one.