A 90-Day Classroom Robotics Rollout Playbook

The failure mode described in Article 1 of this series — the class set that sits in a closet — almost always follows the same sequence: hardware arrives → it gets distributed → teachers try it with students → it is harder than expected → use declines → the kit gets put away. The entire failure chain can be interrupted at the second step. Hardware arrives → teachers develop competence and a plan → one classroom pilots → the district learns → it scales.

The difference between those two sequences is roughly 90 days and a deliberate rollout structure. This playbook provides that structure.

It is designed for a STEM coordinator, makerspace lead, or instructional technology director managing a new platform rollout in one school or one district cohort. The timeline assumes kits have been purchased and are physically on-site. It does not assume any particular platform.

Before Day 1: The Prerequisites

A 90-day rollout only works if three things are true before it starts.

Platform selection is finalized. The decision about which platform to deploy has already been made using criteria like those in Article 4 of this series. There is no point launching a rollout timeline while the purchasing decision is still open.

One pilot teacher is identified and willing. The pilot classroom model requires a specific teacher who has agreed to lead the pilot — not a department, not a grade team, but one person who is genuinely interested, has appropriate planning time, and is comfortable being observed and giving feedback. The pilot teacher does not need to be the most experienced teacher in the building; they need to be curious and communicative.

A program owner is assigned. The rollout coordinator who manages this 90-day process should be named before day one. This is typically the STEM coordinator or a lead makerspace teacher. If no one is explicitly assigned, the rollout will drift by Week 4 as competing priorities accumulate.

Days 1–21: Teacher Preparation (No Students Yet)

The single most important deviation from the typical "get the robots into classrooms" impulse is this: no student touches a robot until the pilot teacher has at least 6–8 hours of hands-on experience with the platform.

Week 1: Coordinator Unpacking and Inventory

Day 1–3: The program owner unpacks all kits, verifies inventory against the packing list, charges all units fully, and documents any missing or damaged items. This is not a delegation task — the program owner needs firsthand familiarity with the hardware before they can support teachers.

Day 3–5: The program owner completes the vendor's getting-started tutorials independently, including the coding environment, at least two complete activity sequences, and the teacher dashboard (if the platform has one). Document: which activities work as described, which require adaptation, and what questions arise.

Questions to answer during this phase:

• Does the app or browser environment work on the specific device model that will be used with students?
• Is Bluetooth pairing reliable at the density we'll need (e.g., 12–15 simultaneous connections)?
• What is the battery life per charge at active use?
• Are all curriculum materials accessible to a teacher without an account, or does account setup need to happen before PD?

Week 2: Pilot Teacher PD — Session 1

Format: Full PD day (6 hours), in-person. Vendor delivery preferred for this session, either in-person or via a live virtual facilitated session. A pre-recorded webinar is not a substitute.

Session objectives:

• Pilot teacher completes all hardware setup: pairing, app installation/login, charging
• Pilot teacher works through 3–4 complete activity sequences at student pace
• Pilot teacher identifies which activities fit their existing scope-and-sequence and which are supplemental
• Pilot teacher asks every question they have before students arrive — this session is explicitly designed for questions

Coordinator role: Participate alongside the pilot teacher. This is not the time to send an email. The coordinator needs firsthand knowledge of what the PD covered in order to support the teacher during the pilot.

Week 3: Curriculum Alignment and Lesson Planning

This week is teacher planning time. The pilot teacher, with coordinator support, maps the platform's activity library to the instructional unit where it will be deployed.

The output of this week is a written lesson plan document covering:

• Which unit in the existing curriculum does this support? (Not "enrichment time" — a specific unit with a specific standard)
• How many sessions, how long each?
• What is the learning objective for each session?
• How will students be grouped?
• What does a successful session look like? What does an unsuccessful session look like?
• What do students need to know or be able to do BEFORE the robot unit begins?

This lesson plan document becomes the evaluation instrument at Day 90. It is not optional.

Also this week: Confirm logistics. Does the cart fit through the classroom doorway? Is there adequate Wi-Fi signal in the classroom? Is the charging cart in a location accessible to the teacher without IT involvement? These details derail pilots at Week 4 if they are not resolved at Week 3.

Days 22–60: Single-Classroom Pilot

The pilot runs for approximately 6 weeks of instruction (acknowledging that school calendars are not clean 6-week blocks; adjust for holidays, standardized test weeks, and field trips when scheduling).

The Pilot Discipline

One classroom. The impulse to spread the robots around — to give every interested teacher a kit, to run the pilot in three classrooms simultaneously — undermines the learning purpose of the pilot. One classroom generates focused, specific data. Three classrooms generate noise.

The teacher observes and records. At the end of each session, the pilot teacher writes 3–5 sentences in a running log: what worked, what didn't, what they would do differently. This does not need to be formal; a shared Google Doc is sufficient. The coordinator reads the log weekly.

