How to write learning objectives that students actually understand
Most teachers can write a technically correct learning objective. The verb is on the approved list, the content is spec-aligned, and the wording would survive a learning walk without comment. What is much harder, and matters more, is writing one that actually means something to the students reading it.
If you have ever watched a class copy down an objective and then asked, ten minutes later, what they thought today's lesson was about, you will know what this guide is trying to fix. There is often a gap between the objective on the board and the picture students hold in their heads, and that gap quietly undermines a lot of the work the objective is supposed to be doing.
This is a how-to. It focuses on the language choices, the editing moves, and the small scaffolds that close that gap. It assumes you already know what a learning objective is and broadly how to structure one; if you want a primer first, our companion guide covers the what and why. This guide is about the writing.
Start with what students should be able to do, not what you'll be teaching
One of the most useful editing moves is to shift the subject of the objective from the teacher to the student. "Today we will look at osmosis" is a teacher-centred objective. "By the end of today you'll be able to predict whether a cell will gain or lose water in a given solution" is a student-centred one.
The shift is not just cosmetic. Once the objective describes a student action, you can ask whether students can do it. Once it describes what you will cover, the only question available is whether you got through your slides. The first question generates feedback you can act on; the second does not.
A quick way to test this is to read your objective and ask: Is this something I will do, or something they will do? If the verb belongs to you, rewrite it so the verb belongs to them.
A useful sentence stem: "By the end of this lesson, you'll be able to [verb] [specific content], using [hint at standard]." Not every objective needs that exact structure, but it is a reliable starting point when you are stuck.
Translate specification language into student language
Exam-board specifications are written for teachers, and they read like it. "Candidates will demonstrate an understanding of stoichiometric calculations including limiting reactants" is a perfectly serviceable spec descriptor and a hopeless learning objective. Students will not parse it, and even if they could, it does not tell them what they will be doing in the lesson.
A reasonable rewrite would be: "By the end of this lesson, you'll be able to work out which reactant runs out first in a chemical reaction, and use that to calculate how much product is made." Same content, same standard, but framed in language a Year 10 can actually use.
The move here is to do the translation work yourself once, when you plan, rather than asking students to do it in real time when the objective goes up on the board. Three patterns help.
First, swap Latinate vocabulary for everyday equivalents where you can. "Demonstrate" becomes "show". "Articulate" becomes "explain". "Interrogate" becomes "question" or "test". The technical vocabulary that genuinely matters, like "stoichiometric" or "meiosis", stays; the decorative academic vocabulary goes.
Second, name the concrete thing rather than the abstract category. "Use a worked example from organic chemistry" beats "engage with subject-specific examples".
Third, replace nominalisations (where verbs have been turned into nouns) with the verbs they came from. "Demonstrate understanding of" becomes "explain". "Make use of" becomes "use". Nominalisations make text feel formal and slightly out of reach, which is precisely what you do not want in an objective.
Reading-age guidance for objectives
It is worth knowing roughly what reading age your students are likely to have. National data tends to put average Year 7 reading age in the low teens, with a significant minority well below that. By Year 11 the average has climbed, but the spread within any single class is usually wider than people expect.
The practical implication is that an objective written at adult reading age, with multiple clauses and unfamiliar vocabulary, is going to lose a meaningful chunk of your class before the lesson has started. That is not a failure of the students; it is a fixable feature of the objective.
A reasonable target for most secondary objectives is a Flesch-Kincaid reading age of roughly 12 to 14, give or take a year for older year groups. Most word processors and online checkers will give you a quick reading-age estimate; you do not need to be precise, just aware. The table below shows the kind of edits that typically lower the reading age without losing the rigour.
| Higher reading age | Lower reading age | What changed |
|---|---|---|
| Demonstrate an understanding of how environmental factors influence the rate of photosynthesis. | Explain how light, temperature, and carbon dioxide affect how fast a plant can photosynthesise. | Verb simplified, abstract category ("environmental factors") replaced with the three concrete examples. |
| Evaluate the relative significance of long-term and short-term causes in the outbreak of the First World War. | Decide whether long-term or short-term causes mattered more for starting the First World War, and explain your reasoning. | Latinate verb replaced, nominalisation removed, reasoning expectation made explicit. |
| Apply algebraic manipulation to rearrange equations involving subjects on both sides. | Rearrange an equation when the letter you're solving for appears on both sides. | Removed jargon ("algebraic manipulation", "subjects"), kept the same skill. |
| Interrogate the reliability of contemporary sources in relation to the Reformation. | Decide how reliable two sources from the Reformation period are, using what you know about who wrote them and why. | Replaced "interrogate", made the criteria visible. |
Roughly
12 to 14
the reading age range that tends to work well for objectives in mainstream secondary lessons. The cognitive demand sits in what the objective asks students to do; the wording itself should not be the barrier.
Pair the objective with success criteria
A learning objective on its own often leaves students with a vague sense of what they are aiming for. Success criteria turn the objective into a checklist they can use during the lesson, not just at the end.
If the objective is "By the end of this lesson, you'll be able to explain how a meander forms over time, using the words erosion, deposition, and slip-off slope correctly", reasonable success criteria might be:
You can describe what is happening on the outer bank of the meander. You can describe what is happening on the inner bank. You can explain how these two processes change the shape of the river over time. You use all three key terms correctly.
The success criteria do two things. First, they make the standard visible: Students can check their own work against the list. Second, they unbundle the objective into manageable moves, so a student who is struggling can see which specific bit they are stuck on.
The Education Endowment Foundation's guidance on assessment and feedback is helpful here. It tends to emphasise that students benefit when both the goal and what counts as progress towards it are made explicit. Objectives plus success criteria are one of the simpler ways to make both visible.
Write success criteria as verbs, not topics
The most common failure mode with success criteria is that they end up reading like a contents list rather than a checklist. "Erosion. Deposition. Meanders." is not a set of success criteria; it is a topic outline.
Written well, each success criterion should describe something a student can do or produce. "You can label a meander diagram with where erosion and deposition occur." "You can explain in two sentences how a slip-off slope forms." Those are observable actions, which means both you and the student can check against them.
Three to five success criteria is usually about right. Fewer than that often means the criteria are too broad to be useful. More than that often means the lesson is too big and the objective probably needs splitting.
Lead with a student verb
Each criterion should start with something the student does or produces: Label, explain, calculate, identify, use. If it starts with a topic noun, rewrite it.
Keep them observable
A success criterion is only useful if both you and the student can tell whether it has been met. "Use the key terms correctly" is observable. "Show understanding of the process" is not.
Match the level of demand to the objective
If your objective is about explaining a process, your success criteria should describe what a good explanation looks like, not just what facts to include.
Use them during the lesson, not just at the end
The point of success criteria is that students can self-check while they work. Build in a moment, midway through the lesson, where students rate themselves against each criterion.
Common writing pitfalls and how to fix them
Several patterns tend to crop up when teachers are writing objectives in a hurry. They are worth knowing because they are easy to spot once you have a name for them.
| Pitfall | Example | Fix |
|---|---|---|
| The mystery noun | Students will understand the importance of context. | Name the context: "Students will be able to explain why the date and audience of a speech matter when interpreting it." |
| The activity in disguise | Students will complete the worksheet on osmosis. | Describe the learning, not the worksheet: "Students will be able to predict whether a cell will swell or shrink in a given solution." |
| The triple bundle | Students will know, understand, and be able to apply Newton's laws. | Pick one: "Students will be able to apply Newton's second law to two worked problems." |
| The unassessable verb | Students will appreciate the beauty of poetry. | Make it visible: "Students will be able to identify one image in the poem that they find effective and explain why." |
| The spec copy-paste | Candidates will demonstrate knowledge and understanding of stoichiometric calculations. | Translate it: "Students will be able to work out which reactant runs out first and use that to calculate how much product forms." |
| The generic objective | Students will improve their analytical skills. | Anchor it in content: "Students will be able to compare how two poems present grief, using a point-evidence-explain structure." |
Saying the objective out loud
Even a well-written objective tends to do more work when it is talked through with the class than when it is silently displayed. The reason is that the talking-through forces you to translate any remaining edu-speak in real time, and it gives students a moment to attach the objective to something concrete.
A reliable script: Read the objective, give one sentence of context for why this matters or what it connects to, and offer one example of what success looks like. That is usually enough to land. Asking a student to put the objective in their own words is also useful, particularly with KS3, because it surfaces misreadings before they propagate through the lesson.
Returning to the objective at the end of the lesson is the part most often skipped, and it is the part that does the most work. A two-minute exit task that asks students to demonstrate the objective directly is more useful than a slide saying "have we met the learning objective?" with thumbs-up votes. The exit task gives you evidence; the thumbs-up gives you compliance.
A small but useful habit: Once a fortnight, ask students to grade the objective itself. Was it clear? Did you know what you were aiming for? You will learn a surprising amount about which of your objectives are doing real work for the people they are written for.
Editing your own objectives
Writing a first draft of an objective is rarely the hard bit. The hard bit is going back over it and tightening it before the lesson. Most teachers do not get the chance to do that under planning pressure, which is a shame, because a five-minute edit tends to produce something significantly better than the first draft.
A simple editing pass: Read the objective, ask whether a student could meet it without you in the room, and ask whether you could spot at the end of the lesson whether they had. If the answer to either is no, the objective needs more work. The most common fix is making the verb more precise and the content more specific.
If you are pulling objectives from a shared scheme of work, the same edit applies. Schemes get written under time pressure too, and the objectives are often the first thing to suffer. Adapting them to your class, your students' reading age, and your own phrasing usually improves them more than starting from a blank page.
Final edit before the lesson
A five-minute pass through the objective and success criteria before you teach.
- The verb describes something a student does, not something you do.
- The verb is precise: "explain", "compare", "apply", not "learn", "know", or "understand".
- The content is specific enough that the objective could not equally fit a different lesson.
- There's some hint of standard: Either a structure to use, evidence to draw on, or a key term to deploy.
- The wording would make sense to a student reading at the lower end of the class's reading-age range.
- There's one objective, not three squashed together. Split if needed.
- There are three to five success criteria sitting underneath it, each starting with a student verb.
- You have a way of checking, at the end of the lesson, whether students have met it.
Where this fits with shared resources
If your department uses shared lesson resources, the objectives baked into them are often a useful starting point that you can adapt rather than rewrite. Resources from teaching platforms like Cognito tend to align their lesson objectives to specification points, which can save the spec-translation step. The student-facing translation, the success criteria, and the editing for your own class, however, still benefit from your own pass.
The broader point is that a well-written objective is rarely the product of a single hand. It tends to be drafted from the spec, sharpened during planning, edited the night before, and reworded on the board in real time as you read the room. None of those steps is wasted. The objective on the board at 9 am is usually a better one than the one in the scheme of work, which is the point of writing them well in the first place.
