Music technology teaching shouldn’t require a technology background

Modular Music School exists because of a gap most exam boards don’t acknowledge: composing, producing and performing components increasingly expect confident use of software like BandLab, GarageBand or notation tools — but the teachers delivering those components are music specialists, not technologists. [Optional: open with your own story of noticing this gap, if you’d like a personal opening paragraph — left as a placeholder rather than invented.]

Our approach

Non-specialist first. Every resource assumes music knowledge, not software fluency. Interface tours, workflow walkthroughs and crib notes are written for someone using the software for the first time, live, in front of a class.

Built from the syllabus, not around it. Every resource is built directly from the current specification — the exact assessment objectives, mark weightings and command words your students will face — not a generic template retrofitted to fit.

One pedagogical voice across five levels. From General Secondary through iGCSE, GCSE, A Level and IBDP, the same evidence-informed teaching principles carry through: prior-knowledge checks, worked examples before independent practice, formative checks before summative assessment, and deliberate cognitive-load management for technical tasks.

International and bilingual-school ready. Cambridge iGCSE and IBDP are treated as first-class from day one, not an afterthought bolted on to a UK-only catalogue.

Every resource follows the same structure

So once you’ve used one, you know how to use them all: a metadata header telling you exactly where it sits in the syllabus, spec-worded learning objectives, a map of where it fits in your teaching sequence, the core teaching content, a differentiation layer, a formative check, a link to the real mark scheme, and editable source files you can adapt for your own classroom.