Sphero BOLT Educator Guide: How to Plan Your First Robotics Unit

Quick answer

Start with a standards-aligned curriculum, choose a course that matches your grade band, then set up your classroom and robots before you teach a single lesson. The Computer Science Foundations Educator Guide (Course 3) is the practical anchor for a first unit because it is designed to be taught in the classroom alongside BOLT, and almost all lessons are fully compatible with BOLT+. Plan your rollout in short weekly chunks so students spend more time coding than waiting on setup.

Your first robotics unit does not need to be complicated, but it does need a clear sequence. The biggest mistake teachers make is jumping straight into robot activities before deciding what students should know by the end of the unit. The second biggest mistake is underestimating setup time on day one.

This guide walks through a repeatable process: choose your curriculum, prepare the classroom, teach the first lessons, and adjust as you go. It uses the Computer Science Foundations Educator Guide (Course 3) as the planning spine, with a few optional accessories that make classroom management easier.

Step 1: Choose the right course for your grade band

Before you touch a robot, decide what your students should be able to do by the end of the unit. Computer Science Foundations is a supplemental, standards-aligned curriculum designed to be taught in the classroom alongside BOLT, and almost all lessons are fully compatible with BOLT+. Course 3 is written so students develop complex programs with the Block Canvas and rewrite simple block programs in JavaScript, which makes it a strong fit if your students already have some block-coding experience.

If your class is brand new to coding, do not start with Course 3 just because it looks more advanced. Match the course to what students can already do, then let the robot lessons stretch them. The guide gives you the standards alignment and lesson sequence; your job is to decide how much time you can realistically give each lesson.

• Checkpoint: write down one learning objective per week before you plan any robot time.
• Common mistake: buying a full classroom set of robots before you have read the curriculum scope and sequence.

Step 2: Set up the classroom and robots before day one

BOLT classroom setup goes faster when you treat it like a lab, not a toy shelf. Charge every robot the day before, label each one with a number, and decide where robots live between lessons. If students share devices, assign a robot number to each group so accountability is built in from the start.

The Maze & Grid Code Mat is a double-sided mat that is great for honing skills, strategizing, and diving into programming challenges. One side provides the official competition field size for BOLT/BOLT+ in The Sphero Global Challenge, so it doubles as a practice surface and a competition-ready field. If you plan to run a class challenge at the end of the unit, set the mat out early so students get comfortable with the grid.

Also decide your repair plan before something breaks. The 2 Year Product Repair under $1,000.00 (ACC + PREPAID) plan covers repair needs for up to two years from the service start date and includes Accidental Damage from Handling plus prepaid shipping. For a classroom, that is less about fear and more about keeping the unit moving when a robot takes a tumble.

• Checkpoint: run a five-minute robot check with each group before the first real lesson.
• Common mistake: waiting until lesson one to discover half your robots are not charged.

Step 3: Teach the first lesson as a routine, not a race

The first lesson should establish how your classroom runs: how robots are distributed, how students pair up, and how you signal a stop. Teaching coding with BOLT works best when students get a predictable loop of instruction, practice, and reflection. Keep the first coding task small enough that every group finishes and can explain what their program does.

Use the educator guide to keep the sequence honest. The lessons are designed to build, so skipping ahead to the fun challenge before students understand the blocks usually backfires. If a lesson runs long, cut the extension activity rather than the core task.

• Checkpoint: every group can describe their program in one sentence before cleanup.
• Common mistake: letting the fastest group set the pace for the whole class.

Step 4: Build in a challenge week with a clear goal

Once students can write and run a simple program, add a challenge that uses the grid. A maze or grid challenge gives students a reason to debug and iterate instead of just following steps. The Maze & Grid Code Mat supports this well because the grid gives a shared reference point for distance, turns, and strategy.

Keep the challenge rules short: one goal, one time limit, and one required element such as a loop or a sensor. If you have competition-minded students, the official competition field size on one side of the mat helps them practice on the same layout used in The Sphero Global Challenge.

• Checkpoint: students can explain what they changed and why after a failed attempt.
• Common mistake: making the challenge so complex that only one group finishes.

Step 5: Plan for repair, replacement, and the unexpected

Robots in a classroom take more wear than robots in a demo. Decide in advance how you will handle a cracked shell, a lost accessory, or a robot that stops charging. The 2 Year Product Repair under $2,000.00 (ACC + PREPAID) plan provides two years of product repair coverage for eligible Sphero items valued under $2,000.00 and includes Accidental Damage from Handling protection plus prepaid shipping for repairs.

If your unit includes littleBits components, the littleBits w29 perf is a standard 0.1-inch perfboard with a VCC and ground bus connected to bitSnap connectors, which makes it a quick way to prototype a circuit for a brand-new Bit. The littleBits w10 inverter is a logic Bit that sends out the opposite of whatever it receives, so it is useful when you want a button that turns things off instead of on. Neither is required for a BOLT unit, but both are handy if you run a circuits extension.

• Checkpoint: keep a simple log of which robot numbers needed service and when.
• Common mistake: waiting until the end of the unit to report a broken robot.

Your first-week rollout checklist

1. Day 1: Set expectations and hand out robots: Introduce the routine for distribution, pairing, and cleanup before any coding task. Give each group a robot number and a job. Checkpoint: every student knows where to return the robot.
2. Day 2: Run the first guided lesson: Use the educator guide lesson as written, even if it feels simple. The goal is a working program and a clear explanation, not speed. Checkpoint: each group can run their program twice in a row.
3. Day 3: Add a small debugging task: Give students a program with one error and ask them to find and fix it. This builds the habit of reading code before changing it. Checkpoint: students can name the block that caused the problem.
4. Day 4: Introduce the grid or maze: Lay out the Maze & Grid Code Mat and give a short challenge with one clear goal, such as reaching a square in a set number of moves. Checkpoint: every group attempts the challenge at least twice.
5. Day 5: Reflect and plan the next cycle: Ask students what was hardest and what they would change. Use their answers to decide whether to repeat a concept or move forward in the guide. Checkpoint: you leave the week with a written plan for the next five lessons.

Products that support a first BOLT unit

• Computer Science Foundations Educator Guide (Course 3): Computer Science Foundations is a supplemental, standards-aligned curriculum designed to be taught in the classroom alongside BOLT, and almost all lessons are fully compatible with BOLT+. By the end of Course 3, students develop complex programs with the Block Canvas and rewrite simple block programs in JavaScript. It gives you a ready sequence and standards alignment so you spend planning time on pacing instead of building lessons from scratch.
• Maze & Grid Code Mat: This double-sided mat is great for honing skills, strategizing, and diving into programming challenges. One side provides the official competition field size for BOLT/BOLT+ in The Sphero Global Challenge. It turns practice into a shared grid, which makes distance and turn-based coding easier to teach and easier to assess.
• 2 Year Product Repair under $1,000.00 (ACC + PREPAID): Covers repair needs for up to two years from the service start date, applies to products valued under $1,000.00, and includes Accidental Damage from Handling plus prepaid shipping for repairs. Classroom robots get dropped and bumped, so a repair plan keeps a unit from stalling when hardware needs service.

A first robotics unit works when the curriculum leads and the hardware supports it. Pick the course that matches your students, set up the room before day one, and keep each week small enough to finish. The Computer Science Foundations Educator Guide (Course 3) gives you the sequence, and a few practical accessories make the classroom side easier to manage.