Help for Australian teachers choosing classroom robotics kits, linking them to Digital Technologies and running a program that lasts.
Guide

A sample ten-week robotics unit for primary classes

A sample ten-week robotics unit for Years 3 to 6 with weekly goals, activities, differentiation and assessment points you can adapt to your own kits.

This sample unit runs ten weeks of one lesson a week, about 50 minutes each, for Years 3 to 6: two weeks of unplugged algorithms, then sequences and debugging, loops and sensors, decisions, a two-week team challenge and a showcase. Adapt it to whatever kit your school has.

How do you use this sample unit?

The unit is a starting point to adapt. It assumes one lesson a week, groups of three, and one small programmable robot per group, either a floor robot or a small wheeled coding robot. If you have fewer robots, use rotating stations: one group programs while others plan on paper, build a course or test a second group’s code.

Each week below gives a goal, a main activity, the vocabulary to teach and the evidence to keep. The order follows the way Digital Technologies concepts build in Years 3 to 6, which you can check against how robotics links to Version 9. Copy content description codes from the official site when you add them to your own plan.

Before week one, do three things. Charge and test every robot. Mark out a course area on the floor with tape. Set up a folder, paper or digital, where each group keeps its plans and debugging notes. Those notes become the assessment evidence at the end.

A practical note on timing: a fifty-minute lesson loses time to packing out and packing up. If set-up and pack-up take ten minutes, students have forty minutes of hands-on time, and the class kit planner can show the effect on your timetable. Short, repeated routines help, so teach the pack-up routine in week one and practise it every lesson.

Weeks 1 and 2: unplugged algorithms and class robot rules

Goal: students can write and follow a precise list of steps, and know how to look after the robots.

Week 1 begins without a robot. The Digital Technologies Hub’s guide to teaching unplugged notes that much of the Digital Technologies curriculum can be introduced without devices. Students pair up on a taped grid. One student is the robot and the other gives instructions using only four commands: forward, back, turn left and turn right. The robot follows the commands exactly and does not guess. When the robot walks into a wall, the pair discusses which instruction was wrong. This shows that a computer follows an algorithm exactly as written.

Introduce the vocabulary: algorithm, sequence, bug, debug, test. Put the words on the wall and use them in every lesson.

Week 2 sets the class rules for robots and introduces the robot itself. Agree rules such as robots on the floor or on a table, never on a chair; two hands to carry; no pressing buttons unless it is your turn; and the roles of programmer, tester and recorder, which rotate each lesson. Let students explore the robot freely for ten minutes, then set a simple challenge, such as getting the robot from a start line to a cone.

Evidence to keep: a written algorithm from the unplugged task and a photograph of the class rules chart.

Weeks 3 and 4: sequences and debugging

Goal: students plan a sequence on paper, program it, test it and fix errors using a method.

Week 3: students plan a route to a target on the course, write the sequence as arrows or words, then enter it into the robot. Before they run it, they predict where the robot will end up and mark that spot with a sticky note. After the run, they compare. Predicting first makes students form a picture of what the program will do before they see the result, which is the habit later debugging depends on. It is also the first step of the PRIMM approach (Predict, Run, Investigate, Modify, Make) that the Hub describes on its teaching programming page.

Week 4: introduce the debugging log, a table with three columns: what I expected, what happened, what I changed. Give groups a program with a deliberate bug, such as a turn that is too large, and have them find and fix it. Then swap programs with another group, which tests whether instructions are clear enough for a stranger to follow.

Useful teacher questions: What did you expect? Which step do you think is wrong? How could you test just that step? Avoid fixing the bug for the group, because the learning is in the search.

Evidence to keep: the written plan, a photograph or screenshot of the program, and the first debugging log entries.

Weeks 5 and 6: loops and sensors

Goal: students use repetition to shorten a program, and use a sensor to give the robot information about its surroundings.

Week 5: students trace a square. First they write the long version, forward and turn repeated four times, then they rewrite it using a repeat. Count the blocks or lines in each version, and ask which is easier to change if the square must be bigger. Extend to a triangle or a hexagon, which uses angle calculations and links to Mathematics. If your floor robot has no repeat function, students write the loop on paper as “repeat 4 times: forward, turn”, then enter the long version, which shows why programming languages have repeats.

Week 6: introduce a sensor. If your robot has a distance, light or line sensor, set a task such as stopping before an obstacle or following a line. Students test the sensor with the robot held still and watch the readings change as they move a hand or card in front of it. Then they decide what reading should trigger a stop.

If your robot has no sensors, a floor robot can still support the idea of feedback through a human sensor: one student calls “stop” when the robot is a hand’s width from the wall, and the group discusses how a machine would know that.

Evidence to keep: a table of sensor readings, for example three readings at three distances, and a short explanation of the repeat used.

Week 7: decisions and branching

Goal: students write a program in which the robot does different things depending on a condition.

Start with an unplugged “if” game. Students walk along a line of tape and follow a rule: if the floor is blue, turn left; if it is red, keep going. Then move to the robot. A line-following robot is the classic example, with a rule such as: if the sensor sees the line, go forward; otherwise turn to find it.

Ask students to write their rule in plain English before they code it, in the form “If … then … otherwise …”. Many students find the code easier once the sentence is clear. Test with a course that has a gap or a corner, and discuss what happens when the condition is never met.

This is a good week for a mid-unit check-in. Ask each group to explain one decision in their program to you, and make a note of who can describe it and who cannot. That conversation is assessment evidence for the branching content in Years 3 and 4 and for the more complex algorithms in Years 5 and 6.

Evidence to keep: a decision rule written in words, the program, and the teacher’s observation note.

