Game Play Reflection

Overview

In this final lesson of “Fast Forces: Play and Learn”, students will play one another’s force games, record performance data, and reflect on how their predictions matched (or differed from) what actually happened. They will use representations (tables/graphs) to identify patterns linked to forces.

Learning intentions

• Students will analyse data from gameplay to compare predicted and actual outcomes.
• Students will use tables and a simple column graph to show patterns in results.
• Students will explain findings using science vocabulary related to forces and motion.

Success criteria

• I can record results from gameplay in a table and use them to make a column graph.
• I can describe patterns I notice in the results (for example, “when we changed ___, the outcome changed”).
• I can explain how the results connect to forces (push/pull/friction/impact) and motion.
• I can compare my prediction with the actual outcome and suggest why they might differ.

Curriculum links

• AC9S3I04 — construct and use representations (tables and simple column graphs) to organise data, show simple relationships, and identify patterns.
• AC9S3I05 — compare findings, consider investigation fairness, identify questions for further investigation, and draw conclusions.
• AC9S3I06 — write and create texts to communicate findings and ideas using scientific vocabulary.
• AC9S3I01 — pose questions and make predictions based on observations (review from earlier lessons to compare prediction vs outcome).

Lesson structure (60 minutes)

1. 0–5 min · Setup and focus. Teacher explains: “Today you will test classmates’ games, collect performance data, and reflect using evidence.” Students gather game materials and get their recording sheets.

2. 5–12 min · Quick safety + fairness reminders. Teacher revisits what makes an investigation fair (same run method, same starting position, same time/attempts). Students repeat the fairness checklist and identify one fairness factor they will watch for.

3. 12–30 min · Game play rotation (data collection). Teacher rotates groups between 3 short game stations (each created in earlier lessons) and sets a timer for attempts. Students play each classmate’s game and record results (for example: points scored, distance travelled, number of successes, or time taken) for each version/rule the game tests.

4. 30–37 min · Consolidate data into tables. Teacher models how to transfer rough notes into a clean table (same categories, clear labels). Students complete their tables for each game version (including totals/averages if used in the game instructions).

5. 37–48 min · Make a simple column graph. Teacher demonstrates drawing a column graph using two categories (for example: “Version A vs Version B” or “with/without an extra push”). Students create a column graph that matches their table and choose an appropriate title.

6. 48–55 min · Reflection: prediction vs actual. Teacher prompts: “What did you predict would happen? What actually happened? Use your graph to find patterns.” Students write a short reflection (3–5 sentences) and complete a “Pattern → Explanation → Evidence” organiser.

7. 55–60 min · Share-out and exit check. Teacher asks each student to share one pattern from their graph and one force-related explanation. Students complete a quick exit ticket: “My prediction was ___ because ___; the evidence shows ___.”

Key vocabulary

• force
• push
• pull
• motion
• speed
• friction
• impact
• evidence
• data
• pattern
• prediction
• conclusion
• fair test
• column graph
• table

Resources

• Student game stations (materials produced across the unit)
• Timer and timer display (visible)
• Recording sheets for each station (table template with labelled columns)
• Plain table/graph paper or pre-made graph templates
• Clipboards or hard-backed boards for recording
• Scissors and glue/tape for graphing if needed
• Scientific vocabulary word bank on the wall/board
• Reflection organiser (Pattern → Explanation → Evidence)
• Exit ticket slips

Assessment

• Formative: teacher checks tables during the “Consolidate data” step for correct headings/values and legibility.
• Formative: teacher listens during share-out for use of scientific vocabulary and whether explanations link to the graph.
• Exit ticket: compare prediction vs actual and identify one pattern supported by evidence.

Differentiation

• Support: provide sentence starters for reflection (for example “I predicted that… because…”, “The results show…”, “This could be because…”).
• Support: offer graph templates with fixed axes labels to reduce drawing load.
• Extension: students can add a “What next?” question (for example, “Would the outcome change if we increased the push amount?”) and suggest how to test it fairly.
• EAL/SEN: use visuals (icons for push/pull/friction) and allow oral rehearsal before writing; pair students strategically for gameplay roles (recorder, timekeeper, player).

Answer sheet (teacher use)

Use to mark the exit ticket and quick reflection organiser.

• Exit ticket expected elements:
• Prediction statement (correctly indicates whether outcome matched or differed).
• Evidence from the graph/table (mentions at least one category and its result trend).
• Force link (uses at least one force term: push/pull/friction/impact).
• Fairness mention (one fairness factor, such as same starting point or same number of attempts), if applicable.

Reflection organiser (success criteria indicators)

• Pattern: identifies a clear trend from the column graph (e.g., “Version B was higher/lower than Version A”).
• Explanation: connects trend to forces (e.g., “More friction slowed the motion”, “A stronger push increased speed”).
• Evidence: refers to at least one data value or comparison from the table/graph.