A turn changes heading without moving to another square

Mark the robot's square before giving a turn command. When the position stays fixed but the arrow changes direction, children can see why turn and move need separate definitions in the chosen notation.

To hand: A directional token and grid.

Mark the starting square. Turn in place. Execute a later forward command.

Trace the turn as its own instruction

A right turn changes heading before the next move.

Use a trace row for the turn itself. The unchanged position helps distinguish a rotation instruction from a movement instruction.

Did the square change during the turn? Use a large arrow.

Do not merge turn and move silently.

Make a turn visible in the record

In a fictional warehouse route, a robot needs to face a doorway before moving through it. Place its token in the middle of a grid, facing the top edge. Mark that starting square with a small ring. Agree that a right turn is a clockwise quarter rotation and a left turn is an anticlockwise quarter rotation. Neither command crosses a grid line.

Lay out right, forward, left. After the first command, ask for two observations: which square holds the token, and which edge its nose faces. Write or point to both answers. The position should still be the marked centre, with the nose facing right. After forward, the position changes; after left, the heading changes again while the new square remains occupied.

Use separate spaces on a recording strip for position and heading. Even a quick sketch of a square beside a tiny nose arrow is sufficient. The purpose is to preserve the state after a turn, which an ordinary route line can hide because it leaves no movement trail.

Compare a rotation with a side step

If someone interprets right as moving one square right, demonstrate both actions with two identical tokens. One rotates inside its square; the other crosses a boundary. Ask which matches the command key. Do not claim that a right arrow universally means rotation: this classroom model needs to declare its own notation.

A useful follow-up is two right turns from the original start. Learners can predict the heading before execution, then check that the position still has not changed. Avoid adding a movement command immediately if that would conceal what the turns themselves did.

Offer a large token with an easy-to-grip front marker, or let children direct an adult's movements. A learner may trace the square boundary or point to a heading card instead of manipulating anything. Keep the table orientation fixed during the comparison.

Conclude with an unexecuted turn card and ask what information it can change. A response that distinguishes heading from position shows more than simply naming left or right correctly during a familiar sequence.

Resources

• Human Robot Commands – Coding Without Screens Printable Game — Check the command conventions before using the sequence or debugging task.

Further reading

• CS Unplugged — Kidbots and algorithm activities
• Australian Curriculum Version 9 — Technologies overview

Read next

• Debug the first wrong state, not just the final destination
• Simplify a route map without deleting what the robot needs
• Go over there: let two readers expose the missing instruction

Explore Coding and computational thinking. Browse all teaching articles.