Mini Minds Hub · Free printable

Code the Pirate Robot: Free Printable Worksheet for Year 2

  • ForYear 2
  • StageKey Stage 2
  • CostFree
  • FormatPrintable PDF
Download free PDF Open and print

Code the Pirate Robot is a free printable computing worksheet for Year 2 (ages 6 to 7). Children steer Rusty the pirate robot to the treasure using arrows. They write a simple code, check it and fix it if it goes wrong. It needs only a pencil, and page 2 gives the grown up notes, help ideas, a stretch task and the answers.

It comes from the Mini Minds Hub, the free library of printables from Jaques of London, the British games and toy company that has been making games for families since 1795. Print both pages, give page 1 to your child and keep page 2 for yourself. Black and white printing works well.

What is on the sheet

Children begin by matching the arrows, then move on to the grid. They draw a finger path from START to TREASURE before they write anything down. Then they write the shortest arrow code they can for Rusty. The sheet has a checklist to tick off, a table to fill in and numbered questions with space to answer. At the end, children act out their code by walking it on a floor grid.

  • A
  • B
  • C
  • D
  • Write the shortest arrow code that takes Rusty from START to TREASURE.
  • Act it out. Mark squares on the floor and walk your code.

Ways to bring the code to life

Floor grid

Mark squares on the floor with masking tape or chalk, or lay out sheets of paper. Your child walks the code one square for each arrow. This turns a drawing into a real journey.

Toy robot

Use a toy figure, a counter or a small building brick as Rusty. Move it across the printed grid as someone reads the arrows aloud, one at a time.

Arrow cards

Cut scrap paper into small cards and draw one arrow on each. Children lay the cards in a row to build a code, then swap cards around to fix mistakes.

Treasure hunt

Hide a small treat or toy in a room. Write arrow codes on paper that lead a friend there across a grid of floor tiles or paper squares.

What is an algorithm?

An algorithm is a set of steps, in the right order, that completes a task. A recipe is an algorithm. So are the steps for getting dressed or brushing teeth. In computing, an algorithm tells a machine exactly what to do. Rusty the robot cannot guess what you mean, so every arrow in the code matters, and the order of the arrows matters too.

Computers follow instructions exactly as they are written. If a program does the wrong thing, the fault is usually in the instructions, and programmers call that fault a bug. Finding and fixing a bug is called debugging. At Key Stage 1, children learn to write simple programs, test them and spot what has gone wrong. This sheet practises all of that on paper.

Did you know?

  • An algorithm is a list of steps in order. A recipe is a good example.
  • Computers do exactly what the instructions say, even if the instructions contain a mistake.
  • A mistake in a program is called a bug. Fixing it is called debugging.
  • Programmers test their code again and again to check that it works.
  • You can write an algorithm without a computer, using only paper and a pencil.

Skills and curriculum link

  • Writing algorithms
  • Finding bugs
  • Testing code
  • Following instructions in order
  • Using arrows for direction

Ideas for the helper

  • Say it aloudAsk your child to read each arrow as a word while they trace the path. Hearing the code helps them notice a step that looks wrong.
  • Ask, then showInstead of pointing out a mistake, ask, "What will Rusty do next?" Let your child follow the arrows and find the problem for themselves.
  • Try and try againTell your child that programmers rarely get a code right first time. Fixing a bug is part of the job, not a failure.
  • Link to real lifeTalk about everyday algorithms such as making toast or packing a school bag. Ask what would happen if two steps swapped places.

Key words

  • AlgorithmA set of steps in the right order that completes a task.
  • CodeInstructions written in a way a computer or robot can follow. Here, the code is made of arrows.
  • BugA mistake in a set of instructions that stops it working as planned.
  • DebugTo find a bug and fix it.
  • TestTo try something out to check whether it works.
  • SequenceThings that happen one after another in a set order.

How to use it

  1. Print both pages. Page 1 is for your child. Keep page 2, which has the notes and answers.
  2. Start by matching the arrows. Check that your child knows what each arrow tells Rusty to do.
  3. Look at the grid together. Ask your child to draw a finger path from START to TREASURE before writing any code.
  4. Let your child write the code, then follow it with a finger, one arrow at a time, to test it. Fix any bugs together.
  5. Check against page 2, then act the code out on a floor grid. Come back another day to try again.