Weeks 8 and 9: team design challenge

Goal: students apply everything to a task they design and plan themselves.

Give a brief with success criteria. Examples: the robot must travel from the start to a target zone, avoid two obstacles and stop within a set distance of the target; or the robot must deliver a small paper cup across the room without tipping it. Write the criteria on the board, and keep them measurable, so that a group can show whether it succeeded.

Week 8 is planning and first tests. Each group writes a design brief in its own words, sketches a course, assigns roles, and writes an algorithm before touching the robot. Week 9 is testing and improving: run the robot at least three times, record each result in a table, and make one change at a time.

The teacher’s role shifts to coaching. Walk around with the debugging questions from week 4, check that groups have a plan, and make sure each student has a job. Limit the number of attempts a group may make before consulting its notes, which discourages random changes.

Evidence to keep: the design brief with criteria, a test results table with at least three runs, and the debugging log with explanations of at least one fix.

Week 10: showcase and reflection

Goal: students present their work, explain their thinking and reflect on their learning.

Run a showcase in the classroom or invite another class. Each group has two minutes to explain the brief, show the algorithm, demonstrate a run and say what they would change. Peer questions follow. Record a short video of the demonstration, aimed at hands and robot rather than faces, as evidence and as a record for the group.

Finish with reflection. Ask students to complete a self-assessment against the criteria: What did I contribute? What was the hardest bug? What would I do differently? A sentence stem list helps younger students begin.

Evidence to keep: the video or teacher observation, the self-assessment and the final version of the program.

Differentiation for different readiness levels

A mixed class will include students who are ahead and students who need more time. Plan for both from the start.

For students who need support: use pre-drawn paths, pairs rather than groups of three, cards with arrows to build a sequence before entering it, and a smaller target. Give clear roles and a checklist. Allow oral explanations in place of written logs, and let students show a program by running it rather than by describing it.

For students ready for more: add constraints such as using fewer blocks, completing the course faster, or using two sensors. Ask them to write a user guide for another group, or to debug a program written by a teacher with several hidden bugs. Invite them to design a new course for the class.

For students with disability, talk to your learning support staff about equipment, seating and roles. Large-button floor robots, tactile tracks and swapping the programmer role for a tester role can all keep students involved. The teacher FAQ covers more on inclusion.

Assessment points and evidence to collect

Collect evidence at three points: after week 4 (sequences and debugging), after week 7 (loops, sensors and decisions) and at week 10 (the challenge). At each point, look at three things: the plan, the program and the student’s explanation.

A simple four-level rubric works. For each criterion, such as “uses a repeat to shorten a program”, mark whether it is not yet shown, partly shown, shown or shown with explanation. Link each criterion to the language of your curriculum document, and moderate a sample with a colleague so your judgements match.

Because students work in groups, collect individual evidence too: a short written or spoken explanation from each, a personal debugging entry, and the self-assessment. The evidence checklist below lists eight items to gather. A photograph of a program on a screen takes seconds and gives you a record for reports and parent interviews.

Can you adapt the unit for other kits and year levels?

For Foundation to Year 2, shorten the unit to six weeks, use floor robots and unplugged games, and drop sensors. Use picture cards instead of written algorithms and run the showcase as a class demonstration. Version 9 brings algorithms into Digital Technologies from Years 1 and 2, so in Foundation link the same tasks to exploring a digital system and representing a plan with pictures and symbols.

For Years 7 and 8, replace the floor robot with a buildable or microcontroller kit, add a build phase in weeks 3 and 4, and shift the programming to text or a hybrid language. Add a data task: log sensor readings to a table and graph them.

If your school has no Wi-Fi or limited devices, run the unit on floor robots with buttons, and use paper for plans and logs. If you have a loan kit, compress weeks 3 to 7 and run the unplugged lessons before the kit arrives; the guide to borrowing kits covers planning. To choose a robot for the unit, see the kit comparison, and for questions about adapting the plan, use the contact page.

Evidence to collect across the unit

0 of 8 ticked

Frequently asked questions

How many lessons does a robotics unit need?

The sample unit uses ten weekly lessons of about 50 minutes. A shorter unit of six to eight lessons can work by combining the sequence and debugging weeks, and by running the unplugged lessons before the robots arrive. Fewer than six lessons leaves little time for a design challenge.

Can this unit work with floor robots?

Yes, with changes. Floor robots suit the sequence and debugging weeks well. For loops, use a model whose app supports repeats or write the repeat on paper first. Without sensors, replace the sensor week with a human sensor activity in which a student calls stop, then discuss how a machine would know.

How should I group students for robotics?

Groups of three with rotating roles, such as programmer, tester and recorder, work well. Pairs suit younger classes or when kits are limited. Rotate roles every lesson and give each role a card, so every student handles the robot and every student records.

What do students do while waiting for a robot?

Give waiting students a job: plan the next attempt on paper, record test results, build a course or check another group's algorithm. If kits are limited, run stations where some groups program while others plan, test or build. Every student should have a task while another group has the robot.

How do I assess teamwork in robotics?

Observe and record roles during lessons, and ask each student to complete a short reflection on what they contributed. Include a team role reflection in the evidence list. Share the criteria before the challenge so students know that explaining and checking count as contributions.

Can I run the unit without Wi-Fi?

Yes. Many floor robots run from buttons and need no network, and block tools often run offline after installation. Use paper for plans and logs, and check each app's offline behaviour before the first lesson. Keep an unplugged option ready in case devices fail.

Was this page useful?

Have a question?

Send it through the contact page or email hello@yesai.au.

Ask about kits
Ask about kits