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

Teaching robotics: answers to common teacher questions

Answers to common teacher questions about classroom robotics: coding experience, group sizes, broken robots, inclusion, assessment and screen time.

You do not need coding experience to teach robotics: the block-based coding many primary robots use is visual, and trying the activity yourself before class is the main preparation. Plan for groups of two to four per robot, and allow about 10 minutes of a 50-minute lesson for set-up and pack-up.

Do I need to know how to code?

No. You need to be willing to try the kit before the lesson and to learn alongside students. Block-based coding is visual: you drag and join instructions, and the robot shows you straight away whether it did what you meant, so you can learn the basics by trying the kit yourself.

What helps more than coding knowledge is a habit of asking good questions. “What did you expect to happen?” and “Which step do you think went wrong?” move students toward finding their own errors, and you do not need to know the answer to ask them. When a student asks something you cannot answer, say so and test it together. Students learn from watching an adult debug a problem calmly.

Prepare in four steps. Charge the robots. Run the activity yourself from start to finish. Note the three things most likely to go wrong, such as a robot that will not connect or a mat that is too small. Then write a one-page plan for the lesson with a backup activity. The ten-week sample unit gives week-by-week plans that suit a teacher new to the kit.

Peer support also matters. Ask whether a colleague at your school or a neighbouring school has used the kit, and spend twenty minutes watching them teach it. See the final section below for where to find professional learning.

How many students should share a robot?

Groups of two to four are common in primary classrooms. Pairs give each student more time on the robot and are easier to manage when kits are scarce. Groups of three allow roles such as programmer, tester and recorder. Groups of four need clearer rules, because one student can end up watching.

Rotate roles every lesson, or every part of a lesson, so each student has a turn at each job. Give each role a card with a sentence that says what that person does. A student who has the “tester” card knows to watch the robot, not to reach for the device.

For a class of twenty-six, groups of three need nine kits. The class kit planner on the home page calculates kits and devices for your own numbers, including spares. If you have fewer kits than groups, use stations: some groups program while others plan on paper, build a course or test a program that another group wrote.

Avoid leaving a student without a job while the robot is in use. A short written task, such as logging the result of each run, keeps everyone involved.

What do I do when robots misbehave or break?

Expect it. Robots misbehave for ordinary reasons, and a short troubleshooting routine fixes many problems. Teach students the routine, put it on the wall, and ask them to run through it before they call you.

A simple routine: check the robot is switched on and charged; check it is connected to the right device; check the program is the one you meant; restart the robot; restart the app. If none of these work, swap in a spare robot and tell the teacher. Having a spare kit in each lesson, even one robot in a drawer, keeps a group working while you investigate.

For physical breakages, record what happened, tape the robot with a label and put it in a “needs repair” tub. Check the maker’s or supplier’s warranty and repair process, and keep receipts and serial numbers in one place. Do not attempt to open sealed units, and keep any broken or swollen battery away from students and report it to your school’s safety officer.

Batteries need particular care, because swallowed button and coin batteries can seriously injure young children. Product Safety Australia’s button batteries guide covers safe use and storage. Check which of your robots use coin cells, and make sure compartments stay closed.

When a robot keeps failing, treat it as a teaching opportunity. A student who can describe a fault precisely, with what they did, what happened and what they tried, is practising the same skills as a programmer reading an error message. Keep a class fault log and let students add to it.

How can every student take part?

Plan for variety from the start rather than adjusting after a student is left out. Offer more than one way to show learning: a spoken explanation, a drawing of the algorithm, a photograph of the program or a demonstration. Offer more than one role in each group, so students can contribute in ways that suit them.

For students with fine motor difficulties, large-button floor robots, tablet controls or a partner who handles small parts can help. For students who find reading hard, use picture cards and colour codes. For students who are anxious about noise, offer a quiet corner or ear protection and warn the class before a loud activity. For students who are ahead, offer open-ended challenges, such as reducing the number of commands or adding a second sensor.

Talk to your learning support teacher or coordinator before the unit begins. They know the students and can suggest roles, seating and equipment. Follow your school’s inclusion policy, and ask the education department for advice about specific adjustments if you need it.

Unplugged versions of every task keep everyone in the lesson when a device fails, and they give students who find screens overwhelming a way in. Acting out a program on the floor involves the whole body and the whole group.

Gender and confidence also deserve attention. Watch who ends up driving the robot and who takes notes, and rotate roles on purpose. If one student dominates, give the others a specific job that cannot be done without them, such as running the stopwatch for each test.

How do I manage noise, floor space and time?

Robotics lessons tend to be louder and more mobile than desk-based lessons. Plan the room before the lesson. Clear a floor area, mark mats or courses with tape, and decide where bags and chairs go. A class of twenty-six in nine groups needs nine courses or a rotation, so a taped grid on the floor that groups share in turn may suit a small room.

Set a noise signal, such as a raised hand or a chime, and practise it. Allow cheering when a robot succeeds, and limit it to a few seconds.

