CANS Robots
CANS Robots is an independent guide for Australian teachers and school leaders choosing classroom robotics kits, linking them to Digital Technologies and building a program that lasts. It sells nothing.
Guides on this site
Classroom robotics kits compared, Foundation to Year 10
Four kit types sorted by year level, programming style, battery type, device needs and the questions to settle before an order.
Open GuideLinking classroom robotics to Version 9 of the Australian Curriculum
A band-by-band map from robot tasks to Digital Technologies Version 9 concepts, plus assessment and moderation ideas.
Open ChecklistStarting a robotics program at your school: a checklist
Fourteen steps from a one-paragraph goal to an end-of-term review, with notes on IT, storage, safety and teacher time.
Open GuideBorrowing robotics kits before your school buys
Three loan programs, how booking works, what a short loan should include and how to turn it into a buying decision.
Open GuideA sample ten-week robotics unit for primary classes
Week-by-week goals and activities from unplugged algorithms to a team design challenge, with evidence to collect.
Open Questions answeredTeaching robotics: answers to common teacher questions
Plain answers on coding experience, group size, breakages, inclusion, noise, assessment, parents and where to find help.
OpenTeachers choosing robotics kits face three decisions first: which year levels the kit is for, how many kits a class needs, and which devices those kits depend on. A class of 26 in groups of three needs 9 kits plus spares, and the planner below works out your own numbers.
What a classroom robotics kit includes
A classroom robotics kit is more than a robot. Most kits are a set: several robots or controllers, chargers or batteries, cables, a container, and some form of lesson material. Some need a tablet, Chromebook or laptop for programming, and others work from buttons on the robot itself. A school that compares prices and features without listing what is in the box can find the gaps only after the order arrives.
A full kit for a class has four parts. The hardware is the robot or controller, with any sensors, motors and structural parts. The power is the battery type and the way it charges. The software is the app, website or programming environment, and its account and privacy rules. The teaching material is the lesson plans, activity cards and teacher guide, which may be thin or detailed. Write down all four for any kit you consider.
This site compares kit types and avoids ranking products. If you want the fuller comparison, classroom robotics kits compared, Foundation to Year 10 sets out four types, their strengths and their limits.
Matching kits to year levels from Foundation to Year 10
Start with year level. The Digital Technologies Hub suggests a year band for each robot it describes. Its examples run from a wooden robot programmed with direction pieces and a push-button floor robot for Foundation, through a colour-code line follower for Years 2 to 6 and wheeled robots with sensors for Years 3 to 6, to buildable kits suggested for Years 5 to 8 and Years 7 to 10.
A rough guide is below.
| Years | Kit type that usually fits | Main learning |
|---|---|---|
| Foundation to 2 | Floor robots, unplugged games | Sequences, describing steps |
| 2 to 6 | Small coding robots | Decisions, repeats, simple data |
| 4 to 8 | Buildable kits with motors and sensors | Design, testing, variables |
| 7 to 10 | Microcontroller and maker kits | Text code, data, systems |
Bands overlap, and a school should treat them as starting points. A Year 4 class new to robots may do well with a floor robot, and a Year 6 class with a year of experience may be ready for sensors.
Unplugged, block and text programming in one sequence
Programming for children need not begin with a screen. A common start is an unplugged activity: students act as the robot on a taped grid while a partner reads instructions. The activity teaches algorithms, precision and debugging with nothing to charge.
Next comes block programming, where students join visual blocks that stand for commands. Blocks remove spelling errors, so students can focus on the logic, and they suit most primary robots. Text-based or hybrid code comes later: Version 9 of the Australian Curriculum expects Years 7 and 8 students to implement and debug programs in a general-purpose programming language, which needs more typing and exact syntax but offers more control.
A school program works best when it plans this sequence across years, so a Year 3 student uses blocks on a small robot, and a Year 7 student meets text code on a microcontroller. A ten-week unit that follows this order for Years 3 to 6 is in the sample robotics unit plan.
How many kits does a class need?
A common set-up is a group of two to four students per kit, each student with a job (driver, navigator or recorder) that changes every lesson. Divide the class size by the group size, round up, and add spares for breakages to get a starting number.
A class of 26 in groups of three makes nine groups. With one spare kit, that is ten kits. If each kit needs one tablet, that is nine devices in use. These numbers shift quickly with group size, which is why the planner on this page asks for it.
Time also matters. A 50-minute lesson with 10 minutes of set-up and pack-up leaves 40 minutes of hands-on time. If your timetable has shorter lessons, plan activities that start quickly and store robots where they can be handed out in a minute.
Class kit planner
Kits needed kits
Devices needed devices
Hands-on time per lesson minutes
Groups of two to four with rotating roles are common. Check device compatibility with your IT team.
Devices, charging and storage
Check the devices before you check the robots. Before you order, ask your IT team whether the app installs through the school’s managed device store, whether the robot connects over Bluetooth and whether the school’s policy allows it, whether student accounts are needed, and what data the maker collects. A robot that works on a teacher’s personal tablet may not work on a managed school device.
Charging needs a plan: one shelf or trolley where every robot charges, and a named person who plugs them in after the last lesson of the day. Battery type matters for safety, because swallowed button and coin batteries can seriously injure young children. Product Safety Australia publishes a button batteries guide that any school with coin-cell devices should read.
Storage affects how often kits are used. Numbered tubs with a parts list inside the lid, kept on a shelf near the classrooms that use them, make kits quick to hand out and quick to check at pack-up. The starting a robotics program checklist lists storage, charging and safety checks in order.
Linking robotics to Digital Technologies
Version 9 of the Australian Curriculum sets out Digital Technologies for Foundation and then in two-year bands from Years 1 and 2 to Years 9 and 10. Its core concepts include algorithms, data, digital systems, and privacy and security, and robots can address many of them. Algorithms first appear in Years 1 and 2, where students follow and describe a sequence of steps, decisions and repetition.
A floor robot following a planned list of steps shows sequence. A line-following robot that turns only when its sensor sees a line shows a decision. A robot that repeats forward and turn four times to trace a square shows iteration. Students who graph how far a robot travels on one charge are working with data. The curriculum guide goes through each band with tasks and assessment ideas, and includes a short quiz to test the mapping.
Schools in New South Wales, Victoria and Western Australia plan from their own state curriculum documents, so check which one applies before you map tasks. Copy content description codes from the official site, not from memory.
Borrow before you buy
A loan lets a school test a kit on its own devices with its own students before buying. The CSER Lending Library at the University of Adelaide gives Australian schools free loans of digital technologies kits, with priority for regional, remote and lower socio-economic schools. The NSW Department of Education’s stem.T4L program lends kits to NSW public schools. In Western Australia, Scitech charges registered schools per term to hire a class set of buildable robots for Years 7 and 8.
A good loan has a plan: test devices before the kit arrives, run a short unit, keep notes on what worked and what broke, and use the notes to decide what to buy. Read the details and the booking steps in borrowing robotics kits before your school buys. Eligibility and terms change, so check each program’s official page.
Building a program that outlasts one keen teacher
A robotics program that depends on one enthusiastic teacher can stop when that teacher leaves. A program is more likely to last when it has a written purpose, a named lead and a backup, a curriculum map, tidy storage, a charging routine, shared planning time and a review at the end of each term.
Start small: one year level, one kit type, one short unit. Collect work samples and write down what worked. Expand by one year level at a time, and budget each year for wheels, cables and batteries that wear out. The teacher FAQ answers questions about coding experience, group size, broken robots, inclusion, assessment and talking to parents.
Who this site is for and what it leaves out
The guides are written for staff in Australian schools: classroom teachers, STEM and digital technologies coordinators, curriculum leaders, business managers and principals. Each of those readers asks a slightly different question. A teacher wants to know whether a lesson will run on Monday. A coordinator wants a sequence across year levels. A business manager wants to know what to ask a supplier and what approvals a purchase needs, and a principal wants to know what a program will demand of staff over several years.
Two topics are left to other resources: robot kits for families to use at home, and robotics competitions. Both raise different questions about cost, time and supervision, and mixing them into a school guide would make every page longer without making it more useful to a coordinator.
The pages are checked each school term, and every page shows the date it was last reviewed. Every external source named in a guide is a public page that you can open yourself. If a link or a date looks out of date, tell us through the contact page.
Where to go next
Choose the page that matches your question:
- Choosing between kit types: compare classroom robot kits.
- Planning around the curriculum: robotics and the Australian Curriculum.
- Starting a program: the checklist.
- Trying before buying: kit loans for schools.
- Teaching a unit: the ten-week unit plan.
- Quick answers: the teacher FAQ.
If your question is not covered, or you spot something out of date, send it through the contact page. We reply by email, and we do not sell kits or pass your details to suppliers.
Frequently asked questions
- Which robotics kit suits my year level?
Start from year level. Floor robots fit the early years, small coding robots the middle primary years, buildable motor and sensor kits upper primary and lower secondary, and microcontroller kits the secondary years. The bands overlap, so test a kit with your own students before buying. The kit comparison page explains the strengths and limits of each type.
- How many kits does one class need?
Divide the number of students by the group size, round up, and add spares. A class of 26 in groups of three needs nine kits, or ten with one spare. The class kit planner on this page works it out for your own numbers, and also shows how much hands-on time a lesson leaves after set-up and pack-up.
- Does robotics have to be taught in Digital Technologies?
No. Version 9 describes concepts and skills, and a robot is one way to teach them. Robots also support Design and Technologies, Mathematics topics such as measurement and angles, and Science investigations. Check the document your state or territory requires, because NSW, Victoria and Western Australia use their own versions.
- Can my school borrow kits before buying?
Several programs lend or hire kits. The University of Adelaide's CSER Lending Library offers free loans to Australian schools, with priority for regional, remote and lower socio-economic schools. stem.T4L lends kits to NSW public schools, and Scitech hires kits to registered Western Australian schools. Eligibility and terms change, so check each program's official page before you plan around a loan.
- Does CANS Robots sell or recommend particular kits?
No. The site does not sell, stock, hire or ship kits, takes no commissions and has no supplier partnerships. Product names appear only to help readers recognise kit types, and a mention is not an endorsement. The guides compare kit types and give questions to ask suppliers.
- How do I ask a question or send a correction?
Use the contact page. Write the question or the page and sentence you think is wrong, and add the source if you have one. Replies come by email. Details you send are not passed to suppliers, and please leave out student names and photographs.