How teachers should choose what to teach
Every curriculum decision is, eventually, a decision about what to leave out. There are more topics, themes, texts, and ideas in any discipline than a five-year secondary curriculum can carry. A specification helps but does not exhaust the question; even within a specification, a department chooses which texts to teach, which case studies to use, which historical periods to deepen, which substantive examples will carry a concept.
This is the part of curriculum design that is most often left implicit. The official documents tend to describe what is taught; they rarely describe what was considered and rejected. That hidden layer of choice (the conversations in department meetings, the things one teacher quietly drops, the topic that gets two lessons instead of four) shapes the curriculum more than the formal documents do.
This guide is aimed at heads of department and curriculum leads facing the broader question of what should and should not be in the curriculum, and it sketches a decision frame for working through that question honestly.
Big ideas worth carrying
5 to 6
Mary Myatt's principle of 'fewer things in greater depth' (in Back on Track, 2020, and The Curriculum: Gallimaufry to Coherence, 2018) points to a subject curriculum held together by a small number of recurring big ideas. The number is our rule of thumb rather than hers, but fewer than that and the curriculum feels thin; many more and the ideas stop being load-bearing. The principle matters more than the count: Not everything can be a priority.
Why the choice matters more than people think
Two departments teaching the same specification can deliver very different educations. One weights its history KS3 toward British political and constitutional history; another weights toward global history with strong threads on empire, migration, and revolution. Both might be defensible. They are different curricula in everything but name.
The choice matters because the act of selecting (and the act of cutting) is where the curriculum reveals what it believes the subject is for. If a department cannot articulate what it left out, it usually cannot articulate what it stands for either. Christine Counsell's framing is useful here: A curriculum is a body of knowledge selected and sequenced with purpose. Borrowing the specification's content list wholesale is not selecting; it is deferring.
What you cannot decide first
It is tempting to start with the topic list and decide topic by topic. That tends to produce a curriculum that is locally reasonable and globally incoherent.
A more useful order is to decide three things first. What is the subject for in this school? What kind of thinking do you want students to be doing by the end of KS4? What body of knowledge do you want them to leave with? Those three answers are the lens through which every topic decision should be evaluated. A paragraph each is plenty, but they do need to be agreed and written down, or the team will quietly default to different answers.
If you find yourself debating individual topics without a shared answer to the three lens questions, the debate will not resolve. People are arguing about different curricula and do not realise it.
A decision frame for individual topic choices
Once the lens is in place, the next step is a frame for evaluating any candidate topic, text, case study, or example. The frame below has worked well for departments we have spoken with. It is not a scoring rubric; it is a small set of questions that surface what the team actually thinks.
Does it serve a big idea?
Map the topic to one of the five or six big ideas the curriculum is built around. If you cannot, that is not automatically disqualifying, but it should give pause. Topics that do not serve a big idea tend to be the first ones quietly dropped when time gets short.
Is it the best example of that big idea you have?
Most big ideas can be illustrated by several topics; you do not need every illustration. A history department teaching the idea of revolution does not need every modern revolution to make the point. Choose the example that does the most work for the concept and the cohort, and trust it.
Does it build on something earlier, or set something up later?
A topic that exists in isolation, with no upstream connection and no downstream payoff, is usually a candidate for removal. The strongest topics are the ones that prior units made possible and that future units depend on. Curriculum coherence comes from these connections, not from any individual topic.
Is it teachable by the team you actually have?
A topic that requires specialist knowledge no one in the team currently has is a CPD commitment, not just a curriculum decision. Sometimes the right answer is to make the commitment; sometimes the right answer is to pick a different topic. Both are legitimate, but they should be explicit.
Will it survive when time gets tight?
Topics taught in the final fortnight of the summer term, with two cover lessons and a wet sports day in the middle, are taught half-heartedly almost by definition. A topic that the team will not commit to teaching properly is worse than no topic at all. Be honest about which topics are at risk and either protect them earlier in the year or replace them with something more robust.
What does it cost to include?
Every topic added is another topic squeezed. Make the cost visible. If you want to add a unit on environmental history, name the unit it will displace. A curriculum that only ever adds, and never subtracts, becomes an exhausted hour-by-hour race.
The hardest question in the frame is usually the cost question. Departments tend to add good ideas without naming what they will displace, and then wonder why the year feels rushed. The displacement is the choice.
Substantive vs disciplinary knowledge
A useful distinction, drawn from Christine Counsell and others, is between substantive knowledge (the actual content: Events, facts, formulae, texts, processes) and disciplinary knowledge (how the discipline thinks: How historians weigh evidence, how scientists design experiments).
Many curriculum decisions involve trading substantive depth for disciplinary depth or the other way round. A history department can teach more periods lightly with less attention to interpretation, or fewer periods in depth with strong work on the historian's craft. Most departments find that a tilt toward disciplinary depth at KS3 pays off across KS4: Students who can think like a historian, scientist, or literary critic absorb new content faster than students who have only met it as isolated facts.
How to handle the specification
The specification was not designed for your school. It was designed as a defensible national assessment of a discipline at age 16, which is not the same as a curriculum. Treat it as a constraint rather than a syllabus: Within that constraint, there is usually more freedom than departments use.
This matters especially at KS3, where the temptation to pre-teach the GCSE specification is strongest. A KS3 that simply foreshadows the GCSE tends to be thin; a KS3 that builds the substantive and disciplinary foundations the GCSE relies on is much richer, even if the topic list does not look like a junior version of the specification.
Choosing texts, case studies, and examples
Every unit involves choosing specific examples: A novel, a play, a war, a case study country, an experiment, a worked example. These choices look small but are where the curriculum's character shows.
Pick examples the team can teach with conviction; an enthused teacher carries more than the abstract best choice on paper. Pick examples students can return to across units, building familiarity. Pick examples that genuinely illustrate the disciplinary move you are teaching, not the ones easiest to resource. And occasionally pick examples that stretch the team or the cohort; a curriculum entirely made of safe choices is its own kind of failure.
When choosing texts or case studies, the question to keep asking is: What does this one do that another could not? If the answer is not specific, the choice is probably arbitrary and could be revisited.
When to cut, and how to do it without losing trust
Cutting is harder than adding, both intellectually and politically. Teams are attached to units they have taught for years, and senior leaders tend to read 'we are cutting two units' as 'we are doing less'.
Frame each cut as a trade rather than a loss; naming what the freed-up time will allow makes the proposition additive. Show the audit evidence behind the decision; cuts grounded in cohort underperformance or time overruns are easier to defend than cuts grounded in HoD preference. Cut deliberately rather than by attrition, and keep what was cut visible somewhere so the next refresh cycle can revisit it.
Edge cases worth thinking through
A few decisions sit awkwardly inside the frame and tend to need a separate conversation.
| Decision type | Why it is hard | What tends to help |
|---|---|---|
| Topics that the team is divided on | Strong feelings on both sides, and the decision is irreversible for at least a year | Frame the decision as a one-year trial, with explicit criteria for review at the end |
| Sensitive or potentially distressing content | Requires careful handling, time, and CPD to teach well | Decide as a department, not as individuals; align on the framing, the language, and the support; do not leave it to whoever happens to teach that unit |
| Topics with weak available resources | Risk of falling back on shallow materials or skipping the topic entirely | Allocate planning time deliberately, or pick a different topic that the same big idea can carry |
| Topics that students enjoy but do not serve a big idea | Engagement is real; coherence is also real | Keep them if you have room; cut them if you do not, and name the trade-off honestly |
| Topics that one passionate teacher carries entirely | Works while they are there; collapses when they leave | Build the topic into the shared resources and CPD plan, or accept that it is a personal contribution and not a department commitment |
How to revisit the choices over time
A good curriculum is not a fixed document; it is a set of decisions you periodically test. The choices you made three years ago might still be right; equally, the cohort, the specification, the team, or the discipline might have moved.
A practical cadence is to review topic-level choices every two or three years against the same lens questions. Most will hold; a few will not, and those are the candidates for the next refresh. This is where written rationales pay off: A department that documented why it picked this novel over that one in 2023 will have a far easier conversation in 2026 than one reconstructing the reasoning from memory.
Choosing what to teach: A working checklist
Use this when working through topic-level decisions across a unit, a year, or a full key stage.
- Write down the three lens questions and agree the team's answers before debating topics
- Name the five or six big ideas the curriculum is built around
- For each candidate topic, ask whether it serves a big idea and is the best example of that idea you have
- Check the topic's upstream and downstream connections within the curriculum
- Be honest about whether the team can teach it well, or whether it requires explicit CPD
- Name the cost of inclusion: What will it displace, and is that trade worth making
- Decide consciously between substantive and disciplinary emphasis for each unit
- Treat the specification as a constraint, not a syllabus, especially at KS3
- Frame any cuts as trades; record what was cut and why, so future reviews can revisit
- Build in a review cycle every two or three years against the same lens questions