Grades 2–7 · STEM & Computer Science
Unplugged computer science activities for Grades 2–7
Short answer: Strong unplugged computer science activities give students a precise rule set and a way to trace it by hand. For Grades 2–7 that means debugging grid commands, comparing linear and binary search on a sorted list of book numbers, calibrating a paper sensor with known reference values, and testing alert rules on a row of simulated readings.
- Grades2–7 (extends to Grade 8)
- DevicesNone required
- ConceptsSequencing, debugging, search, calibration, conditionals
- Per unit4 × 90-minute double lessons with answer keys
Unplugged lessons have a reputation as something to do when the laptops are out for repair. Done well, they are often the clearest way to teach the ideas underneath programming, because students have to slow down and execute every step themselves. Nobody can click Run and hope.
The units on this page are designed to work entirely on paper. Each one sets up a small system with exact rules, asks students to trace it, then changes one condition so they have to predict and test again.
Units for this topic
Unplugged Robot Debugging Cards
Lead unit for younger grades: grid commands, tracing and debugging with a length constraint.
Build a Library Search Algorithm
Linear versus binary search on a sorted list, with the sorted precondition made explicit.
Design a Water-Leak Detector
Teaches conditional alert rules and the trade-off between speed and false alarms.
Sensor Calibration with a Paper Microcontroller
Calibration with known references and pseudocode, tested on new readings.
Test an Evacuation Route with a Paper Simulation
Token-based queue modeling that also teaches the limits of a classroom simulation.
Accessible Game Design in Scratch
A next step into Scratch once students have planned behaviors on paper.
Debugging comes before coding
In Unplugged Robot Debugging Cards, students start at (1,1) on a grid with a goal at (4,3). The program is E E N N E, E increases x, N increases y, and (3,1) is blocked. Tracing reveals the first invalid move, and the task is to repair the program without making it longer.
That constraint matters. Students who just rewrite the route from scratch miss the point; the skill is finding the exact line that fails. Later cards ask them to name the first invalid instruction when W N is run from (0,0) on a grid with no negative coordinates, which introduces boundaries without any code at all.
- Grades 2–5
- Coordinates, sequences, first-invalid-move tracing
- Repairs judged by length and legality
Search algorithms with a stack of book numbers
Build a Library Search Algorithm uses a sorted list of IDs: 11, 19, 22, 38, 47, 55, 62. Students search for 55 by checking the middle remaining ID each time and counting comparisons, then compare that with checking one by one. A follow-up case gives an unsorted list and asks what must happen before binary search can work.
Physical cards make this lesson. Put the IDs face down on a table, and the halving becomes visible as students flip only the cards the algorithm allows.
Conditionals and thresholds without a microcontroller
Older students can handle systems with noise. Design a Water-Leak Detector gives readings of 0,0,1,0,1,1,1,0, where 1 means wet. Rule A alerts on one wet reading; Rule B needs two in a row. Students find the first alert under each rule and discuss what happens when the isolated wet minute was only a splash.
Sensor Calibration with a Paper Microcontroller works in the same spirit. A paper sensor reports 3, 13 and 23 for references 0, 10 and 20. Students write a correction in pseudocode, test it on a raw 18, and then check whether a reference of 30 reading 38 still fits the rule.
Matching activities to grade bands
The grid cards suit Grades 2–5 and work well as a first unplugged unit. The library search sits in Grades 4–7. Calibration, leak detection and the paper evacuation model in Test an Evacuation Route with a Paper Simulation fit Grades 5–8, where students can add totals and compare trade-offs.
If your class later moves to block coding, Accessible Game Design in Scratch is a natural next step, since it asks students to implement two behaviors they have already planned on paper.
A practical tip for any of these: keep a class trace table on the board. One row per step, with columns for position or value, the rule applied, and whether the step is legal. When students disagree about an answer, the table shows exactly where their traces split, and the discussion becomes about one step instead of the whole program. That habit carries straight into reading error messages once students start writing code.
A five-step sequence
-
Hand out the rule set
Give students the exact rules on a card: directions, sort order, thresholds or reference values.
-
Trace one example together
Use the slides to trace the first case aloud, writing each step in a table.
-
Let pairs trace and record
Pairs work through the worksheet cases, recording the step where something changes or fails.
-
Change one condition
Introduce a new blocked square, a missing target or a different threshold and ask for a prediction first.
-
Check and explain
Use the answer keys and learning check, asking students to explain why their trace works.
Common mix-ups and what to try
Unplugged activities are a lighter version of real computer science.
Tracing, debugging and algorithm comparison are core CS ideas. Doing them by hand often makes them clearer.
Binary search works on any list.
It needs a sorted list. The library unit includes an unsorted case to make that precondition stick.
An alert that fires faster is always better.
Faster rules can raise false alarms. The leak-detector unit has students weigh speed against reliability.
More STEM & Computer Science units
Related teaching guides
Frequently asked questions
Do I need robots or devices for these activities?
No. Every unit runs on paper with printed worksheets, cards and the slides. Scratch is optional in the related game unit.
Which unit is best for Grade 2 or 3?
The robot debugging cards. They use a small grid, four directions and short programs.
How much class time does a unit take?
Each is planned as four 90-minute double lessons, which many elementary teachers split into shorter sessions.
Do these connect to coding later?
Yes. Tracing, conditions and pseudocode carry directly into block or text coding, and the calibration unit asks for pseudocode already.
Can I adapt a unit to the CS standards my district uses?
Every resource is built around the curriculum you teach – and if something doesn't fit your standards, the TeachLessons Guarantee applies: we adapt it for you.
Where can I browse all STEM units?
The STEM and computer science collection lists all thirteen units, including accessibility and data labs.
Ready for your next lesson?
Print the first grid card, hide the laptops, and see how many students can find the first bad move without help.
View Unplugged Robot Debugging CardsInstant digital download. Every resource is built around the curriculum you teach – and if something doesn't fit your standards, the TeachLessons Guarantee applies: we adapt it for you.