Time needs planning too. In a fifty-minute lesson with ten minutes of set-up and pack-up, students have forty minutes of hands-on time. Use a visible timer, give each group a job for pack-up, and practise the routine until it takes five minutes. Keep robots in numbered tubs near the door so that distribution is quick. If you can, set up the room before students arrive.

Plan for the lesson that goes wrong. Have a laminated challenge card for students who finish early, a debugging poster for those who are stuck and an unplugged activity for when the devices will not connect. A lesson with a backup is less stressful than one without.

How do I assess robotics fairly?

Assess what students understand, and treat the robot’s runs as one source of evidence. A robot that completes a course can be a result of luck, a teacher’s help or a stronger partner, and a robot that fails can come from a student who understood the algorithm and met a loose wheel.

Collect evidence of thinking over time: a plan drawn or written before coding, a photograph or screenshot of the program, a debugging log with an explanation of at least one fix, test results from repeated runs and a short reflection. The unit page lists eight evidence items that cover these.

Build criteria from your curriculum document. Ask where in the student’s work there is a decision, a repeat or a variable, and whether the student can explain it. For group work, collect individual evidence: each student explains their role, describes a change they made and says why. A thirty-second video of a student explaining their program is quick to collect and easy to moderate with a colleague. The curriculum page explains how to link these to achievement standards.

Tell students the criteria before they start. Students who know what a good plan looks like make better plans, and a rubric shared in week one makes the final grade less of a surprise.

How do I explain robotics to parents?

Some parents ask whether robotics is just playing with toys, and a short, specific answer helps. Explain that students are learning to plan a sequence of steps, test it, find mistakes and fix them, which are skills in Digital Technologies and also in Mathematics and Science. Show a work sample, such as a program, a debugging log and a photograph of the course, rather than a general description.

Address screen time directly. Many robot activities are unplugged or use a screen for a short part of the lesson, and much of the time is spent planning on paper, building courses and talking. Say how much time students spend on devices in a typical lesson, and what they do when they are not on one.

Be open about data. If the robot’s app collects student information or needs an account, tell parents what is collected, who can see it and how to ask questions. Your school’s privacy policy and IT team can supply the details. Students’ faces should not appear in photographs shared outside the class without the consent your school requires.

A newsletter item with two photographs of robots and courses, a sentence on what students are learning and an invitation to the showcase is a simple way to share the work.

Where do I find help and professional learning?

Several free sources exist. The Digital Technologies Hub publishes classroom resources, a list of programmable robots and drones with a suggested year band for each, and a scope and sequence for Foundation to Year 10. Its page on training courses and communities points to free open online courses, among them a series from the University of Adelaide’s CSER group. Loan programs add lesson plans or guides to their kits; see borrowing robotics kits before your school buys for the programs described there.

Within your school, ask your curriculum leader or STEM coordinator, and look for a colleague who has used the kit. Plan a shared session where two or three teachers try the activities as students, and keep a shared folder for plans, photographs and lessons learned. The start-up checklist includes training and planning time as steps.

Your state or territory education department may run networks, workshops and online communities for technologies teachers, and teacher associations offer events. If you are unsure where to begin, ask your curriculum leader or education department which providers are approved for your school and sector.

For a question this page does not cover, or a correction, use the contact page, and we will reply by email.

Frequently asked questions

Do I need to know how to code to teach robotics?

No. Block-based coding is visual, and the robot shows straight away whether a program did what you meant, so trying the activity yourself before class is the main preparation. Ask students what they expected and which step went wrong, and test ideas together. Keep a backup activity ready in case the robot will not connect.

How many students should share one robot?

Two to four is common. Pairs give more hands-on time, groups of three suit roles such as programmer, tester and recorder, and groups of four need clear jobs. Rotate roles each lesson. If kits are limited, run stations so some groups plan on paper while others program.

What should I do when a robot keeps failing?

Run a simple routine: check it is on and charged, check it is connected to the right device, check the program, then restart the robot and the app. If it still fails, swap in a spare and label the faulty robot for repair. Keep batteries that look damaged away from students.

How can students with disability take part in robotics?

Offer several roles and several ways to show learning, such as speaking, drawing or demonstrating. Large-button floor robots, picture cards and unplugged versions of tasks help. Talk to your learning support staff before the unit and follow your school's inclusion policy.

How do I assess group robotics work?

Assess thinking over time using plans, program screenshots, debugging logs and test results, and add individual evidence such as a reflection or a short explanation from each student. Build criteria from your curriculum document and share them before the project starts.

Where can I find free robotics professional learning?

The Digital Technologies Hub lists free open online courses for teachers, including a series from CSER at the University of Adelaide, alongside classroom resources and a scope and sequence. Loan programs add lesson plans or guides to their kits. Your education department and teacher associations may also run networks and workshops, so ask your curriculum leader which providers suit your school.

Was this page useful?

Have a question?

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

Ask about kits
Ask about kits