Sphero BOLT in the Classroom: A Teacher's First-Week Guide

Quick answer

Set up and charge the BOLTs before students arrive, then introduce one skill per day: driving, aiming, block coding, and a short build challenge. Keep groups to two or three students per robot and finish the week with a share-out so every student has touched the robot at least once.

The first week with Sphero BOLT sets the tone for everything that follows. If you spend it troubleshooting pairing and dead batteries, students learn that robots are frustrating. If you spend it on small, concrete wins, they learn that robots are something they can control.

This guide walks through a five-day plan you can run with one class or several. It assumes no prior robotics experience on your part, and it uses a few littleBits accessories where they genuinely extend what students can build.

Before Day One: Prepare the Robots

Unbox every BOLT, charge it fully, and label each robot and its charging cable with a number. Pair each robot to a classroom device once, then leave that pairing intact so students are not reconnecting every period. Test the Sphero Edu app on the devices students will actually use, not just your own tablet.

Decide how students will store robots between classes. A numbered bin or a charging cart prevents the two most common first-week problems: missing robots and dead batteries. If you are sharing BOLTs across grade levels, write the schedule on the bin lid.

• Charge overnight before the first lesson, not during it.
• Keep a spare charging cable per four robots.
• Write robot numbers on tape, not permanent marker.

Day 1: Introduce the Robot Without Screens

Hand out the BOLTs with the app closed. Let students roll them, tilt them, and watch the LED matrix. Ask them to describe what the robot does when it moves and what it cannot do. This builds curiosity before any instructions appear on a screen.

Close the lesson with one rule: the robot stays on the floor or a marked table zone. Students who understand the boundary on day one are far less likely to chase a BOLT across the room on day five.

• Use painter's tape to mark a driving zone on the floor.
• Have students name their robot and write the name on the bin.

Day 2: Teach Driving and Aiming

Open the Sphero Edu app and demonstrate the drive joystick, then show the aim function. Aiming is the step students skip, and it is the reason their robot drives in circles for the rest of the week. Make every student aim once before driving.

Run a simple relay: each group drives to a cone, aims, and returns. Keep turns short so no one waits more than two minutes. The goal is repetition, not precision.

• Aim the robot toward the same wall each time to make drift visible.
• Pair a confident student with a hesitant one rather than letting one student dominate.

Day 3: First Block Program

Move to the block canvas and build a program with three blocks: roll forward, wait, stop. Have students change one number and predict what happens before they run it. Prediction is what turns driving into coding.

If a program does nothing, check that the robot is connected before rewriting the blocks. Most first-week coding problems are connection problems, not logic problems.

• Save each group's program with the robot number in the filename.
• Ask students to say the sequence out loud before pressing start.

Day 4: Add a Physical Build

Give students something to move. littleBits accessories attach to builds and let you extend the robot's job beyond rolling. The littleBits bitShoes come in magnet, hook-and-loop, adhesive, or variety pack options, which makes them useful when students want to mount a cardboard flag, a cup, or a sensor holder to a base.

Keep the build small. A robot that pushes a ping pong ball across a line teaches more than an elaborate structure that falls apart before it moves.

• Pre-cut cardboard and tape so building time is not consumed by material hunting.
• Photograph each build before disassembly so groups can document their work.

Day 5: Share, Reflect, and Reset

Have each group demonstrate one thing their robot can do and one thing that failed. Naming a failure out loud normalizes iteration and gives you a clear picture of what to reteach next week.

End with a two-minute reset: robots on chargers, cables coiled, bins closed. A predictable reset routine is what keeps a classroom set usable through the whole term.

• Collect one sentence from each student about what they want the robot to do next.
• Note which groups needed the most help and seat them near you next lesson.

Your Five-Day First-Week Plan

1. Day 1: Hands on, screens off: Let students handle the BOLT and describe what it does before opening any app. Checkpoint: every student has touched the robot.
2. Day 2: Drive and aim: Teach the joystick and the aim function together, and require an aim before every drive. Checkpoint: students can aim at a target and hit it twice in a row.
3. Day 3: Build a three-block program: Roll, wait, stop. Change one value and predict the result before running. Checkpoint: each group can explain what their program does.
4. Day 4: Add a physical attachment: Use bitShoes or a simple cardboard mount so the robot pushes or carries something. Checkpoint: the build survives one full run.
5. Day 5: Demonstrate and reset: Each group shows one success and one failure, then returns robots to chargers. Checkpoint: robots are charged and stored for the next class.

Accessories That Help in Week One

• littleBits bitShoes: Available in Magnet, Hook & Loop, Adhesive, or a Variety Pack, these shoes let you attach modules to different surfaces and materials. They give students a quick way to mount a flag, cup, or holder onto a build without designing a custom bracket.
• littleBits w7 fork: The fork lets you connect a single Bit to as many as 3 others; if you place an input before the fork, it controls all 3 outputs at once, such as light, sound, and motion. Useful when a group wants one trigger to drive several outputs in a demonstration build.
• littleBits a19 Servo Hub: Compatible with the Hub Mount Servo, this hub lets you securely attach various materials to the servo to create rotating movements. A simple way to add a rotating element to a student build when a rolling robot is not enough.
• littleBits Invention Logs: Each log includes 19 pages of documentation support, an assessment rubric, and a feedback chart; each pack includes 10 logs. Gives you a ready-made way to capture student thinking during the first build week and assess it later.

A calm, structured first week does more for a Sphero BOLT program than any single lesson plan. Get the robots charged, teach aiming early, and keep the builds small enough to finish. By Friday, students will be ready for longer projects, and you will know exactly which groups need a slower start next week.