Help, stretch and game ideas

If it feels too hard

Let your child move a toy along the grid one arrow at a time. Say each arrow aloud as the toy moves. If the toy ends up in the wrong place, look back along the code together and find where it first went wrong.

To stretch confident children

Ask your child to hide a new rock on the grid, then write a fresh code for a friend. The friend tests the code by following it. If it fails, they work together to find the bug and fix it.

Make it a game

One child is Rusty and stands on a floor grid. Another reads the code aloud, one arrow at a time. Rusty takes one step for each arrow. Swap roles, then try writing a code that is shorter.

Mistakes to watch for

Watch forA child counts the START square as a step, so Rusty ends up one square out.

Try thisPut a finger on START. Explain that the first arrow moves Rusty off it. Count only the squares Rusty moves into.

Watch forA child mixes up left and right and sends Rusty the wrong way.

Try thisCheck the arrows on the matching task again. Let your child hold a toy and turn it to face the direction before writing the arrow.

Watch forThe code works but is longer than it needs to be.

Try thisTrace the code with a finger and ask, "Is there a quicker way to get there?" Try crossing out steps that cancel each other out.

Talk about it

  • What does an algorithm do?
  • How did you decide which arrow to write first?
  • What happened when you tested your code? Did Rusty end up where you wanted?
  • Where was the bug, and how did you fix it?
  • How would you explain your code to a friend who has not seen the grid?
  • What would change if we hid a rock in a different place?

Take it off the page

Robot walk

Take turns to be the robot and the programmer. The programmer gives simple spoken instructions such as forward or turn. The robot follows them exactly, even if they are silly.

Sandwich algorithm

Write the steps for making a jam sandwich in order, then read them out. Ask a grown up to follow them exactly and see whether any step is missing.

Draw a map

Draw a simple map of a pretend island with a start and a treasure. Write an arrow code and ask someone to follow it with a finger.

Who it is for

Parents

Sit beside your child for the first go and let them lead. Ask them to explain their thinking as they follow each arrow. If something goes wrong, treat it as a bug to fix together, not as a mistake.

Teachers

Use it as a starter, a plenary, an early finisher task or a table activity. It needs no preparation beyond printing. It supports teaching on algorithms and debugging, and page 2 offers help and stretch ideas for mixed groups.

Home educators

Pair it with a floor grid, outdoor play and everyday talk about instructions. The sheet is free to print again for brothers and sisters, or for a quick revisit a few weeks later.

Where this fits in computing

Before this sheet, children benefit from following and giving simple instructions in everyday life, such as directions around the classroom or steps in a routine. Knowing left, right, forwards and backwards also helps them read the arrows with confidence.

After this, children can write longer codes and begin to plan ahead before they test them. Later they meet repeating steps and on screen programming tools. The habits practised here, writing exact steps, testing and fixing bugs, carry through all of them.

Questions parents and teachers ask

What age is Code the Pirate Robot for?

It is written for Year 2 (ages 6 to 7), in Key Stage 1. Older children who need a gentle start with algorithms can use it too, and the stretch idea on page 2 gives confident children more to do.

What will children practise?

Children practise writing and debugging simple arrow algorithms to steer a robot. They write a code, test it by following it, and fix any bugs they find. These are core ideas in Key Stage 1 computing.

Does my child need a computer or tablet?

No. It is a screen free printable that needs only paper and a pencil. A toy and a few floor squares are useful extras for acting out the code, but you can do without them.

What if my child finds it hard?

Let them move a toy along the grid one arrow at a time, saying each arrow aloud. If the toy goes wrong, look back through the code together. Page 2 has more help ideas for the grown up.

Is it free to use?

Yes. It is free to print for home and classroom use. You can print it again for brothers, sisters or a later revisit, and black and white printing works well.

Can teachers use it in class?

Yes. Teachers can use it as a starter, plenary, early finisher task, homework or table activity. It needs no preparation beyond printing, and page 2 supports mixed ability groups.

Can I use it for home education?

Yes. Home educators and tutors can use it alone or as part of a wider computing plan. It pairs well with floor games, books and everyday talk about instructions and directions.

Preview the full PDF

Made by Jaques of London, making games for families since 1795. A printable supports classroom learning and does not replace a teacher.

Download free PDF