Teacher Planner: What to Track (and What to Skip) to Stay Sane
Most teacher planners are either too empty or too full. Here is the lean, four-section teacher planner that actually keeps you sane through the year.
Compare five ways to organize planning, marking and resources. Use a time log and one measured trial to find what helps in your own teaching week.

Workload is real, but one worldwide average cannot describe every teacher. In England’s 2024 Working Lives of Teachers and Leaders survey, teachers reported 48.1 hours in their most recent term-time week, while full-time teachers reported 51.2 hours. The survey covers teachers and leaders in English state schools and was conducted in 2024. It is not a global estimate. See the UK Department for Education’s Wave 3 report and data tables.
The useful question is where your time goes and which change improves the work without weakening feedback, safeguarding, accessibility, or curriculum alignment.
Key takeaways
- Keep a five-day time log before choosing a solution.
- Test one change against a comparable week and record both minutes and quality checks.
- Batch similar decisions, reuse reviewed material, and narrow feedback to the learning purpose.
- Treat AI output as a draft that still needs subject, level, and accuracy review.
- Do not promise yourself a fixed number of hours. Keep a strategy only when your own record shows a worthwhile result.

Batch the parts that use the same mental context: outline a week’s objectives together, select texts together, or prepare exit tickets together. Do not force every lesson into one long session if your timetable or student evidence changes daily.
Use a stable template for recurring lesson types. Pre-fill only what remains true, then update the objective, evidence, misconceptions, and adaptations for the actual class.
Use AI where a first draft saves setup time: question variants, examples, a rubric outline, or a lesson sequence. Give it the subject, level, objective, constraints, and required answer key.
Then verify facts, calculations, reading demand, instructions, answers, accessibility, and local curriculum references. Record review time in your log. A draft that takes longer to repair has not saved time. The guide to creating lesson plans with AI gives a fuller review process.
Save only resources you would use again. A simple filename and three fields are enough:
Copyable text
Copy includes the complete text. No signup needed.
Unit - objective - level
Last reviewed:
Worked well for:
Change before reuse:
Archive superseded versions so search results do not become another workload. Check licenses before adapting material from an external library, and remove student data from reusable files.
Match feedback to the purpose of the task:
Peer or self-assessment needs clear criteria, modeling, and teacher oversight. It is an instructional choice, not merely a way to transfer marking.
Replace “make this perfect” with a checkable finish condition: the objective is aligned, examples are correct, instructions are readable, adaptations are ready, and the exit evidence is defined. Set a review point, not an arbitrary cutoff that leaves a lesson unsafe or unusable.
If workload is persistently unmanageable, a personal productivity technique cannot solve staffing, policy, or timetable causes. Bring the time record to the appropriate school leader or representative so the conversation is about specific tasks and constraints. Watch for the early warning signs of teacher burnout.

Copy this table into a note or spreadsheet. Log close estimates on ordinary workdays. Do not change your routine during the baseline week. The two Monday rows are fictional examples of how to record the work.
| Day | Task | Start-end | Minutes | Output | Rework or quality issue |
|---|---|---|---|---|---|
| Monday | Grade 6 lesson planning | 4:10-5:00 | 50 | Two lesson plans | Needed a better exit check |
| Monday | Marking | 7:30-8:05 | 35 | 24 responses | Six repeated comments |
At the end of the baseline week:
In this fictional example, Ms. Chen’s baseline shows 165 minutes spent writing similar individual comments on three sets of low-stakes exit tickets. She does not assume batching will save a particular amount. The next week she tests one workflow:
If the corrections show that students know their next step and the time log improves, she keeps the workflow for similar low-stakes tasks. If quality falls or the class needs substantially different feedback, she changes it. The result belongs to this task and class, not to every week of her career.
Small systems can accumulate value, but the total varies with role, subject, class, school requirements, and the quality threshold. Start with one measured trial. The goal is a sustainable workflow with sound teaching decisions, not a headline number of hours.