Computing is the one subject where the technology is also the content, and that changes how the grid reads. Writing a Scratch quiz or a Python Magic 8-ball program is Creative, but it is Creative Replace: coding is what the lesson was always going to be.

A lot of good computing teaching is about reading code before writing it. Year 8 trace tables, Parsons puzzles with one distractor line, and predict, run and check in Replit all sit in Interactive Replace. Put the class's pseudocode-to-Python translations side by side on a Padlet, or have Year 9 count comparisons in three search algorithms and re-vote on which is most efficient, and the teacher can see the reasoning as it happens. That is Interactive Amplify.

Transform here often means putting the machine itself under test. Year 9 check Gemini's phishing verdicts on twelve fictional emails against the evidence. Year 10 test Copilot-written Python functions against their own edge cases.

The lessons run from a Year 3 Bee-Bot route to a Year 13 line-by-line code review.

Creative Amplify

Each child programs their own ScratchJr version of Aesop's race, setting speeds and a sleep for the hare, then tests and debugs it until the tortoise crosses the line first.

Read the lesson and why it sits here →

Creative Replace

Grade 3 Scratch character that dances, changes colour and reacts to key presses

Grade 3 (Year 4, age 8 to 9) · 45 min · 1 device per child

Creative Replace

Each child programs a Scratch character of their choice to dance in a loop, change colour and jump when the space key is pressed.

Read the lesson and why it sits here →

Grade 4 Scratch quiz on the Anglo-Saxons with a sprite that reacts to answers

Grade 4 (Year 5, age 9 to 10) · 50 min · 1 device per child

Creative Replace

Each child builds a three-question Scratch quiz about the Anglo-Saxons, using if-then-else so the sprite reacts to right and wrong answers and keeps a score.

Read the lesson and why it sits here →

Grade 5 junction traffic lights with a pedestrian button, coded on a micro:bit

Grade 5 (Year 6, age 10 to 11) · 60 min · 1 micro:bit and laptop per pair

Creative Replace

Pairs clip red, amber and green LEDs to a micro:bit and code the UK traffic-light sequence, with a button that brings in a pedestrian phase.

Read the lesson and why it sits here →

Grade 6 Scratch story with two characters and timed dialogue

Grade 6 (Year 7, age 11 to 12) · 50 min · 1 device per student

Creative Replace

Each student programs a short Scratch story in which two characters take turns to speak across two scenes.

Read the lesson and why it sits here →

Grade 7 robot character drawn from p5.js shape commands on a 400 by 400 canvas

Grade 7 (Year 8, age 12 to 13) · 50 min · 1 device per student

Creative Replace

Students plan a robot on the squared page of their book, then write p5.js commands such as rect(), ellipse() and fill() to draw it at the coordinates they planned.

Read the lesson and why it sits here →

Grade 7 rock, paper, scissors game coded on a micro:bit with pupil-designed icons

Grade 7 (Year 8, age 12 to 13) · 50 min · 1 device and 1 micro:bit per student

Creative Replace

Each student codes a micro:bit to show a random rock, paper or scissors icon of their own design when it is shaken, then plays a classmate.

Read the lesson and why it sits here →

Grade 9 Magic 8-ball program using a Python list and random.choice

Grade 9 (Year 10, age 14 to 15) · 50 min · 1 device per student

Creative Replace

Each student writes a Python program that answers a yes-or-no question with a random reply from a list of eight answers they wrote.

Read the lesson and why it sits here →

Creative Transform

Grade 9 cross-school pair programming of a number-guessing game in Replit

Grade 9 (Year 10, age 14 to 15) · 60 min · 1 device per pair

Creative Transform

Groups of four, two students from each of two schools, write one Python number-guessing game over a staff-hosted Teams call, passing the driver role between schools every ten minutes.

Read the lesson and why it sits here →

Interactive Amplify

Grade 7 hunting planted bugs in a remixed Scratch game and posting fixes to Padlet

Grade 7 (Year 8, age 12 to 13) · 50 min · 1 device per student

Interactive Amplify

Every student remixes a teacher-made Scratch game with two planted bugs, hunts them in their own copy and posts the cause and fix to a class Padlet wall that the teacher uses to run the debate.

Read the lesson and why it sits here →

Grade 7 trace and explain three pseudocode algorithms on a class Padlet

Grade 7 (Year 8, age 12 to 13) · 40 min · 1 device per student

Interactive Amplify

Each student traces one of three pseudocode snippets, posts a plain-English explanation of what it does to a class Padlet, and challenges classmates' explanations in the comments.

Read the lesson and why it sits here →

Students vote on which of three search algorithms is most efficient, test each in Scratch on growing lists, chart the class's comparison counts and vote again.

Read the lesson and why it sits here →

Grade 8 predict the next debugging move in an Edpuzzle screencast

Grade 8 (Year 9, age 13 to 14) · 45 min · 1 device per student

Interactive Amplify

Students watch the teacher's screencast of fixing a buggy Python program in Edpuzzle and must predict each next debugging step before the video continues.

Read the lesson and why it sits here →

Grade 9 predict, run and check: tracing eight Python snippets in Replit

Grade 9 (Year 10, age 14 to 15) · 50 min · 1 device per student

Interactive Amplify

Students write a prediction for each of eight short Python snippets, run it in a shared Replit project, and explain in one sentence any prediction that missed.

Read the lesson and why it sits here →

Grade 9 pseudocode-to-Python translations compared on a class Padlet

Grade 9 (Year 10, age 14 to 15) · 50 min · 1 device per student

Interactive Amplify

Students translate three OCR Exam Reference Language algorithms into Python, test them in Replit, and post them to Padlet so the teacher can compare contrasting versions.

Read the lesson and why it sits here →

