Teaching

How to Write a Lesson Note That Inspectors Love (Step-by-Step)

Alex Asamoah October 3, 2026 5 min read
How to Write a Lesson Note That Inspectors Love (Step-by-Step)

Every Ghanaian teacher knows the moment. Footsteps at the classroom door, a district official with a clipboard, and one question: where is your lesson note? A good note is more than a compliance document though. Done properly, it's the most useful thing you write all week, and this guide walks through what a strong note contains, why each part matters, and how to produce one quickly enough that you actually do it every week.

What a lesson note actually is

A lesson note is your plan for a specific lesson, written before you teach it. Inspectors read it for one purpose: to see whether your teaching follows deliberately from the curriculum rather than being improvised day to day. That's why the format matters less than the chain of logic inside it. Standard, objective, activity, assessment. When that chain holds, any reasonable format passes. When it's broken, no format will save you.

The parts inspectors look for

  • Header details. School, class, subject, date, duration, and the week of the scheme this note serves. Trivial, yes, but missing headers are the most common reason a note gets returned.
  • The standard or strand reference. The exact line from your curriculum or scheme that this lesson serves. One sentence connects your lesson to the national framework, and that's what turns "a lesson" into progress on the syllabus.
  • Measurable objectives. Statements starting with verbs you can observe: state, identify, calculate, compare, construct. "Understand" and "appreciate" can't be checked, so they can't be assessed. Rewrite them until an observer could verify the objective actually happened.
  • Keywords. The new terms the lesson introduces. Inspectors use these to see whether subject vocabulary is being built deliberately or stumbled into.
  • Phase-by-phase activities with timings. Starter, development, plenary, each with what the teacher does, what the learners do, and the minutes for each. The learner column matters most. A note where the teacher's voice fills every phase describes a lecture, not a lesson.
  • TLMs. Real objects, charts, the board, a worksheet. List what you'll actually have in hand, not what would be nice to have.
  • Assessment. How you'll check each objective before the lesson ends. Three questions, a task, an exit problem. Inspectors often ask to see where this happened in the students' books.
  • Reflection. Completed after teaching. What worked, what to change next time. Two honest reflection lines are worth more to an inspector than a beautiful untouched plan.

The method, in about fifteen minutes

  1. Open your scheme of learning. Find this week's row. The standard and indicator are already decided, so never invent your own on the day.
  2. Write objectives from the indicator. Two to four for one lesson is right. Convert each into a measurable verb.
  3. Choose the assessment first. Decide the three questions or the task that will prove the objectives. Planning backward from here keeps the lesson honest.
  4. Design the development phase. One clear explanation, one modelled example, one guided practice, one independent task, with minutes attached that actually sum to your lesson length.
  5. Add the starter and plenary. The starter retrieves last lesson's key idea. The plenary runs your assessment questions.
  6. List TLMs and keywords, complete the header, done.

The mistakes that get notes returned

Objectives that can't fail are the classic. If no observer could imagine a student not meeting the objective, there's nothing in it. Timings that don't add up come a close second; inspectors add, and sixty minutes of activities in a forty-minute lesson undermines everything else on the page.

Copied notes from a colleague read as paperwork instantly, especially with the same "reflection" on all three. And the class you copied it for will fail the same quiz your copy was wrong for. Then there's assessment with no follow-through: questions planned, never asked. Your reflection should say what the assessment revealed, even when the answer is uncomfortable. Finally, the note written in a hurry on the morning it's needed. Inspectors can tell. More importantly, you can feel the difference when you stand up to teach it.

A sample objective, before and after

The fastest way to see the difference is to watch one objective get rewritten. Before: "Learners will understand photosynthesis." An inspector reading that line immediately has questions. Understand which parts? To what depth? How would anyone check?

After: "Learners will state the raw materials and products of photosynthesis, and describe, in order, the two main stages." Now the line tells the inspector, and you, exactly what success looks like, and the assessment writes itself. List the materials and products. Sequence the stages. Apply that rewrite to every objective in the note and the document stops being a form and becomes a plan.

The modern shortcut that inspectors accept

Nothing in the rules says the note must be written from scratch by hand. Generating a strong first draft from an AI planner that already knows your curriculum, then editing it, personalising the examples and completing the reflection yourself, produces the same document in a fraction of the time. The thinking you invest lands where it matters: on the activities and the assessment. LexsEdu's AI Lesson Planner generates notes already structured in this inspector-friendly shape, aligned to your scheme and exportable to Word or PDF. If the scheme itself is the weak point, start with the Curriculum Engine and build the term properly first.

Notes for practical subjects and the early years

The format bends without breaking outside the classroom. A practical-science note names the experiment, the group roles and the safety points where another note would name the worked example. An early-years note carries activity-based objectives, the skill demonstrated rather than written, with the TLMs section doing the heavy lifting. Inspectors adjust expectations by phase. What never changes is the chain: something from the curriculum, something the learners will visibly do, something that shows you checked. Keep the chain intact and your format will always be recognised as a lesson note, wherever the clipboard finds you.

The habit that makes it stick

Notes written on Sunday evening for the whole week take one focused hour. Notes written each morning under pressure take twenty miserable minutes each, five days running. Batch the week, reflect daily in one line, and by the time inspection season arrives you won't be preparing notes for the inspector. You'll simply be showing the work you already do. That confidence, not the paper, is what the clipboard is really testing.

AA
Alex Asamoah
Founder, LexsTech — the company behind LexsEdu
Alex builds AI-powered tools for teachers and schools across Africa, and writes about the practical side of technology in education. Reach the team any time at support@lexstech.com.

See it in LexsEdu

The tools behind this article:

Resource Studio Curriculum Engine School ERP

Put these ideas to work

LexsEdu turns best practice into a click. Start free today.