Claude for Teachers: A Unit Pacing Guide From Your Standards
6 min read
A pacing guide is the document that decides whether a unit ends well. It says what you teach on which day, where the assessment falls and how much slack you have for the week the fire drill, the assembly and a snow day all arrive at once. Most teachers build one from a standards list and a calendar, and most of the pain is in the arithmetic: twenty-three standards, fourteen teaching days, two of them half days.
Claude is good at the sorting and the arithmetic, and it will produce a tidy table whether or not the plan is realistic. The value is in what you tell it and how you check the result. This article walks through a method. For Claude basics, start with the Complete Beginner's Guide to Claude.
Give it your real standards, not its memory
Do not ask Claude to "write the standards for grade 7 ratios." It may produce something that sounds official and is not the text your school uses. Paste the actual standards or learning goals from your curriculum document. That one habit prevents the most serious error, which is a plan built on invented requirements.
Common mistake
Letting an assistant supply the standards from memory. Always paste the exact wording from your own curriculum, and ask Claude to work only from that text.
Step one: collect the facts of the unit
Write these down before you open Claude. They are the inputs that decide whether the plan can work.
- 1
The goals, as written
The standards or objectives, in your curriculum's own wording. Mark which are essential and which are supporting.
- 2
The real calendar
Start and end dates, days off, half days, testing windows and assemblies. Count the actual teaching minutes, not the days on the calendar.
- 3
The fixed points
The assessment date, any common assessment your department sets, and report card deadlines.
- 4
What students already know
Two or three lines on prior knowledge and the usual stumbling blocks.
- 5
How you teach
Lesson length, group work habits, how much practice time you want.
Step two: work backward from the assessment
Backward planning keeps a unit honest. Start from what students must be able to do at the end, then ask what they need before that.
Here are the learning goals for a unit, exactly as written in our curriculum: [paste]. The unit assessment is on [date]. Work only from this text. First, group the goals into three or four teachable clusters in a sensible order, noting which goal depends on which. Then tell me, for each cluster, what students must be able to do by its end, as a sentence I could check.
”You get a skeleton: what has to be taught first, what depends on it, and what "done" looks like for each cluster.
Step three: fit it to the calendar
Now give Claude the calendar and ask for a pacing table.
Using the clusters above, build a day-by-day pacing guide for these teaching days: [list with minutes per day]. Requirements: one buffer day before the assessment, one review day, and no more than one new goal introduced per lesson. Show a table with the date, the focus, the goals touched and the practice or check for the day. If the goals cannot realistically fit, say what you would cut or combine and why. Do not squeeze them in silently.
”The last line is the most important. Without it, Claude will happily fit twenty-three goals into fourteen days by making each lesson impossible. A good answer will tell you the plan does not fit and offer trade-offs, which is the honest response to a tight unit.
Step four: audit the plan
Before you trust the table, check it with a coverage matrix. Ask Claude to build one, then check it yourself.
Make a coverage matrix: one row per learning goal, one column for the days it appears. Mark where each goal is introduced, practiced and checked. List any goal that appears only once, any goal that is never checked, and any day that contains more than one new idea.
”Then read the matrix as a teacher. Do the days feel teachable? Does a lesson try to do too much? Is there enough repetition on the hard concept? You know your students and your room, and the table does not.
Step five: build in what always happens
Almost every unit loses days. Plan for it.
- Mark which lessons you could shorten and which you must keep.
- Choose, in advance, which goal you would move to a later unit if you lose two days.
- Put one "catch-up" point in the middle of the unit, not only at the end.
If I lose two teaching days, show me two versions of the plan: one that drops the supporting goals and one that compresses the practice. For each, tell me what students lose.
”Seeing the cost of each option beforehand is calmer than discovering it in week three.
What to keep for yourself
Good uses of Claude here
- Grouping goals and ordering them by dependency
- Checking the arithmetic of days and minutes
- Building a coverage matrix and finding gaps
- Drafting practice or check-for-understanding ideas for each day
Decisions that stay with you
- Which goals are truly essential for your students
- How long a concept really takes your class to grasp
- Whether the sequence matches the way your curriculum is assessed
- Anything that must follow school or district policy
A reusable project
If you plan several units a year, put your curriculum document, your calendar template and your lesson-length notes in one Claude project with a short instruction block. Setting Up a Claude Project You'll Actually Keep Using shows how, so the next unit starts from your standards instead of an empty chat.
Student information is another matter: do not paste names, grades or notes about individual students. Keep your planning inputs about the class as a whole. Claude Privacy Settings: A Real Walkthrough explains what to check.
Other assistants help with related planning tasks: ChatGPT for Teachers: Building a Rubric-Aligned Quiz and Gemini for Teachers: Turning a Unit Into a Study Guide cover the assessment side.
Official sources
Checked on October 24, 2026. Features, plans and names change often, so the vendor's own pages are the final word.