Mini Minds Hub · Free printable
Fairy Tale Flowchart Fix: Free Printable Worksheet for Year 6
- ForYear 6
- StageKey Stage 2
- CostFree
- FormatPrintable PDF
Fairy Tale Flowchart Fix is a computing worksheet for Year 6 (ages 10 to 11). Children follow a flowchart that retells a fairy tale, trace a path through it, then find three bugs and write the fixed instruction for each one. It suits children who can already follow numbered steps and are ready to explain why an algorithm goes wrong.
Before children hunt for bugs, ask them to trace the flowchart exactly as printed. They should use a finger, say each step number aloud and choose YES or NO at each question. The usual slip is following the story they already know instead of the arrows, so remind them that the flowchart is the only set of instructions.
What is on the sheet
Children read a flowchart of six numbered steps that tells a fairy tale. They trace the path to say which step comes next, then pick out the steps that ask a question. After that they hunt for three bugs. For each bug they write the step number and a fixed instruction. There is space to answer and lines for writing.
- 1 START. Climb up one leaf. Go to step 2.
- 2 Is Jack at the top? YES: go to step 1. NO: go to step 3.
- 3 Is the giant asleep? YES: go to step 4. NO: go to step 5.
- 4 Take the golden hen. Go to step 6.
- 5 Hide in the cupboard. Go to step 6.
- 6 Chop down the beanstalk. Then climb down. END.
- Jack is at step 3 and the giant is asleep. Which step comes next?
- Which two steps ask a question? Write both step numbers.
- Bug 1: write the step number and the fixed instruction.
- Bug 2: write the step number and the fixed instruction.
- Bug 3: write the step number and the fixed instruction.
A worked example: tracing a path
Here is a different flowchart. 1 START. Walk to the bridge. Go to step 2. 2 Is the troll under the bridge? YES: go to step 3. NO: go to step 4. 3 Offer the troll a riddle. Go to step 5. 4 Skip across the bridge. Go to step 5. 5 Wave goodbye. END. The troll is under the bridge. Which steps do you follow, in order?
This flowchart is different from the one on the sheet. It shows two ways to trace a path.
Method 1: finger and voice- Put a finger on step 1 and read it aloud.
- Go to step 2. It asks a question. The troll is under the bridge, so choose YES.
- YES says go to step 3. Read it, then follow its arrow to step 5.
- Stop at END.
- Write 1 on a strip of paper.
- At each step, write the next number the flowchart tells you to go to.
- At step 2, use the YES arrow, because the troll is there.
- Read your list back to check it matches the arrows.
How to trace and debug a flowchart
Start at START
Put a finger or counter on the first step. Do not look ahead. A flowchart only tells you the next step, one at a time.
Answer each question honestly
At a question step, decide YES or NO using the facts you have been given. Then follow only that arrow.
Check every arrow
A bug can hide in an arrow as well as in a sentence. Ask where each step sends you and whether that makes sense.
Fix and explain
Write the step number, the corrected instruction and one sentence saying why the old version did not work.
Algorithms, flowcharts and bugs
An algorithm is a set of clear steps that solves a problem or completes a task. A flowchart is one way to show an algorithm as a picture. Steps are joined by arrows, so you can see the order at a glance. Many flowcharts also include questions, where the path splits depending on the answer. Children meet this idea when they plan a program before they write it.
A bug is a mistake in an algorithm or program. Debugging means finding the mistake, working out why it causes a problem and putting it right. Programmers do this all the time, so it is a normal part of the work, not a sign of failure. The Key Stage 2 computing curriculum asks children to use logical reasoning to explain how simple algorithms work and to detect and correct errors.
Skills and curriculum link
- Reading a flowchart
- Tracing an algorithm
- Debugging
- Logical reasoning
- Explaining your thinking
Ideas that help with flowcharts
- Order mattersAn algorithm only works if its steps happen in a sensible order. Swapping two steps can change the whole result.
- Questions split the pathA step that asks a question usually has two ways out. Which way you go depends on the answer.
- Every step needs a way onEach step should tell you where to go next, until the flowchart reaches its end.
- Arrows are instructionsFollow the arrows exactly, even if you think you know what should happen. The computer only does what it is told.
Key words
- FlowchartA diagram that shows the steps of a task joined by arrows.
- AlgorithmA set of clear steps that gets a job done.
- BugA mistake in an algorithm or program.
- DebugFind a bug, work out why it is wrong and fix it.
- DecisionA step that asks a question and sends you down different paths depending on the answer.
- TraceFollow an algorithm step by step to see what it does.
How to use it
- Print both pages. Page 1 is for your child. Keep page 2, which has the notes and answers.
- Read the story aloud, then ask your child to trace the flowchart with a finger, saying each step number out loud.
- Let them work alone on the questions. Bugs can be found in any order.
- Check against page 2. Ask them to explain each fix in their own words. Accept any clear sentence that gives a sensible reason.
- Come back another day and ask them to explain the flowchart to someone else. Teaching it is a good test of understanding.
Help, stretch and game ideas
If it feels too hard
Let your child trace the path with a finger or a counter and say each step aloud before writing anything. Cover the steps they have not reached yet with a piece of paper, so they only see one instruction at a time.
To stretch confident children
Ask your child to add a new decision, such as the giant waking up, and draw the new flowchart. They should check every arrow, then swap with a friend who traces it and tries to find a bug.
Make it a game
One child acts as Jack. Another reads each step aloud and follows the printed flowchart exactly, even if the story seems odd. Jack does only what the reader says. Swap roles and see if anyone spots a problem.
Mistakes to watch for
Watch forA child follows the story they know, not the arrows on the page.
Try thisAsk them to point to the arrow they are following. Remind them that the flowchart is the only instruction.
Watch forA child finds a bug but only writes that it is wrong.
Try thisAsk what the step should say and why. Then write the step number and the new instruction.
Watch forA child writes a fixed instruction but forgets the step number.
Try thisDraw a box beside each bug with two parts, one for the number and one for the new instruction.
Talk about it
- Which step was the easiest to follow, and why?
- How can you tell that a step is a question?
- What would happen if two steps swapped places?
- How did you spot the first bug?
- Is there more than one way to fix a bug? Which fix is best?
- Where else do you follow steps in a fixed order, at home or at school?
Take it off the page
Flowchart for a morning
Draw a flowchart for getting ready for school. Include at least one question, such as whether it is raining. Ask someone at home to follow it exactly.
Human robot
One person gives step by step instructions to cross a room. The other follows them exactly. Fix any step that goes wrong.
Story flowchart
Choose a favourite fairy tale and turn the main events into a flowchart. Add one decision that changes the ending.
Who it is for
Parents
Sit beside your child for the first go and let them lead. Ask them to explain each fix aloud. Praise careful tracing and clear reasons, not only correct answers.
Teachers
Use it as a starter, plenary, early finisher task or table activity. It fits a unit on algorithms and debugging, and needs no preparation beyond printing. Page 2 gives support and stretch ideas for mixed ability groups.
Home educators
Print it as part of a wider computing plan. It pairs well with building simple instructions for a game or craft, and it needs only paper and a pencil. Use it again later for revision.
Where this fits in computing
Before this sheet, children learn that instructions must be precise and in the right order. They give and follow simple directions, and read short sequences of steps.
After it, children can move on to debugging programs on screen, such as in block based tools like Scratch. They can also plan their own algorithms with questions and repeated steps, then test them.
Questions parents and teachers ask
- What age is Fairy Tale Flowchart Fix for?
It is written for Year 6 (ages 10 to 11), in Key Stage 2. Younger confident children can try it with help, and older children can use it as revision of tracing and debugging.
- What will children practise?
They practise reading and tracing a simple flowchart, then finding and fixing errors and explaining their reasoning. These are core computing skills at Key Stage 2, and they need no computer.
- What is a bug in a flowchart?
A bug is a mistake in the instructions that stops the algorithm working properly. It might be a wrong arrow, a step in the wrong place or an instruction that does not make sense. Fixing it is called debugging.
- Do children need a computer for this?
No. It is a screen free activity that needs only paper and a pencil. It works well for quiet time at home or as a computing lesson in a classroom with no devices.
- What if my child cannot find the bugs?
Ask them to trace the path with a finger or counter and say each step aloud. Bugs usually show up when the path does not make sense. Page 2 has support ideas and the answers.
- Can teachers use it in class?
Yes. It works as a starter, plenary, early finisher task, homework or table activity. It needs no preparation beyond printing, and page 2 includes help and stretch ideas for mixed groups.
- Are the answers included?
Yes. Page 2 is for the grown up and includes the answers, notes on how to use the sheet, help for children who find it hard and a stretch idea. Keep it separate from page 1.
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.