Computing and ICT resources: plan a useful school collection

Organise resources around learning

A useful computing collection begins with what pupils should understand and be able to do. List the concepts and experiences in the school's curriculum, then identify the resources that support them. Avoid building a programme around whichever devices happen to be available or whichever application has recently been promoted.

For England, the national curriculum computing programmes of study describe a progression that includes computational thinking, programming, purposeful use of technology and safe, responsible participation. The curriculum arrangements of Wales, Scotland and Northern Ireland differ, so use the framework applicable to the school. This guide concerns resource planning rather than a complete curriculum scheme.

Map resources to year groups, prior learning and intended outcomes. A sequence should help a teacher explain why an activity follows the previous one and what pupils will revisit later. Repeatedly changing applications can consume lesson time without improving conceptual understanding.

Include both physical and digital resources

Paper instructions, sorting cards, maps and classroom objects can support discussion of sequences, choices and patterns. Programmable equipment, computers and approved software then allow pupils to test ideas in a digital setting. Choose the medium because it supports the task, not because every computing lesson must look the same.

Create complete activity sets. A box of programmable devices is less useful if charging leads, mats or instructions cannot be found. Label the contents, record where they belong and provide a simple check-in routine. Where several classes share equipment, include setup and return time in the booking arrangement.

For digital resources, record the approved application, account requirements and where pupils save work. Teachers should not discover during a lesson that an activity requires an unapproved personal account or an additional paid feature.

Test the classroom workflow

Trial resources with the school's actual devices and network. Check sign-in time, browser compatibility, accessibility settings, sound and the ability to save or export work. Ask whether a whole class can start together and whether the teacher can recover from a common mistake without administrator access.

Make pupil instructions clear and concise. Use consistent names for folders, files and commands, with examples that match the screens pupils will see. Avoid screenshot-heavy instructions that become unusable after a minor interface change; explain the purpose of the action as well as its location.

Keep an offline or alternative activity for a network failure where it supports the same learning objective. The fallback should not feel like an unrelated holding task. It may focus on prediction, discussion or planning that pupils can later test on the device.

Make access and participation visible

Consider pupils who need alternative input, enlarged text, audio support or more time to navigate an interface. Check whether the activity can be adapted without removing its central learning. The assistive technology guide offers a process for individual barriers.

Review the language and examples in resources. Instructions should not assume every pupil has the same experience of technology at home. Explain essential concepts in school and provide the equipment needed for the planned task. Homework should have an accessible route for families with limited devices or connectivity.

Include online safety within the activity itself: choosing what to share, recognising a concern and asking for help. Do not rely on a single annual lesson to support every new application or communication feature pupils encounter.

Support the adults using the collection

Give teachers a concise overview of each unit: intended learning, required resources, likely misconceptions and essential setup. Provide a working example and a way to practise before teaching. Training is most useful when it answers the questions teachers will face in the lesson.

Agree who maintains software approvals and who updates teaching notes. Keep the curriculum owner and IT support connected so a security or licence change does not unexpectedly remove a resource mid-unit. Similarly, teachers should give support staff enough notice of specialist requirements.

Review quality before adding more

At the end of a unit, ask whether pupils achieved the intended learning and whether technical friction interfered. Record resources that are rarely used, unreliable or duplicating something better. Retire them deliberately instead of leaving an ever-growing list of choices that new staff cannot evaluate.

Plan consumables, repairs, subscriptions and replacement in the equipment planning process. A smaller collection with clear progression, dependable setup and confident teaching can be more useful than a large catalogue of disconnected activities. The goal is a resource collection the school can explain, maintain and use well over time.