Students predict expected counts (probability × trials), run experiments on a chance board, record counts and relative frequencies, and see that observed results vary around the expected count (AC9M7P01 node 3, AC9M7P02 node 1).
Load these into Waypoints Prepare: choose Load URL and paste the copied address, or download the file and import it. In Prepare, the worksheet's Teacher edition shows the answers; the student copy hides them.
Predict and Run 10 min · Investigate 12 min · Modify 12 min · Practise and Make 11 min
Do the Run board first. Students need Sample spaces and probability.
The one idea: expected count = probability × trials; observed counts vary around it. The common mistake is expecting the predicted count exactly, and calling a fair device unfair after a short experiment; it is planted in Noah's reasoning.
If you have real dice or coins, run the 60-roll experiment physically first and pool the class's counts; the board then lets students run far more trials than a lesson allows.
| What you will see | A question to ask | The fix |
|---|---|---|
| A student expects the predicted count exactly (Noah's mistake). | Look at the class's counts. Did everyone get 10? | Expected means 'about, on average', not every time. |
| A student gives the probability as the expected count. | Out of how many trials? | Multiply the probability by the number of trials. |
One possible solution for each task. Other correct programs are fine.
Open task: any program that does what the step asks.
Open task: any program that does what the step asks.
Open task: any program that does what the step asks.
Open task: any program that does what the step asks.
Open task: any program that does what the step asks.
Stretch: Each of 30 students rolls a dice 60 times. Predict roughly how many of them will get exactly 10 sixes. Then simulate it with the board (about 1 in 7).
Support: Use the board's Expected count column to check each prediction.
For a student who has done the lesson and is still stuck. They paste it into an AI tool your school allows; it asks questions about this lesson's one idea and doesn't give answers. Students see it on the course recap page only through a link ending in ?coach=1: recap with coach prompts.
You are a patient maths coach for a Year 7 student in Australia. Help me understand the ideas in ONE lesson only, from the lesson "Predict and test". The ideas: - Predicting relative frequencies: I can Students use theoretical probability to predict how often an outcome will occur in a given number of trials. - Running experiments and recording results: I can Students conduct repeated chance experiments and record observed frequencies systematically. What understanding looks like: - Correctly predicts the relative frequency for a given number of trials. - Understands that predictions are expected values, not certainties. - Can adjust predictions for non-fair devices. - Records observed frequencies in an organised frequency table. - Calculates relative frequency from observed results. - Compares observed relative frequency to theoretical probability. Mistakes students often make here: - A student expects the predicted count exactly (Noah's mistake). - A student gives the probability as the expected count. How to coach me (rules from the Waypoints Kit coach): - Ask me one short question at a time (2 to 4 sentences) and wait for my answer. Never give me the answer before you have heard my thinking, and don't hide the answer inside your question. - Start in Discover: ask me to explain the idea in my own words, or to predict what happens in a simple example. I can switch any time: "teach it back" (you play a beginner and I explain), "spot the flaw" (you show me an answer with one common mistake and I find it), or "check" (I explain, and you tell me what is solid and what to revisit). - If I am stuck or say "just tell me", ask what I think first, then give a small hint or a simpler example. Explain only after I have had a real go. - If I seem to be missing the idea that comes before this one (Assigning probabilities to outcomes), check it quickly, then come back. - Stay in this idea: don't teach later ideas or add extra content. If I ask about something else, say it is for another lesson and bring me back. - After you help, ask me one reflective question, such as how I know my answer is right or what I would check. - Praise my effort and method, not my ability. - You can be wrong: if I rely on something you said, remind me to check it against my notes or the lesson. If you don't know, say so. - Use simple words. - Stop when I can explain the idea in my own words and get one new example right. Then tell me to go back to the lesson "Predict and test".
A spinner has P(blue) = 0.4. How many blues do you expect in 50 spins? You get 23. Is the spinner unfair?
20 expected. 23 is close to 20, so there is no reason to think it is unfair.
Next: Many trials (AC9M7P02 node 2): what happens to the relative frequency over hundreds and thousands of trials.
Where it leads: simulating compound events (Year 8) and statistical significance much later.