#pacing guide

High School Unit Calendar Prompt From Your Pacing Guide

Turn your pacing guide and school calendar into a day-by-day high school unit plan with real day counts, buffer days, checkpoints, and a family overview.

Act as a high school instructional coach who builds unit calendars from a teacher's pacing guide and the real school calendar, and who always protects buffer days because something gets cancelled. Inputs: - Course, grade, and unit name: [CourseUnit] - Learning targets or standards for the unit, worded as in my pacing guide: [Targets] - First and last day of the unit, and the length of a class period: [DatesPeriod] - Days with no class or a short class (assemblies, testing, holidays, early release): [Disruptions] - Assessments with fixed dates (common unit test, project due date): [FixedAssessments] - Lessons, labs, or activities I already plan to use: [MyActivities] - Supports I plan for, described for groups, never named students: [Supports] - Who reads the student and family overview, and in what language: [OverviewAudience] Generate: 1. Day count: list every school day in DatesPeriod, remove the Disruptions, mark short days, and give the count of full and short class days. 2. Unit calendar: a day-by-day table with date, target, lesson or activity, quick check for understanding, and homework if any. Use MyActivities where they fit and mark any lesson you added yourself as "suggested". Keep FixedAssessments on their dates. 3. Buffer and catch-up: put at least one buffer day before each fixed assessment. If the targets do not fit the days, say which target to compress and why, instead of cramming two lessons into one period. 4. Checkpoints: two short checks before the unit test, each tied to a target, that tell me who needs reteaching. 5. Supports by day type: for new content, practice, review, and assessment days, one concrete move drawn from Supports. 6. Student and family overview: a short plain-language summary of the unit, key dates, and how to get help, written for OverviewAudience. Rules: - Use only the dates I give; if a date or weekday looks wrong, ask before planning. - No student names, grades, or other personal information; keep everything FERPA-safe. - Keep my targets in my wording; do not rewrite standards.