How to create a lesson plan template that actually works

Every department has one. The lesson plan template that someone designed in 2014, lives in a shared drive, and ranges from politely ignored to actively resented. It has 14 boxes, three of which ask the same question, and a section for differentiation strategies that everyone fills in with the same three bullet points each time. Nobody, including the person who built it, would claim it has made anyone teach better.

A good lesson plan template is not an accountability document. It is a thinking tool. Its job is to prompt you through the planning decisions that tend to make the biggest difference to student learning, without adding paperwork that has nothing to do with the lesson itself. The best ones are short enough to fit on a single side of A4 (or a single screen), structured enough to guide a tired Wednesday-afternoon brain, and flexible enough that you do not feel like you are filling in a form to satisfy someone else.

This guide walks through how to design a template that hits that brief. It assumes you are either building one from scratch (perhaps as a head of department) or trying to fix one that the team quietly refuses to use. The principles tend to apply at any phase, although the examples lean towards secondary teaching.

Templates that fail tend to fail for the same reason: They were designed to serve too many purposes at once. The senior leadership team wants something they can audit during a learning walk. The mentor wants something an ECT can use to demonstrate progress. The department wants something that supports planning. The individual teacher wants something they will reread before period three. These are different documents.

Before you build anything, write down the single primary purpose. For most departments, the honest answer is: We want a tool that helps teachers plan better lessons more quickly. Everything else is a secondary use. If a feature only exists to satisfy the secondary uses (a box for the SLT visitor to tick, a column for differentiation language that nobody actually plans against), it should probably come out.

This sounds obvious, but in practice most templates accumulate features over years. New initiatives bolt on new sections. Nothing ever gets removed. The eventual document tries to do everything and supports nothing. A periodic ruthless trim, ideally led by whoever uses the template most, tends to be the single highest-leverage change a department can make.

Across the templates that teachers actually report using, the same handful of elements show up. The wording varies. The order varies. The substance is more or less constant. These five tend to be enough for the document to do useful work, and any additional sections need to earn their place.

Equally important is the list of sections that often appear on lesson plan templates and tend to add little value to the planning itself. None of these are inherently bad ideas (they are pedagogical considerations that matter), but they often live more comfortably in the scheme of work, the department handbook, or the teacher's head than in a per-lesson document.

National curriculum reference boxes. These usually get filled in with the same line for weeks at a time. If the lesson is part of a unit, the curriculum link belongs at scheme-of-work level.

Generic differentiation grids. The classic three-column "support / core / stretch" box rarely captures how a thoughtful teacher actually adapts a lesson. Adaptive teaching tends to happen in the moment, in response to what students do, not via a pre-written paragraph. A short note about who needs what is more useful than a structured grid.

Long literacy and numeracy boxes. These often become a box-ticking exercise. If literacy or numeracy is a real focus for the lesson, mention it in the lesson structure where it lands. If it is not, leaving the box empty is fine.

Separate sections for SEND, EAL, and pupil premium learners. The pedagogical thinking belongs in your overall planning, but a template that asks for three separate paragraphs on every lesson plan creates compliance fatigue. A single line about specific students or groups who need something different today tends to work better.

Lengthy "professional reflection" sections. Reflection after a lesson is genuinely useful, but it usually wants its own document or a coaching conversation, not a footer on every plan.

Here is what a stripped-down template might look like in practice for a Year 10 chemistry lesson on neutralisation. The whole thing fits on half a side of A4 and took the teacher under fifteen minutes to fill in.

If you are designing a template for a department, the document also has a secondary job: It should make it easier for colleagues to share planning, cover each other's lessons, and onboard new staff quickly. That changes a few of the design decisions.

Use consistent vocabulary. If your department talks about "hinge questions", use that phrase in the template. If you call them "diagnostic checks", use that. Mixing the language across templates and meetings makes the whole system feel less coherent.

Make it editable in the format people actually use. A locked PDF that has to be printed and handwritten will not get used. A Google Doc or Word file in a shared drive, or a Notion or OneNote page with a saved template, tends to fit more naturally into existing workflows.

Agree as a team what is mandatory and what is optional. "You must fill in the learning outcome and check-for-understanding boxes; everything else is for your own benefit" is a reasonable middle ground for many departments. It respects teacher autonomy while still creating a shared baseline.

One template will not fit every situation, and trying to make it do so is part of why templates accumulate sections. A handful of variants tends to work better than one master document. Three are worth considering.

A short daily template for normal teaching, of the kind described above. This is what most teachers will use most of the time.

A fuller observation template for formal lesson observations, ECT reviews, and learning walks. This version can include the additional sections that observers and mentors find useful (more detail on differentiation, links to teacher standards, post-lesson reflection space). It is fine for this to take 45 minutes to complete because it is used a handful of times a year, not weekly.

A practical-lesson or fieldwork template for subjects where the day-to-day looks different. Science practicals need a risk assessment and an equipment list. PE lessons need a kit and space note. Geography fieldwork needs travel and safety information. Build a separate template for these rather than bloating the main one to accommodate them.

A digital question bank, like the one in Cognito, can also reduce some of the per-lesson prep that ends up on the template, particularly for starters and homework. Less time writing retrieval questions means more time on the parts of the plan that actually need your thinking.

Templates rot. New initiatives, new senior leadership, new inspection frameworks all push toward adding sections. Without active maintenance, the lean template of 2026 becomes the bloated template of 2029.

Build in a review cadence. Once a year, ideally at the end of the summer term, the department reads the template and asks two questions. Which sections did we actually use to plan with this year, and which sections do we keep filling in out of habit? Then you cut what does not earn its place.

This kind of review is a small thing that pays back over years. Ten minutes saved per lesson plan, across 600 lessons a year, adds up to roughly 100 hours, or about two-and-a-half to three working weeks of teacher time recovered. The template should serve the teaching, and that means actively defending it from accumulation.