Weekly Lesson Plan Template: What Admins Actually Want to See

Most weekly plan templates online are just blank grids — five columns, a row per subject, no guidance on what actually belongs in each box. That's a real problem, because a weekly plan submitted to administration is a genuinely different document from a daily lesson plan, and treating it the same way — either too vague or too exhaustive — is the most common reason these submissions land badly.

1Why Admins Ask for Weekly Plans

A weekly plan serves a few purposes at once, and understanding them explains what belongs in the document. Administrators use it to confirm pacing is on track against a curriculum map, to have something on file if a walkthrough or instructional coaching visit happens mid-week, and — practically — to have a starting point available if a teacher is unexpectedly out and a plan needs to be handed to a substitute or covering colleague on short notice.

None of these purposes require the level of detail a full daily lesson plan has. They require enough to confirm the week is coherent and on pace — which is a different, lighter document.

2What to Include

• A brief topic or objective for each day — one line, not a full paragraph
• The general activity type per day (direct instruction, lab, group work, assessment) rather than a full script
• Standard codes, if your school requires them, without the full standard text
• Assessment checkpoints — where a quiz, project deadline, or test falls in the week
• Homework or major deadlines students should be aware of
• Anything unusual that week — an assembly, a field trip, a shortened schedule

3What's Safe to Leave Out

• Minute-by-minute timing for each activity — that level of detail belongs in your personal daily plan, not the weekly submission
• Full differentiation notes for every student — a brief, general note is enough at this altitude
• The complete text of every standard cited — the code is sufficient unless your school specifically asks for full text
• Exact wording of discussion questions or worked examples — save that detail for your own working lesson plans

4Common Mistakes

1. Too vague. "Continue unit" or "same as last week" tells an administrator nothing and defeats the point of the submission — even a one-line topic per day is a meaningful improvement.
2. Too detailed. Pasting in full daily lesson plans for all five days turns a document meant to be skimmed in a minute into something nobody actually reads, which paradoxically makes it less useful as documentation.
3. Inconsistent format week to week. A plan that looks completely different every week makes it harder for an administrator scanning several teachers' submissions to find what they're looking for quickly — a repeatable structure is worth more than a creative one here.
4. Submitting late or as an afterthought. A weekly plan finished five minutes before it's due tends to be the vague, unhelpful kind — building it into a regular Friday or Sunday routine (see how loop scheduling and buffer days work for weekly planning more broadly) tends to produce a more genuinely useful document.

5Formatting Tips

• Keep it to one page — if it doesn't fit, it's probably carrying too much detail
• Use the same structure every week so it's scannable at a glance
• Lead with the essential question or unit goal if the week is part of a larger unit, so daily topics read as connected rather than a disconnected list
• Note the standard code, not the paragraph

If your week is part of a longer unit, tying each day back to a single essential question is worth doing explicitly — see Lesson Plan Format: The 8 Sections Every Plan Should Have for how a strong objective anchors both a single lesson and a full week.