Curriculum Mapper

Curriculum mapping makes the invisible visible: what is taught, when, in what order, and whether the sequence actually serves learning. The costly failure it prevents is discovered in April - a standard that was never taught, a unit taught twice by different teachers, or a year whose cognitive ceiling never rose above recall. A good map surfaces those problems in August, when they cost a planning hour instead of a cohort's outcomes.

Operating procedure

Order matters: parameters constrain units, units constrain sequence, and standards alignment is only checkable once the sequence exists.

Step 1: Gather parameters

Collect before mapping; label estimates as estimates:

• Grade level or course, and duration (semester, trimester, year).
• Instructional days actually available: start from the calendar total, subtract testing windows, assemblies, and predictable non-instructional days. Most planners overestimate by 10-15%; a 180-day calendar commonly yields 150-160 teachable days.
• The standards set or framework in force.
• Non-negotiable anchor events: state testing dates, major projects, schedule breaks. These are fixed points the sequence must route around.

Step 2: Identify the big units

• Break the course into four to eight major units. Fewer than four means insufficient granularity to spot gaps; more than eight creates scheduling fragility, because one lost week cascades.
• Name each unit by its essential question or central concept, not its topic. "How do ecosystems respond to disruption?" drives instruction; "Ecosystems Unit 3" does not.
• Assign each unit a preliminary week allocation, and hold roughly 10% of total weeks unallocated as flex - reteach time, snow days, and assessment slippage are certainties, not risks.

Step 3: Sequence with intention

Unit order follows learning logic, not textbook order:

• Place prerequisite concepts before the units that consume them.
• Exploit seasonal context where students will have real-world hooks.
• Place the year's most cognitively demanding unit where stamina and assessment load allow - typically not the week before state testing, and not the final weeks of the year.
• Mark every unit that could move without damaging the sequence; these are the scheduling flexibility reserves used when the calendar slips.

Step 4: Align standards with I/D/M notation

For each unit, list the primary standards and tag each as Introduced, Developed, or Mastered in that unit. Then read the tags across the whole map:

• A standard that appears only once is a coverage flag, not a mastery plan - one exposure is not learning.
• A standard that never appears is a gap; it must be placed or its omission explicitly justified.
• A standard tagged in every unit signals over-reliance or a scope problem.
• Every M should be preceded by at least one I and one D in earlier units. An M with no I/D history is a rigor illusion.

Step 5: Check the Bloom's progression

Tag each unit's key assessments with their dominant Bloom's level: Remember, Understand, Apply, Analyze, Evaluate, Create. Then apply two checks:

• Trajectory: the year should climb. Early units may live at Remember/Understand/Apply; by the final third, major assessments should demand Analyze, Evaluate, or Create. A course whose assessments never exceed Apply has a rigor ceiling regardless of how complete its standards coverage looks.
• Within-unit floor: even early units should include at least one task above Understand, or the map is training recall and calling it learning.

Step 6: Flag vertical and horizontal connections

Horizontal connections link to other subjects taught at the same grade in the same window - interdisciplinary reinforcement opportunities. Vertical connections link to what students learned the prior year and will learn the next. Flag both, even briefly; they inform pacing and depth decisions.

Step 7: Produce the map

Deliver a table with columns: Unit Name, Essential Question, Weeks Allocated, Primary Standards (with I/D/M notation), Bloom's Level of Key Assessments, Key Assessments, and Connection Notes. Include a summary row with total weeks (including flex) and a gap/redundancy flag column. Offer two views: a condensed one-page overview and a detailed unit-by-unit breakdown.

Worked example: two map rows

| Unit | Essential Question | Weeks | Standards (I/D/M) | Bloom's | Key Assessment | Connections |
|------|-------------------|-------|-------------------|---------|----------------|-------------|
| Ecosystems Under Pressure | How do ecosystems respond to disruption? | 5 | LS2-1 (I), LS2-4 (I), LS2-6 (D) | Understand -> Analyze | Case-study analysis of a local watershed | Horizontal: stats unit on data display. Vertical: builds on Gr7 food webs |
| Designing for Resilience | Can human systems mimic ecological resilience? | 4 | LS2-6 (M), ETS1-1 (D) | Evaluate -> Create | Design proposal + peer critique | Vertical: feeds Gr10 environmental engineering |

Read the rows: LS2-6 moves Introduced-elsewhere → Developed → Mastered across units, and the Bloom's level climbs from Analyze to Create - both progressions a gap audit should confirm for every mastered standard.

Deliverable

Produce a complete curriculum map: the parameter block (instructional days after subtractions, standards set, anchor events), 4-8 units with essential questions and week allocations plus ~10% flex, the full table with I/D/M and Bloom's columns, a gap/redundancy flag list, and the two views (one-page overview, detailed breakdown).

Do NOT

• Do not map to the calendar's raw day count - subtract testing windows and lost days first, or every unit runs short.
• Do not name units by topic - topic names hide the thinking the unit demands.
• Do not treat a single appearance of a standard as coverage - once is exposure, not mastery.
• Do not let the textbook's chapter order dictate sequence - it was built for generality, not this course's learning logic.
• Do not allocate 100% of available weeks - a map with no flex fails at the first assembly.
• Do not ship a map whose assessments never exceed Apply on Bloom's - complete coverage at low rigor is still a weak year.

Quality bar

• Instructional-day math shown, not assumed; anchor events placed before units.
• 4-8 units, each named by essential question, with ~10% flex weeks held back.
• Every standard in the framework is placed, flagged as a gap, or explicitly excluded with a reason; every M has prior I and D.
• Bloom's trajectory climbs across the year and is tagged per unit.
• Movable units are marked as flexibility reserves.
• Both views delivered: one-page overview and unit-by-unit detail.