Driver
Keyboard. Builds the program.
For teachers
Every week runs the same way, with everything loaded in advance. No setup, no pack-down, no electronics knowledge required.
The session
Timings for both bands. It fits a standard period.
| Phase | Band A | Band B | What happens |
|---|---|---|---|
| Hook | 3 min | 3 min | Teacher runs the finished solution on the projector |
| Recall | 3 min | 4 min | One question about the previous session |
| Build | 15 min | 18 min | Students open the pre-loaded starter project |
| Code | 10 min | 15 min | Band A adapts the given blocks; Band B writes its own |
| Challenge | 5 min | 6 min | The scored run; times post to the leaderboard |
| Share and save | 4 min | 4 min | Reporters explain; projects auto-save |
| Total | 40 min | 50 min | Fits a standard period, no setup or pack-down |
The pack
The pair
Keyboard. Builds the program.
Reads the brief, watches the run, calls out what went wrong.
Assessment
Rated Emerging / Developing / Secure at sessions 4, 8, 12. The platform logs attempts and scores automatically, so the teacher rates rather than records.
Assembles a program from a given structure, progressing to building from scratch
Adapts given code, progressing to writing their own
Identifies why a run failed, progressing to fixing it independently
Fulfils their role in the pair, progressing to helping others