Build a week-by-week or unit-by-unit pacing calendar that pins a curriculum's order to real dates with review time built in
You are a curriculum coach who builds the calendar a curriculum map does not: the pacing guide. A curriculum map decides which units exist and in what order. A pacing guide takes that order and pins it to actual dates, actual testing windows, and actual instructional weeks, the document a teacher checks every Monday to know whether the year is on track or falling behind. Build a pacing guide for [SUBJECT] at the [GRADE_LEVEL] level, running [NUMBER_OF_WEEKS:number:4-40] weeks. Here are the units or standards to pace, in the order they should run: [UNITS_OR_STANDARDS]. If the guide should start on a specific date, name it here: [START_DATE?]. If there are testing windows, benchmark dates, or long breaks that need to be blocked off, list them here: [TESTING_DATES?]. Set [GRANULARITY:select:week-by-week,unit-by-unit] to choose the level of detail. Week-by-week assigns a specific focus to every single week of the term. Unit-by-unit gives each unit a date range instead, useful for a first-draft calendar before the weekly detail gets filled in. 1. Build the pacing calendar in order, one row per week or per unit depending on [GRANULARITY]. For each entry, name the week number or date range, the unit or standard being taught, and flag it if that week also needs to absorb a testing date, holiday, or shortened week from [TESTING_DATES?]. 2. Build in review time before any date in [TESTING_DATES?] that is a real assessment, not just a marked event, so students get a buffer instead of testing cold on brand-new content. 3. Flag any point where the pacing looks unrealistic, a unit assigned too few weeks for its standard load, or a stretch with no review time before a major assessment, and suggest a specific fix, borrow a week from a lighter unit, cut a unit, or extend the term. 4. Total the instructional weeks used against [NUMBER_OF_WEEKS] and confirm the math holds, accounting for the dates already blocked off in [TESTING_DATES?]. Close by naming the single riskiest stretch in the calendar, the point most likely to slip if the year gets interrupted, and what I should protect first if a week gets lost to a snow day, an assembly, or anything else outside my control.
Range: 4 - 40
Use this prompt anywhere
10,000+ expert prompts for ChatGPT, Claude, Gemini, and wherever you use AI.
Get Early AccessA curriculum map decides which units exist and in what order. A pacing guide takes that same order and pins it to real dates: which week each unit starts, where the testing windows fall, and where a holiday or a benchmark eats into the calendar you actually have.
Set [SUBJECT], [GRADE_LEVEL], and [NUMBER_OF_WEEKS], list the units or standards to pace in [UNITS_OR_STANDARDS], and flag any [TESTING_DATES] that need to be blocked off. Set [GRANULARITY] to week-by-week for a full weekly calendar, or unit-by-unit for a faster first draft before the weekly detail gets filled in.
The guide builds in review time before every real assessment date and flags any stretch where the pacing looks unrealistic before the year starts, not after. Pair it with the curriculum map generator if the unit order still needs deciding, or the unit plan generator to build out any single unit's internal detail. Build and adjust the calendar in the Dock Editor as the year actually unfolds.
Run this through the Dock Editor, or ChatGPT, Claude, or Gemini, then set [SUBJECT], [GRADE_LEVEL], and [NUMBER_OF_WEEKS] to define how long the guide needs to run.
Fill in [UNITS_OR_STANDARDS] in the order they should be taught, and add [TESTING_DATES] for any window that needs review time built in ahead of it.
Set [GRANULARITY] to week-by-week for a full calendar or unit-by-unit for a faster overview.
Read the point the tool flags as most likely to slip, and decide ahead of time what you would cut or move if a week gets lost.
Come back and rerun the guide with new [TESTING_DATES] any time a snow day, assembly, or schedule change eats into the calendar.
Keep a single course on track week to week against real testing dates. Rerun the guide any time the calendar shifts instead of erasing a paper copy.
Build a shared pacing calendar all teachers of a course follow. Every section starts from the same [UNITS_OR_STANDARDS] list and testing window.
Check a teacher's pacing against the district testing calendar before problems compound. Spot a unit running too long weeks before it becomes a crisis.
Adapt a standard pacing guide to a non-traditional bell schedule. Set [NUMBER_OF_WEEKS] and [GRANULARITY] to match a block, trimester, or alternating-day calendar.
Discover more prompts that could help with your workflow.
Write a warm, specific back-to-school welcome letter from a teacher to families for a new year or a new student
Build a multi-week unit plan with essential questions, standards alignment, and a day-by-day lesson sequence for any subject and grade level
Build a full-year or full-semester curriculum map that sequences units in order with the standards each one carries
10,000+ expert-curated prompts for ChatGPT, Claude, Gemini, and wherever you use AI. Our extension helps any prompt deliver better results.