Linking classroom robotics to Version 9 of the Australian Curriculum
Version 9 of the Australian Curriculum sets out Digital Technologies for Foundation and then in two-year bands to Year 10, and a classroom robot can serve most of its core concepts, from algorithms and data to digital systems and privacy. Plan the learning first and choose the kit second.
How is Version 9 Digital Technologies organised?
The Australian Curriculum, Assessment and Reporting Authority (ACARA) publishes Version 9 of the Technologies learning area, which contains two subjects: Design and Technologies, and Digital Technologies. ACARA describes the structure on its Technologies learning area page. Content is arranged in six levels: Foundation, Years 1 and 2, Years 3 and 4, Years 5 and 6, Years 7 and 8, and Years 9 and 10. Each level has an achievement standard that describes what students typically know and can do by the end of it, and content descriptions that describe what is taught.
Digital Technologies content sits in two strands, Knowledge and understanding and Processes and production skills, and each content description carries a code. Version 9 codes begin with AC9TDI, followed by a marker for the level (F for Foundation, 4 for Years 3 and 4, 6 for Years 5 and 6, and so on), K or P for the strand, and a number. AC9TDI6P02, for example, is the Years 5 and 6 content description on designing algorithms with branching and iteration. Because codes are easy to mistype, copy them from the official site into your planning document rather than from another teacher’s unit.
Nine core concepts sit behind the content descriptions: abstraction, digital systems, data representation, data acquisition, data interpretation, specification, algorithms, implementation (programming), and privacy and security. The Digital Technologies Hub’s core concepts page gives ACARA’s definition of each. The Hub also offers a scope and sequence from Foundation to Year 10, updated for Version 9 and organised by level, which is a useful second reference when you plan a sequence of lessons.
Robotics is not a requirement. Version 9 describes concepts and skills, and a school can address them with a robot, with unplugged activities, with a game or with a data project. Robots are useful because they make an abstract idea visible: students can watch a loop repeat or a decision change the robot’s path.
Foundation to Year 2: following and describing sequences
Version 9 treats Foundation and Years 1 and 2 differently. Foundation Digital Technologies covers recognising and exploring digital systems for a purpose, representing data as objects, pictures and symbols, and identifying data that is personal to the student. Algorithms begin in Years 1 and 2, where students follow and describe algorithms involving a sequence of steps, branching (decisions) and iteration (repetition).
A floor robot suits both levels. Students plan a route on a mat, say the steps aloud, then press the buttons and watch the result. If the robot misses the target, they find the faulty step and change it. In Foundation the same activity is a way to explore a digital system and to record a plan with symbols.
Useful activities for these years include:
- Acting as a robot on a taped grid while a partner reads instructions, which needs no equipment.
- Planning a path to a picture on a floor mat using direction cards, then checking it with the robot.
- Recording a route as a row of arrow cards, which represents the plan with symbols and matches the Foundation content on representing data.
- Sorting robot features into groups, such as things that move, things that sense and things that need charging, which links to digital systems.
- Counting and recording how many steps a route needed, which links to Mathematics.
Language matters here. Students should hear and use words like step, order, repeat and fix, because they form the vocabulary for later bands.
Years 3 and 4: decisions, repetition and visual programs
By the end of Years 3 and 4, the achievement standard expects students to follow and describe simple algorithms involving branching (a decision) and iteration (repetition), and to implement them as visual programs. This is the point at which block-based coding on a small coding robot suits many classes.
Typical tasks: a robot draws a square using a repeat block rather than eight separate move commands; a robot follows a line and stops when it sees a colour; students predict what a short program will do, then test their prediction. Prediction before running a program is worth the minute it takes, because it separates students who understand the code from students who guess.
Data runs through every level. In Years 3 and 4, students recognise different types of data and explore how the same data can be represented differently depending on the purpose (AC9TDI4K03). Students can collect measurements from the robot, such as the distance travelled on one command, record them in a table, then show the same results as a bar chart. The sample ten-week unit shows one way to build these tasks across a term.
Years 5 and 6: sensors, variables and user input
In Years 5 and 6, students design algorithms involving multiple alternatives (branching) and iteration (AC9TDI6P02), and implement them as visual programs involving control structures, variables and input (AC9TDI6P05). Robots with light, sound, distance or colour sensors fit this band.
A sensor task shows several concepts at once. A robot that stops before a wall uses a distance sensor, a variable that holds the reading, a condition that compares the reading with a threshold, and a loop that keeps checking. Students then test with different thresholds and record which one works on a carpet and which on a hard floor. That is investigation, data and programming in one lesson.
User input can be as simple as a button press that starts a routine, or a tablet interface that lets another student drive the robot. Ask students to write a short user guide for another class. The guide tests whether they understand their own program.
Privacy content in this band asks students to access multiple personal accounts using unique passphrases and explain the risks of password re-use (AC9TDI6P09). A robot app that needs a class or student login gives that content a real setting.
Years 7 and 8: general-purpose programming and data
In Years 7 and 8, students design algorithms involving nested control structures, represent them as flowcharts and pseudocode, and implement, modify and debug programs involving control structures and functions in a general-purpose programming language. For many schools that means a text-based or hybrid language. Microcontroller kits and buildable kits with a capable controller fit here, and so do drones and sensor-based robots where the school has them. The privacy content for this band asks students to explain how multi-factor authentication protects an account when the password is compromised.
Good tasks include a robot that logs sensor readings to a table, a program that uses functions to avoid repeating code, and a comparison of two algorithms for the same task, such as searching for a line by turning left first or right first. Students can analyse the trade-offs using test data.
Many Year 7 and 8 students also meet design briefs in Design and Technologies. A shared project, such as a robot that carries a lightweight load across a classroom, can serve both subjects if the assessment tasks and criteria are drawn up with care.
Years 9 and 10: modular programs and complex systems
In the final band, students design and validate algorithms, test programs by comparing their output against a range of test cases, and implement, modify and debug modular programs, including in an object-oriented programming language. Where Years 9 and 10 Digital Technologies is an elective at your school, a robotics program at this level can run as an elective unit or a cross-curricular project.
Examples: a robot that communicates with a second device, a program built from reusable modules with documented interfaces, or a data logging project where students analyse readings and report findings. The assessment emphasis moves toward documentation: a student who can explain a design decision and show test evidence demonstrates more than one who delivers a working robot with no record of how it was made.
Links to Design and Technologies, Mathematics and Science
Robotics lends itself to cross-curricular planning, which helps when timetable space is limited.
| Learning area | Robot-related task | Concept to name |
|---|---|---|
| Design and Technologies | Build a chassis to carry a load and test alternatives | Design criteria, testing, iteration |
| Mathematics | Calculate distance from wheel rotations; measure turning angles | Measurement, angles, ratio |
| Science | Compare speed on surfaces; investigate friction | Fair tests, variables |
| English | Write instructions or a procedure for another group | Procedural text |
State the learning area outcome you are assessing in each case. A lesson that touches three subjects without assessing any of them tends to leave students busy and teachers with little evidence.
NSW, Victorian and WA syllabuses
States and territories decide how Version 9 is used. The Digital Technologies Hub notes that the Australian Curriculum provides the basis for each state or territory syllabus or implementation plan, and that education authorities, sectors and schools decide when and how it is delivered. NSW teachers work from NSW Education Standards Authority syllabuses, published on the NSW Curriculum website. Victoria uses the Victorian Curriculum, which adapts the Australian Curriculum, and Western Australia publishes its own implementation through the School Curriculum and Standards Authority. Other states and territories largely follow the Australian Curriculum with local advice. If you teach in NSW, Victoria or WA, plan from your own authority’s document and use the Australian Curriculum content here as a cross-check only.
A planning habit that avoids mistakes: write the name and version of the document at the top of each unit plan, and keep a link to it. When a syllabus changes, the unit plan shows what needs revising. Your state or territory education department and your school’s curriculum leader can say which document governs your school.
Assessing robotics work against the achievement standard
An achievement standard describes a typical standard of learning at the end of a band, so assessment should gather evidence over time. A single successful robot run shows that something worked on one occasion. A planning sketch, a debugging log with at least one fix explained, test results from repeated runs and a short explanation by the student show understanding.
Build criteria from the standard’s language. The Years 3 and 4 achievement standard expects students to follow and describe simple algorithms involving branching and iteration and implement them as visual programs, so the rubric can ask where in the student’s program a decision occurs and where a repeat occurs. Privacy content is assessable too: in Years 3 and 4, students identify what personal data is stored and shared in their online accounts and discuss the risks (AC9TDI4P09), so a short discussion of what data the robot app collects shows learning without any code.
The Digital Technologies Hub suggests reading each achievement standard as a set of smaller elements within the two strands, which gives a starting point for designing assessment tasks. Its achievement standards page sets out those elements for every level.
Group work needs individual evidence. Ask each student to submit a personal reflection, to explain their role, or to describe one change they made and why. Teacher observation notes taken during the lesson help too, and a thirty-second video of a final demonstration with the student explaining the program is quick to collect.
How do work samples and moderation help?
Moderation means teachers comparing student work against the standard so that judgements are consistent. Robotics gives plenty to moderate: photos of programs, debugging logs, and short videos. Keep a small folder of work samples per class at each level, with a note on why each sample meets, exceeds or falls short of the standard. The folder is useful at report time and gives a new teacher a reference point.
Consider moderating across year levels. A Year 4 teacher and a Year 6 teacher who read each other’s samples see how the concepts grow, which helps both set expectations. Where a school has only one teacher for technologies, an online moderation group or a conversation with a nearby school can fill the gap, and your education department may run its own network.
Match the robot task to the concept
A floor robot follows a planned list of button presses to reach a target. Which concept is this?
Show the answer
Answer: Sequence. A fixed, ordered list of steps is a sequence, the simplest form of algorithm. There is no decision and no repeat.
A robot turns left only when its sensor detects a black line. Which concept is this?
Show the answer
Answer: Branching. A condition that changes what the robot does is a decision, which Version 9 calls branching.
A robot repeats forward then turn four times to trace a square. Which concept is this?
Show the answer
Answer: Iteration. Repeating the same steps is iteration, which a repeat block expresses without writing the steps out four times.
Students record how far the robot travels on each charge and graph the results. Which concept is this?
Show the answer
Answer: Data acquisition and interpretation. Collecting the measurements is data acquisition, and reading meaning from the graph is data interpretation, two of the Version 9 core concepts.
Students compare two robots' sensors and motors to choose one for a task. Which concept is this?
Show the answer
Answer: Digital systems. Comparing hardware components and how they work together is about digital systems, which ACARA describes as hardware controlled by software and connected to form networks.
Students set a password on the class robot account and discuss what data the app collects. Which concept is this?
Show the answer
Answer: Privacy and security. Protecting an account and asking what data is collected are privacy and security tasks, the core concept about protecting data when it is stored or transmitted.
Copy exact content description codes from the Version 9 site when you map these tasks into a unit plan. Once the concepts are mapped, a kit comparison helps you choose equipment that fits them, and the teacher FAQ answers common classroom questions. For anything this page leaves open, use the contact page.
Frequently asked questions
- Is robotics compulsory in the Australian Curriculum?
No. Version 9 describes concepts and skills in Digital Technologies, such as algorithms, data and digital systems, and schools choose how to teach them. A robot is one option. Unplugged activities, games and data projects can also meet the content, so check your state or territory document for what your school must cover.
- Which Version 9 content descriptions mention algorithms?
Algorithms start in Years 1 and 2, where students follow and describe algorithms with a sequence of steps, branching and iteration. In Years 5 and 6, AC9TDI6P02 covers designing algorithms with branching and iteration and AC9TDI6P05 covers implementing them as visual programs. Years 7 and 8 add flowcharts, pseudocode and a general-purpose programming language. Copy the exact codes from the official Version 9 site into your plan.
- Can robotics count towards Design and Technologies?
Yes, when the task includes a design brief, criteria, making and testing. A group that builds a chassis to carry a load, tests alternatives and evaluates the result is working in Design and Technologies as well as programming. State which learning area you are assessing in each task so evidence is clear.
- How do NSW schools link robotics to their syllabus?
NSW teachers plan from the NSW Education Standards Authority syllabus for their stage, not directly from the Australian Curriculum. Name the syllabus document in your unit plan and map robotics tasks to its outcomes. The Australian Curriculum material on this site is a cross-check, and your department or curriculum leader can advise.
- How do I assess a group robotics project?
Collect evidence of thinking over time: a plan made before coding, a photo or screenshot of the program, a debugging log, test results and a short reflection. For group work, ask each student to explain their role and one change they made. Build criteria from the achievement standard's wording.
- Where can I find curriculum-linked robotics lessons?
The Digital Technologies Hub publishes classroom resources and a scope and sequence from Foundation to Year 10. University and state loan programs, such as CSER and stem.T4L, offer lessons and guides alongside kits. Check any lesson against your curriculum document before you rely on its stated links.