What Actually Works in A Level Physics Lessons

First week of September, my Year 12s tried to use F=ma to “explain” terminal velocity in a fluids question. They weren’t wrong, but they weren’t A Level-right either. In the British · A Level pathway, the jump from GCSE isn’t bigger numbers; it’s multi-step reasoning, explicit modelling assumptions, and exam-board flavour: AQA’s “show that” with given answers, OCR’s emphasis on vector notation, Edexcel’s tidy graph work and uncertainties. Practical endorsement (CPAC) adds another layer—quality of method, not just outcomes.

I’ve binned plenty of slick-looking resources because they skip units, avoid error propagation, or use American spellings and constants that won’t match our data booklets. That mismatch burns time and confidence. These days I filter hard for command words, significant figures, vector clarity, and a practical thread that matches our scheme. I park shortlists in ClassPods and then prune. If you want to see what the wider science crowd shares, you can browse and stash ideas in the community science library and adapt from there.

By Week 3, my Year 12 mechanics group face-planted on a “derive” question because the sheet mixed radians and degrees mid-solution. That was my fault for not preflighting it. Now I run quick checks: do the command words match AQA/OCR/Edexcel glossaries? Are constants and units straight from the data booklet? Are vectors bold or arrowed consistently? Do solutions show reasoning—not just keystrokes? Are significant figures and uncertainties enforced all the way through?

I also skim the last page for a graph: is there a clear linearisation step and treatment of intercept vs. gradient? If a resource claims “practical,” I look for risk assessment language and a results table with units in headers only. When something passes, I’ll still generate two or three parallel questions at easier/harder levels to see where it breaks. If you want to spin up a quick variant set to test these checks, you can mock one in minutes with a blank draft and stress‑test before copying classwide.

Last Tuesday my Year 12s kept using time of flight from vertical launch on a 30° problem. Here’s the flow that fixed it. Objective: resolve projectile motion into horizontal and vertical components, apply SUVAT vertically, and link flight time to range. Worked example: “A ball is launched at 20 m s⁻¹ at 35° from ground level; find maximum height and range (g = 9.81 m s⁻²).”

• Starter (6 min): Two mini whiteboard prompts: identify u_x and u_y from u=20 m s⁻¹ at 35°. One misconception checkpoint on mixing sin/cos.
• Main I (15 min): Model component method. Annotate the worked example; highlight independent axes. Students complete max height.
• Main II (15 min): Pairs tackle range; fast finishers add launch from 1.2 m platform.
• Formative check (12 min): 4-question hinge: angle up, angle down (cliff), given-answer “show that” with 3 s.f., and a graph of y vs. t labelled.
• Plenary (7 min): “Which assumption mattered most?” (no air resistance vs. level ground). Exit ticket: one sentence + one equation they’ll remember.

I built the slides and variants in ClassPods in under ten minutes; if you want to try, you can start from a blank pack here and paste in your board’s data sheet reminders.

Two Fridays ago my Year 13s wrote limp answers on photoelectric effect because they jotted facts, not an argument. This is the 6‑mark structure I now paste under the question so expectations are plain and markable across AQA/OCR/Edexcel.

Use this rubric under any extended response:

• Physics accuracy (0–2): 0 = major errors or missing law; 1 = core law named but misapplied; 2 = correct principles and relations (e.g., E=hf−ϕ) with consistent units.
• Method and structure (0–2): 0 = list of facts; 1 = partial chain (some links missing); 2 = coherent sequence from assumption to conclusion, referencing given data.
• Use of data/representation (0–1): cites data booklet values, draws/reads graph/diagram appropriately, shows substitutions.
• Communication (0–1): correct symbols, vector notation where needed, significant figures and unit handling match the question’s demand.

Teacher note: Add a one-line board cue: “Command word = Explain/Derive/Show that.” I keep this as a slide/handout and tweak the examples in ClassPods; if you want a quick editable starting point, spin a draft and drop this rubric in a new lesson pack.

In March mocks my bilingual Year 13s stumbled on “hence”/“therefore” in a derivation even though they knew the physics. For mixed-language classes I pre-teach a tiny glossary (derive, hence, resolve, proportional), use dual-language stems (“Therefore, … / Por lo tanto, …”), and pair diagrams with one annotated sentence. I also script one model answer they can shadow-write, then gradually remove scaffolds.

Pacing: I run the same lesson arc slower in September (more hinge checks, fewer numbers) and tighten it by January with mixed MCQ + short explain combos. For homework I set one board-style long question, one quick retrieval grid, and one uncertainties or units mini. For revision, I convert our best hinge questions into spaced starters and add a practical planning prompt weekly (identify variables, risks, and graph). I’m not precious about tools, but I do appreciate how cleanly ClassPods lets me swap contexts or simplify language without rebuilding. If you need to check what that’ll cost your department, the details live on the pricing page so you can make the case.