SubjectNest resource library

Development draft · local review needed

Day 48 · Revise a boundary for a reasonFoundation Design Tech · T1 W9–10 · Day 48 lesson

Prepare this lesson

Foundation / Design And Technologies / Term 1 / Weeks 09 10

Part of the full two-week lesson sequence. Check the pack guide and taught point before teaching.

Open for this lesson: Pack guide · Sources and materials · Worked swaps · Fresh learner checks · Aids and text routes.

Download full sequence

Teacher copy: This page may include teaching prompts or answer keys. Answer keys in this public library can be viewed by anyone. Give learners a clean prompt, use checks as formative evidence, and change a case locally when prior access matters.

Learner choices

Target/codes: Evaluate a design against actual evidence or a named unknown and propose a specific change; AC9TDEFP01.

  1. Welcome · 3 min. A card moving is useful information about one setup, not a wrong child answer.
  2. Read source · 4 min. Reopen the child's own Day 47 record. If there was no trial, use the blank revision mat and keep result NOT TRIED.
  3. Model · 5 min. Say explicitly as a hypothetical: “If a card crossed the line, I might draw a wider box or place it farther from the boundary; then I would check again.” A thicker printed line is not proven to stop a physical card.
  4. Child response · 7 min. Children propose one change to zone width, label position, border or card placement. Connect the change to an observed problem or untested question. With fresh local approval, a second real try gets a new record; otherwise remain a proposal.
  5. Check/respond · 4 min. Record evidence/unknown → proposed change → next check. If only decoration changes, ask how it serves the stated viewer/source purpose.
  6. Exit · 2 min. “I saw/was told , so I would ,” or “I still need to find out ___.”