Systèmes de fichiers imbriqués
Virtualized storage in Proxmox VE, written in French for networking students: six 3D scenes, a configuration simulation and a bilingual lexicon.
Choose your experience. Every page is written for it, and you can switch any time.
Meta DAX › See it
Every one of these started as one sentence from a guide and what the learner already loves. Made-up names, nothing identifying. A way, never the way.
The same recipe built every one of these.
Virtualized storage in Proxmox VE, written in French for networking students: six 3D scenes, a configuration simulation and a bilingual lexicon.
A tutor's kit for turning sentences into equations: five interactive 3D scenes, three routes for the time you have, and a pause before every example.
Edition Words into Algebra: Nova's Edition · Play
A Jaffna curry in a 3D kitchen, Tamil & English, read by someone from the community.
A whole Grade 6 science year from one brief: 36 weeks mapped, misconceptions named, one week built in full.
A 3D Biology 101 lesson on how mitochondria make ATP, with instructor notes.
One tutor's week: rough notes, a parent-ready report, and the guide coach on a real problem.
A staff onboarding module made from a one-page brief.
French fractions in a 3D stadium.
Each showcase was built by the MetaDAX course factory from a short brief. Model-generated; reviewed for safety, not certified.
24 packages built from parents’ descriptions: one page for the guide, one for the child.
24 of 24 shown
Stuck: freezes before trying; writes column totals side by side instead of carrying
A made-up example built from a parent's description. A way, never the way.
Guide: Nora · Learner: Eli · Age band: 7–9 · Subject: Math
Eli could add the digits in each column of a two-digit addition problem, but wrote the two column results side by side rather than grouping them. Asked to add 27 and 15, Eli produced 312: the tens total (3) and the ones total (12) placed next to each other, with no carrying. Eli also froze before trying when a column of numbers appeared, saying "I can't" before making any attempt.
Marble runs already model overflow: when too many marbles pile up in one spot, extras roll to the next track. The session starts with Eli teaching Nora how to set up an overflow track, then Nora names the connection — the ones spot holds up to nine, and when you reach ten, one marble rolls up to the tens track. That is carrying. Every example in the session is framed this way: count the ones, check for overflow, roll the extra ten up. The game uses the same language, and Eli can hear the "roll" happening in each question.
A session has three parts. First, Eli teaches — Nora asks how the overflow track works and genuinely does not know how Eli has set it up. Second, Nora names the math connection in one sentence, using Eli's own words. Third, Eli tries the game at the learner's own pace, with Nora beside them. The guide's job during the game is to notice the face, not the score. If Eli goes quiet after a wrong answer, Nora does not wait or ask why — she gives Eli something to do in the first two seconds: "let's count the ones together" and starts counting herself. Keeping the page to one question at a time, or folding a printed page, prevents the overwhelm that a full column of numbers triggers.
Nora can see the moment before the freeze — the held breath, the looking away — and interrupt it before it sets in. She can connect the marble run to one Eli actually built, not a generic one. She can tell when Eli is guessing versus thinking. She can read the room: if the session starts to feel like a test, she can stop the game, return to the marble run, and let Eli be the guide again. A page cannot do any of this. The decision to stop early, to shift tone, to follow an unexpected question — those belong entirely to Nora.
The session opens with Eli as the guide. Eli knows more about building a marble run that works than Nora does. Eli sets up the overflow track and explains why the marbles go where they go. Nora listens and asks one question: what happens if the extras have nowhere to go? That question is real — Nora wants to know. Eli's answer contains the whole idea of carrying; Nora's job is to name it afterward.
The game presents two-digit addition problems one at a time, each with a visual showing the column structure. There are three levels, each with four questions. After three correct answers in a row, the numbers get a bit bigger. After a miss, the next question is a bit easier. Wrong answers name the specific mistake — side-by-side writing, forgetting the carry, or dropping the ones — so Nora's note after the session can say exactly what came up. Nothing bad happens on a wrong answer. The game says: wrong answers help us know what to work on next.
Most children find carrying awkward at first and get it with practice. But if a child consistently cannot hold two things in mind at the same time — a partial result and what to do with it next — even after many patient tries, or if numbers seem to slip and rearrange in ways the child cannot explain or notice, or if the frustration is sharp and persistent across many subjects and types of work, it may be worth talking to someone whose work is understanding how children learn. A professional who observes children and learning can watch, ask questions, and tell you what they see. You do not need a label to have that conversation, and the information you get is yours to use however you choose.
The marble run is one way to think about carrying. Another child might reach for a different picture — a full row of LEGO bricks moving up to the next layer, a score counter that rolls over, anything. If the learner reaches for their own model, follow it. The goal is that the learner can carry tens reliably. How they get there is open.
Stuck: says each letter sound correctly but cannot push the sounds together into a word
See a learning record from this package → published by the learner or guide
A made-up example built from a parent's description. A way, never the way.
Guide: Nora · Learner: Dash · Age band: 7–9 · Subject: Reading
Dash could say every letter sound on its own without any trouble. The problem was that the sounds would not join up. Sounding out s-u-n out loud, Dash would then say a completely different word that started with s. Each sound stayed separate, like beads that would not string together into a word. Worksheets and flashcards had not shifted this. The frustration showed up quickly: after about two misses in a row, Dash would cover the page and stop.
Dinosaur names are built from the same phonics chunks that appear in ordinary words, and Dash already knew those names. That meant every blending exercise could feel like a dinosaur game rather than a reading drill. Short names came first — three sounds in rex, four in tops — and the game built up to five-chunk names like Velociraptor. Because Dash wanted to get the dinosaur names right, there was a reason to push the sounds together. The game also stepped up in difficulty after three correct answers in a row and stepped down after a miss, so the difficulty stayed close to the edge of what Dash could do.
A session starts with Dash in the lead: Dash teaches Nora something about how to tell two dinosaurs apart. This is not a warm-up exercise — it is a real moment where Dash is the expert. Only after that does the blending work begin. The guide's steps are short: introduce one name, model the blending (say the sounds slowly, then faster, until the word pops out), then let Dash try. The game records which blends break down most often so the next session can target exactly those. Sessions are kept short, stopping before frustration rises too high. If Dash covers the page, the guide moves immediately to doing the sounds together rather than waiting or asking why.
Nora can see Dash's face change a moment before the page gets covered, and can move in before the frustration lands. Nora can also connect a specific dinosaur name that Dash mentioned to the sounds in that session, making the example feel personal rather than generic. Deciding when to stop — even if the game is not finished — is something only Nora can judge. A short successful moment at the end of a session matters more than getting through all the questions.
At the start of every session, Dash teaches Nora one thing about dinosaurs: how to tell a Stegosaurus from an Ankylosaurus, or what made a Triceratops different from other ceratopsians. Nora listens and asks questions. This is not decoration — it signals that being the expert matters, and it lets the session start from a place of confidence. The same pattern appears on Dash's side of the page: the first thing Dash sees is an invitation to teach, not a question to answer.
The game shows letter sounds one at a time, using chunks from real dinosaur names. Dash picks which name the sounds blend into. Wrong answers are tied to the specific mistake behind them: for example, picking a word that starts with the first sound (guessing from the beginning rather than blending all the sounds) gives a different response than saying the sounds out loud but not joining them into a word. The game has three levels. Level one uses short three- and four-sound names like rex and raptor. Level two uses longer chunks like stego and bronto. Level three uses full names across four or five chunks. Difficulty steps up after three correct answers in a row and down after one miss, so it stays close to the edge of what Dash can do.
If a learner can say each sound correctly but the sounds still do not join into words after several sessions — even with short bursts, patient modelling, and a topic they love — it is worth describing that to a professional and asking whether an evaluation would help. Other things worth noting: mixing up the order of sounds inside a word, frequently forgetting which sound goes with which letter even after practice, or getting much more tired from reading tasks than from other kinds of learning. When asking, describe what you see: say that the learner can produce each sound on its own but the sounds do not connect into words, and that the pattern has continued across multiple sessions. You do not need a label before asking for an evaluation. Getting one earlier rather than later means more options.
This page shows one approach that worked as a starting point for one child at one moment. A different child who loves something else entirely would need a different anchor. A child who connects to the sounds but freezes under any game pressure would need a different shape. The blending steps here — model slowly, speed up, let the word emerge — are grounded in how sounds work, but the way they are delivered, the pacing, and when to stop are all things only the guide in the room can judge. Use what fits. Leave the rest.
Stuck: keeping mixed ages engaged together without the oldest waiting and the youngest drifting
A made-up example built from a parent's description. A way, never the way.
Guide: Margot · Learners: Theo (8), Bea and Ines (both 5) · Age band: 4–9 · Subject: Science
Margot had three children to teach at the same time: Theo, who reads fluently and finishes activities quickly, and Bea and Ines, who cannot yet read and lose focus within a few minutes. Every curriculum she tried was aimed at one grade, which meant Theo was bored while the little ones were lost, or the little ones were left behind while she worked with Theo. The real wrong answer the little ones gave when asked what plants need — "candy" — told her they were not yet connecting the question to anything real. She wanted one lesson that held all three without splitting her attention three ways.
The lesson gives each child a different job based on what they can already do. Theo reads questions aloud and, later in the session, explains answers back to Bea and Ines in simple words. Bea and Ines always have something to touch, pour, or point at — their job is never to sit still and listen. The whole session runs in short bursts of two to three minutes of listening followed by a doing moment: pouring water on soil, lifting a rock, touching a leaf. The doing moments reset the little ones and give Theo a break from being the reader so he can observe and ask his own questions.
The session opens outside, not at a table. Theo knows where the ants nest in the yard; Margot asks him to take everyone there and show Bea and Ines what he knows. This puts Theo in the guide seat from the start and gives the little ones something real to look at before any words are spoken. After the ant visit, everyone collects one thing: a bug, a leaf, a handful of soil. They hold them while Theo reads the first question aloud. The water experiment — pouring water onto soil and watching the colour change — is the moment that anchors the session for the little ones, because they can splash and pour freely. The session closes with a game on the page: Theo reads each question, Bea and Ines point at the screen to pick their answer, and the three levels let Theo try harder questions while the little ones stay with the doing parts.
Margot is the one who notices when Bea has gone somewhere else in her head and decides whether to bring her back or let a minute pass. She can tell the difference between Theo being bored and Theo being frustrated — those need different responses. She knows that Ines will stay with anything if she is allowed to get her hands wet, and that Bea sometimes needs a moment to herself before she can join in again. No page can carry that knowledge. The page gives a shape; Margot fills it with what she sees.
Theo knows the ant nest better than anyone. Before the lesson content begins, he leads: he takes everyone to the nest, points out the trails, and tells the group what he has noticed about what the ants carry. This is not a warm-up exercise — it is the real start of the lesson, and Theo is the guide for it. Later in the session, the hardest game questions ask Theo to explain an answer back to a younger child in words they can understand. Explaining something simply to someone who does not yet know it is harder than answering a quiz question, and it tells Margot more about what Theo actually understands.
The game has three levels. The first level is pure doing: questions that require pouring, lifting, or touching something to answer. The second level is listen-and-pick: Theo reads the question aloud, Bea and Ines point at the answer on the screen. The third level is explain-it: the question asks the oldest to put an answer into simple words for a younger child. The game steps up after three correct answers in a row and steps back down after one miss, so it finds each child's level without Margot having to track it. Wrong answers are mapped to the specific mistake behind them, so the feedback is not just "wrong" but "here is what got mixed up."
If, across several sessions, one child consistently cannot stay with even a short doing task — not distraction, but a pattern that does not shift when the task changes — that is worth watching. Similarly, if a child seems to have significant difficulty connecting words to the things they stand for, even after many hands-on experiences, or if a child's understanding seems noticeably further behind what you would expect compared to other children the same age in ways that do not improve over time, those are patterns that go beyond ordinary variation. You do not need a label or a diagnosis to ask for an outside view. A conversation with a family doctor, a child development centre, or an early learning specialist at a local school board can give you more information. Asking early is not an alarm — it is information, and you remain in charge of what to do with it.
This is one shape that worked for one parent's description of three children. Another family with the same ages and the same loves might need more time outside, or less reading, or a different anchor entirely. The oldest being the reader works here because Theo likes that job; if an older child does not, the whole shape shifts. Take what fits and leave the rest. The point is not to follow this plan but to find the version that fits your three.
Stuck: the younger thinks a bigger bottom number means a bigger piece; the older can name fractions but not add halves and quarters
An illustrative example made with a simulated family — not a real family's record. A way, never the way.
Guide: Priya · Learners: Sam (6) and Max (10) · Age band: 4–9 · Subject: Math
Two children learn at the same kitchen table, and fractions caught both at different points. The younger, Sam, thought a bigger bottom number meant a bigger piece — asked whether a quarter or a half was more cake, Sam chose the quarter because "four is bigger than two." The older, Max, could name any fraction on sight and reduce it, but when a recipe needed a half cup plus a quarter cup, Max wrote three-quarters only by guessing, and could not say why. One wanted to see the pieces; the other needed the pieces to add up to something real.
The whole session is one batch of dough and one recipe, worked at two levels so neither child waits. Sam's level is cutting: fold and cut the dough into halves, then quarters, and line them up to feel that a half is the bigger piece even though "two" is the smaller number. Max's level is combining: the recipe calls for a half cup of one thing and a quarter cup of another, and Max's job is to say how much that is together and prove it by pouring. Same dough, same recipe, same table — the little one builds the pieces and the older one adds them.
Start with the dough, not the page. Sam cuts and arranges while Max reads the recipe aloud. Priya names one connection in plain words — "a half is one cut, a quarter is one more cut" — and then lets each child work their own level. The page comes out at the end: Sam answers which-piece-is-bigger questions by pointing, and Max answers add-these-two questions, each at their own pace with Priya between them. Keeping the two levels side by side, rather than running two separate lessons, is what lets one guide hold both children without the older one idling or the younger one lost.
Priya can see that Sam has stopped looking at the dough and started guessing, and move the dough back under Sam's hands before the guess hardens. She can tell that Max's "I don't get it" means boredom, not confusion, and hand Max the harder job of checking Sam's cuts. She knows which child needs to be first and which can wait a minute. A page gives the two levels; only Priya can read which child needs which one right now, and swap a job the moment the table tips from baking into testing.
Both children lead something. Sam knows, better than anyone at the table, how to cut dough into even pieces so nobody complains their piece is smaller — that fairness is exactly what equal fractions mean, and Sam teaches it by doing. Max leads by teaching down: the hardest moment of the session asks Max to show Sam why a half and a half make a whole, using the pieces Sam just cut. Explaining it to a six-year-old is harder than adding the fractions alone, and it shows Priya what Max truly understands.
The game runs one activity at two levels. The first level shows two pieces and asks which is more cake — built to catch the "bigger bottom number" slip, so a wrong answer names it: "four pieces means each one is smaller." The second level gives two fractions from the recipe and asks for the total, with a picture of the measuring cups filling. It steps up after three correct in a row and steps back down after a miss, so each child settles at their own level without the guide tracking it. Nothing bad happens on a wrong answer; it just tells the table what to cut next.
Most children sort out that a half is bigger than a quarter once they have cut enough real things, and most come to adding fractions slowly. But if a child, after many hands-on tries across a long stretch, still cannot hold the idea that the same whole can be split into different numbers of pieces, or seems unable to line up a number with an amount they can see and touch in a way that does not shift over time, it may be worth asking someone whose work is how children learn. A family doctor or an early-learning specialist can watch and tell you what they see. You do not need a label to have that conversation, and what you learn is yours to use as you choose.
Baking is one way in because this table already bakes together. Another pair of children might reach fractions through folding paper, sharing a pizza, or splitting a score — and another mix of ages might need the levels further apart or closer together. The point is not the dough. It is that the younger learner can see that a half is the bigger piece and the older can add the pieces into a whole. If your children reach for a different thing to cut, follow it.
Stuck: can argue a point out loud for ten minutes but freezes when asked to put the same case in a written paragraph
An illustrative example made with a simulated family — not a real family's record. A way, never the way.
Guide: Dana · Learner: Theo · Age band: 13–15 · Subject: Writing
Theo, who is fourteen, can argue for ten minutes straight about which player belongs on a line — reasons, counter-examples, the lot — but asked to write a single argument paragraph, Theo stalls at the first sentence and writes nothing. Session one got the spoken case onto paper in fragments: a strong claim and one reason, but the reasons ran together and there was no line answering the other side. The next-time note the learner page left at the end of session one said, in Theo's words: "the start is fine now, but the middle is a pile — and I don't know how to say the other guy is wrong without just saying he's wrong."
This session keeps what landed and moves one step on the exact spot the note named. The claim sentence is left alone — it works now, so it is not re-taught. The whole session is the middle: taking the pile of reasons and giving it a shape. The move is to pick the two strongest reasons and give each its own sentence, then add one sentence that names what the other side would say and answers it — the thing the note asked for. Every example is a real hockey argument Theo already makes out loud, written down in that four-part shape: claim, reason one, reason two, the answer to the other side.
Open with a callback, not a reset: Dana reads back Theo's claim sentence from session one and says it is staying because it works. Then the whole session is the middle. Theo argues a hockey take out loud first, Dana catches the two strongest reasons and reflects them back, and Theo writes each as its own sentence. The hardest sentence — answering the other side — comes last, modelled once on a take Theo does not hold, then written on one he does. Pace it to how session one ended: the note said Theo tired quickly once it felt like an English class, so keep it short, keep it hockey, and stop while it is still going well.
Dana can hear which two of Theo's five spoken reasons are actually the strongest and say so — a page cannot weigh an argument it has never heard. Dana can tell when Theo's "this is dumb" means the task is too long rather than too hard, and cut it there. She can catch the moment Theo argues brilliantly out loud and freeze it — "say that again, that exact sentence, now write that" — turning speech into the written line before it evaporates. And she can decide to answer the other side together, out loud, before Theo has to write it alone.
Theo knows hockey far better than Dana, and that is the engine of the session. Before any writing, Theo leads: he lays out the argument in full, and Dana genuinely learns something about the game she did not know. The hardest written sentence — the one answering the other side — works because Theo already does it in speech without noticing; Dana's job is to point out that Theo just answered an opponent out loud, and that the paragraph needs exactly that sentence. The learner supplies the argument; the guide names the shape.
The game builds one paragraph in four moves, each a short choice rather than a blank page. First it offers three claim sentences and asks which states a position rather than a fact. Then it gives a jumble of reasons and asks Theo to pick the two strongest and drop the rest — the step the note asked for. Then it shows four sentences and asks which one answers the other side instead of just repeating the claim louder. It steps up as Theo gets a run right and eases back after a miss, and every wrong choice names the slip — "that is a fact, not a position," or "that repeats your claim, it does not answer theirs" — so Dana's next-time note can say exactly where to pick up.
Plenty of people argue far better than they write, and a gap between a confident speaker and a stalled writer is ordinary, especially at this age. But if, over many sessions and many subjects, getting any words onto the page stays far harder than it should given how fluently the learner speaks — if the hand freezes in a way that does not ease with practice, or written output stays sharply behind spoken ability across everything, not just writing — it may be worth asking someone whose work is how young people learn. A family doctor or a learning specialist can observe and tell you what they see. You do not need a label to ask, and what you learn is yours to use as you choose.
Hockey is the way in here only because it is the thing Theo argues about without being asked. Another learner would turn a paragraph through a video game, a court case on a show, or a fight about a band. And session two went to the middle only because that is where this learner's note pointed; another note would send the next session somewhere else entirely. The shape — claim, reasons, an answer to the other side — is worth keeping; the subject it is built through is yours to choose, and the note tells you where to go next.
Stuck: reads the hour hand but not the minutes; cannot yet work out how long until something happens
An illustrative example made with a simulated family — not a real family's record. A way, never the way.
Guide: Ruth · Learner: Jun · Age band: 7–9 · Subject: Math
Jun, who is seven, can read the hour hand and say roughly what o'clock it is, but the minutes are a blur, and "how long until the bus comes" is a question Jun cannot yet work out at all. Asked how long from 2:10 until 2:40, Jun said "thirty o'clock," counting the numbers on the clock face rather than the minutes between them. Jun loves buses and already knows the timetable at the stop near home by heart — which bus, roughly when — but cannot connect that known thing to the hands on a clock.
The session is built on the one thing Jun already cares about: the real timetable at the local stop. Each question is a bus Jun knows — "it is 2:10, the bus leaves at 2:40, how long do you wait?" — so the minutes finally point at something real. The move is to count minutes in fives around the clock face, the way the timetable jumps in neat steps, rather than counting the printed numbers. Telling the time and working out how long until the bus become the same skill, anchored to a stop Jun can picture.
This one is built for paper, not a screen. Print the one page and fold it so only a single question shows at a time — Jun gets overwhelmed when a whole sheet of clocks appears at once, so the fold is doing real work. Jun answers the showing question, says the time or the wait out loud, and only then unfolds to the next. The guide keeps the answer key on a separate page, not on Jun's sheet, so Jun never sees the answers sitting beside the questions. Ruth sits beside Jun with the key, confirms or gently redirects, and lets Jun set the pace. Short is better than complete: a folded page of six questions done calmly beats a full sheet rushed.
Ruth can see the fold doing its job — or failing — and refold, cover, or set a question aside the moment Jun's face tightens. She can tell the difference between Jun guessing and Jun counting, and she holds the answer key so the page stays a set of questions rather than a test Jun can peek at. She can connect a question to a bus ride the two of them actually took last week, which no printed page can do. And she decides when six questions is plenty and it is time to walk to the real stop and watch a real bus come.
Jun knows the local timetable better than Ruth does — which bus comes when, which one is always a little late. Before the page, Jun leads: Ruth asks Jun to walk her through the stop's schedule, and genuinely learns something. The hardest questions on the page flip it — Jun has to tell Ruth how long until the next bus, teaching the wait out loud — because explaining the gap is harder than reading a single time, and it shows Ruth what Jun has really grasped.
Because this is print-first, the "game" is the folded page itself: one question visible at a time, each a clock face and a bus from the timetable, getting one step harder as Jun gets a run right and easing back after a miss — the guide turns to an easier question on the key if Jun stalls. Early questions ask only the time shown; later ones ask the wait between two times, counting in fives. The guide's separate answer key names the likely slip beside each answer — counting the numbers instead of the minutes, or losing track at the top of the hour — so Ruth can name exactly what happened rather than only "not quite," and note where to start next time.
Many seven-year-olds take a while with minutes and longer with elapsed time, and muddling the two is ordinary. But if, after many patient tries with real and concrete things over a long stretch, a child still cannot line up a number with an amount of time they can feel, or counting on consistently slips and resets in a way the child cannot notice or correct, it may be worth asking someone whose work is how children learn. A family doctor or an early-learning specialist can watch and tell you what they see. You do not need a label to have that conversation, and what you learn is yours to use however you choose.
A bus timetable is the way in here only because this child already loves the buses. Another child would find the minutes through a favourite show's start time, a sports clock, or an egg timer in the kitchen — and another child might do better on a screen than on paper, where this one needed the fold. Keep what works: one question at a time, the answers kept apart, the pace set by the learner. The goal is that the child can read the minutes and work out the wait. The thing you hang it on is yours to choose.
Stuck: can recite the words evaporation and condensation but cannot say what is actually happening to the water or why
An illustrative example made with a simulated family — not a real family's record. A way, never the way.
Guide: Carmen · Learner: Felix · Age band: 10–12 · Subject: Science
Felix, who is ten and working at about a grade five level, could reel off the words — evaporation, condensation, precipitation — and label a diagram with arrows. But asked what the water was actually doing, or why a cloud forms at all, he went quiet. The words sat on top of nothing. He could match the term to the picture in a workbook and still believe, when pressed, that the water in a puddle simply "disappears." The vocabulary had been learned as a list to return on a test, not as a description of something real happening to real water.
Felix loves watching things change state — ice going to water, water going to steam on the stove. So instead of starting from the words, the session starts from a change he can watch for himself. A sealed jar with a little warm water and a lid goes on a sunny windowsill. Over an hour, water climbs the inside of the glass as vapour, beads on the lid, and runs back down. That is the whole cycle, small enough to hold. Only after Felix has watched it and described it in his own words does the session attach a term to each thing he saw: the water that left the pool is evaporation, the drops on the lid are condensation, the run-back-down is precipitation. The word lands on an event he has already witnessed, not the other way round.
Set the jar up together first, warm water and a tight lid, and put it where the sun hits. Then leave it and do something else — the waiting is part of it, and checking back every fifteen minutes keeps the attention fresh rather than forced. Carmen's job while they wait is to ask, not tell: "Where did the water on the lid come from? It was at the bottom a minute ago." Let Felix reason it out loud, even when the first answer is wrong, before naming anything. Keep a single printed page with the jar drawn on it and blank lines where the words will go, and fill them in only once Felix has described each step without the term. Stop while he is still curious — one clean run of the cycle understood beats three terms memorised.
Carmen can hear the difference between Felix reciting "condensation" and Felix actually explaining that the vapour cooled against the glass and turned back to drops — the same word, two completely different states of understanding, and only a listener in the room can tell which one is happening. She can follow the unexpected question ("what if the jar were cold instead of warm?") into a second, better experiment, where a page would simply mark the first answer and move on. She can decide that today the jar is enough and the rain part waits for next time. And she can catch the moment the idea clicks — the look up from the glass — and let him teach it back to her while it is fresh.
Felix leads the watching. He decides how often to check the jar, he is the one who first notices the beads on the lid, and he narrates what is changing before any term is offered. When he gets to explain, unprompted, that the water "went up invisible and came back as drops," he is doing the real science — observing, describing, reasoning from what he saw — and the words are just labels for work he has already done. Carmen's part is to ask the question that makes him look again, and to name the thing once he has seen it. The learner supplies the understanding; the guide supplies the vocabulary that pins it down.
The game is a build-the-cycle screen, one step at a time rather than a whole diagram at once. It shows the sunny pool and asks: the water is leaving — is it disappearing, moving as invisible vapour, or sinking into the ground? A wrong choice names the specific slip ("it feels like disappearing, but the water is still there — it is just spread out as vapour you cannot see") rather than just marking it wrong. The next screen shows vapour meeting the cool lid and asks what happens; the next, the drops growing heavy and falling. Three levels: level one labels the steps Felix just watched in the jar, level two asks him to predict what changes if the air is colder or the water warmer, level three runs the cycle outward from a jar to a cloud and back. It steps up after three right in a row and eases back after a miss, and every mistake it logs is a reasoning slip the guide can pick up next time — not a score.
Plenty of children can recite science vocabulary long before the ideas underneath settle, and the gap between the words and the understanding is ordinary at this age — it is exactly what hands-on work is for. But if, across many topics and many months, a learner keeps returning memorised words with nothing underneath them, cannot hold a two-step cause and effect ("this happened, which made that happen") even after watching it directly, or tires sharply from any task that asks him to explain rather than recall, it may be worth describing what you see to someone whose work is how young people learn. A family doctor or a learning specialist can observe and tell you what they notice. You do not need a label to ask, and what you learn is yours to use as you choose.
A jar on a windowsill is one way into the water cycle, chosen because this learner loves watching things change state. Another child would get there through a puddle measured on the driveway over three dry days, a kettle and a cold spoon, or a drawing that animates. The thing worth keeping is the order — watch the real change first, reason about it out loud, attach the word last — not the jar itself. Use what fits your learner and your week; leave the rest.
A Meta DAX session can close by writing one entry to a learning record — a single dated JSON object, readable by a person and a program, append-only, kept privately on the guide's machine and published only if the family ever chooses to. Here is the entry this simulated session would write, in the metadax-record v1 shape (nickname only, no real name, no location, behaviour never a diagnosis):
{
"format": "metadax-record",
"v": 1,
"entry_id": "hs-sc52-s1",
"package": {
"ref": "HS-SC52",
"session": 1,
"title": "The Water Cycle in a Jar",
"subject": "Science",
"age_band": "10-12"
},
"date": "2026-10-09",
"attempted": [
{ "game": "Build the Cycle", "answered": 9, "right": 6 }
],
"reached": [
{ "game": "Build the Cycle", "level": 2, "of": 3 }
],
"mistakes": [
{ "name": "said the water disappeared rather than turned to vapour", "count": 2 },
{ "name": "named the term correctly but could not say what was happening", "count": 1 }
],
"learner_words": "Felix watched the lid for ages and then said: the water went up invisible and came back as drops, so it never actually left. He wanted to know what would happen if the jar were cold instead of warm.",
"guide_note": "The hardest moment was before the jar fogged up, when Felix still thought the puddle water just vanishes. Waiting and asking where the lid drops came from worked better than telling him. The click came when he said it never actually left. Next time I would like to try his own question — a cold jar — and get to the rain part. What only I could do: I could hear the difference between him reciting the word and him actually explaining it, and we stopped while he was still curious.",
"links": {
"sample": "https://daxfoundation.org/metadax/samples/#science-water-cycle-jar",
"package": "",
"play": "https://daxfoundation.org/metadax/play/"
},
"generated_by": "metadax-homeschool skill"
}
The entry stays on the guide's machine by default. Keeping a record over time is what the learning-record template is for; producing one entry, as above, needs nothing but the session. A way, never the way.
Stuck: treats history as dates and names to memorise and cannot see it as something that happened to actual people
Play with companion notes → guide-facing sidecar notes, shown only to the guide
An illustrative example made with a simulated family — not a real family’s record. A way, never the way.
Guide: Rosa · Learner: Luca · Age band: 10–12 · Subject: History
Luca, who is twelve, could pass a quiz on dates and names but experienced history as a wall of facts with no one behind them. Asked what any of it had to do with a real person, he shrugged — it was just stuff that was already over, printed in a book, memorised for the test and then gone. The idea that history is made of ordinary people's days, that someone alive today remembers a version of the past firsthand, had never quite landed. He was not uninterested; he simply had never met history as something a person could tell you about over a cup of tea.
Luca does love the family's own stories, and will happily sit and listen to an older relative remember things. So this session makes that the history lesson. The plan is a single real interview with a grandparent, kept fictional and generic here, about one small town they knew. Three questions carry it: what did the town look like back then, one job they held, and one change they watched happen over the years. Luca prepares the questions, asks them, listens, and takes rough notes. Afterward, the raw answers become the first page of a local history written in a real person's voice — not a list of dates, but what one person saw. History stops being a book and becomes a conversation he was part of.
Help Luca write his three questions before the interview, and keep them open — "what did the main street look like?" draws a story where "how many shops were there?" draws a number. Agree a signal for "ask the next one" so Rosa can sit in without taking over. During the interview, Luca leads and the grandparent talks; Rosa's whole job is to stay out of it unless the thread drops. Afterward, sit with the notes and help Luca turn three spoken answers into three short written passages, keeping the grandparent's own phrasing wherever it is vivid. Keep it to the three questions — a first interview that goes deep on three beats a scattershot twenty. Stop while there is still a story Luca wants to write down.
Rosa can read the room during the interview — notice when a question has opened something the grandparent wants to say more about, and quietly let the silence run instead of rushing Luca to the next question. She can tell when Luca is genuinely curious versus just working through his list, and nudge him to follow the live thread. She can judge which memories are the grandparent's to share and which to leave, a decision no page could make for a family. And afterward she can hear which plain spoken line — "the whole street smelled of bread on a Tuesday" — is the one worth keeping exactly as it was said, and help Luca build the passage around it rather than flattening it into a fact.
This whole session runs on Luca being the one who asks. He chooses the three questions, he conducts the interview, he decides which answers struck him enough to write down first. The grandparent is the expert on the town, but Luca is the one drawing the history out and shaping it — the historian's actual work. When he reads his finished page back and realises he has written something that did not exist in any book, because he made it from a real person's memory, the point of the subject arrives on its own. The guide sets it up and steps back; the learner does the history.
Between the interview and the writing, the game helps Luca turn spoken memories into a history. It shows one of the grandparent's answers and asks what kind of source it is — a firsthand memory, a guess, or something they heard from someone else — because a historian has to know. A wrong choice explains the difference rather than just marking it ("that is something they were told, not something they saw — still useful, but you would write it differently"). Then it offers three ways to open the written passage and asks which keeps the person's own voice rather than turning it into a textbook sentence. Three levels: level one sorts memory from fact, level two keeps the speaker's voice while tidying a sentence, level three asks Luca to place one remembered change on a simple before-and-after timeline. It steps up after three right in a row and eases after a miss, and every slip it notes is about handling a source, so Rosa knows what to pick up next time.
Finding history dry and disconnected is ordinary, and for most children it dissolves the moment the past becomes a real person talking — which is the whole point of this session. But if, across many subjects and many months, a learner cannot hold a sequence of events in order, loses the thread of a story told aloud and cannot say what came before what, or tires sharply whenever a task asks him to connect one thing to another rather than recall a single fact, it may be worth describing what you see to someone whose work is how young people learn. A family doctor or a learning specialist can observe and tell you what they notice. You do not need a label to ask, and what you learn is yours to use as you choose.
Interviewing a grandparent is one way into history, chosen because this learner loves the family's own stories. Another child would get there through old photographs of one street, objects from a kitchen drawer, or a song that was popular once. The thing worth keeping is the move — history as a real person's firsthand account, drawn out by the learner and handled like a source — not the particular grandparent or the particular town. Keep the interview fictional, generic, and the family's to share or not. Use what fits your learner; leave the rest.
This package carries a companion.json sidecar: the machine-readable file a cognitive companion reads alongside the package, in the metadax-companion shape. It is published in the repo at companion/examples/history-grandparent-interview.companion.json. The sidecar states the single next step for guide and learner, the reach band for this learner, the behavioural signals a companion may watch (each naming the inference it must never become), the moves the companion may offer and their ceilings — and, required and non-empty, the work reserved for the human guide, each with a reason it stays with a person. It names capabilities, never products, and everything it describes degrades to a once-a-day bundle. It is a sidecar, read with the package, never a profile of a child. A way, never the way.
Stuck: no prior fractions; curious about the why but cannot yet say what a fraction means or how a shape can be divided into equal parts
An illustrative example made from a parent's request — nothing identifying. A way, never the way.
Guide: a parent at home · Learner: un apprenant de 11 ans · Age band: 10–12 · Subject: Math · Language: French
A fractions course in French, in seven steps, set inside a single 3D stadium built with three.js. The learner arrives with no prior fractions and leaves having covered: what a fraction is (the pitch cut into equal parts), comparing fractions (two runners on the 400 m track), adding and subtracting (laps repainted with new equal parts), a fraction of a number (balls shared into hoops), finding the whole from a fraction — and a ten-penalty final to close. Done with a parent at home, in one sitting or across a few.
Every step has four parts: Regarde (a step-by-step 3D walkthrough), Pourquoi ? (the reason), À toi ! (five questions on the stadium, two tries, then the answer and why), and Guide (what to say, what to ask, what to watch for, an off-screen activity, the answer key). A Bilan at the end writes a next-time note — what happened in this session, never a label — to paste into the next one.
Built from a real parent's request; everything identifying is left out. Illustrative example.
Stuck: can count on to reach a fact but has not made the facts automatic; rebuilds every answer from one
A made-up example built from a parent's description. A way, never the way.
Guide: Hana · Learner: Milo · Age band: 7–9 · Subject: Math
Milo, who is eight, can already count on to find an answer. Asked for 6 plus 7, he starts at 6 and counts seven more on his fingers, and he gets there — slowly, and the same slow way every time, even for sums he has met a hundred times. Nothing has become automatic. Each fact is rebuilt from one, as if for the first time. When anything is timed or rushed, the counting falls apart and he guesses. The problem is not accuracy when he has all the time in the world; it is that the facts are not yet at his fingertips, and the counting eats all his attention before he can get to the actual maths.
A domino shows a number as a fixed pattern of dots, not a row to be counted one at a time. Milo already reads the pips on a tile as a shape — he sees five without counting to five — and that is exactly the habit quick facts are built on. So every fact starts on a tile. Doubles are the double tiles: the double-six is 6 and 6. Doubles plus one is that same double with one more pip beside it: 6 and 6 is twelve, so 6 and 7 is one more, thirteen. Make ten is two tiles whose pips fill a ten-frame: a six needs a four to make ten, so 6 and 5 is one past ten, eleven. The work is five minutes a day, not one long weekly sit, because facts become automatic through short, frequent practice. The game steps up after a streak of correct answers and eases back after a miss, so it stays at the edge of what Milo can do without tipping into guessing.
A session is short — five minutes is the whole thing, done most days rather than once a week. It opens with Milo in the lead: he sets up a topple run and teaches Hana his rule for how far apart the tiles have to stand so the whole line falls. This is real; Hana does not set them up as well as he does. Then one strategy at a time, named on an actual tile in Milo's hands: "that is a double, six and six, so you just know it is twelve." The guide's job is to listen for the difference between Milo recalling a fact and Milo quietly recounting under the table — the same answer arrives, but they are not the same thing, and only the recalled ones are the goal. Stop at five minutes even if a run is going well; coming back tomorrow matters more than pushing today.
Hana can hear the two-second pause and the moving lips that mean Milo is counting on in his head rather than remembering, and she can gently say the fact with him so the recall path gets used instead. She can tie a fact to a tile he toppled a minute ago, not a generic one. She can tell when a wrong answer is a tired guess rather than a real gap, and call it there for the day. And she decides when five minutes is up — stopping on a good one, so the next session starts from willingness rather than dread. A page cannot judge any of that.
Milo leads the setup. He knows, better than Hana, how to space a long line of dominoes so none of them is left standing after the first push, and he teaches her his rule for it. That reading of the tiles as whole patterns — seeing the pips without counting them — is the very thing that makes maths facts quick, and it is already his. Hana's part is to name it: the thing you do when you glance at a tile and just know it is a five is the same thing we are building for six and six, and for six and four making ten. He supplies the skill; she points out that he already has it.
The game shows a fact as two domino tiles and asks for the total, one at a time. Three levels: level one is the doubles, read straight off the double tiles; level two is doubles plus one and make ten, with the tiles arranged so the strategy is visible; level three mixes the facts within twenty with the tiles faded, so Milo is leaning on recall. Difficulty steps up after three correct in a row and steps back down after a miss. Wrong answers name the specific slip — counted on from one instead of using the double, went one too far on a near-double, or did not use the ten — so Hana's note after can say exactly which strategy to practise next. Nothing bad happens on a wrong answer; it just tells the two of them what tomorrow's five minutes is for.
Most children make their facts automatic with short daily practice over a few weeks or months, and needing to count on for a while is completely ordinary. But if, after a long stretch of patient five-minute sessions, a child still rebuilds every basic fact from one with nothing at all sticking, or if numbers and amounts seem to slip and rearrange in ways the child cannot notice or correct, or if the effort is sharp and persistent across many kinds of work and not just maths, it may be worth talking to someone whose work is understanding how children learn. A family doctor or an early-learning specialist can watch, ask questions, and tell you what they see. You do not need a label to have that conversation, and what you learn is yours to use however you choose.
Dominoes are one picture of quick facts, chosen because this child already loves them and already reads their dots as shapes. Another child would get there through finger patterns, a ten-frame, dice, or a number line they can picture. The parts worth keeping are the strategy-first order — doubles, then doubles plus one, then make ten — the five-minutes-a-day rhythm, and stopping while it is still going well. The goal is that the facts come without counting. What you hang them on is yours to choose.
Stuck: reads every word aloud accurately but cannot say what a passage was about afterwards
A made-up example built from a parent's description. A way, never the way.
Guide: Tomas · Learner: Ada · Age band: 10–12 · Subject: Reading
Ada, who is ten, reads aloud smoothly. Every word is right, the pace is good, and from the outside it sounds like reading is going well. But ask her what the passage was about and she goes blank, or offers one stray detail from the last line she read. Reading had quietly become the act of saying the words, with nothing arriving underneath. When a page has more than a few lines on it, she shuts down before she starts — not because she cannot decode it, but because holding the meaning of all of it at once feels like too much. The decoding is fine. The meaning is not landing.
Ada loves animals and the surprising true facts about them, and she will happily read a sentence to find out something strange. So the passages are exactly those: an octopus has three hearts; honey does not spoil, and jars of it have been found still edible after thousands of years; a group of flamingos is called a flamboyance; sea otters hold paws so they do not drift apart while they sleep. Because she wants to know the fact, there is a reason to read for what it means and not just how it sounds. The move has four small steps, the same every time. Read the question first, so she knows what she is looking for. Read one short chunk — a sentence or two, not the whole page. Say it back in one sentence, in her own words. Then point to the sentence that proves the answer. The chunks lengthen only gradually, from two sentences to a short paragraph to two.
Read the question before the passage, every single time — knowing the goal first is what makes the right words findable. Keep the chunk short: if the passage looks long to her, cover everything but one part with a hand or a card, because a long passage is only a few short ones stacked up. After each chunk, ask her to say it back in one sentence; if she can, she understood it, and if she cannot, read that part again together, slower. Then ask which sentence proves it and have her point to it — going back to the text beats guessing, and it is the habit that lasts. Celebrate the one-sentence summary out loud; that, not the number of questions done, is the real win for the day. Keep it short and stop while she is still curious about the next fact.
Tomas can hear the difference between Ada reading the words of a passage and Ada actually understanding it — the same sentences said aloud, two completely different things, and only a listener in the room can tell which is happening. He can see the shut-down coming when the page lengthens, a beat before she says a word, and cover all but one chunk before it lands. He can pick the next passage around an animal she mentioned this morning, so it feels like hers. And he can decide that four passages understood calmly is a better day than ten rushed, and end there. A page cannot read her face or follow her sideways question into a better passage.
Ada knows a great deal about animals — more than Tomas, on her favourites — and the session starts there. Before any reading, she teaches him one thing: why an octopus might need three hearts, or that otters wrap themselves in seaweed so the current does not carry them off while they sleep. He listens and asks a real question. This is not a warm-up; it puts her in the expert's chair, and the confidence of being the one who knows carries straight into the reading that follows. On her side of the page, too, the first thing she meets is an invitation to pick the animal she wants to read about, not a question to answer.
The game is called Read and Prove It. It shows the question first, then a short passage, and asks Ada to pick the answer she can prove from the words in front of her. Wrong answers are tied to the specific comprehension slip behind them: picking a true but small detail instead of what the passage was mostly about; choosing the option that repeats words from the text even though it does not match the meaning; answering without going back to look; or mixing up who did what. Three levels set the length — level one is two sentences, level two a short paragraph, level three two short paragraphs — and difficulty steps up after three correct in a row and steps back down after a miss, so the length stays close to what she can hold. Every wrong choice explains the difference rather than only marking it, so Tomas's note after can say exactly which kind of mistake to work on next.
A gap between fluent reading-aloud and weak understanding is common, and for many children it narrows quickly once the question-first, one-chunk habit takes hold — which is the whole point of this session. But if, over many months and across many subjects, a learner still cannot hold the meaning of even a two-sentence passage, cannot say it back in her own words even when it is read aloud to her, loses the thread of a story told out loud, or tires sharply whenever a task asks her to explain rather than recall, it may be worth describing what you see to someone whose work is how children learn. A family doctor, or a reading evaluation through your province or state, is the right place to ask. None of this is a diagnosis, you do not need a label before asking, and asking earlier rather than later means more options.
Animal facts are one way in, chosen because this child will read almost anything to find out something strange about an animal. Another child would read for meaning through jokes, a sports report, the instructions to a game, or a comic. The parts worth keeping are the moves, not the topic: read the question first, take one short chunk, say it back in one sentence, and point to the proof. The goal is that she can say what she read. What she reads to get there is hers to choose.
Stuck: arrived home learning behind in both reading and maths, with scattered gaps, and the guide cannot tell where to restart
A made-up example built from a parent's description. A way, never the way.
Guide: Grace · Learner: Wren · Age band: 7–9 · Subject: Other
Wren, who is eight, came to learning at home after a hard year, described by the parent as "behind" in both reading and maths — but behind in a scattered, uneven way. Wren reads some words easily and stalls on others that look no harder; adds some small numbers instantly and is lost on others; seems fine one minute and at sea the next. Every curriculum Grace opened assumed a starting line, and Wren might be ahead of it in one place and well behind it in another. Start too high and Wren shuts down; start too low and Wren is bored and insulted. The real stuck point was not any single skill — it was that Grace had no way to tell where the first real gap was, and so no idea where to begin.
Wren loves crossing the creek behind the house on its line of stepping stones, and already knows the rule: you cross in order, you test each stone with a bit of weight before you trust it, and if one wobbles you steady yourself there — you do not leap for the far bank. That is exactly the shape of the check. It lays a short line of stones in the order skills are usually built: hearing and saying letter sounds, blending simple three-sound words like cat and sun, adding within ten, and reading a two-digit number as tens and ones — knowing that 24 is two tens and four ones. Grace walks Wren across gently, one stone at a time, and the first stone that wobbles is where the next real session will begin. The point is to find the earliest wobble, not the latest — to go back to the first loose stone, not to leap ahead to where the trouble shows most.
Say what this is before you start: "We are finding the comfy place to begin, not catching you out." Then cross the stones in order and keep it light. Ask each one plainly, give Wren time, and move to the next stone only while they are steady. Once two stones in a row wobble, stop asking harder ones — you have found the edge, and pushing past it only teaches Wren that the check is a test to fail. Note which stones were solid, which wobbled, and which were not there at all. Reading the results is simple: find the earliest wobble, and begin the next real session one stone before it, on the last solid stone, so the first lesson is a win Wren can feel. Keep the whole thing under ten minutes. A short, kind crossing tells you more than a long one that ends in tears.
Grace can tell a true gap from a nervous stumble — the wobble that means "I never learned this" from the one that means "I am tired, or shy, or testing whether this is safe." She can keep her face and voice easy so a check never curdles into an exam. She can notice when "I don't know" arrives because the session has simply run out of road for today, and stop there. She can hold the whole picture — that Wren was solid on letter sounds but wobbled on blending — in a way that turns four small observations into one clear place to start. And she decides, watching Wren, when enough has been found for one day. A page cannot read a child it has upset.
Wren knows the real creek far better than Grace does — which stones are safe, which tip if you land wrong, how to test one with your weight before you trust it. Before the check, Wren leads: teaching Grace how to cross the real stones without getting a wet foot. And that method Wren is teaching — go in order, test gently, steady yourself at the first wobble rather than leaping — is precisely the method of the check itself. Grace's part is to point that out: the careful way Wren crosses the creek is the careful way the two of them will find where to start. The learner supplies the method; the guide names what it is for.
This one is built to be gentle, not to push, so it works differently from a game that races ahead. It shows one stone at a time: a letter sound to say, a short word like cat to blend, a sum within ten, a number to split into tens and ones. There is no timer and no score shown to Wren — stones simply light up as "crossed," and the mood is a walk across the creek, not a quiz. If a stone wobbles twice, the path pauses there kindly — "this is a good stone to practise; let's start here next time" — rather than marking anything wrong. The stones stay in their fixed, build-up order instead of jumping harder after a streak, because the whole job is to find the earliest gap, not to find the ceiling. The guide key quietly records which stone was the first to wobble, so Grace knows exactly where the next real session begins.
Starting behind after a disrupted year is ordinary, and most gaps close once you begin at the right stone and build forward patiently. But some patterns are worth raising plainly with a professional. If letter sounds are not there at all even after lots of gentle exposure, if blending simple words does not come even with short daily practice over months, if the whole picture stays far behind what you would expect for the age and does not shift over a long stretch, or if you notice things like not seeming to hear the difference between similar sounds, squinting or headaches or losing the place when reading, or words that seem to move on the page — these are worth a conversation. Your family doctor, or an educational or reading evaluation through your province or state, is the right place to ask. None of these is a diagnosis, you do not need a label before asking, and you are not expected to work this out on your own. Asking early simply gives you more information and more options.
Stepping stones are one way to picture finding the first gap, chosen because this child already crosses a real creek this way. Another guide would picture the lowest loose rung on a ladder, the first wobbly block in a tower, or the earliest bar in a song where the fingers stumble. The parts worth keeping are the moves, not the creek: check in the order skills are built, find the earliest wobble rather than the latest, and begin one stone before it so the first lesson is a win. The goal is to find the first real gap kindly, and to start there. How you picture the crossing is yours to choose.
Stuck: reads a little but writes a string of random letters for a spelling word, because he does not yet hear the separate sounds in it
A made-up example built from a parent's description. A way, never the way.
Guide: Priya · Learner: Jonah · Age band: 4–6 · Subject: Writing
Jonah, who is five, can read a handful of words and loves to. But when Priya asks him to write a word — even one he has just read — he writes a long string of letters that have little to do with its sounds: "bdjxid" for bridge, "kprln" for garden. He is not being careless; he is writing down the letters he can think of, because a word still arrives in his ear as one lump of sound rather than a row of separate sounds he could match to letters. Spelling lists and copying had not shifted this, because they ask him to remember letters before he can hear what the letters are for. The gap is not his memory and not his effort — it is that he cannot yet pull a spoken word apart into the sounds that make it.
Jonah likes lining up and sorting small things — buttons, bottle tops, a handful of counters — and a counter is a perfect stand-in for a single sound. So before any letter is written, Priya says a short word slowly and Jonah pushes one counter forward for each sound he hears: c–a–t is three counters, pushed one at a time. Only then does he write one letter above each counter. This runs the opposite way to the blending sample, where separate sounds are pushed together into a word; here a whole word is pulled apart into its separate sounds. They start with CVC words — cat, sun, map — where every sound is a single letter. Digraphs come next: sh, ch and th each get one counter, because each is a single sound even though it takes two letters, so "ship" is three counters and "chop" is three. Five minutes a day, and they stop on a word he got.
Keep it to five minutes, most days. Start with Jonah leading — he sorts the counters into colours or lines them up his own way, and Priya follows his rule — so the counters are his before they are the lesson's. Then one short word at a time: say it slowly, let Jonah push a counter per sound, and only write once the sounds are counted. Treat a phonetic spelling as a success, not an error: if he writes "treet" for treat or "nite" for night, he has heard every sound and matched a reasonable letter to each, which is exactly the skill being built — say so out loud, then show the grown-up spelling alongside without rubbing his out. Exception words that cannot be sounded out come separately, only two at a time, and are learned by sight rather than forced onto the counters. Stop on a word he got right, even if the five minutes could have held one more.
Priya can hear the difference between Jonah missing a sound and Jonah hearing it but not knowing its letter — the same wrong spelling on the page, two completely different things, and only a listener beside him can tell which. She can slow her own voice on the exact word where his counters stall, stretching caaat until the middle sound surfaces. She can decide that "treet" is a win worth stopping on rather than a mistake worth correcting today. And she can tell when a tired guess means the session is over, and end it there, on a good one, so tomorrow starts from willingness. A page cannot stretch a sound in response to the child in front of it.
Jonah leads the counters. He lines them up and sorts them better than Priya does, and she lets him set them out his way before any word is said. That lining-up — one thing, then the next, in a row — is the very move that spelling needs: a word is sounds in a row, pushed out one at a time, just like his counters. Priya's part is to name it: the careful way he lays the counters down is the careful way the two of them will lay a word down, sound by sound. He supplies the habit; she points out what it is for.
The game is one short round the parent runs at the table with a handful of counters. Priya says a word; Jonah pushes one counter for each sound, then writes a letter above each counter. Three levels set the words: level one is three-sound CVC words where every sound is one letter; level two brings in digraphs — sh, ch, th — each as a single counter; level three mixes them and lets a word run to four sounds. It steps up after a streak of words he spells sound-for-sound and eases back after a miss, so the words stay at the edge of what he can hear. A phonetic spelling counts as correct for the game, because every sound is there; the guide key quietly notes which one it was, so Priya knows which grown-up spellings to show next. Exception words are kept out of the levels and practised separately, two at a time. Nothing bad happens on a miss; it just tells the two of them which sound to listen for tomorrow.
Hearing the separate sounds in a word is a skill that grows with exactly this kind of short, playful practice, and spelling a word the way it sounds is a normal, healthy stage on the road to standard spelling — not a problem to fix in a hurry. But if, after a long stretch of patient five-minute sessions, a child still cannot hear or push out the separate sounds in a simple word, cannot tell where one sound ends and the next begins even when you stretch the word right out, or tires sharply whenever sounds and letters are involved and not with other work, it may be worth describing what you see to someone whose work is how children learn. A family doctor or an early-learning or reading specialist can watch, ask questions, and tell you what they see. None of this is a diagnosis, you do not need a label before asking, and asking earlier rather than later only gives you more options.
Counters are one picture of the sounds in a word, chosen because this child already loves to line small things up. Another child would hear the sounds through claps, taps on the table, blocks snapped onto a row, or coins laid down one at a time. The parts worth keeping are the order — say the word, push one counter per sound, then write one letter per counter — with CVC words before digraphs, phonetic spellings welcomed as progress, and exception words kept separate and few. The goal is that he can hear a word as separate sounds and write a letter for each. What he pushes to feel them is yours to choose.
Stuck: after a read-aloud or short passage, cannot recall it, or gives a one-sentence summary that misses the point
A made-up example built from a parent's description. A way, never the way.
Guide: Owen · Learner: Lily · Age band: 7–9 · Subject: Reading
Lily, who is eight, listens to a whole story read aloud and then, asked what it was about, says "I don't remember" — or gives one short line that catches a stray detail and misses the point, like "there was a dog" after a story in which the dog barely mattered. It is not that she was not listening; it is that the story arrives as a stream and nothing holds it together afterwards, so when it stops there is nothing to reach back for. Pages of comprehension questions had not helped, because they ask her to find what she never gathered in the first place. The gap is not attention and not her memory for things she cares about — it is that she has no handle to pick a story up by once it is over.
Lily loves to draw, and she will tell you everything happening in one of her pictures before she can tell you a thing about a page of words. So the retell is built on pictures and on her own hand. First the chunks are kept short: Owen reads one or two paragraphs, stops, and they retell that much before going on, instead of waiting for the end of a long story once it has all run together — the chunks lengthen only as retelling the short ones gets easy. Then comes the handle: three fingers. One finger for who, one for what happened, one for how it ended; she says the three answers in a row, and those three said together are the summary. For a story she is struggling to hold, she draws a quick three-box sketch first — who, what happened, how it ended, one rough picture each — and tells it from the boxes. While Owen reads, she is allowed to jot a single word now and then, so her hands stay in it. Five minutes, and they stop on a retell she nailed.
Keep the chunks short at first — one or two paragraphs, then stop and retell — because a long passage is only a stack of short ones, and she can hold a short one. Start with Lily leading: she shows Owen a picture she drew and tells him everything in it, which is retelling, done fluently, on her own ground. Then read a chunk and hold up three fingers: who? what happened? how did it end? Let her answer each, then have her say all three in a row so she hears that the three together are the whole thing. If she stalls, reach for the three-box sketch before reaching for more questions. Lengthen the chunks only when the short ones come easily. Celebrate the three-in-a-row retell out loud — that, not the number of pages, is the win — and stop while she still wants the next chunk.
Owen can hear the difference between Lily not remembering a story and Lily not knowing how to pick it back up — the same "I don't remember," two different problems, and only someone listening can tell which. He can choose where to stop reading so a chunk breaks at a natural seam rather than mid-thought. He can see when she needs to draw the three boxes before she can say them, and hand her the paper without making it a big deal. He can pick the next passage around something she drew that morning, so the story feels like hers. And he can decide that three retold calmly beats ten rushed, and end on a good one. A page cannot choose where to pause for the child in front of it.
Lily retells better than anyone when the story is one of her own drawings — she will narrate every corner of a picture, who is there, what is happening, how it turns out, without being asked. That is the whole skill, already hers. Owen's job is to point it out: the way she tells what is happening in her picture is exactly what three fingers ask of a story someone else wrote — who, what happened, how it ended. She supplies the retelling; he names it and turns it onto a new story. On her side, too, the first thing she meets is an invitation to tell the story in her own picture before anyone asks her about a page.
The game is one short round a parent can run with nothing but their hands and, if it helps, a scrap of paper folded into three boxes. The grown-up reads a chunk aloud — one or two paragraphs — then holds up three fingers and asks for who, what happened, and how it ended, and Lily says the three in a row. Three levels set the length: level one is a single paragraph, level two is two paragraphs, level three is a short whole story told in parts. It steps up after a run of clean three-finger retells and eases back after one that misses, so the chunk stays as long as she can hold and no longer. A retell that catches a small detail but misses the point is not marked wrong; it is named — "that is a true thing from the story; now give me the who and the how it ended" — so she learns the difference between a detail and the point. The three-box sketch is always allowed, and so is a single jotted word while she listens.
Losing the thread of something heard once, and needing a handle to pick a story back up, is ordinary — and for most children the three-finger retell, built on shorter chunks, is enough to turn it around, which is the point of this session. But if, over many months and across many kinds of material, a child cannot say back even a one- or two-paragraph story told slowly and in parts, loses a spoken story almost as soon as it is told, cannot hold who did what from the start of a tale to its end, or tires sharply whenever a task asks her to retell rather than recall a single fact, it may be worth describing what you see to someone whose work is how children learn. A family doctor, or a reading or language evaluation through your province or state, is the right place to ask. None of this is a diagnosis, you do not need a label before asking, and asking earlier rather than later means more options.
Three fingers and a three-box sketch are one way to give a story a handle, chosen because this child thinks in pictures and tells them easily. Another child would hold a story with a comic strip, three toys stood in a row for beginning-middle-end, or simply the question "who wanted what, and did they get it?" The parts worth keeping are the moves, not the fingers: shorten the chunk until she can hold it, then retell who, what happened, and how it ended as three answers in a row, and lengthen only as it gets easy. For an older learner who reads every word fluently but still cannot say what a passage was about, the next step is reading-for-meaning-animal-facts. The goal is that she can say what happened. What she holds it with is hers to choose.
Stuck: capable and careful, but freezes and writes nothing when asked to write something open-ended
A made-up example built from a parent's description. A way, never the way.
Guide: Rosa · Learner: Felix · Age band: 10–12 · Subject: Writing
Felix, who is eleven, is a careful, capable worker who freezes the moment a task is open-ended. Hand him a worksheet with blanks to fill and he is fast and accurate; ask him to "write about anything you like" or "write a paragraph about the book" and he sits, pen up, writing nothing for the whole session. It is not that he has no ideas — talk to him and they pour out — it is that an open page offers too many choices at once and he will not commit to one in case it is the wrong one, or not good enough. The blank page is not too hard for him; it is too wide, and his care for getting things exactly right has hardened into a wall he cannot start over.
Felix loves getting things exactly right and building from clear step-by-step instructions — a model kit with every piece numbered is his idea of a good afternoon — and the approach gives writing the same scaffolding. It removes the choices. Instead of a blank page, Rosa gives him a topic-sentence frame with three "because" slots: "____ is the best ____, because ____, because ____, and because ____." They fill every slot aloud together before a single word is written, so the committing happens in speech, where he is fluent, not on the page, where he freezes. Once the frame is full, the "writing" is just copying down what he already said. The next step keeps the rails on: he takes a short model paragraph and rewrites it changing exactly one thing — one noun, one opinion — then two things, growing from the model a little at a time rather than facing an empty page. Five minutes, and they stop on a finished sentence.
Never open with a blank page. Start with Felix leading — he explains the order of steps in something he built, which is him being fluent and exact, the very strengths the session will lean on. Then put the frame in front of him and fill it aloud first; do not let him near the writing until every slot has been said out loud, because the freeze lives in the choosing, and choosing out loud with Rosa is safe. When it is time to write, offer to take dictation for the first draft — he says it, she writes it — so that getting words down and forming them by hand stay two separate jobs and neither jams the other. Keep the one-change rewrite small on purpose: one change is a decision he can make without it feeling like the whole thing rests on him. Stop on a finished, correct sentence — for a perfectionist, ending on something right is what makes him willing to start again tomorrow.
Rosa can tell the difference between Felix having no idea and Felix having too many and refusing to pick — the same blank page, two different problems, and only someone talking with him can tell which. She can take dictation at the exact moment the handwriting is what is jamming him, separating the composing from the writing so he can do one at a time. She can hold the standard where he cannot: telling him that a first draft is allowed to be ordinary and that they will make it better afterwards, which is a thing a perfectionist often cannot give himself. And she can decide to stop on one good sentence rather than push for a whole paragraph, because for this child a clean ending is what unlocks the next start. A page cannot lower a wall it cannot see.
Felix knows, better than Rosa, how to follow and explain a sequence of exact steps — the thing he does when he builds from instructions. Before any writing, he leads: he walks her through how something is put together, in order, leaving nothing out. That is the skill the frame borrows: a paragraph is steps in an order — claim, because, because, because — followed one at a time, exactly the way he follows a build. Rosa's part is to name it: the careful, in-order way he explains his model is the way the two of them will build a paragraph, one slot at a time. He supplies the method; she points out that writing is just another thing built in steps.
The game is one short round the parent runs on paper, and it never shows a blank space. It gives a topic-sentence frame with three because-slots and a small bank of filled-in options to choose from, so every move is picking, not generating from nothing. First Felix picks what the sentence is about, then chooses or says each "because" aloud, and only then writes the full sentence down — or has it taken down for him. Three levels loosen the rails a step at a time: level one is choosing from options to fill the frame; level two is rewriting a model sentence with one change of his own; level three is two changes, then three, until the frame is doing less and he is doing more. It steps up after he finishes a round without stalling and eases back the moment he freezes, so the page is always narrow enough to start on. Nothing is ever blank and nothing is ever wrong for being plain — a finished, ordinary sentence is the whole win.
Freezing at an open-ended task while sailing through a structured one is common, especially for a careful child who wants to get it right, and for most the frame-first, fill-aloud approach is enough to get writing moving — which is the point of this session. But if, over many months and across many subjects, getting any words onto the page stays far harder than how fluently the child speaks, if the hand itself freezes or tires in a way that does not ease with practice, or if the distress at starting is sharp and persistent rather than ordinary reluctance, it may be worth describing what you see to someone whose work is how young people learn. A family doctor or a learning specialist can observe, ask questions, and tell you what they see. None of this is a diagnosis, you do not need a label before asking, and asking earlier rather than later only gives you more options.
A topic-sentence frame with three because-slots is one way to make an open task startable, chosen because this child trusts clear steps and freezes without them. Another child would need a spoken sentence caught and written down, a picture to label, or three options to choose between. The parts worth keeping are the moves, not the frame: remove the choices, fill the frame aloud before writing anything, take dictation so composing and handwriting stay separate, and grow by one small change at a time from a model. The teen version of the same freeze — fluent out loud, stalled on the page — is turning a hockey argument into a paragraph. The goal is that he can start. The rails you give him to start on are yours to choose.
Stuck: gets upset and walks away whenever he gets something wrong — a count, a puzzle piece, a letter — so being wrong ends the work before it starts
A made-up example built from a parent's description. A way, never the way.
Guide: Mara · Learner: Theo · Age band: 4–6 · Subject: Math
Theo, who is four, is quick and willing right up until the moment something comes out wrong. He miscounts a row of buttons, or a puzzle piece will not go where he thought, or he writes a letter that does not look like the one on the card — and his face falls, he says "I can't do it," and he gets up and walks away. It happens the same way whatever the work is: counting, a puzzle, a letter. He is not refusing to learn and he is not short on ability; the trouble is that being wrong feels like a small disaster, and so the first mistake ends the session before any learning can stand up again. Longer sessions and gentle "try again"s had made it worse, because they kept him sitting at the exact spot where the bad feeling lives. The gap is not his thinking — it is that a mistake is not yet a safe place to be.
The one thing Theo cannot resist is catching a grown-up being wrong — the delight of being the one who knows better. So Mara hands him that on purpose. First they do a thing together, her hands alongside his, so a right answer is already in the room and nobody is being tested. Then she plays it wrong: she counts three buttons "one, two, three, four," slowly, straight-faced, and waits. Theo lights up — "No! That's three!" — and counts it right himself, laughing, because now the mistake is hers and catching it is the whole fun. Being wrong has quietly changed its meaning: it is the thing you look for and pounce on, not the thing that ends the game. She keeps it to five or ten minutes and stops while he is still winning, so the session's last feeling is the good one. Every time he tries — even a try that misses — she names it out loud: "you had a go at that, that's the brave bit." If he does walk off, she lets him, and comes back later with an easier version, so the next start is one he can win.
Keep it short — five to ten minutes, most days — and end it on purpose while he is ahead, not when he tires. Start together: do one round hand-in-hand so a correct version exists before anyone is on the spot. Then switch to catch-my-mistake, where Mara is the one who gets things wrong and Theo is the catcher. Make the mistakes obvious at first — count a clear three as four — and only later make them subtler. Praise the trying, out loud and specifically: not "good boy," but "you kept going even when it was tricky." If he gets one wrong himself, treat it exactly as he treats hers — "oh, catch me out, let's count it again" — so his mistake and hers are the same friendly thing. If he walks away, let him go without a fuss; the walking away is information, not defiance. Come back later the same day with a version one notch easier, so the door he reopens is one he can get through.
Mara can read the exact half-second when Theo's face starts to fall and head it off with a deliberate mistake of her own, turning the moment away from collapse before it arrives. She can judge how wrong to be — obvious enough to catch today, subtle enough to stretch him tomorrow. She can tell the difference between a walk-away that means "I am done" and one that means "make it easier," and answer each differently. She can decide that four happy minutes beats ten that end in tears, and stop on the laugh. And she can hold, steadily and warmly, the one thing the whole approach rests on: that being wrong is safe here. A worksheet cannot be caught out, cannot laugh with him, and cannot choose to end on a win.
Theo leads the catching. Nobody taught him to delight in spotting a wrong count — that is his, already, and it is exactly the attention a mistake needs: looking closely, checking, noticing when something is off. Mara's part is to point out what it is for. The sharp eye he turns on her counting is the same eye he can turn on his own, gently, once being wrong stops stinging. He supplies the pounce; she turns it, over time, from catching her into checking himself — not as a test he passes or fails, but as the fun of finding the slip and fixing it. The lead is his; she only shows him where it points.
The game is "Catch my mistake," one short round a parent runs at the table with anything there is a handful of — buttons, blocks, grapes, counters. The grown-up counts a small group out loud and gets it wrong on purpose — says "four" for three, skips a number, counts one button twice — and the child catches it and counts it the right way himself. Three levels set the challenge: level one is an obvious miss in a group of three or four; level two is a trickier miss — a double-count or a skipped number — in a group up to six; level three lets the child take a turn making the mistake for the grown-up to catch. It steps up after a run of happy catches and eases back the moment the fun dips, because the fun is the point and the counting rides along underneath it. There is no wrong move in this game — a missed catch just means the grown-up gets away with it that round and tries an easier one next. This is a game a parent plays by hand; it is not a screen to switch on.
Getting upset at being wrong, and needing mistakes made safe before learning can go on, is an ordinary and very common stage for a young child — and for most, short playful sessions that turn being wrong into a game are enough to loosen it, which is the whole point of this one. But if, over many months and across many kinds of gentle, low-pressure play, a child still comes apart at the smallest error, cannot bear to try anything he is not already sure of, stays distressed long after a mistake rather than recovering with a laugh, or shows the same sharp upset around other everyday changes and not only around being wrong, it may be worth describing what you see to someone whose work is how young children learn and feel. A family doctor, or an early-childhood or early-learning specialist, can watch, ask questions, and tell you what they see. None of this is a diagnosis, you do not need a label before asking, and asking earlier rather than later only gives you more options.
Catch-my-mistake is one way to make being wrong safe, chosen because this child already loves catching a grown-up out. Another child would need a different door: a puppet who gets things gloriously wrong, a "whoops, let's fix it" song, a tally where every mistake-caught earns a point for the team you are both on. The parts worth keeping are the moves, not the buttons: do it together first, let the guide be the one who is wrong so being wrong turns funny, praise the trying out loud, keep it to five or ten minutes, stop while he is winning, and when he walks off let him and return later one notch easier. The goal is that a mistake becomes a safe, even funny, place to be — so that trying can carry on. What you count, and who gets caught, is yours to choose.
Stuck: traces letters and short sentences neatly, and the parent wonders whether tracing is enough writing or whether something more should be happening
A made-up example built from a parent's description. A way, never the way.
Guide: Ellen · Learner: Wren · Age band: 4–6 · Subject: Writing
Wren, who is in kindergarten, traces beautifully. She follows the dotted letters, she copies a short sentence underneath a model, and the page comes out neat. Ellen is not worried that Wren cannot do it — she can — but she has started to wonder whether tracing is actually writing, or whether it is handwriting practice that stops short of the thing itself. Wren can form the letters; what she has not yet done is put her own words onto a page and watch them become writing. The gap, if it is one, is not skill and not effort — it is that tracing gives her someone else's words to follow, and nobody has yet shown her that the words can be hers. This sample is less about a stuck child than about the next small step past a step done well.
Wren will tell you everything about her day if you let her, and she draws what she did before she has the words for it. So the writing starts from her mouth and her pictures, not from a worksheet. Each day she says one sentence about her day — "We found a snail by the step" — and Ellen writes it down, saying each word as she writes it so Wren sees talk turn into marks. Then Wren copies just a word or two of her own sentence; not the whole line, only a piece she can finish while still fresh. The other half is labelling her own drawings: Wren draws a dog and writes the sounds she hears for it, and "dg" counts as a win, because she has listened to a word and matched letters to its sounds — which is the real engine under spelling. Nobody fixes "dg" to "dog" today. Five or ten minutes, and they stop on a word or a label she is pleased with. Hearing and writing the sounds in a word is the very next thing this leads to, built out fully in spelling-by-sound-counters.
Keep it short — five to ten minutes — and let Wren's talk start it. Ask for one sentence about her day and write it down for her, speaking each word as you write so she watches speech become print. Then have her copy only a word or two, not the whole sentence, so copying ends while she is still interested. On other days, or the same day, let her draw first and label the drawing with the sounds she hears; welcome "dg" for dog and "sn" for snail out loud as real writing, and resist tidying them into correct spelling — that comes later and not here. Praise the having-a-go at the sounds, specifically. Keep her own words at the centre: the sentence is hers, the drawing is hers, the labels are hers, and your job is to catch them on paper and hand them back. Stop on something she made, not when a line is "finished."
Ellen can take the sentence Wren actually says and write it down as she said it, so the words on the page are genuinely the child's — a worksheet can only offer words chosen in advance by a stranger. She can hear that "dg" means Wren caught the first and last sounds of dog and tell her that is exactly right, rather than marking it wrong. She can judge how much of a sentence Wren can copy before interest fades, and stop one word short of that. She can decide that today's win is one proud label and end there. And she can hold the quiet distinction at the heart of this: tracing builds the hand, but only a person can invite the words that make it writing. A page of dotted letters cannot ask Wren what she did today.
Wren leads with her voice and her pictures. The sentences are hers before any pencil moves; the drawings carry the meaning that the letters will later spell out. That is the whole of early writing, already in her — she has things to say and ways to show them. Ellen's part is to name it: the story you just told me, and the picture you just drew, those are writing, we are only catching them on the page. She supplies the words and the pictures; Ellen supplies the handle that turns them into marks Wren can make herself. Over time the writing-down shifts from Ellen's hand to Wren's, a word at a time, as the child's own sentences pull her pencil along.
The game is one short round a parent runs at the table with paper, a pencil, and whatever Wren drew that day. First, "one-sentence news": Wren says a sentence about her day, the grown-up writes it, and Wren copies a piece of it. Then, "label your picture": Wren writes the sounds she hears for the things in her drawing. Three levels set the reach: level one is copying a single word of her own sentence and writing a first sound or two on a drawing; level two is copying two words and labelling with beginning-and-end sounds, like "dg"; level three is Wren having a go at a whole short word's sounds and copying a short phrase. It steps up after a run of happy, willing goes and eases back the moment it feels like a chore, because willingness is the thing being protected. There is no wrong answer here: a sound-spelling is a success by design, and a copied word that wobbles is still her own word on the page. This is a game played by hand with a pencil; it is not an app to open.
Moving from tracing to a child's own words happens gradually, and sound-spellings like "dg" for dog are a normal, healthy stage on the road to standard writing — not a sign that anything is wrong, and for nearly every child this gentle kind of daily invitation is all it takes. But if, over many months of short, low-pressure sessions, a child cannot hear or write even the first sound of a spoken word, cannot copy a short familiar word she has just watched being written, shows real distress whenever a pencil and her own words are involved and not with other play, or seems unable to connect the marks on a page to the words she says aloud, it may be worth describing what you see to someone whose work is how children learn. A family doctor, or an early-learning or literacy specialist, can watch, ask questions, and tell you what they see. None of this is a diagnosis, you do not need a label before asking, and asking earlier rather than later only gives you more options.
Dictating a sentence and labelling a drawing is one way to carry a child past tracing into her own words, chosen because this child talks and draws readily. Another child would get there through a different door: telling a story into a toy microphone for you to write, making a label for every toy in a box, or captioning a photo from the day. The parts worth keeping are the moves, not the snail or the dog: let the child's own sentence be the text, write it down for her and let her copy a piece, welcome sound-spellings as real progress, and keep each session short and willing. The goal is that she sees her own words become writing and starts putting the sounds she hears onto the page. What she says, and what she draws, is hers to choose.
Stuck: reads decodable readers fine in lessons but will not try a real book on his own — closes it, or asks to be read to instead
A made-up example built from a parent's description. A way, never the way.
Guide: Tomas · Learner: Cass · Age band: 7–9 · Subject: Reading
Cass reads his decodable readers in lessons without trouble — he sounds the words, he gets through the little book, he is accurate. But hand him a real book, the kind with a story in it, and ask him to read it on his own, and he closes it, or pushes it back, or asks to be read to instead. It is not that he cannot read the words; it is that a real book looks like a wall of them, with no promise that each one will be sound-out-able the way the decodables are, and the risk of hitting a word he cannot get feels too big to start. The decodables are safe because they only use what he has been taught; a real book makes no such promise, and so he will not step onto it alone. The gap is not his decoding — it is confidence, and the size of the leap between a controlled reader and an open book.
Cass loves being read to, and he loves animals — he will happily read a page out loud to the family cat when nobody is making him. So the bridge is built out of sharing and out of a soft audience. First, take turns: Tomas reads a page, Cass reads a line, and that is all that is asked of him to begin with. Over days, Cass's share grows — a line, then two, then a short paragraph — but only as fast as he stays willing, so the book never tips back into a wall. Second, the real books they choose are a notch easier than his lesson level, so that the words he meets are nearly all ones he can already get; a real book he can almost coast through does more for courage than a hard one does for skill. Third, when he reads his part, he reads it to the cat — or a stuffed animal, or his little sister — because reading to someone who cannot judge him takes the pressure clean off. And Tomas keeps his own read-alouds separate, at another time of day, purely for the pleasure of a story, so that being read to never turns into a turn Cass has to take. Ten minutes, and they stop on a page that went well.
Start with the turns clearly small: you read a page, he reads a line. Say so up front, so he knows exactly how little is being asked before he opens the book. Choose a real book a notch below his lesson level — easy enough that he meets almost only words he can already read. Grow his share by one line at a time, and only after a run of easy turns; the moment he tenses, shrink it back. Let him read his part to a pet or a toy, and sit a little to the side rather than leaning in, so it is reading-to-the-cat and not reading-to-be-checked. When he hits a word he cannot get, supply it quickly and move on — no stopping to sound it out mid-story, because the story's flow is what is being protected. Keep your own bedtime or sofa read-alouds entirely separate and pressure-free, so the pleasure of being read to stays pure and never becomes a lesson. Stop while he still has appetite, on a page that felt good.
Tomas can feel the exact moment Cass's willingness is about to tip and shrink the turn before the book becomes a wall again. He can choose the real book — judging it a notch easy, picking a story about the animals Cass loves — in a way no reading level alone could. He can supply a stuck word in half a second so the story never stalls, and know when to supply it and when to wait. He can keep two things apart that matter: the shared take-turns reading, and the pure read-aloud that asks nothing of Cass at all. And he can tell the difference between "this book is too hard" and "I am just nervous to start," and answer each rightly. A levelled book list cannot watch a child's shoulders and know when to make his turn smaller.
Cass leads when he reads to the cat. Nobody has to push him; he picks a page and reads it aloud to an animal that will never correct him, and in doing it he is doing the whole thing — reading real words, off a real page, out loud, for the pleasure of it. That is the skill, already his, in the one setting where the fear is switched off. Tomas's part is to notice it and gently widen the circle: from the cat, to the cat-with-Tomas-nearby, to taking turns with Tomas on a book they share. Cass supplies the willing reading; Tomas keeps the audience soft and the turns small enough that the willingness survives being seen. The pace is set by the child, one line at a time.
The game is take-turns reading, one short round a parent runs with a real book a notch easier than lesson level and a soft audience — the cat, a stuffed animal, a patient sibling. The grown-up reads a page; the child reads his share to the animal. Three levels set the child's share: level one is one line per page; level two is two or three lines; level three is a whole short paragraph, or alternating pages. It steps up after a run of pages the child read happily and eases straight back after one that felt like too much, so his turn always sits just inside what he can do without strain. There is no losing: a word he cannot get is simply supplied by the grown-up and the story rolls on, because keeping the story moving matters more than winning any single word. The read-to-a-pet audience stays throughout, because the whole game rests on reading to someone who cannot judge. This is a game played with a paper book and a willing listener; it is not a screen that reads along. The step before this one — getting separate sounds to blend into whole words at all — is built out in reading-blending-dinosaurs.
Hanging back from real books while reading decodables fine is common and usually about confidence, not ability — and for most children, small shared turns on easy, loved books are enough to carry them across, which is the point of this session. But if, over many months of gentle take-turns reading on books well within his decoding, a child still cannot read even a single easy line of unfamiliar text on his own, loses words he clearly knows the instant they appear outside a controlled reader, shows real and lasting distress at the sight of any book that is not a decodable, or tires sharply whenever reading is asked of him and not with other work, it may be worth describing what you see to someone whose work is how children learn to read. A family doctor, or a reading specialist through your province or state, can watch, ask questions, and tell you what they see. None of this is a diagnosis, you do not need a label before asking, and asking earlier rather than later only gives you more options.
Taking turns and reading to the cat is one way across the gap from decodables to real books, chosen because this child loves being read to and loves animals. Another child would cross it differently: a comic where the pictures carry half the load, a book he has heard read aloud so many times he half-knows it, or reading a line each to a friend on a video call. The parts worth keeping are the moves, not the cat: take turns and grow the child's share slowly, pick real books a notch below lesson level, let him read to an audience that cannot judge, supply stuck words fast to protect the story, and keep your own read-alouds separate so they stay pure fun. The goal is that he will open a real book and read a little of it himself. What the book is about, and who he reads it to, is his to choose.
Stuck: counts out loud to ten by rote but cannot say how many are in a small pile — the words are a song, not yet a count of things
A made-up example built from a parent's description. A way, never the way.
Guide: Nadia · Learner: Posy · Age band: 4–6 · Subject: Math
Posy, who is four, can say "one, two, three, four, five" all the way to ten, and she says it proudly. But put four toy cars in front of her and ask how many, and she points and recites the number song — sometimes touching the same car twice, sometimes running the words faster than her finger — and lands on a number that has nothing to do with four. Ask her again and she gives a different answer. Nadia had wondered whether to buy a workbook, but the trouble is not that Posy needs more pages. The counting words have arrived as a tune, the way a nursery rhyme does, before they have been hooked onto actual things. The gap is not her memory and not her effort — it is that she does not yet know that counting means one word for one thing, and that the last word you say is the answer to "how many?"
Posy lines things up all day — her toy cars nose to tail along the skirting board, pasta shapes sorted into little rows, blocks stacked and counted off. That lining-up is already the exact move counting needs, so Nadia builds on it rather than bringing in anything new. They start with a small pile of the real things Posy plays with. Posy touches one and moves it to a new spot as she says the number — touch and move, one car at a time, so a counted car physically leaves the pile and cannot be counted twice. When the pile is gone, Nadia asks "so how many?" and, at first, answers it herself: "four — the last number you said is how many there are." After a few days Posy says the last number back. Then comes "one more": add a car, and instead of recounting from one, "we had four, one more, so…" — the first taste of counting on. Last, with just three or four things on a plate, Nadia covers and uncovers them for a moment and asks how many without counting — small groups the eye can simply see. Five minutes, and they stop on a pile she got. No worksheets anywhere: the maths is in her own hands moving her own toys.
Keep it to five minutes, most days, with whatever Posy is already playing with — cars, pasta, blocks — never a special "maths" object. Begin with the move that makes counting honest: touch one thing and slide it away as you say its number, so each thing is counted once and only once. If she double-counts or outruns her finger, slow her hand, not her voice. When the pile is counted, always ask "how many?" and, for the first while, answer it yourself so she hears that the last number is the total; hand that question to her only once she is ready. Keep the piles tiny — three, four, five — because number sense is built on small amounts seen clearly, not large ones rushed. Bring in "one more" as its own small game: add one, and nudge her to say the next number rather than starting over. Save subitising — knowing three at a glance — for a plate of two, three, or four, uncovered for a second. Praise the careful one-at-a-time touching, out loud, because that care is the skill. Stop on a pile she counted right, even if there was time for one more.
Nadia can watch Posy's finger and her mouth at the same time and see the exact place they come apart — the finger on the third car while the mouth is already saying "five" — and gently bring them back together, which no page of printed dots can do. She can tell the difference between Posy not knowing the number words and Posy knowing them but not yet hooking them to things, two very different situations that look identical from across the room. She can decide the pile is one car too big today and quietly take one away. She can answer "how many?" for Posy for exactly as many days as Posy needs, and not one day longer. And she can read the moment the attention goes and stop on a win, so counting stays a thing Posy wants to come back to. A worksheet cannot move a car, follow a finger, or choose when to stop.
Posy leads with her lining-up. Nobody taught her to set her cars nose to tail in a careful row — that is already hers, and it is the very heart of counting: things in a line, dealt with one at a time, in order. Nadia's part is to name what it is for. The careful way Posy lays her cars down is the careful way the two of them will count them: one car, one word, the next car, the next word. She supplies the habit of order; Nadia supplies the words that ride along on top of it. When Posy wants to count her own things, in her own line, her way, that is not a detour from the lesson — it is the lesson, and Nadia follows her lead.
The game is one short round a parent runs on the floor or at the table with a handful of whatever the child lines up — cars, pasta shapes, blocks, buttons. Deal out a small pile; the child touches and moves each thing to a new spot as she counts, then answers "how many?" with the last number she said. Three levels set the reach: level one is counting a pile of up to four, touch-and-move, with the grown-up saying the total; level two has the child say the total herself and play "one more" — add one, count on instead of starting over; level three covers a group of two, three, or four for a second and asks how many without counting at all. It steps up after a run of piles counted right and eases back the moment a pile gets muddled, so the amounts stay small and seeable. There is no losing: a miscount just means the grown-up and child slide the things back into the pile and count again, slower. This is a game played by hand with real toys; it is not a screen to switch on. It pairs well with the catching game in the mistakes-are-safe sample, where a grown-up miscounts on purpose for the child to catch.
Reciting the number words long before they attach to actual things is an ordinary, healthy stage — for almost every four-year-old, a few weeks of exactly this kind of short, playful counting is all it takes for "how many?" to click. But if, over many months of gentle five-minute sessions, a child still cannot count a pile of three or four things one at a time without doubling back, cannot tell you that the last number said is the total even after you have shown her again and again, cannot hold the smallest amount in mind from one moment to the next, or grows sharply upset whenever counting comes up and not with other play, it may be worth describing what you see to someone whose work is how young children learn. A family doctor, or an early-learning specialist, can watch, ask questions, and tell you what they see. None of this is a diagnosis, you do not need a label before asking, and asking earlier rather than later only gives you more options.
Counting her own toy cars in a line is one way into number sense, chosen because this child already lines small things up for the pleasure of it. Another child would get there through a different door: steps climbed and counted out loud, grapes eaten one at a time off a plate, spoons laid out for dinner, stones dropped into a tin. The parts worth keeping are the moves, not the cars: touch and move one thing per number so nothing is counted twice, answer "how many?" with the last number said, add "one more" to begin counting on, and let the eye learn to see two, three, and four at a glance. The goal is that she knows counting means one word for one thing and that the last word is the answer. What she counts to get there is hers to choose.
Stuck: treats science as facts to be told and has stopped wondering out loud — never asks why things happen, and waits to be given the answer
A made-up example built from a parent's description. A way, never the way.
Guide: Marcus · Learner: Devi · Age band: 10–12 · Subject: Science
Devi, who is eleven, can learn science facts when they are handed to her and give them back on a quiz. But somewhere along the way the wondering went quiet. She no longer asks why the kettle steams or why the apple slice goes brown; she waits to be told, and treats "science" as a pile of other people's answers to memorise. Marcus noticed it most on a walk, when she shrugged at something she would have pestered him about a year before. The gap is not that she cannot think — she thinks sharply when a thing is hers — it is that science has stopped being a question she gets to ask and become a lecture she sits through. A fact told is forgotten by the next week; a question she chased herself stays. What is missing is the asking.
Devi still notices odd little things — she just stops short of asking about them — and she loves being proved right. So the household builds a small weekly habit around her own noticing, and Marcus holds himself to one hard rule: he asks, he never lectures. On Monday one question goes on the fridge, written on a card — often one Devi half-wondered aloud, sometimes one Marcus offers if the week is quiet. She writes a guess underneath it, in pen, and signs it; the guess is allowed to be wrong, and being wrong on Monday is part of the fun of Friday. Midweek they do one small thing about it — a two-minute test at the kitchen counter, a look in the garden, or, if it truly cannot be tested at home, a quick look-up together — just enough to see what actually happens. On Friday Devi writes the answer in two sentences, in her own words, under her guess, and they compare the two. That is the whole week: notice, guess, check, say it back. Five minutes on Monday, a few midweek, five on Friday. The point is never the single fact; it is that she asked and chased it herself.
Three example weeks, all from the kitchen or the garden:
Hold the one rule above everything: you ask, you do not lecture. When Devi guesses wrong on Monday, say nothing to correct it — the wrong guess is what makes Friday worth reaching. Let the question be hers whenever you can; a question she half-asked on a walk, caught and written on the card, beats a better one you supply. Keep the midweek check genuinely small — one plate, one look, two minutes — because an experiment that needs a whole afternoon never happens twice. Prefer something testable at home; keep the look-up for the questions that truly cannot be seen. On Friday, make her write the answer in her own words, not copy a sentence from anywhere, and hold her to just two sentences — the squeeze is part of the thinking. When you compare guess and answer, celebrate a changed mind as the win: "you thought X, you found Y — that's exactly how it is meant to go." Never let it sprawl into a lesson. Stop on the two sentences, and let the next week's question start itself.
Marcus can catch the question Devi only half-asked — the shrug on the walk that a year ago would have been a "but why?" — and write it on the card so the week grows from her own wondering, which no curriculum printed in advance can do. He can decide a question is better tested than looked up, and the opposite, reading which one will keep her curious. He can keep his mouth shut when she guesses wrong, holding the surprise for Friday instead of flattening it with the answer on Monday. He can hear whether her two sentences are truly hers or borrowed, and ask one more "but why?" when they are borrowed. And he can model the thing itself — wondering out loud, being happily wrong, chasing it down — because science is caught from a person who does it, not delivered from one who recites it.
Devi leads by choosing the question, more weeks than not. The noticing is already hers — she sees the odd little things; she had only stopped saying them aloud — and the whole habit is built to coax that noticing back into the open and treat it as the start of real science. Her guess leads too: it is her claim, signed in pen, and the week exists to test her idea, not Marcus's. His part is to name what she is doing — "that question you just asked, that's science, let's chase it" — and to keep the answer in her words, not his. Over the weeks the fridge fills with questions she thought of, and the asking, which had gone quiet, comes back as a habit.
The game is the week itself, run by the family at the fridge — no equipment but a card, a pen, and whatever is already in the kitchen or garden. Monday: a question goes up and the learner writes and signs a guess. Midweek: one small test or look to see what really happens. Friday: a two-sentence answer in the learner's own words, set beside the guess. Three levels set the reach: level one, the guide offers the question and the learner guesses and checks; level two, the learner supplies the question from something she noticed; level three, she also designs the small midweek test herself — what to compare, what to keep the same. It steps up after a run of weeks she drove herself and eases back if a week feels like a chore, because the wondering is the thing being protected. There is no losing: a guess proved wrong on Friday is the best kind of week, because something got learned the hard, memorable way. This is a habit a family keeps by hand at the fridge; it is not a screen to switch on. It runs well alongside the science-words sample, where the words from each week's answer earn a place on a running word wall.
Going quiet on wondering for a stretch is ordinary — curiosity ebbs and flows, and for almost every child a gentle weekly habit that hands the asking back is enough to bring it out again, which is the whole point of this one. But if, over many months, a learner cannot form a guess about an everyday thing even with a friendly prompt, cannot say back in her own words something she saw with her own eyes a day before, cannot follow a two-step "notice, then check" from one day to the next, or grows sharply distressed whenever she is asked to think rather than recall and not with other work, it may be worth describing what you see to someone whose work is how children learn. A family doctor, or a learning specialist, can watch, ask questions, and tell you what they see. None of this is a diagnosis, you do not need a label before asking, and asking earlier rather than later only gives you more options.
One-question-a-week is one way to turn science from facts-told back into questions-asked, chosen because this child notices things and likes being proved right. Another family would get there through a different door: a jar of questions drawn at random, a nature walk that must produce one "why," a single "wonder of the week" photographed and puzzled over. The parts worth keeping are the moves, not the fridge: one question, a guess written down before any checking, one small at-home test or look midweek, and a short answer in the learner's own words set against the guess — with the guide asking and never lecturing. The goal is that she wonders out loud again and learns to chase an answer herself. What you put on the card, and where you look for the answer, is yours to choose.
Stuck: learns a science word for the quiz and loses it a week later — the definition was memorised, never attached to anything real
A made-up example built from a parent's description. A way, never the way.
Guide: Yusuf · Learner: Omar · Age band: 10–12 · Subject: Science
Omar, who is eleven, can learn a science word for Friday's quiz and get it right — then lose it clean by the following week. "Evaporation," "friction," "dissolve": he memorises the definition the night before, says it back, and a few days later looks blank at the same word. Yusuf used to think Omar was not trying, but he is: he is cramming definitions as strings of words with nothing underneath them, the way you might memorise a phone number you never dial. A word learned that way has no handle, so there is nothing to pick it back up by. The gap is not his memory for things that matter to him — he can tell you every part of a thing he built — it is that these words never got attached to anything he could see, touch, or do. A definition with nothing behind it slides straight off.
Omar is a maker: he would rather do a thing than be told about it, and he draws easily. So each new word is given something to hang on, in four small steps, and never more than three new words in a week. First, the word gets an object or an action — something he can hold or do. "Dissolve" is a spoon of sugar stirred into warm water until it vanishes; "friction" is rubbing his two hands together until they are warm; "evaporation" is a wet handprint on the counter watched until it is gone. Second, he writes his own definition, in his own plain words — not the textbook's. Third, he makes a quick drawing of it, however rough. Fourth, he uses the word in a sentence about something he actually did that week: not "friction is a force," but "I slowed my bike by braking, and friction is what the brakes used." Those four — object, own words, picture, real sentence — go on a card, and the card joins a running word wall on the kitchen door. Each day, for two minutes, they glance over the wall: he reads a word, says what it means in his words, and that is all. At most three new words a week, so the wall grows slowly and nothing is ever crammed.
Cap it at three new words a week, and defend that cap — a full wall of half-learned words is worse than three that stick. For each word, insist on all four handles, in order: hold or do the thing first, because the object is what the word will hang on; then his own definition, and gently refuse the textbook wording even when it is more "correct," because a word in his words is a word he owns; then a drawing, rough is fine; then a sentence tied to something he really did this week, which is where the word stops being abstract. Keep the daily review to a true two minutes — read a word, say it back, move on — because it is the coming-back, not the length, that fixes a word in place. Review old words more than new ones; the wall is there so nothing quietly falls off it. When a word has survived a couple of weeks of two-minute glances, let him retire it to a "known" list and feel the wall turn over. Praise the drawing and the real-life sentence, not the matching of a definition. Stop on a word he said back easily.
Yusuf can find the object or action that makes a particular word click for this child — that warm-hands moment for friction — rather than the generic example a book prints for everyone. He can hear the difference between Omar reciting a definition and Omar understanding it, the same words in the air meaning two different things, and only a listener beside him can tell which. He can hold the line at three words a week when Omar, or a worksheet, wants to pile on ten. He can tie a word to something Omar actually did on Tuesday, because he was there on Tuesday. And he can decide a word has stuck and retire it, or that it is wobbling and send it back for another week — a judgement no quiz score, taken on one anxious Friday, can make. A printed glossary cannot rub its hands together or remember what the child did this week.
Omar leads with his hands and his own words. The definition that will last is the one he phrases himself, so the session hands him that job rather than a sentence to copy. His drawing leads too — it is his picture of the thing, and a word pinned to his own picture has somewhere to live. Yusuf's part is to name what is happening: the thing you just did, and the way you just said it, that is the word — we are only giving it a label to carry around. He supplies the doing, the wording, and the picture; Yusuf supplies the handle and keeps the wall honest. When Omar wants to add a word of his own, something he met while making something, that goes straight on the wall — a word he came to himself is already halfway stuck.
The game is the word wall itself, run by the family on a door or a wall with cards, a pen, and whatever small thing shows the word. Making a card is the first round: do or hold the thing, write your own definition, draw it, use it in a sentence about your real week. The daily round is two minutes: read a word off the wall and say back what it means in your own words. Three levels set the reach: level one, the guide supplies the object and the learner does the other three handles; level two, the learner finds his own object or action for the word; level three, he adds a word he met himself while making something and builds its whole card. It steps up after a run of words that survive the two-minute review and eases back if words start slipping, which is the signal to add fewer and review more. There is no losing: a word that slips just goes back to the "still learning" side of the wall for another week. This is a wall a family keeps by hand; it is not a screen to switch on. It runs well alongside the one-question sample, where the words from each week's answer are exactly the ones worth putting on the wall.
Learning a word for a quiz and losing it soon after is extremely common — it is what cramming does, to all of us — and for nearly every child, tying words to real objects and reviewing them two minutes a day is enough to make them hold, which is the whole point of this one. But if, over many months of this gentle, object-first practice, a learner cannot hold on to even a single new word tied to something he touched and did, cannot say back in his own words a term he used correctly a day before, loses words as fast as they are added no matter how few are introduced, or grows sharply distressed whenever words and their meanings are involved and not with other work, it may be worth describing what you see to someone whose work is how children learn. A family doctor, or a learning or language specialist, can watch, ask questions, and tell you what they see. None of this is a diagnosis, you do not need a label before asking, and asking earlier rather than later only gives you more options.
A word wall with four handles per word is one way to make science vocabulary stick, chosen because this child makes and draws and learns by doing. Another child would get there through a different door: a word acted out in a charade, a term taught to a younger sibling, a card shuffled into a game, a word spoken into a running list. The parts worth keeping are the moves, not the door on the kitchen: give each word an object or action, let the learner define it in his own words and draw it, tie it to something he really did that week, review it two minutes a day, and add no more than three new words at a time. The goal is that a word learned is a word kept, because it has something real to hang on. What you hang it on is yours to choose.
Stuck: can do a grammar worksheet but cannot find the same thing in a real sentence, or use it in his own writing — the rule and the reading live in separate boxes
A made-up example built from a parent's description. A way, never the way.
Guide: Rosa · Learner: Milo · Age band: 7–9 · Subject: Writing
Milo, who is eight, can fill in a grammar worksheet — circle the verb, underline the noun — and often gets it right. But close the worksheet and open the adventure book he reads at bedtime, and the grammar vanishes: he cannot find the verb in a sentence he just read and loved, and nothing from the worksheet shows up in his own writing. The rule lives in one box and his reading in another, and the two never meet. Rosa had a workbook on the shelf and a nagging sense it was not working, and it was not — not because Milo cannot learn grammar, but because grammar taught on strangers' sentences stays stuck to strangers' sentences. The gap is not his ability — he knows the story better than she does — it is that the grammar never touched a sentence he cared about. What is missing is the bridge from the rule to the book in his hands.
Milo loves his adventure book and loves being the expert on its story, so the grammar comes straight out of it — tonight's chapter, not a workbook. Each session, Rosa and Milo pick three sentences from the pages he is already reading, and they do one move with them — only one, the same move across all three, never a grab-bag. The moves rotate across sessions:
Always, the last sentence is Milo's own: after three from the book, he writes one sentence doing the same move, about the story or about his day. Grammar words like verb and conjunction can come in once the plain version is solid, laid over something he already understands. Five or ten minutes, and they stop on a sentence he got. No workbook anywhere.
Use the book he is actually reading, and pick the three sentences from the pages he read most recently, so the grammar lands on words still warm in his head. Do one move per session and only one — the point is depth on a single idea, not a tour of five. Lead with plain language before the technical word: "the doer and the doing" before "subject and verb," "joining words" before "conjunctions," so the idea is understood before it is labelled. For joining and for changing time, always read both versions aloud — the ear is doing half the teaching, hearing why a writer chose one shape over another. Keep the three book-sentences short and clear; skip a sentence that is too tangled today. End every session with Milo's own sentence doing the same move, because using it himself is where the rule finally crosses the bridge into his writing. Praise the finding and the having-a-go, not neat handwriting. Keep it to five or ten minutes and stop on a sentence he got right, even if there was room for one more.
Rosa can open the very book Milo is reading tonight and pull the grammar from a sentence he already cares about — a worksheet can only offer sentences chosen in advance for no child in particular. She can hear whether "find the doer" has clicked or whether he is guessing, and ask the one more question that settles it. She can skip the sentence that is too knotted for today and pick a cleaner one from the same page, a judgement no printed exercise can make. She can read both the joined and unjoined versions aloud and let Milo hear which the author chose, then follow his ear into why. And she can decide that one good sentence of his own is the win and stop there, so grammar stays tied to a book he loves rather than a chore he dreads. A workbook cannot reach for the book in the child's hands.
Milo leads with the book. He is the expert on its story — he knows what the dragon did and why — and the session starts from that authority, not from a rule handed down. He often picks the three sentences himself, choosing bits he liked, and a sentence he chose is a sentence he will look at closely. His own sentence at the end leads too: it is his, about his story or his day, and it is where the grammar stops being Rosa's and becomes his. Her part is to name what he is already doing — you found who was doing the thing; that doer has a name, we call it the subject — so the labels land on understanding he already had. He supplies the book, the sentences, and the expertise; she supplies the one small move and the bridge from the page to his own writing.
The game is one short round a parent runs with the book the child is reading, a pencil, and a scrap of paper — nothing else. Pick three sentences from tonight's chapter and do one move with all three: find the doer and the doing, join two short ones, or change the time; then the child writes one of his own. Three levels set the reach: level one, the guide points to the sentences and names the move in plain words; level two, the child picks the three sentences and tries the move himself; level three, the child names the move using the proper word — subject and verb, joining word, past and present — and writes two of his own. It steps up after a run of sentences he handled easily and eases back the moment a move gets muddled, so the grammar stays close to what he can do. There is no losing: a wrong guess just means reading the sentence aloud together and trying again, slower. This is a game played by hand with a real book; it is not a screen to switch on. It pairs well with the decodables-to-real-books sample, where the same real book is the thing a reluctant reader is coaxed into on his own.
A gap between doing a grammar worksheet and using grammar in real reading and writing is very common at this age — and for nearly every child, pulling the grammar out of a book they love is enough to close it, which is the whole point of this one. But if, over many months of short, gentle sessions, a child still cannot find the doer and the doing in a simple sentence he has just read, cannot hear the difference when two sentences are joined or a sentence's time is changed even when you read both aloud, cannot carry a single move into a sentence of his own, or grows sharply distressed whenever sentences and their parts come up and not with other work, it may be worth describing what you see to someone whose work is how children learn. A family doctor, or a literacy or language specialist, can watch, ask questions, and tell you what they see. None of this is a diagnosis, you do not need a label before asking, and asking earlier rather than later only gives you more options.
Pulling three sentences from tonight's chapter is one way to make grammar stick, chosen because this child loves his book and likes being its expert. Another child would get there through a different door: sentences from a comic, the words of a favourite song, a recipe, or the back of a cereal box. The parts worth keeping are the moves, not the adventure book: take the grammar from something the child is already reading and cares about, do one move per session — doer and doing, joining two sentences, changing the time — read the changes aloud so the ear teaches, and finish with the child's own sentence. The goal is that grammar crosses the bridge from a rule into the sentences he reads and the ones he writes. What book you open to find it is his to choose.
Stuck: the parent works from home and cannot see how lessons fit a working day, and the learner drifts when a lesson runs long
A made-up example built from a parent's description. A way, never the way.
Guide: Priya · Learner: Jonah · Age band: 4–6 · Subject: Reading
Priya works from home and wanted to start Jonah, who is six, on learning at home. Two things were tangled. The first was hers: between calls and messages she could not picture where lessons would actually go, or how many hours a day it should take, and every plan she sketched assumed a school-shaped day she did not have. The second was Jonah's: when a lesson ran long he drifted — eyes to the window, sliding off the chair, a sudden need for water — not because the work was too hard but because it went on past the point a six-year-old can hold. The stuck point was the shape of the day, not the content: Priya could not see how the lessons fit around her work, and Jonah could not stay with a lesson that outlasted his attention.
Jonah loves trains, and more than the trains he loves the order of them — which car comes after which, the whole line laid out so you know what is coming. Priya built the day to look like that. The guided part is about ninety minutes in total, but never in one block: it is cut into short cars the length a six-year-old can ride. Reading is the longest car at about twenty minutes, maths about fifteen, writing about ten, strung through the day in two or three sittings that sit in the gaps around Priya's calls. Each car is a picture on one schedule taped where Jonah can reach it — a book for reading, counters for maths, a pencil for writing, and just as real: a car for play, a car for a chore, a car for outside, and a read-aloud car at the end. Jonah ticks each car as the day rolls through it, so he can always see what is now and what is next. The rest of the day — most of it — is play, chores, outdoor time, and being read to. Ninety minutes of guided work, predictably placed, is the engine; the long free stretches are the rest of the train.
Each car is short on purpose. Start the reading car first, when attention is freshest, and keep it near twenty minutes; stop it while Jonah is still with you, not when he has drifted. Maths and writing are shorter still. Put the cars in the gaps your work leaves — one before your first call, one after, one in the afternoon — and keep them in the same order most days so Jonah can predict them. Five minutes into a car that is going well is not a reason to add ten more; stop on a win, tick the car, and let the next free stretch be the reward. If a call runs over, the car waits; the schedule bends around the work rather than breaking. The ninety minutes does not have to be exact or unbroken — it is a rough shape, not a quota — and some days two cars is plenty. What matters is that Jonah can see the line of the day and feel each car end before he tires of it.
Priya can see the exact moment Jonah starts to drift and end the car a minute early, so the reading block finishes on a good line rather than a lost one. She can slide a car later when a call runs over without the whole day falling apart, and she can judge, watching him, whether today is a three-car day or a two-car one. She can tell restlessness that means "I am done" from restlessness that means "I need to move first," and send him outside before the next car rather than fighting through it. And she can hold the thing the schedule is really for — that the day is predictable and the work ends before it sours — in a way no fixed timetable printed once could. A plan on paper cannot watch a child's attention; a parent can.
Jonah leads the order. He is the one who knows how a train should be made up, and Priya lets him build the day's line each morning — choosing which car comes after which among the few that have to happen, and setting the play and outside cars where he wants them. That ordering is not a frill; deciding what comes next, and seeing the sequence through, is real thinking, and it is already his. Priya's part is to name what it is for: the care he gives to making up the train is the same care that gets the reading car and the maths car done, because he can see them coming and knows the free car is just down the line. He supplies the order; she points out that the order is what makes the day work.
The game is "build the day's train," played by hand at the start of the morning with a small set of picture cards — one for each car: reading, maths, writing, play, a chore, outside, read-aloud. Jonah lays them out in order on the table or along the floor, and ticks or flips each card as that part of the day is done, so the schedule is something he makes and runs, not something done to him. Three levels set how much he leads: level one, Priya lays the must-do cars and Jonah adds the play and outside cars and ticks them off; level two, Jonah orders the whole line himself with Priya checking; level three, Priya slips one card into the wrong place on purpose and Jonah catches it and fixes the order. It steps up as building the train becomes easy and eases back on a scattered morning. There is no losing — a card in the wrong spot just gets moved. This is a game played with paper cards by hand; it is not a screen to switch on.
A six-year-old who can only stay with a lesson for a short stretch is doing exactly what six-year-olds do, and short predictable blocks are usually all it takes for the drifting to settle as attention grows. But some patterns are worth describing plainly to someone whose work is how young children learn. If, over many months of short, gentle, well-placed blocks, a child still cannot settle to even a few minutes of anything, or seems not to hear or follow simple spoken instructions, or the restlessness is sharp and constant across play as much as lessons and not easing with age, it can be worth a conversation. Your family doctor or an early-learning specialist can watch, ask questions, and tell you what they see. None of this is a diagnosis, you do not need a label before asking, and asking earlier only gives you more to work with.
A train of cars is one way to shape a short guided day around a parent's work, chosen because this child already loves the order of things. Another family would picture stepping stones across the morning, a row of boxes to tick, or simply three short "chapters" with long play between them. The parts worth keeping are not the trains: guided work kept to roughly ninety minutes of short, predictable blocks — reading about twenty, maths about fifteen, writing about ten — placed in the gaps around the work, one visible schedule the learner can see and tick, the rest of the day given to play and outside and a read-aloud, and every block stopped on a win before it sours. This is one family's way of fitting it around a working day, not the way, and it makes no claim about what any law or place requires of you. How much a day it takes, and how you lay the cars out, is yours to choose.
Stuck: multi-digit multiplication and long division keep falling apart, and the parent is about to switch maths programmes to fix it
A made-up example built from a parent's description. A way, never the way.
Guide: Omar · Learner: Beth · Age band: 7–9 · Subject: Math
Beth, who is nine, worked through one maths programme to the end of its grade-four material, and there multi-digit multiplication and long division came apart. She sets a two-digit-by-one-digit problem out neatly and then stalls, or carries the wrong number, or loses her place partway down a long division. Omar's read was that the programme had stopped working and it was time to switch to another one — the question he brought was which. But the trouble was not really the programme. Watching Beth, the carrying and the dividing fell apart in the same place every time: at the moment she needed a times-table fact and did not have it to hand, so she stopped to count it out, lost the thread of the bigger procedure, and the whole thing collapsed. The stuck point was underneath the multiplication, not in it — and a new programme would land her at the very same spot.
Before changing anything, Omar does a five-minute check to find the one topic that is actually wobbling — the same idea a companion sample, find-the-earliest-gap-stepping-stones.md, lays out for mixed early gaps, pointed here at one maths procedure. It has three quick steps. First, the facts: he runs through the times tables and sorts each one, with Beth, into the ones she just knows and the ones she counts out — not to score her, just to see. Second, place value, and here Beth's own thing does the work: she loves the coin jar, and she already trades ten pennies for a dime without thinking. That trade is place value — ten ones regrouped as one ten — and the same trade is exactly what carrying and long division lean on. He lays out one number in coins and has her say it as tens and ones. Third, a single two-digit-by-one-digit problem, talked through out loud, so he can hear where it breaks. Almost always it breaks at a fact that is not automatic. So the fix is not a new programme: it is five minutes a day on the handful of facts that are still counted out — the strategy-first way the companion sample math-facts-fluency-dominoes.md describes — and only once those facts come without counting does Omar judge whether the programme itself is the problem.
The check is short and kind — five minutes, not an exam. Say what it is first: "We are finding the one thing to fix, not testing you." Run the facts and simply note which are instant and which get counted; two seconds and moving lips is a counted one. Do the coin step next: can Beth say a number as tens and ones, and trade ten ones for a ten without having to think? Then one multiplication problem, out loud, and listen for the exact moment it breaks. You are looking for the earliest wobble, not the latest — the counted fact underneath the failed carry, not the failed carry itself. Then the daily work is five minutes on those facts, most days, stopping while it is going well. Keep a short note of which facts are still counted so each session starts where the last left off. Do not switch programmes yet; give the facts a few weeks first, and judge the programme only against a child who now has them.
Omar can hear the difference between Beth recalling six times seven and Beth quietly counting it under her breath — the same answer arrives, but only one of them is the skill the multiplication needs. He can tell a carry that failed because the procedure is shaky from a carry that failed because the fact underneath was missing, and chase the earlier one. He can watch one talked-through problem and locate, in a few seconds, the single place it breaks — something no finished worksheet, marked right or wrong at the end, can show him. And he can decide, before spending months on a different programme, whether the programme was ever the problem at all. A page can mark the answer; only a person can find the reason.
Beth leads the coins. She sorts the jar better than Omar does and already knows, without being told, that ten pennies make a dime and ten dimes make a dollar's worth — trading up a handful of small coins for one bigger one as a matter of course. That trade is the whole of place value, and it is already hers. Omar's part is to name it: the swap she does in the coin jar — ten ones become one ten, and you write the one in the next column along — is the very move that carries in multiplication and regroups in long division. She supplies the trading; he points out that the thing she finds obvious with coins is the thing the hard problems are built on.
The game is a hand-played sorting game with the facts and the coin jar, no screen involved. It comes in two small piles and three levels. First Beth meets a times-table fact on a card and drops it into one of two piles — "I just know it" or "I had to work it out" — which turns the five-minute check into something she runs herself and can watch shrink as the worked-out pile gets smaller week by week. Level one is the facts she counts most, a few at a time; level two takes a fact from the "know it" pile and builds its answer in coins, trading ten ones for a ten out loud; level three talks a whole two-digit-by-one-digit problem through with the coins on the table, carrying by trading. It steps up as the "work it out" pile shrinks and eases back when a new set of facts goes in. Nothing is marked wrong — a counted fact just goes back in the pile for tomorrow's five minutes. It is played by hand with cards and coins; it is not a game to switch on.
Needing to count out some facts at nine, and having multi-digit work wobble because of it, is ordinary, and for most children a few weeks of short daily fact practice is enough for the bigger procedures to steady. But if, after a long stretch of patient five-minute sessions, the facts still will not stick and every one is rebuilt from counting, or if numbers and amounts seem to slip and rearrange in ways the child cannot catch or correct, or if the same sharp effort shows up across many kinds of work and not only in maths, it can be worth describing what you see to someone whose work is understanding how children learn. A family doctor or an early-learning specialist can watch, ask questions, and tell you what they see. You do not need a label to have that conversation, and what you learn is yours to use however you choose.
A five-minute check before switching is one way to tell the programme from the one topic underneath it, chosen here because the trouble sat under the multiplication rather than in it. Another family would get at the same thing with a number line, finger patterns, or base-ten blocks instead of a coin jar. The parts worth keeping are the order: check the facts first, then place value, then one problem talked through; find the earliest wobble, not the latest; fix it with five minutes a day and stop on a win; and judge the programme only after, not before. The companion samples find-the-earliest-gap-stepping-stones.md and math-facts-fluency-dominoes.md carry the same two moves — find the first gap, make the facts automatic — further. The goal is to fix the right thing before changing everything. What you check with, and whether you switch in the end, is yours to choose.
No samples match that filter.
Six family pages, three iterations in: the plan for step four, with steps one to three visible as history. One side for the guide, one made for the learner. These six now live here; they used to be the showcase.
Adding fractions with different bottom numbers, through baseball.
A persuasive paragraph: claim, evidence, reasoning.
Checking for understanding in the moment; help that fades on purpose.
Meetings where everyone is heard, across three time zones.
Handling a live incident; the blameless review.
Spotting phone, text and email scams.
If you have run the homeschool skill on your own, you are invited to offer a generic version through a “Share a sample” issue. A person reviews each one before it appears here. A free GitHub account is all it needs.