What “fit” looks like for A Level Geography (and how I plan it)

Period 4 last Thursday, my Year 13s were revising tectonics when a well-made YouTube clip slid from plate boundaries into hazard management frameworks without the UK-centric depth our board expects. The topic was fine; the drift wasn’t. British · A Level Geography isn’t just about being on-topic—it’s about matching assessment objectives, command words, and the synoptic weave that links human and physical. I’ve binned plenty of gorgeous slides because the 6-marker scaffolds didn’t mirror our mark scheme language.

Here’s the mismatch I see most: resources teach “what” efficiently but dodge “so what?” and “how do we know?” AO1 is overfed; AO2 and AO3 are hungry. Another blind spot is scale: examples sprawl across continents when the papers push for precise place detail and contrasting contexts. When I hunt for support pieces, I look for exam-style prompts nested in each subtopic and data sets that smell like fieldwork or secondary sources we actually use. I keep a short list of community-made bits I trust, and when I need fresh spark, I browse the geography corner here and only save what maps cleanly to our spec bullets.

On Monday with Year 12, a resource on urban change tanked when the 9–12 mark band expected “evaluate the relative significance…” but the task said “discuss”. That one word cost thinking time. Now I run a five-minute audit: command words first—do they match the board’s list and meaning?—then AO balance, then data difficulty, then mark scheme voice. If the exemplar paragraph reads like a textbook and not a candidate, I rewrite.

Concrete checks help: scan for synoptic links (can students bring in systems or place interdependence unprompted?), look for data you can annotate, and test a 6-marker against a real band descriptor. I also check that “place” is more than a name: is there process, scale, and players? When I build or adapt tasks, I like seeing them side by side with band descriptors so my prompts nudge AO2/AO3, not just recall. If you want to prototype a pack quickly and compare wording to your board, you can spin one up in ClassPods and trim until the verbs and evidence feel right.

Tuesday period 2, my Year 12s hit glacial landforms after mixing up abrasion with plucking in a quiz. The aim was to secure process-evidence explanation with a UK place. I used Cwm Idwal (Snowdonia) as the worked example so I could push scale, process, and rock type without hand-waving.

• Objective (2 min): Explain how erosional processes form corries and link evidence to process pathways.
• Starter (8 min): Two photos of Cwm Idwal—students label horns/aretes vs corries; quick cold-call on process definitions.
• Main (30 min): Mini-lecture with diagram build; paired sequencing of corrie formation; annotate a map snippet; embed a short field-sketch. Worked example: Cwm Idwal corrie (north-facing aspect, nivation hollow to rotational slip, bergschrund, overdeepening, rock-basin + lip).
• Formative check (12 min): 6‑mark “Explain how erosional processes form corries. Use a UK example.” Students write, then swap and apply AO bands on a strip.
• Plenary (8 min): One-sentence exit ticket: “The evidence that best supports plucking at Cwm Idwal is… because…” Collect to shape next lesson.

If you want this structure as a ready-to-edit pack, I keep my timings, slides, and AO strips together in ClassPods so I can duplicate it for Year 13 refreshers with a harder 10‑marker.

Friday morning, my Year 13s tackled a 10‑mark “Evaluate the extent to which hard engineering is effective on high-energy coastlines.” The scripts wobbled between case detail and judgement. I now hand out a one-page rubric that mirrors A Level banding but is student-facing.

Teacher rubric (10 marks):

• AO1 (3): Accurate, relevant concepts (processes, place, scale). Weak if generic or misapplied.
• AO2 (4): Developed reasoning that compares effectiveness across contexts; clear line of argument. Weak if list-like with no links.
• AO3 (3): Selects and integrates evidence (figures, place specifics, stakeholders); weighs reliability. Weak if anecdotal.

Student checklist (use in margin):

• Command word decoded: I wrote a balanced judgement (“to a greater extent… because…”).
• Two contrasting places named with specific evidence (e.g., cost, recurrence, geomorphology).
• One limitation or counterpoint acknowledged, then weighed.
• Final line returns to the question and scales the claim.

I store this as a reusable page and attach it to each 10‑marker so peer assessors can circle bands without guesswork; you can clone a version for your board here and tweak the phrasing to your descriptors.

Wednesday after school, I ran a catch-up with two EAL students in Year 12 who could explain processes fluently in their first language but froze on “assess” vs “evaluate”. I keep a micro-glossary of command words with sentence stems (assess: “on the one hand… however… overall…”) and dual-language key terms for new topics. During lessons, I allow verbal planning first, then a 90-second write. It slows the bustle a touch but the paragraphs improve.

For pacing, I bank 5 minutes at transition points for quick retrieval: one AO1 recall, one AO2 link, one AO3 critique. Homework extends the same pattern: short source work (a figure, a map, a table) plus one exam-style item. Revision-wise, students curate a two-page case digest with process, players, evidence, and a mini-judgement. If you’re coordinating across a department or trialling digital packs before a mock cycle, check the plan that fits your groups and budget on the pricing page so you can standardise without losing teacher control.