How to Structure Your Curriculum Maps So They Stay Useful Year After Year
Guidance from the Atlas team on building curriculum maps that remain relevant, maintainable, and genuinely useful to teachers - not just satisfying to administrators.
Curriculum mapping has a reputation problem. Done poorly, it produces beautifully structured documents that no teacher ever opens voluntarily - artefacts of compliance rather than tools of practice. Done well, it creates a shared understanding of what is taught, when, and why, and becomes the foundation for curriculum review, accreditation preparation, and collaborative planning.
This guide is written by the Atlas team to share the structural decisions that determine whether curriculum maps stay useful over time or become maintenance burdens. It is aimed at curriculum coordinators, IB coordinators, and school admins who own or co-own the curriculum mapping process in Atlas.
From the Atlas team: The most durable curriculum maps are built with the teacher in mind, not the administrator. If a teacher finds the map useful for planning, they will keep it updated. If they see it only as a reporting obligation, they will do the minimum required and the map will drift from reality within a term.
Start With the Right Level of Granularity
The most common structural mistake in curriculum mapping is trying to capture too much. When every lesson is mapped, every resource listed, and every assessment cross-referenced, the map becomes unwieldy and quickly falls out of date. When the map is too sparse, it communicates nothing useful.
In Atlas, the unit is the right level of granularity for curriculum maps that stay maintainable. A unit typically spans two to six weeks and contains:
- A clear title and overarching question or concept
- The key knowledge, skills, and understandings being developed
- The standards or framework elements being addressed
- The major assessment or culminating task
- Approximate timing within the academic year
Daily lesson plans, individual resources, and supplementary materials belong in a teacher's planning documents - not in the curriculum map. Keeping this distinction clear prevents maps from bloating into something nobody can maintain.
Design for Horizontal and Vertical Coherence
A curriculum map that only shows what happens within a single subject and year level is useful but limited. The real value of Atlas comes when maps are structured to support horizontal coherence (across subjects in the same year) and vertical coherence (across year levels in the same subject).
Horizontal coherence
When units across different subjects are visible in Atlas simultaneously, coordinators and teachers can identify opportunities for interdisciplinary connections, avoid unintentional clashes (two major assessments in the same week), and plan collaborative projects around shared themes. To support this, ensure that unit timing is entered consistently across all subjects - approximate calendar months are enough; precision to the day is not needed and will not be maintained.
Vertical coherence
Vertical coherence means students encounter concepts, skills, and frameworks in a deliberate sequence across year levels - building on prior learning rather than repeating it. To support this in Atlas, structure your maps so that the same standards or learning objectives can be traced across year levels in the same subject. This makes scope-and-sequence reviews significantly easier and is directly useful for accreditation and IB programme reviews.
Build in a Review Cycle, Not a Rebuild Cycle
Curriculum maps that are rebuilt from scratch each year are not sustainable. The goal is a review cycle - where the structure and most of the content persist, and teachers update what has genuinely changed.
A sustainable Atlas review cycle looks like this:
| Stage | Timing | What Happens |
|---|---|---|
| End-of-year reflection | Final weeks of term | Teachers add brief notes to each unit in Atlas noting what worked, what they would change, and any resource updates needed - while it is still fresh |
| Coordinator review | Summer or inter-year break | Curriculum coordinator reviews maps across the department or programme; identifies gaps, overlaps, and misalignments; flags units for deeper review |
| Teacher update | First two weeks of new year | Teachers update units based on coordinator feedback and their own end-of-year notes; timing is adjusted to reflect the new calendar |
| Full curriculum review | Every three to five years | A deeper review of scope, sequence, and standards alignment - typically aligned to an accreditation or programme review cycle |
The key to making this cycle work is the end-of-year reflection step. If teachers capture their observations while they are still teaching the unit, the coordinator review and teacher update steps become much faster and more grounded in real experience.
Common Structural Pitfalls to Avoid
- Over-customising the unit template - adding many custom fields to the Atlas unit template increases the burden on teachers without proportional benefit; start with the standard fields and add custom ones only when there is a clear reason
- Mapping units that do not reflect what is actually taught - aspirational maps that do not match classroom reality undermine trust in the process and make review data meaningless; if a unit is consistently skipped or significantly changed in delivery, the map should reflect that
- Treating the map as finished once it is complete - a curriculum map is a living document; a completion date in the past is a signal that it needs reviewing, not a sign of success
- Building maps in isolation - curriculum maps are most valuable when built collaboratively; a map created by one coordinator without teacher input will not reflect how the curriculum is actually experienced
In Summary
- Map at unit level - detailed enough to be useful, broad enough to be maintainable.
- Structure maps to support both horizontal coherence (across subjects) and vertical coherence (across year levels).
- Replace the rebuild cycle with a review cycle: end-of-year teacher reflection, coordinator review, and start-of-year updates.
- Build maps collaboratively with teachers - maps built without teacher input rarely reflect reality and are rarely used.
The Atlas team can support your school with curriculum mapping strategy, template configuration, and review facilitation. Speak to your FariaSupport contact to find out what is available as part of your plan.