# Technologies choice menu · Years 5–6 band · Days 11–20

**Use:** One optional 12-minute block per day. Days 11–15 are Design and Technologies; Days 16–20 Digital Technologies. No child account, public post, real password or identifying data is required. Provide an approved visual coding environment before Day 19 if claiming `AC9TDI6P05`; a paper algorithm is planning only. Learners use [design/code mat](print/design-code-mat.pdf); the [text alternative](print/TEXT-ALTERNATIVES.md) works without printing.

### Day 11 · Carry a paper cup safely · AC9TDE6P01, AC9TDE6K05
**Kit:** empty paper cup, paper strips, tape, binder clips. 0–2: Define user: someone carrying a dry cup one metre. 2–4: Inspect materials for grip, flexibility and safe edges. 4–10: Draw two handles and choose one against criteria “holds cup, comfortable, minimal material.” 10–12: Check how a property influenced choice; a drawing is not a tested product. **Routes:** handle material; tactile compare; direct a scribe. **Next/home:** notice a handle and describe one design property, without buying supplies.

### Day 12 · Make and test a handle · AC9TDE6P03, AC9TDE6P04
**Kit:** Day 11 cup/strip/tape, dry bean bag or paper balls; no hot drink. 0–2: Revisit safe edges. 2–4: Agree one test load (three paper balls). 4–10: Build, lift low over a tray, record held/slipped and revise once. 10–12: Check against the original criterion and log actual test; a diagram alone does not meet making. **Routes:** build; steady/test with help; observe and document (evaluation evidence only). **Next/home:** sketch a redesign after asking what the user found difficult.

### Day 13 · More than one good choice · AC9TDE6K01, AC9TDE6P04
**Kit:** two fictional lunchbox closures: A easy to open but uses new plastic; B reused fabric but harder to clean. 0–2: Read case. 2–4: Choose criteria: access, durability, resource use. 4–10: Give each a reasoned trade-off; propose one improvement rather than a “perfect” score. 10–12: Check that sustainability is considered without unsupported lifecycle claims. **Routes:** matrix; oral debate; sketches. **Next/home:** compare two reusable containers by how easy *you* can open them.

### Day 14 · Plan a two-person build · AC9TDE6P05, AC9TDE6P02
**Kit:** fictional mini plant shade task; cardboard, string, tape, pencil. 0–2: State constraints: no sharp tools, five-minute build. 2–4: Assign measurer, maker, tester with access flexibility. 4–10: Draw an annotated plan, order steps and reserve material; rehearse one likely failure. 10–12: Check whether plan has user need, material and a test; no claim of finished build. **Routes:** timeline cards; labelled sketch; audio plan. **Next/home:** ask an adult what they would check before building a shelf.

### Day 15 · Review: design decision · AC9TDE6P01, AC9TDE6P04
**Kit:** fresh bag-strap brief in [ASSESSMENT](ASSESSMENT.md). 0–2: Revisit user/criterion/test. 2–4: Model an unrelated pencil-grip decision. 4–10: Independent Technologies Check A. 10–12: Staff sorts by user fit and measurable criterion; actual making from Days 12/14 is recorded separately. **Routes:** write; annotate; dictate. **Next/home:** find one item you would improve and say whose need it serves.

### Day 16 · Instructions need branches · AC9TDI6P01, AC9TDI6P02
**Kit:** fictional library return sorter: book is fiction or nonfiction; damaged or sound. 0–2: Read user story: library helper wants the correct box. 2–4: Predict why “put book away” is too vague. 4–10: Write a branching rule with two decisions and a repeat until no books remain; trace two fictional books. 10–12: Check every branch has an outcome. **Routes:** arrow cards; verbal trace; pseudocode. **Next/home:** explain a daily if/then choice, no private details.

### Day 17 · One bit, two states · AC9TDI6K03, AC9TDI6K04
**Kit:** four two-sided paper tiles marked 0/1. 0–2: State this is a simplified representation, not all digital data. 2–4: Predict how many patterns two tiles allow. 4–10: List 00, 01, 10, 11; use four tiles to encode an invented four-step light pattern. 10–12: Check that 0/1 represent two states, not “bad/good,” and that meaning needs an agreed code. **Routes:** flip tiles; tactile raised dots; dictate pattern. **Next/home:** notice one on/off control and describe its two states.

### Day 18 · Design an interface for a user · AC9TDI6P03, AC9TDI6P04
**Kit:** fictional “find a library book” screen brief; no device needed for *design*. 0–2: Name user and task. 2–4: Identify input and feedback. 4–10: Sketch two screens, one with text labels plus obvious controls; peer tests by pointing to “search” and “back.” Revise one label. 10–12: Check that a wireframe documents a design, not a working app. **Routes:** paper sketch; movable labelled tiles; describe screen order. **Next/home:** note one accessible label on a device you already use.

### Day 19 · Run a visual program · AC9TDI6P05, AC9TDI6P06
**Kit:** teacher-prepared approved offline/managed visual coding workspace with “on start,” variable `count`, button input and repeat block. 0–2: State user story: count up to three library returns. 2–4: Predict output for two clicks. 4–10: Learner assembles and **runs** blocks; tests zero, two and four clicks, then changes one block and reruns. 10–12: Check: Record observed screen output and mismatch. Without a device, trace the [mat](print/design-code-mat.pdf) and mark `planned only`, not implemented. **Routes:** mouse/touch; keyboard/switch with support; pair programmer who makes a real change. **Next/home:** describe a bug and correction without sharing a screenshot.

### Day 20 · Review: private by design · AC9TDI6P09, AC9TDI6P10
**Kit:** fictional app asking for full name, address and favourite book; no real accounts. 0–2: Recall a service needs only relevant data. 2–4: Ask what information is needed for a local book suggestion. 4–10: Independent Technologies Check B in [ASSESSMENT](ASSESSMENT.md). 10–12: Staff uses private key; do not collect actual passphrases or publish content. **Routes:** write; sort data cards; dictate. **Next/home:** with an adult, review one already-used app’s permission request; share no credentials.