SubjectNest resource library

Development draft · local review needed

Day 157 · Check the step, fix the cueFoundation HASS · T4 W31–32 · Day 157 lesson

Prepare this lesson

Foundation / Hass / Term 4 / Weeks 31 32

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: Compare a practical message with its source and revise a bounded mistake without inferring use; AC9HSFS01, AC9HSFS02 and AC9HSFS04 partial. Actual route/codes: AC9HSFK03 conditional sourced-care explanation opportunity. Ready: P: C/F, first draft and broad revision flap; R: actual procedure/plan, willing responsible checker or approved exact words, permission scope.

Child product: Source-checked child cue with preserved first draft and one recorded correction/check gap.

  1. Open · 3 min. Ask “Does our cue say the step our source gives?” P: keep C visible. R: identify responsible checker; missing checker doesn't become approval.
  2. Read source · 4 min. P: read F and C exactly; F checks the helper's message, not automatically the child's new draft. R: read actual procedure, ask checker “Does this say our step? May we use it here?” Record actual words/time/scope or refusal/absence.
  3. Model · 5 min. P: show a deliberately unfinished cue, then compare its arrow/ASK text to C; don't alter C/F. R: demonstrate checking a blank label against the procedure, retaining first version.
  4. Child inquiry · 7 min. Play cue repair station: child points to each source-supported part, fixes one unclear/missing cue or confirms a supported part with its source tab. P: adult in paper Sol role checks words against C only; mark ROLE PLAY. R: exact checker correction/permission stays local; revise only within permitted scope. Ask “What did you fix? Who checked? Do we know anyone used it?”
  5. Check/respond · 4 min. If wording approval becomes observed use or all-user benefit, put use evidence in a separate blank field. F doesn't approve all later child messages.
  6. Exit · 2 min. Save draft/revision and actual help. Next move: use only the permitted step, record what really happens.