The Australian Curriculum: Digital Technologies (F–6), unpacked for primary teachers

Australian primary schools teach computing through two complementary pieces of the Australian Curriculum (ACARA): the Digital Technologies subject (one of the two Technologies subjects) and the Digital Literacy general capability (renamed from "ICT Capability" in version 9). The subject teaches children to create digital solutions and understand how digital systems work; the capability describes the operational and safety skills every learning area is meant to draw on. Most implementation pain lives in the gap between the two — the subject assumes fluencies the capability was supposed to deliver, and no timetable line owns the capability.

Version note: schools are variously teaching against v8.4 and v9 of the Australian Curriculum, with state adaptations on top (NSW syllabuses differ structurally; Victoria has its own curriculum framing). This page follows the v9 organization and flags where bands moved; check your state's adoption. Per our house rules, we'd rather flag version drift than paper over it.

The subject's two strands, in plain language

Knowledge and understanding — two big ideas that spiral through every band:

• Digital systems: hardware, software, peripherals, and (by upper primary) networks — what the parts are and how they work together.
• Data representation: how information (numbers, text, images, sound) is represented digitally — from patterns and symbols in early bands toward binary-flavored understanding by band 5–6.

Processes and production skills — the doing strand:

• Data: acquiring, organising, interpreting and visualising data — the strand where spreadsheets earn their keep.
• Creating digital solutions: the design-make-evaluate cycle around programming — defining problems, designing algorithms, implementing them, evaluating results.

Band by band: what "age-appropriate" means here

Foundation–Year 2: recognising and using digital systems for a purpose; representing data as pictures, symbols and patterns; and following/describing sequences of steps — algorithms as recipes, no branching yet. Evidence context: sequencing in concrete, visible worlds is exactly where computational thinking research says to start.

Years 3–4: digital systems including peripherals; data as different types; collecting and presenting data; and the big step — implementing simple solutions as visual programs involving branching and user input. This is where "the program decides" enters a child's model of computing.

Years 5–6: digital systems including networks and data transmission (the band's most commonly under-taught content); whole numbers/off-on representations underneath data; data acquisition and visualisation with purpose; and visual programs now involving branching, iteration and user input — the full core-constructs set — plus evaluating solutions against criteria including sustainability, and collaborative project practices.

The construct ladder embedded in the bands (sequence → branching → iteration) matches the research-supported progression, and each band's programming expectation is meaningless unless tasks force the construct — a "branching" task solvable with straight-line steps assesses nothing (why we prove construct-necessity mechanically).

The Digital Literacy capability: the unfunded mandate

The capability describes what children should be able to do operationally — practising digital safety and wellbeing, investigating (searching and evaluating), creating and communicating, managing content (files!), and operating devices including typing. Two structural truths every Australian subject leader knows: the capability has no dedicated hours, and its skills are assumed by every learning area's digital work. The digital-native myth explains what happens next — the skills arrive only for children whose homes provide them. If your school timetables one explicit hour a week for the capability's fundamentals, you are ahead of most.

Honest coverage map (Wiz Kids against the F–6 expectations)

• Creating digital solutions / algorithms: strong — sequences through branching, iteration (counting and condition-controlled), and named procedures (beyond band expectations), with construct-necessity proven per task.
• Data strand: strong for organising/interpreting/visualising (spreadsheets from cells through formulas, conditions, charts, applied projects); acquiring data from real-world collection is inherently classroom work — pair us with a real survey or sensor activity.
• Digital Literacy capability: our core territory — typing, files and search, email, safety and judgment, evaluated by doing.
• User input in programs (3–4 and 5–6): covered — the ❓ ask block pauses a running program to take input from the user, and goal-varying task worlds make asking the only viable strategy (a fixed program cannot hit a moving target).
• Data representation (all bands): covered — a dedicated realm walks symbols-as-agreed-codes → why two states → reading 8-4-2-1 binary, capped by the child building a working binary decoder in the spreadsheet engine, plus the everything-is-numbers idea (photos as gridded numbers).
• Digital systems (hardware/peripherals): partial — parts-of-the-computer and printer peripherals are taught; broader hardware exploration suits physical classroom kit.
• Networks and data transmission (5–6): covered (conceptual) — addresses, packets-as-numbered-envelopes, routers, and rerouting-around-damage, taught as judgment scenarios; a hands-on network simulator is a possible later deepening.
• Design thinking breadth (defining problems with users, sustainability evaluation): partial by design — our tasks are goal-verified; open-ended design projects belong to the classroom and we'd argue both halves are necessary.

In the classroom

1. Timetable the capability, not just the subject — one explicit weekly hour for fundamentals pays for itself across every learning area.
2. Audit the 5–6 networks content — in our experience it's the band's most skipped item because it's the hardest to make hands-on.
3. Insist on construct-forcing tasks for the programming content descriptions; "made something in a block language" is not evidence of branching or iteration.
4. Use the data strand as the spreadsheet mandate it quietly is — bake sales, class surveys, weather logs; the strand's verbs (acquire, organise, interpret, visualise) are a project template.

Reference

• ACARA. Australian Curriculum, Version 9: Technologies — Digital Technologies (F–10); and Digital Literacy general capability (v9; formerly ICT Capability in v8.4).
• ACARA. Australian Curriculum v8.4: Digital Technologies — for schools still teaching against 8.4 band descriptions.
• Falkner, K., Vivian, R., & Falkner, N. — Australian research program on Digital Technologies implementation and teacher readiness (University of Adelaide CSER; multiple reports supporting national rollout).
• State adaptations: NSW Education Standards Authority syllabuses; Victorian Curriculum and Assessment Authority (Digital Technologies).

© Glu IO Pty. Ltd. — Wiz Kids (wiz.kids). Link freely; republication requires permission — see terms. Found an error in our reading of the research? We correct fast: tell any teacher piloting Wiz Kids.