SubjectNest resource library

Development draft · local review needed

Day 86 · A request is not an answerFoundation Design Tech · T2 W17–18 · Day 86 lesson

Prepare this lesson

Foundation / Design And Technologies / Term 2 / Weeks 17 18

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: Adapt the handoff folder to a care-request user while preserving unknown permission status; AC9TDEFK01 and AC9TDEFP01.

  1. Welcome · 3 min. A pretend class wants to ask a school contact about returning a teacher-provided paper picture to an agreed shelf, for a clearer shared table. No action is approved by the story.
  2. Notice source · 4 min. Read care request brief. The proposed question has a reason; SCHOOL CONTACT ANSWER is blank.
  3. Model · 5 min. “Our folder might carry the question to the right adult and later carry their real answer back. Until that happens, the answer is WAITING / NO ANSWER.” Do not let the child folder look like an authority notice.
  4. Child design talk · 7 min. Child says what the outside should tell the adult, what blank inside place is reserved for an answer, and who would be authorised to fill it. They may propose a large word/shape cue but not a made-up YES.
  5. Check/respond · 4 min. Record user, purpose, message locations and status. If child announces permission from the printed card, ask who actually answered and return to blank.
  6. Exit · 2 min. “We asked ; we still need .”