What Works for My Year 10s in IGCSE Biology

Last Thursday, my Year 11s stalled on a seemingly easy graph about enzyme activity. They could plot points, but two forgot axis labels with units and one chose a bar chart. That’s the issue: “good science” isn’t always IGCSE-fit. The spec nudges students toward precise command terms—state, define, describe, explain, suggest—and expects them to handle data in the way the mark scheme rewards. Lots of general resources teach concepts, but they miss those habits.

Inside IGCSE, I watch for three fit issues. First, vocabulary: “control variable” vs “controlled variable,” “energy transfer” vs “energy transformation.” Second, assessment style: structured questions that ladder from recall to application, and Paper 6/5 style practical reasoning. Third, quantitative bits: percentage gain/loss, magnification, food chain energy calculations, units and significant figures that match the scheme. When I vet something, I skim the verbs, scan for data handling, and ask: would this help on Paper 2/4, not just in a lab notebook?

When I’m hunting exemplars, I start with science items in the community library because I can sort quickly for data-led practice and command-term variety; you can browse the same pool in the science library.

In Week 3 of Term 2, I marked a mini-mock and realised half my class treated “describe” like “explain.” That night I built a quick gatekeeper for any new sheet or slide deck. It’s not fancy—just five checks that stop me from teaching the wrong habits.

Here’s what I do: 1) Highlight all command terms and see if they map to the IGCSE list (state/define/describe/explain/suggest). 2) Look for at least one question that moves students from knowledge to application using unfamiliar data (think a new enzyme graph or unseen food web). 3) Verify graph conventions: axes labelled with units, sensible scales, a line graph for continuous data. 4) Check a calculation appears where it should—percentage change in mass, magnification, or rate with units. 5) Skim for practical reasoning that mirrors Paper 6/5: control variables, sources of error, improvements.

If a resource fails two of those, it doesn’t make the lesson. When I’m short on time, I spin up a one-page check with those items baked in—you can prototype a quick version here—and I’ll keep that in ClassPods so my future self isn’t reinventing the wheel.

On 9 May, Period 2, I taught osmosis with a group that ranges from 5s to strong 8s. The objective was tight: define osmosis, predict water movement across a membrane, and calculate percentage change in mass from data. The worked example anchored everything: potato cylinders in sucrose solutions (0.0–1.0 M), presented as an unfamiliar results table and a scatter graph prompt.

• Starter (8 min): Two images—plant cell in distilled water vs concentrated solution. Students “state” and “describe” differences using the terms water potential and turgid/flaccid. Quick cold-call.
• Main input (12 min): I model the worked example: pick one cylinder, calculate percentage change, plot two points, and narrate why it’s a line graph. Class notes include units and the equation.
• Guided practice (18 min): Pairs finish plotting, draw the best-fit line, infer the sucrose concentration where mass change is zero (isotonic). Three hinge questions target misconceptions.
• Formative check (12 min): Mini structured question: (a) Define osmosis (2). (b) Explain water movement for 0.8 M cylinder (3). (c) Suggest one improvement to reduce error (2). Peer mark using my rubric.
• Plenary (10 min): Exit ticket: one “explain”, one “suggest” tied to the graph.

If you want a pack built around that worked example, you can generate a clean, editable version here and keep it in ClassPods for your next rotation.

Two Mondays ago, my Year 11s peer-marked a respiration question and the room went quiet in that productive way. What helped was a simple rubric tuned to Paper 2/4 style. Paste this under any 4–6 mark item that climbs from describe → explain → suggest.

Rubric bands
6 marks: Accurate science throughout; all required points made in a logical sequence; uses precise terms (e.g., diffusion, osmosis, active transport) and includes data reference/units where relevant; addresses command term fully; no major omissions.
4–5 marks: Mostly accurate; most key points present; some sequencing; occasional vague language; partial data reference; command term mostly addressed.
2–3 marks: Basic recall; misses links; limited or incorrect vocabulary; no data reference; command term poorly addressed.
1 mark: Fragmented ideas; significant inaccuracies.
0: No creditable response.

Common credit points (adapt per topic): define key term; identify trend; link cause to effect; refer to figure/table with units; state control variables; suggest realistic improvement.

I keep this as the first comment slide so students can see it while they write—you can rough out your own version in a minute here and drop it next to your question.

Last half-term, my Year 10 set included four students new to English-medium science. I built a dual-language word wall (osmosis, dilute, concentrated, membrane), sentence stems for command terms (“Explain means give a reason because…”) and allowed labelled diagrams as part of an answer when appropriate. For homework, I gave short bilingual glossaries tied to next lesson’s verbs so students could rehearse language before content. ClassPods holds my decks and glossaries so I can share the same slides with the EAL co-teacher without fuss.

Pacing-wise, I treat the two-year IGCSE curve as spiralled: revisit transport during cells, return to enzymes when we hit digestion, and thread in a Paper 6/5 practical-style question every second week. For revision, I move to retrieval: 8–10 short items mixing command terms, one graph, one calc, and one practical improvement suggestion. Homework mirrors the exam: one structured question, one multiple-choice page, 12–15 minutes total.

If budget is part of the conversation this year, I found it helpful to skim options and work out what I can reasonably centralise and what I’ll continue to homebrew; the breakdown that shaped my decision is here, and I still keep my core in ClassPods so it’s all in one place.