All insights

    Pacing & mastery

    How to Build a Curriculum Pacing Guide That Survives a Real School Year

    A step-by-step method for building a curriculum pacing guide from real teaching days, with buffer weeks, mastery checks and a plan for when classes fall...

    GrowWise · Team · Last updated

    Short answer: Start from the number of days you'll actually teach, not the number of lessons in the textbook. Map standards to units and units to weeks, build in buffer and reteach time, attach a short mastery check to each week, and treat the guide as a living document that adjusts when classes fall behind.

    Step 1: How many days will you actually teach?

    Count real instructional days first. Edutopia's guidance is to subtract holidays, half days, school events, testing days, and shortened class periods from the calendar before planning anything.

    This step matters more than any other. Instruction Partners documented a school whose curriculum had 160 lessons but only 148 instructional days, 600 instructional minutes short before the year began. A guide built on the textbook's lesson count is behind on day one.

    Step 2: Which standards matter most?

    Rank standards before placing them. Identify priority standards: the ones later units and later grades depend on. When time runs short, and it will, you'll know what to protect and what to compress.

    Step 3: How do you map units to weeks?

    Use a simple, shared structure. Edutopia recommends one row per week with these columns:

    ColumnPurpose
    Week number and date rangeTies the plan to the real calendar
    Lesson focus and learning objectiveWhat students should be able to do
    StandardsAlignment to national or state standards
    Key skillsThe specific skills taught that week
    AssessmentsMidpoint and end-of-unit checks
    NotesReminders and adjustments

    Add one column most guides lack: mastery check. A three-to-five-question check on the week's key skill tells you whether the class is on pace in learning, not just in coverage.

    Step 4: Where do buffer weeks go?

    Put buffer time after the units most likely to need reteaching, typically the first unit that introduces a new concept, and before any cumulative assessment. A common approach is a short buffer at the end of each term. The exact amount depends on your calendar; the principle is that reteaching time should be planned, not stolen from the next unit.

    Step 5: How should assessments fit into the guide?

    Design them backward from the goal. Edutopia recommends sketching midpoint and end-of-unit assessments that match the formats students will ultimately face. Weekly mastery checks sit underneath them as early warnings.

    Step 6: How do you keep the guide consistent across teachers?

    Share one guide across everyone teaching the same course, and review pacing together regularly. Consistency across teachers matters even more in multi-teacher schools and tutoring centers, where two sections of the same course can drift weeks apart.

    Step 7: What happens when a class falls behind?

    Plan for it now. Decide in advance which lessons are compressible and which priority standards are protected. When a class falls behind, re-sequence rather than rush. See What to Do When Teachers Fall Behind the Pacing Guide.

    Pacing guide checklist

    • Built from real instructional days, not textbook lesson count
    • Priority standards identified
    • One row per week with standards, skills, and assessments
    • Weekly mastery check on the key skill
    • Buffer time after high-risk units
    • Shared across all teachers of the course
    • A plan for what gets compressed when time runs short

    Where Omnix360 fits - and where it doesn't

    Where it fits: Omnix360 turns an uploaded curriculum document into a standards-mapped daily pacing calendar, then tracks each class against it using student mastery, not just what was taught. When a class drifts, the teacher sees which misconception is holding students back.

    Where it doesn't: It doesn't choose your priority standards or decide what to cut; those remain professional decisions. If your pacing is set centrally by a network, the calendar-generation feature matters less than the drift and diagnosis features.

    Proof so far: Live at GrowWise School in Dublin, California (50 students, 4 teachers). Grades supported: grades 3–8.

    Scope a pacing pilot

    About Omnix360: Omnix360 is teacher-facing instructional infrastructure built by GrowWise. It reads students' wrong answers, names the misconception behind them, gives the teacher a reteach plan to approve, and shows whether the reteach worked. The AI never interacts with students. It runs on its own built-in LMS today. LTI 1.3 tool launches for connecting beside an existing LMS are on the roadmap; see integrations.

    Sources

    Related: What to Do When Teachers Fall Behind the Pacing Guide · Reteaching Strategies That Prove They Worked

    </user_query>

    Frequently asked questions

    How do you create a curriculum pacing guide?
    Count real instructional days, rank priority standards, map units to weeks with standards and assessments, add buffer time, and attach a weekly mastery check.
    What should a pacing guide include?
    Week and dates, lesson focus and objectives, standards, key skills, assessments, notes, and ideally a weekly mastery check.
    Why do pacing guides fail?
    Many are built on the textbook's lesson count instead of real teaching days, so classes start the year behind.
    Should a pacing guide be fixed or flexible?
    Flexible. Decide in advance what's compressible and what's protected, and adjust when mastery checks show a class is behind.

    Ready to prove pacing alignment in one program?

    Start with the pilot playbook, then scope one program with our team, pricing comes after the scorecard.