How I build DP Physics lessons that survive Paper 2

Two weeks before autumn mocks, my DP2 mechanics class melted down over a “show that” problem on power and efficiency. They knew the physics, but the structure—stating assumptions, unit consistency, and a clean final line—wasn’t there. That’s where non-IB packs often trip us. They’re on-topic but off-curriculum: AP-style derivations without command terms, or A-level mark schemes that expect different rounding and don’t stress uncertainty propagation.

Inside IB · DP, alignment means a few concrete things: command terms drive the cognitive demand; data-based questions are common; uncertainty and graphical reasoning appear beyond the token first unit; and Paper 1 versus Paper 2 expect different habits (no calculator fluency versus set-out working). SL and HL also need slightly different depth—HL extensions can’t be tacked on as a footnote.

When I sanity-check a resource, I look for IB phrasing (“deduce,” “hence,” “determine”), clear unit treatment, and worked examples that model tidy reasoning. If you want a quick scan of science materials, you can browse what colleagues have shared in the community library and decide what suits your cohort.

Last Tuesday my DP1 group blitzed vectors, but three students gave “prove” answers to a “state” question and lost time. That’s my cue to audit the resource, not the kids. I run the same checks every time: do the command terms match the required rigor, does the numeric work reflect IB rounding and sig figs, and is uncertainty treated as a living thread rather than a single starter lesson?

Concrete checks you can run in five minutes: scan the verbs—“explain” and “outline” need sentences, “determine” demands a calculation, “deduce” requires reasoning from given data; check units and constants (is g = 9.81 m s⁻² or 9.8, and is it consistent?); verify that vector notation is clear (î, ĵ, or components with signs); look for a data-based item with graph interpretation and uncertainty bars; compare an SL task’s cognitive load against HL expectations.

If a pack passes those, I’ll keep it. If not, I’ll adapt the phrasing and add a quick uncertainty prompt. It helps that I can spin up and tweak a draft in ClassPods and then layer my own questions on top.

Week 6 of Term 1, DP1 Mechanics. My class could chant “components” but still projected mg the wrong way on ramps. Here’s the lesson that fixed it and held up to Paper 2 marking. I set it up in ClassPods once and reuse it with tweaks each year.

• Objective: Determine frictional force and acceleration for a block on a rough incline; communicate working consistent with IB command terms.
• Starter (10 min): Two Paper 1–style MCQs on components and normal reaction; no calculator; mini whiteboards.
• Main task (35 min): Worked example: a 4.0 kg block on a 30° incline with μ = 0.20. Draw FBD, resolve mg into parallel/perpendicular, write ΣF∥ = ma. Calculate friction (limiting vs kinetic) and a. Students then tackle a paired variant at 25° with a different μ.
• Formative check (10 min): One “show that a ≈ 2.1 m s⁻²” prompt with an extra significant-figure trap; quick peer mark using the rubric language.
• Plenary (10 min): “Deduce” question: if μ increases, what happens to a? Justify with components, not vibes.

If you want to clone this flow and drop in your own numbers, you can spin one up in minutes here.

Friday’s DP2 clinic on circular motion proved a point: my strongest students still lost marks to messy communication. I now staple this rubric to any multi-step calculation sheet. Feel free to paste it straight into your next pack.

Rubric (0–6):
6: Fully correct physics, clear FBD/equations, consistent units/sig figs, explicit assumptions; reasoning supports “hence/deduce” steps.
5: Correct method and result; minor notation/slip; units and sig figs mostly consistent.
4: Method sound but incomplete explanation or one substantive arithmetic/rounding error; units present.
3: Partial method; key step missing or misapplied; limited justification.
2: Fragmented work; equations recalled but not applied; units/sig figs largely missing.
1: Minimal attempt; unrelated equations; no units.
0: Blank/irrelevant.

Command-term prompts to mirror IB style: State…, Determine…, Deduce…, Show that…, Hence calculate…, Comment on the reasonableness…

Teacher note: For SL, accept fewer algebraic lines if the reasoning is explicit; for HL, insist on a clearer variable definition line and uncertainty where data are provided. I keep the rubric as a reusable block in ClassPods.

In my bilingual DP1 cohort, Wednesday’s exit tickets showed understanding but wobbly language: “prove” crept in where “state” belonged. I now pre-teach a tiny glossary (state/outline/describe/explain/determine/deduce) with sentence stems in both languages and pin it to the board. During ramp problems, I pair a confident speaker with a quieter one and script think-alouds: “We resolve mg into components; therefore, we deduce…”

Pacing: I run the same lesson for SL and HL but add one HL extension—variable μ or a follow-up with energy. For strugglers, I keep one no-friction practice set and a picture-only FBD scaffold. For homework, students complete two Paper 1 MCQs and one Paper 2 short response with the rubric on top; next lesson opens with a 6-minute re-mark.

If you’re trying to budget department-wide templates and shared packs, our head of science wanted transparent costs, so we reviewed what’s public and the paid tiers on the pricing page. ClassPods has been worth it for me because I can keep SL/HL forks tidy.