The irony of workload reduction
Every school knows teacher workload is a problem. Most have tried to address it. The irony is that many workload reduction initiatives create more work: a new platform to learn, a new reporting template to fill in, a new professional development session to attend.
Teachers do not need another initiative. They need the planning burden cut in half.
Where planning time actually goes
When a teacher plans a lesson, the work is not just "decide what to teach." It is:
- •Checking which outcomes need to be covered this term
- •Sequencing topics so skills build progressively
- •Writing learning intentions and success criteria
- •Designing timed activities for mixed-ability classes
- •Differentiating for individual students with specific needs
- •Formatting the plan to meet school submission standards
- •Finding or creating resources
- •Ensuring cross-curriculum priorities are addressed
For an experienced teacher with years of plans to draw on, this might take 30 to 60 minutes. For a new teacher or an out-of-field teacher, it can take 3 to 5 hours — per lesson.
What does not work
Shared drives full of old plans. Useful in theory, but plans from three years ago may not align to the current syllabus. Formatting is inconsistent. There is no guarantee of quality. Teachers spend as long adapting someone else's plan as writing their own.
Generic AI tools. ChatGPT can draft a lesson in seconds, but the output needs extensive verification. Outcome codes may be wrong. Differentiation is generic. There is no connection to the term scope. Teachers trade planning time for checking time.
Template mandates. Standardised lesson plan templates ensure consistency, but they do not reduce the time it takes to fill them in. The template is not the bottleneck — the thinking and writing is.
What actually works
The strategies that genuinely reduce planning time share a common thread: they remove repetitive scaffolding work without removing teacher judgement.
1. Start with the scope, not the lesson. When the term plan is built first — outcomes mapped, topics sequenced, progression planned — individual lessons become easier to write because the hard thinking has already been done.
2. Build learner profiles once. Instead of remembering which students need what accommodations for every lesson, build an anonymised profile once per class. Let the planning tool pull those profiles into every lesson automatically.
3. Use tools that verify curriculum alignment. If a tool claims to align to the NSW syllabus, ask whether it actually checks outcome codes against the database — or just generates plausible-sounding ones.
4. Make output editable, not precious. The best planning tools produce a strong starting point that teachers can shape. Not a rigid template. Not a finished product. A foundation that saves the first 80% of the work.
5. Export in the format schools already use. If teachers have to reformat AI output into a Word table before submitting it, you have not saved them time. You have moved the bottleneck.
The real measure
The test of any workload reduction strategy is simple: does the teacher's Sunday night get shorter?
Not "does it feel innovative." Not "does it tick a compliance box." Does the teacher spend less time on planning and more time on teaching, recovery, and family?
If the answer is yes, you have found something worth keeping.
Smart Syllabus Assistant generates NESA-aligned scope and sequence and differentiated lesson plans for NSW secondary teachers — editable, exportable, and shaped around your actual students. See how it works or start free.