Learning objective examples for every key stage

Writing learning objectives is one of those skills that gets easier once you have seen a lot of them. The trouble is that most of us only ever encounter our own and the ones in our department's shared schemes, which means the same patterns and the same blind spots tend to repeat themselves.

This is a working bank of examples across the secondary phase. Each section pairs weaker objectives, the kind that crop up under planning pressure, with stronger versions that do more for the lesson. They are deliberately ordinary lessons rather than showpiece ones, because that is where most of the real planning gets done.

Use it as a reference when you are stuck for a verb, when you are mentoring an ECT, or when you are pulling together a department-wide objectives bank. It works alongside our separate guides on what learning objectives are and how to write them in student-facing language.

The examples below are not templates to copy verbatim. They are worked illustrations of how a generic-sounding objective can be sharpened into something the lesson can actually be built around.

For each example, the weaker version tends to suffer from one of three issues: A vague verb that cannot be assessed, content that is too broad to fit in a single lesson, or both. The stronger version usually fixes the verb, narrows the content, and hints at the standard of work expected.

If you adapt these for your own classroom, the part to keep is the structure: A precise verb, specific content, and some indication of what good looks like. The exact wording should change to fit your students and your scheme.

KS3 objectives tend to live at the lower end of Bloom's taxonomy, which is appropriate: Students are building the foundational knowledge they will apply later. The risk is that they stay there. Mixing in some applying and analysing across the unit makes the curriculum feel richer without overreaching.

At GCSE the pressure to cover specification content can push objectives towards becoming bullet points of spec descriptors. That tends to produce objectives that read like a contents page rather than a lesson. The examples below show how to honour the spec content while keeping the objective lesson-shaped.

These examples assume mixed-ability groups and are pitched broadly at grade 5 work, with the assumption that you would layer extension success criteria for higher-attaining students. The objective itself stays the same; the differentiation lives in the success criteria.

A-Level objectives tend to climb higher up Bloom's taxonomy by default, because the specifications themselves demand more analysis, application, and evaluation. The challenge here is the opposite of KS3: It is easy to write an objective that demands everything at once and ends up unteachable in a single lesson.

The stronger versions below tend to be narrower than their weaker counterparts, not broader. Splitting an over-ambitious objective across two lessons is almost always a better move than trying to deliver it in one and ending up with shallow coverage.

It is worth keeping a sense of how your objectives are distributed across the levels of cognitive demand. A scheme of work that lives entirely at "explain" and "describe" can quietly underprepare students for the analytical and evaluative questions that show up in the higher-mark exam questions.

The examples below take a single topic, the causes of the First World War, and show how the same content could anchor objectives at different levels of Bloom's. The point is not that one is better than another. They are different lessons, suited to different stages of a unit.

Not every lesson is content acquisition. Practical lessons, exam-technique lessons, and rehearsal-based sessions need objectives too, and the same principles apply. The verb should describe a visible move, the content should be specific, and the standard should be hinted at.

These examples often live closer to the applying and creating end of Bloom's, because that is the kind of cognitive work skills-led lessons demand.

Objectives in PSHE, citizenship, and cross-curricular lessons are often the hardest to write well. The content tends to be more abstract and the desired outcomes more attitudinal, which pushes teachers towards weak verbs like "appreciate" or "be aware of". It is worth resisting that pull, because the same principles apply: A learning objective still needs to point at something visible.

A useful move in these lessons is to focus on the discussion or product, not the internal state. Instead of "students will appreciate the importance of consent", an objective might be "students will be able to identify two scenarios where consent has been compromised and explain what should have happened instead". The shift is from feelings to evidenced reasoning.

If you are a HoD or a curriculum lead, it is worth turning examples like these into a shared bank rather than letting each teacher reinvent them under planning pressure. The bank does not have to be exhaustive; it should be representative.

A workable structure is to organise objectives by unit, with two or three sample objectives per lesson, paired with the success criteria you would expect to see. The point is not to enforce a single phrasing, but to give teachers a starting point and a sense of the standard the department is aiming for. ECTs and new joiners benefit particularly, because they can see what good looks like without having to ask.

If you use a teaching resource library like Cognito for your scheme of work, the objectives baked into the lesson resources can be a useful seed for that bank. Pull the ones that work, adapt them, and discard the ones that do not fit your context.