One 12-minute block daily. Days 11–15: Design and Technologies; Days 16–20: Digital Technologies. Use design and data mat. Product briefs are invented; no real account, personal dataset, purchase, cooking or mains electricity. A physical prototype must actually be made/tested for making claims. A visual program must actually run in a school-approved environment for implementation claims; paper arrows remain design evidence.
Day 11 · A sign for more than one reader · AC9TDE6P01, AC9TDE6K05
Kit: recycled card, thick pen, large-shape stickers. 0–2: Brief: guide visitors to a fictional quiet reading corner. 2–4: Identify user needs such as readable distance, simple words and non-colour-only cues. 4–10: Compare two sign sketches by legibility and material stability; select measurable criteria. 10–12: Check: an attractive sign may still fail at distance. Routes: sketch; movable symbols; spoken design brief. Response move: if criterion is “nice,” ask what a reader must do successfully. Home: notice a sign that works without colour alone.
Day 12 · Make, place, test, revise · AC9TDE6P03, AC9TDE6P04
Kit: Day 11 design, safe card/tape, marked viewing point, no personal names. 0–2: Confirm class space and accessibility. 2–4: Predict which label will be readable from two metres. 4–10: Make a small sign, place it with adult approval, ask a willing viewer to locate the corner from marked point, revise label/size once. 10–12: Check: record actual viewer result; a sketch alone is not a tested product. Routes: make card; position with support; conduct viewing test. Response move: if test merely asks “like it?”, use task success. Home: suggest a no-cost sign improvement at home.
Day 13 · Resource trade-off without green guesses · AC9TDE6K01, AC9TDE6P04
Kit: invented sign materials: reused thick card with short life, new plastic with long life; no lifecycle figures supplied. 0–2: List competing factors: durability, readability, resource use, replacement. 2–4: Predict a decision that depends on missing information. 4–10: Build a criteria matrix and mark claims requiring data (production impact, lifespan). 10–12: Check: “reused always best” and “plastic always best” both overreach. Routes: rank cards; diagram trade-off; oral conditional choice. Response move: turn absolute claim into “if…then…”. Home: ask what happens to a worn sign rather than buying one.
Day 14 · Plan a small collaborative revision · AC9TDE6P02, AC9TDE6P05
Kit: Day 12 viewer feedback: “arrow hidden behind a door”; card, tape, string. 0–2: Define the new problem. 2–4: Assign researcher, maker and tester flexibly. 4–10: Draw two placements, choose resources, plan a safe test from two approaches and a fallback if door movement hides sign. 10–12: Check: a plan includes roles, materials, sequence and criterion; no build is claimed today. Routes: floor-plan tiles; drawing; dictated work order. Response move: if tester missing, assign a real test step. Home: ask how a family checks that a label is visible.
Day 15 · Technologies Check A · AC9TDE6P01, AC9TDE6P04
Kit: new wheelchair-height notice brief in ASSESSMENT; do not assume one universal height. 0–2: Recall user, criterion and actual test. 2–4: Model a different low-stakes label. 4–10: Independent Tech A. 10–12: Check: staff uses private key; making evidence from Day 12 logged separately. Routes: annotate; write; dictate. Response move: ask whose access has not been tested. Home: name one user question before redesigning an object.
Day 16 · How a message crosses a network · AC9TDI6K02
Kit: original cards: device, local connection, network equipment, destination; no actual network settings. 0–2: Identify input device and a place data may travel. 2–4: Predict why two devices need a connection. 4–10: Route a fictional message card through a physical network model, marking where it could fail; compare to a local file that stays on one device. 10–12: Check: the cards simplify real network operation and do not reveal actual school topology. Routes: floor arrows; tabletop cards; verbal trace. Response move: if “internet stores everything,” distinguish transfer, storage and destination. Home: no network inspection.
Day 17 · A branching algorithm with a repeat · AC9TDI6P01, AC9TDI6P02
Kit: fictional lost-property classifier: item has name label? fragile? 0–2: State user story: school helper sorts safely. 2–4: Set criteria, including “unknown” option. 4–10: Design if/else branches and repeat for every item; trace three invented cases, including one that reaches no obvious branch. 10–12: Check: every path ends in a safe action; no real child names used. Routes: arrows; block words; oral trace. Response move: if branch fails, add a “refer to adult” outcome. Home: describe a safe if/then household routine.
Day 18 · Interface with minimal data · AC9TDI6P03, AC9TDI6P10
Kit: fictional classroom resource finder wireframe; no account. 0–2: User needs “find a quiet book.” 2–4: List useful inputs (topic, format) and unnecessary ones (address, birthday). 4–10: Sketch two screens with labels and a back route; peer tries the paper interface and reports one confusion. 10–12: Check: paper wireframe is design, not a built app. Routes: paper tiles; tactile button cards; audio-described layout. Response move: if personal data appear, remove and justify why. Home: discuss a permission request with an adult, no data shared.
Day 19 · Implement and test a visual quiz · AC9TDI6P05, AC9TDI6P06
Kit: teacher-prepared approved offline/managed blocks workspace with button input, score variable, if/else and repeat. 0–2: User story: an anonymous three-question recycling quiz. 2–4: Predict score after a correct and incorrect click. 4–10: Learner builds and runs the blocks, tests three input sequences, changes one rule and reruns; note observed output. With no device, trace a paper algorithm and mark plan only. 10–12: Check: implementation claim requires an actual run with input/variable/control. Routes: touch/mouse; keyboard/switch; pair programmer making a real change. Response move: if score is guessed, run a new case. Home: explain a bug without screenshots or account details.
Day 20 · Technologies Check B · AC9TDI6P02, AC9TDI6P05, AC9TDI6P10
Kit: fresh privacy/algorithm prompts in ASSESSMENT. 0–2: Recall branch, repetition and data minimisation. 2–4: Trace a different two-step example. 4–10: Independent Tech B. 10–12: Check: staff key separates a correct paper trace from an observed running program. Routes: draw arrows; oral; written. Response move: prepare a supervised run where implementation evidence is missing. Home: no public posting or new account required.