How to use curriculum maps for classroom planning

A curriculum map is one of those documents that is easy to produce and easy to misuse. Most departments have one. Many of them sit on a shared drive and are read once a year for the Ofsted deep dive. A useful curriculum map looks roughly the same as a useless one, which is part of the problem. The difference is in how it gets made and how it gets used.

This guide is for heads of department, middle leaders, and ECTs who have inherited a curriculum map and are trying to work out what to do with it. It covers what a curriculum map actually is (and is not), how it differs from a scheme of work, how to use it to plan, and how to share it with students and parents without it becoming a compliance artefact. The thinking here is conventional rather than novel; the value is in being honest about where the document tends to fall down.

A curriculum map is the high-level view of what your subject teaches across the years. It shows units in teaching order, with rough timings, and ideally also shows the big ideas, key skills or disciplinary threads that run through them. It is the view you would give to someone who had ten minutes to understand what your department is doing, before drilling into any specific year, unit or lesson.

It is not the same as a scheme of work. A scheme of work is the unit-level plan: Lesson sequences, resources, assessments, knowledge organisers. A curriculum map is the layer above that. You can have a coherent map without having every scheme of work finalised, and you can have detailed schemes of work without a map (though the map is usually what makes them hang together).

It is also not the same as a long-term plan. A long-term plan tends to be the school-level scheduling document: Which year group is doing what in which term, when assessments fall, when reports are due. A curriculum map sits inside the subject and answers a different question: Not 'when are we teaching this', but 'why are we teaching this in this order'.

A useful map shows three things at once: The units in teaching order, the conceptual threads that connect them, and the rough position of each unit in the progression from KS3 to KS4. Some maps add a fourth layer: How assessments are placed across the year, which units feed into which exam content, and where the difficult transitions sit.

The simplest format is a grid: Years across the top, terms or half-terms down the side, units in the cells. A more useful version adds colour-coding or icons to show which big ideas each unit serves, and a column showing what disciplinary skill is being developed. The point of the visual is that someone reading the map should be able to see the conceptual structure of your curriculum, not just the topic list.

The honest answer about how most teachers plan is that they look at the next unit in the scheme of work and start designing lessons. The curriculum map rarely features. This is not unreasonable for week-to-week planning; the map is at the wrong level for that scale. But there are three planning moments where the map should do real work, and tends not to.

The first is the start-of-year planning conversation. Before the autumn term begins, the department should sit down with the map and work out what is coming, what changed from last year, what the assessment data from last year suggests needs more time, and where the difficult transitions are. The map is the document that makes that conversation tractable; without it, planning at this level tends to drift into unit-by-unit chat.

The second is the mid-unit check-in. When you are halfway through a unit and feeling rushed, the map is what tells you what the unit was actually trying to do, and what concept it was building toward in the next unit. That tells you what you can compress and what you cannot. Teachers under time pressure tend to compress the conceptual depth (which the map says was the point) and protect the surface content (which the map says was the vehicle). The map, if consulted, would reverse that choice.

The third is the end-of-year review. The map is the natural reference point for evaluating the year: Did we get through what we planned, were the assessments aligned with the threads we said we were teaching, did the difficult transitions land. Without the map, the end-of-year conversation defaults to topic coverage and grades, both of which are too narrow.

There is an argument that sharing the curriculum map with students may support their metacognition. The robust EEF evidence on metacognition is really about explicit strategy instruction rather than map-sharing specifically, but when students can see where they are in the year, what is coming next, and how the units connect, it could help them feel more in control of their learning. This is not a guaranteed effect (some students will glance at the map and never look again), but the upside is large enough to be worth the small cost of producing the student-facing version.

The student-facing map does not have to be the same as the department version. It tends to work better with simpler language, fewer threads visible at once, and concrete examples of what each unit will involve. Some departments produce one map per year group and stick it in the front of the exercise book. Others build a single 'where are we?' poster that lives on the classroom wall and gets pointed at across the year. The format matters less than the consistency of reference.

It is also worth being clear with students about what the map is not. It is not a promise that every lesson will follow it exactly. It is not a study guide. It is a picture of the journey, and one of the small but real benefits of metacognition research is that students who can see the journey tend to handle the bumps in it better.

Parents who can see the curriculum map are often better placed to ask informed questions at parents' evening and to support their children's learning at home. Publishing a simplified, jargon-light version on the school website or sending it home at the start of the year is a relatively low-effort move that can build trust over time.

The risk is that a poorly produced parent-facing map either says too little ('Term 1: History') or too much (a screenshot of the internal document with all its acronyms intact). The version that works is closer to a paragraph plus a simple table: Here is what we are teaching this year, here is roughly when, and here is what your child should be able to do by the end of it. Parents do not need to know your big ideas vocabulary; they need to know what their child is learning and how to support it.

It is also worth being honest about the limits. A map sent home at the start of the year and never referenced again is not really shared. Departments that follow up (a brief note when the unit changes, a parent-facing summary in the school newsletter) tend to see the engagement compound. Departments that publish and forget tend to see the same parental confusion at parents' evening as before.

The most common failure mode of curriculum maps is conflating the map with the curriculum. A polished map can convince a department that the curriculum is in good shape when the actual lessons are doing something different. Inspectors and observers can be similarly fooled. The map can show beautiful coherence while the Year 9 mid-term test is on content the Year 8 units never built, and nobody has noticed.

The useful question to ask, regularly, is: Does the teaching match the map? This is partly a question for lesson observations (does the Year 8 lesson look like what the map said Year 8 was doing), partly a question for assessment design (does the test measure what the map says was taught), and partly a question for student voice (do students recognise the journey the map describes). When the answer is yes, the map is genuinely doing its job. When the answer is consistently no, the map is decoration.

This is also a reason to treat the map as a living document. Annual review, ideally with the department around the table after the summer exams, is what keeps the map honest. A map that has not been updated since the HoD wrote it three years ago is almost certainly diverging from the actual teaching, regardless of how good the original version was.

If you have inherited a department without a useful map, or with one that does not really describe the teaching, the work is mostly conversational. Start by listing the units actually being taught (which may differ from the unit list on the shared drive), in the order they actually happen. Add the rough timings. That gets you the chronology layer.

Next, work with the department to name three to six conceptual threads that the subject is genuinely developing across the years. These are the big ideas or disciplinary moves that recur. Map each unit to one or more of them. This step exposes both the strong threads (concepts that recur naturally and deepen) and the weak ones (units that do not really serve any thread and are there mostly out of habit). Both insights are useful.

Then sketch the progression layer: For each thread, what should a Year 7 student be able to do at the start, what should a Year 11 student be able to do at the end, and what are the stepping stones? You do not need the full progression maps yet; rough end points are enough to make the map functional. Schemes of work will fill in the detail later.

Finally, place the assessments. Where do they fall, what do they test, and do they line up with the threads the map says you are developing? This is often the question that exposes how seriously the rest of the map is being taken.