Skip to main content
Teacher Resources4 min read

Bee-Bot and floor robot lessons: move beyond pressing buttons

Use Bee-Bot and floor robots to teach prediction, sequences and debugging. Includes illustrative classroom tasks and a clear route to later build-and-code work.

Contents (6 sections)

A useful floor robot lesson asks children to predict a route, enter a sequence, test it and explain a change. Reaching the destination matters, but the explanation shows you more than the movement alone.

Bee-Bot is a programmable floor robot from TTS. This article offers illustrative teaching ideas for schools using Bee-Bot or a similar robot. It does not claim that Hyett Education supplies Bee-Bots in its workshops.

A yellow Bee-Bot floor robot on an illustrated activity mat.
A Bee-Bot floor robot on an activity mat.Photo: jungwhan cho. CC0 1.0.

Start with a route children can see

Use a clear starting position and destination on a surface suited to your robot. Check the manufacturer's current instructions for movement, charging and safe use. Test your mat before the lesson, including whether the robot moves reliably across it.

Begin with a short route and a consistent starting direction. Invite children to point along the route or use arrow cards before entering commands. That lets you separate planning from button pressing.

With Bee-Bot, clearing a previous sequence matters. Model resetting the robot and returning it to the same starting position before comparing attempts. Otherwise, an old command or a changed starting direction can obscure the reason for an unexpected result.

Teach turns as changes of direction

A turn changes the way the robot faces. It does not take the robot into the next square. Give children time to see that distinction before adding long routes.

The TTS Bee-Bot manual describes forward and backward movement of approximately 15 centimetres and right or left turns of approximately 90 degrees, subject to tolerances. Check your specific model and mat rather than expecting exact movement on every surface.

For an illustrative task, place a destination one forward move and one turn away, followed by another forward move. Ask children to show what the robot will face after the turn before running the whole sequence.

Make prediction part of each attempt

Before pressing GO, ask a child to show the predicted stopping point. Use a finger, a counter or a spare arrow, depending on the resources you have.

After the robot runs, compare the result with that prediction. If it stops elsewhere, return to the same start and look for the first point where the route differed. Change one command where possible, then test again.

This approach gives debugging a visible meaning. It also helps you distinguish a child who planned the route from one who reached the destination through repeated guesses.

For KS1 in England, these activities can support selected computing expectations around simple programs, prediction and debugging. See the DfE computing programme of study. They do not cover the whole subject.

A yellow Bee-Bot floor robot on a grid of numbered cards, with its packaging behind it.
A Bee-Bot on a numbered grid, one possible setting for a prediction task.Photo: “Bee - Bot.jpg”, María Laura Martín Gascón. CC BY-SA 4.0. Unmodified.

Use small-group roles that rotate

A planner can arrange the arrows, a programmer can enter them, and a checker can compare the result with the prediction. Rotate roles between attempts so each child has a chance to make decisions.

For children needing additional support, shorten the route, reduce the number of arrow choices or let them explain through demonstration. For children ready for another challenge, ask them to find a second route or identify a deliberately incorrect command.

Keep the learning question clear. Adding a story mat can give a route meaning, but too many destinations and instructions can make it harder to see what a child understands.

Connect floor robots to the next programming step

Progression comes from the concept you introduce, not simply from replacing one robot with another. Once children can explain a sequence and correct an error, you can consider activities involving a build, a motor or an input.

Hyett's Beginner STEMbotics workshop is for Years 1 to 6. Its current equipment includes LEGO Spike Essentials and WeDo 2.0, with icon-based and word-block coding. It offers a different build-and-program experience from a Bee-Bot lesson.

Nursery and Reception teachers considering construction and engineering should instead review Early Engineers Express. That distinction helps you choose a session for the actual cohort and learning need.

Check understanding before adding complexity

Ask children to explain what one command does, predict a short sequence and show how they would fix an error. Keep examples of the route and explanation that reveal their thinking.

If you need a broader purchasing comparison, the existing educational robot guide is a separate starting point. Verify specifications, support and current quotes with manufacturers before buying.

For a specialist build-and-code visit, compare the robotics workshop options and get a current school quote. Hyett brings the equipment specified for the booked format; the school supplies the agreed space, furniture and power.

Free STEM Resources for Your School

Get termly teaching ideas, funding alerts, and workshop updates.

No spam. Just one email per half term.

We will never sell or share your email with other organisations for their own marketing. You can unsubscribe at any time. Newsletter terms

Ready to Bring STEM to Your School?

Explore our curriculum-aligned workshops or get in touch to discuss your needs.