Standards Alignment in Atlas: The Common Mistakes and How to Get It Right
From the Atlas Support Desk - Standards alignment errors we see most often and the practices that make alignment meaningful rather than mechanical.
Standards alignment is one of the most powerful things you can do in Atlas - and one of the easiest to get wrong in ways that undermine its value entirely. When alignment is done well, it gives coordinators a clear picture of curriculum coverage, helps teachers see connections across units, and provides strong evidence for accreditation reviews. When it is done poorly, it produces a map full of tags that nobody trusts.
Here are the mistakes we see most often and how to avoid them.
Support desk insight: The most common standards alignment problem is not a configuration issue - it is an interpretation issue. Teachers aligning standards to units often have different understandings of what "alignment" means. Some tag a standard if it is mentioned once in the unit; others tag only standards that are a primary focus. Without a shared definition, your alignment data is not comparable across teachers or subjects.
Mistake 1: Aligning to Too Many Standards per Unit
This is the most widespread issue we see. A teacher opens a unit, browses the standards list, and tags everything that could plausibly be connected to the unit. The result is a unit with 20 or 30 standards attached, which makes the map look comprehensive but communicates almost nothing meaningful.
What to do: Establish a school-wide alignment convention before teachers begin mapping. A useful starting point is to distinguish between standards that are a primary focus of the unit (taught, practised, and assessed) and those that are incidentally addressed. Only primary focus standards should be tagged in the formal curriculum map. Three to eight standards per unit is a reasonable target for most unit types - if a unit has significantly more than this, the alignment almost certainly includes incidental connections that should be removed.
Mistake 2: Importing the Wrong Standards Framework
Atlas supports a wide range of standards frameworks, including IB frameworks, national curricula, and custom school-defined standards. The issue we encounter regularly is schools that import a framework that sounds right but is not actually the version or variant their school follows - for example, importing a generic Common Core framework when the school has adopted a state-modified version, or importing an older IB framework when a revised one is in effect.
What to do: Before importing any standards framework into Atlas, confirm with your curriculum coordinator or IB coordinator exactly which framework and version your school follows. Check the import preview carefully - if the strand names or standard codes do not match your official programme documentation, stop and verify before proceeding. Re-aligning units after the wrong framework has been imported is significantly more time-consuming than getting the right framework in from the start.
Mistake 3: Treating Alignment as a One-Time Task
Schools often treat standards alignment as something to complete for an accreditation review and then not touch again. The problem is that standards frameworks are updated, units are revised, and the alignment drifts from reality within a cycle or two.
What to do: Build a brief alignment review into your annual curriculum map update process. When teachers review and update their units at the start of each year, standards alignment should be one of the items they confirm - not just whether the unit content is current, but whether the standards tagged still reflect what the unit actually teaches. A 10-minute review per unit is enough; the goal is not to remap from scratch but to catch drift before it compounds.
Mistake 4: Not Using the Coverage Report to Identify Gaps
One of Atlas's most useful features is the standards coverage report - a view that shows which standards are addressed across your curriculum map and which are not. Many schools never open it, which defeats a significant portion of the value of doing alignment work in the first place.
What to do: Run the coverage report at least once per year, ideally at the end of the academic year when maps are being reviewed. Look for standards that appear across many units (potential over-coverage or misalignment) and standards that appear in no units (genuine gaps). Share the report with subject heads and use it as the starting point for curriculum review conversations. This is the output that makes all the alignment work visible and actionable.
An Underused Feature Worth Knowing
Atlas allows you to create custom standards frameworks alongside official ones. Schools that have school-specific graduate profile attributes, learner profile outcomes, or institutional learning goals can map these in Atlas alongside IB or national standards. This means a single unit can show alignment to both the official programme framework and the school's own outcomes - something accreditation reviewers find particularly compelling. If you are not using custom frameworks and your school has its own learning goals, this is worth exploring with the Atlas Support Desk.
In Summary
- Define a school-wide alignment convention before teachers begin mapping - distinguish primary focus standards from incidental connections.
- Verify your standards framework version carefully before importing - re-aligning after an incorrect import is a significant rework.
- Build an annual alignment review into your curriculum update cycle to prevent drift.
- Use the standards coverage report to turn alignment work into actionable curriculum insight.
The Atlas Support Desk can assist with framework imports, coverage report interpretation, and custom standards setup.