The running-total exit ticket was passed 4/4 on a fresh task (7-day sponsored walk), produced unprompted and then written by hand and photographed; the outstanding gap check was also closed. Ran ~14:05–14:55 against block 17. Starter, no notes, 3 set / 3 attempted / 3 unaided / 0 blank: jar = jar + 5 with jar holding 10 → "15"; predict a loop printing "go" inside and "done" after → "go go go done" exactly; speed >= 30 at 30/29 → "slow down / fine". Gap check 2 (even counter, missing counting line): "i don't know" twice to the open form and to "what should count be holding"; narrowed to a tally ("0 or 1 ticks?") → "1", then the line asked as "make count go up by 1" → "count = count + 1". Exit ticket, 4 marks: asked for a one-line plan first, she skipped the plan and typed the full program in one reply: cost = 0 / for i in range(1,8): / money = int(input()) / cost = cost + money / print(cost) — every line correct, no hint, first attempt. Told to write it by hand with a better name; photo arrived in the next reply. Handwritten copy: logic identical (cost = money + cost, print after the loop) but four transcription slips: Cost/cost mixed case, range[1,8] with square brackets, no colon after the for line, Print capitalised; name kept as cost despite the instruction. Marked 4/4 on logic as the AQA guidance allows; all four slips named to her. P04 moved notstarted → developing (single level). Nothing new opened: she asked to log at ~14:58 as the block ended. P05 while loops may open next session. PARENT: Friday's Code Lab run ('Add them up', 3/3) still not sent from the app; stale client_run_id lab-mtwz56ci issue still open.
Open while loops (P05) — the running-total exit ticket passed 4/4 by hand today. Starter, no notes, one question per message: values of total each time round a 3-line running-total loop; one P03 boundary at an unseen value with >; spot-the-error on `for i in range[1, 6]` (square brackets, no colon). Then P05 from zero: worked example (keep asking until the word is "stop") one line at a time with a say-back per line; two predictions (how many times does this loop run?); a production check with the condition line blank BEFORE Code Lab 'Until you say stop' (p05-stop), capped at 3 runs/10 min then teach. Ask for the one-line plan and wait for it before code. Next handwritten program: give a 3-item checklist (case, round brackets, colon) — a third mixed-case session demotes the P02 naming loose end. PARENT: Friday's Code Lab run still not sent; stale client_run_id lab-mtwz56ci still open.
| Topic | Name | Change | Evidence recorded |
|---|---|---|---|
| P04 | Not started → Developing | 22 Sep exit ticket, fresh 4-mark task (sponsored walk): cost = 0 / for i in range(1,8): / money = int(input()) / cost = cost + money / print(cost), unprompted, first attempt, no hint; then handwritten and photographed, same logic. 4/4 on logic. Gap check 2 (count = count + 1) after two narrowings. Starter 2/2 unaided. Developing bar met: taught 17–21 Sep, supported practice, exit ticket passed. Secure needs an independent retest on a different loop task later. | |
| P03 | Developing → Developing | Starter Q3, 22 Sep, no notes: speed >= 30 at 30/29 → "slow down" / "fine" unaided. Fifth correct boundary read of >=. Secure still needs an independent selection task with an unseen boundary in a later session. | |
| P02 | Secure → Secure | 22 Sep handwritten program: Cost on line 1, cost on lines 4–5, Print capitalised — mixed case by hand for the second session (18 Sep attempts 1–2, 22 Sep). Name cost kept for money raised despite being asked for total/raised; it says roughly what it holds. Typed version was consistently lower case. |