Grade 10 bug hunt: syntax and logic errors in a Python average function

Grade 10 (Year 11, age 15 to 16) · 45 min · 1 device per student

Interactive Amplify

Students post bugs from a planted-error Python function to syntax and logic columns on Padlet, and the teacher targets the bug nobody found.

Read the lesson and why it sits here →

Grade 10 sticky-note critique of a small office LAN diagram in FigJam

Grade 10 (Year 11, age 15 to 16) · 45 min · 1 device per student

Interactive Amplify

Students place sticky notes on the weakest parts of an office network diagram in FigJam, then propose fixes and vote on which to make first.

Read the lesson and why it sits here →

Grade 11 comment trail on a trip-booking table: which dependencies break 2NF and 3NF

Grade 11 (Year 12, age 16 to 17) · 60 min · 1 device per student

Interactive Amplify

Students comment on the attributes of a trip-booking table that break 2NF or 3NF, and the plenary starts from the attributes the class disagrees on.

Read the lesson and why it sits here →

Grade 12 line-by-line code review of a practice library-loans program

Grade 12 (Year 13, age 17 to 18) · 60 min · 1 device per student

Interactive Amplify

Two named peers comment on each student's practice library-loans code in a shared Doc, and writers fix the flagged lines in Replit and rerun the teacher's tests.

Read the lesson and why it sits here →

Grade 12 vote: linear, binary or hash search for one lookup versus ten thousand

Grade 12 (Year 13, age 17 to 18) · 50 min · 1 device per student

Interactive Amplify

Students vote on the best search method for one lookup and for ten thousand lookups in an unsorted list, and the teacher uses the split to expose the cost of sorting.

Read the lesson and why it sits here →

Interactive Replace

Grade 2 groups program and debug a Bee-Bot route around a set floor course

Grade 2 (Year 3, age 7 to 8) · 40 min · 1 Bee-Bot per group of 3-4

Interactive Replace

Groups plan a sequence of moves to get a Bee-Bot from the start square to a target on a grid mat, predict the route, run it and fix any errors.

Read the lesson and why it sits here →

Grade 7 Parsons puzzles on Microsoft Whiteboard with one distractor line each

Grade 7 (Year 8, age 12 to 13) · 45 min · 1 device per pair

Interactive Replace

Pairs drag shuffled pseudocode lines into working order for three algorithms on a shared Microsoft Whiteboard, spotting the one line in each puzzle that belongs to no correct solution.

Read the lesson and why it sits here →

Grade 7 probing a provided micro:bit program in the MakeCode simulator

Grade 7 (Year 8, age 12 to 13) · 45 min · 1 device per pair

Interactive Replace

Pairs run a teacher-provided micro:bit program in the MakeCode simulator, press each virtual input, record what happens and test a prediction by swapping two event handlers.

Read the lesson and why it sits here →

Grade 7 trace tables for three short Python loops, filled in on a Google Doc

Grade 7 (Year 8, age 12 to 13) · 50 min · 1 device per student

Interactive Replace

Students trace three short Python programs line by line, recording each variable's value in trace tables in their own copy of a Google Doc, which the teacher marks for the next lesson.

Read the lesson and why it sits here →

Interactive Transform

Pairs tilt, turn and carry a school tablet while phyphox shows its accelerometer, magnetometer and pressure sensor live, to work out which sensor sits behind screen rotation, the compass, step counting and floor detection.

Read the lesson and why it sits here →

Students each ask Microsoft 365 Copilot Chat for five short character sketches of someone in an assigned job, log the names and pronouns in a class sheet, and compare the pooled results with published UK workforce figures.

Read the lesson and why it sits here →

Students judge twelve teacher-written emails as phishing or genuine, ask Gemini for its verdict and reasons, and test every reason against what the email actually shows.

Read the lesson and why it sits here →

Grade 9 testing Copilot-written Python functions against their own edge cases

Grade 9 (Year 10, age 14 to 15) · 50 min · 1 device per student

Interactive Transform

Students write test cases from a password rule, ask Copilot Chat for a password checker from a one-line brief, run its code against their tests in Replit and find out which rules it assumed.

Read the lesson and why it sits here →

Passive Replace

Grade 6 watch a Scratch tutorial on drawing a square with a repeat loop

Grade 6 (Year 7, age 11 to 12) · 45 min · Teacher device and projector

Passive Replace

Grade 6 watch a ten-minute tutorial on the board that builds a draw-a-square program with a repeat block, then predict in their books what other loops would draw.

Read the lesson and why it sits here →

Grade 7 follow an animated slide explanation of a data packet's route across the internet

Grade 7 (Year 8, age 12 to 13) · 45 min · Teacher device and projector

Passive Replace

The teacher runs an animated PowerPoint that follows one web page request from a school laptop to a server and back, while Grade 7 label a network diagram in their books.

Read the lesson and why it sits here →

Grade 8 read binary and hexadecimal worked examples before a data representation test

Grade 8 (Year 9, age 13 to 14) · 50 min · 1 device per student

Passive Replace

Grade 8 read a Google Doc of worked examples on binary, denary and hexadecimal conversion, doing each matching question in their books.

Read the lesson and why it sits here →

Passive Transform

Grade 12 watch Copilot answer one prompt five times to see how language models work

Grade 12 (Year 13, age 17 to 18) · 50 min · Teacher device and projector

Passive Transform

The teacher runs Copilot on the board, asking the same questions in fresh chats and following its cited links, while students record what changes and what holds, then connect it to how language models predict text.

Read the lesson and why it sits here →

Lessons that look like one cell but sit in another

Useful counter-examples when you are checking your own lesson placement on the PICRAT grid.

This page is one of a growing set of PICRAT examples by cell, subject and grade. Page maintained by Andy Perryer.