The coordinator visits at least twice. In-person observation of two pilot sessions — one early, one mid-pilot — allows the coordinator to see what the self-report log may not capture. Specifically: How much time is spent on logistics (pairing, troubleshooting) vs. learning? Are students on task? Is the activity pacing correct for this grade?

Measurement Checkpoints

End of Week 4 (Day 43): First checkpoint. The coordinator reviews the lesson log and asks the pilot teacher three questions:

1. Are we on track with the lesson plan?
2. Has anything in the activity design needed to change for this grade/class?
3. Is there anything that, if not fixed, will cause the second half of the pilot to fail?

If the answer to question 3 is "yes" — curriculum pacing is wrong, Bluetooth is unreliable, students are progressing much faster or slower than planned — adjust now, not at Day 90.

End of Week 6 (Day 57): Pilot concludes. Pilot teacher completes a structured reflection covering:

• Sessions completed vs. planned
• Average time-on-task per session (estimate)
• Student engagement (simple 1–5 scale, teacher rated)
• At least two things to keep, at least two things to change
• Overall recommendation: ready to scale, scale with modifications, or do not scale

This reflection document is shared with the building principal and, for district-level programs, with the superintendent's office. It is the evidence base for the scale decision.

Days 61–75: Reflection and Scale Decision

Analyzing Pilot Data

The program owner aggregates the pilot teacher's reflection, coordinator observation notes, and any student work samples into a brief program summary. This summary should answer four questions:

1. Was the program used? (Sessions completed vs. planned)
2. Did it work for teachers? (Teacher confidence, teacher recommendation)
3. Did it work for students? (Engagement rating, learning objective completion)
4. What would we change before scaling?

If the answers to questions 1–3 are broadly positive (not perfect — broadly positive), the program is ready to scale with the modifications identified in question 4.

If question 1 or question 2 is negative, scaling is premature. Diagnose the root cause before expanding. Common root causes at this stage:

• Curriculum-platform mismatch: the platform's activity library does not actually address the target standards
• Logistics friction: a device management or Bluetooth reliability issue that makes setup time eat into instruction time
• PD gap: the pilot teacher did not have adequate preparation for a specific aspect of the curriculum

Modifications Before Scale

Every successful pilot identifies modifications. This is expected and valuable. Common modifications at this stage:

• Adjusting session length estimates in the lesson plan template
• Creating a simplified pairing and setup checklist for students (reducing startup time from 10 minutes to 3)
• Reordering activities in the vendor curriculum to better match the school's existing sequence
• Identifying which activities should be whole-class demonstrations and which should be small-group exploration

Document the modifications explicitly. These become the institutional knowledge that makes the teacher-two rollout faster than the pilot.

Days 76–90: Scale Planning and Teacher-Two Onboarding

Selecting the Scale Cohort

For a single-school program, the scale decision is typically expanding from one teacher to two or three. For a district program, it may mean expanding from one school to two or four.

Select scale cohort teachers using the same criteria as the pilot teacher: genuinely interested, adequate planning time, comfortable with iterative learning. Do not assign teachers to the program who have not opted in. Reluctant adopters produce low utilization and often produce negative program data that makes it harder to sustain the program for the willing teachers.

PD for the Scale Cohort

The teacher-two PD is substantially faster than the pilot PD because the program owner now has a lesson plan template, a setup checklist, a tested activity sequence, and a documented set of known issues and fixes. What took 6 hours of vendor-delivered PD for the pilot can often be delivered in 3–4 hours by the program owner with the pilot teacher as co-facilitator.

The pilot teacher should be explicitly involved in training subsequent teachers. This serves two purposes: it validates the pilot teacher's expertise and investment, and it produces more practically grounded training than any vendor can provide.

PD session structure for scale cohort:

• 60 min: hardware familiarization and setup (led by pilot teacher)
• 60 min: curriculum walkthrough — activity sequence, learning objectives, common student questions (led by pilot teacher)
• 60 min: lesson planning with the template from the pilot (each teacher begins their own adaptation)
• 30 min: coordinator overview — utilization tracking, program owner contact, consumables/maintenance process

Establishing Program Infrastructure

By Day 90, the following infrastructure should be in place:

What Day 90 Should Look Like

At Day 90, a robotics program rollout that followed this playbook should have:

• One completed pilot with documented data (utilization, teacher reflection, learning outcomes)
• One to three additional teachers in onboarding or early instruction
• A written lesson plan template that any subsequent teacher can adapt in one planning session
• A program owner who has firsthand knowledge of the platform, the curriculum, and the institutional logistics
• A scheduled end-of-year program review

It should not have: all district teachers using the platform simultaneously, a formal announcement to parents about the "robotics program," or a presentation to the school board about learning outcomes. Those milestones come after the first full year of data — not at the end of a 90-day launch.

Sustainable programs earn their scale. The 90-day playbook builds the foundation. The first-year review justifies the expansion.

Before you select a vendor and sign a contract, review the questions and red flags every school buyer should bring to an RFP process — see The Education Robot Vendor RFP: Questions and Red Flags.