Worksheets and drills are the better tool for building fluency in a narrow, well-defined skill; projects are the better tool for transfer — applying that skill to a new, real situation. Treating them as rivals, where one is "modern and good" and the other is "old-fashioned and bad," gets the comparison backwards. They do different jobs, and most strong KS3 teaching uses both, in sequence, not one instead of the other.

The actual difference in what each one trains

A worksheet asks a student to do the same kind of question many times, usually with immediate feedback on whether the answer is right. That repetition is exactly what spaced, retrieval-based practice research says builds fluency and long-term recall — the same principle behind flashcards and times-tables drills. The skill being built is narrow and specific: recall a fact, apply a fixed procedure, recognise a pattern quickly.

A project asks a student to hold several things in mind at once, decide what matters, make choices with no single right answer, and produce something real at the end. It's a poor way to drill a multiplication fact. It's a strong way to find out whether a student can actually use multiplication when a real problem — working out material costs for a garden bed, say — needs it and doesn't announce itself as a maths question.

At a glance:

Worksheets / drills Projects
Best for Fluency, recall, a fixed procedure Transfer, connecting ideas, sustained motivation
Feedback loop Immediate, right/wrong Slower, iterative, often no single right answer
Time needed Minutes, regularly Days to weeks
Assessed on Accuracy and speed Process and output together
Risk if overused Fluent but can't apply it Enthusiastic but shaky on fundamentals

When to reach for a worksheet

Three signs a worksheet (or an equivalent short drill) is the right call:

  1. The skill is discrete and well-defined. Times tables, common spelling patterns, balancing simple equations, recalling command words in an exam question. There's a right answer, and getting faster at producing it is the whole goal.
  2. The student hasn't yet automated something they'll need automatically later. A student still counting on fingers for 7×8 will struggle in a project that needs quick arithmetic mid-flow — the project gets bogged down in the thing that should have been automatic.
  3. You need to know exactly what's shaky, fast. A worksheet is diagnostic in a way a project rarely is — a page of fraction problems shows precisely which fraction skill is missing. A project that goes wrong could be wrong for a dozen reasons.

Example: a student who mixes up "there/their/they're" needs targeted, repeated practice noticing the difference — not a creative writing project, which will let them dodge the pattern by avoiding it. Example: recalling the electron configuration rules in chemistry benefits from short, repeated retrieval far more than from a single big project that touches them once.

When to reach for a project

Three signs a project is the right call:

  1. The goal is applying several skills together, not practising one in isolation. Real problems don't come labelled "this is a fractions question" — they come as "we have £40 and need to buy enough paint," which requires noticing that fractions or ratios are even relevant.
  2. Motivation is the actual blocker, not the skill itself. A student who understands a topic but has stopped engaging with it often re-engages through ownership — choosing what to build, what to investigate — in a way a tenth worksheet on the same topic won't achieve. See helping your child choose a project topic.
  3. You want evidence the student can transfer knowledge to something unfamiliar, not just repeat a pattern they've seen before. This is the strongest argument for projects and the weakest spot for worksheets — see the research summarised in is project-based learning effective?.

Example: a student who can solve percentage problems on a worksheet but has never had to decide when a real situation calls for a percentage calculation benefits from a project like planning a budget travel itinerary, where the maths is one ingredient among several. Example: a student who knows plant biology facts individually but hasn't connected them benefits from designing an actual garden bed, where soil, light, and species all have to work together — see designing a school garden project.

The mistake in both directions

All-worksheets, no projects produces a student who is fluent but brittle — fast and accurate on familiar-shaped questions, and stuck the moment a problem doesn't announce which skill it wants. This is a common complaint about heavily drill-based KS3 teaching: strong test scores on narrow formats, weaker performance the moment a question is phrased unusually.

All-projects, no worksheets produces the opposite problem — a student who's used to reasoning about real, messy situations but doesn't have the underlying fluency to execute quickly, so every project takes three times as long as it should because basic steps aren't automatic. What is project-based learning? is explicit that PBL was never meant to replace fluency work — it was meant to give fluency somewhere real to go.

A simple rule of thumb

If a student is guessing at what to do, that's usually a fluency gap — reach for a worksheet or targeted drill. If a student knows how to do several things but doesn't know when to reach for which one, or has stopped caring, that's usually a transfer or motivation gap — reach for a project. Most terms need both, at different points, often in the same week.

FAQ

Are worksheets bad for learning?

No. Worksheets and other forms of repeated practice are the right tool for building fluency in a discrete, well-defined skill — times tables, spelling patterns, algebraic manipulation. The research on spaced, repeated practice is strong. The mistake is using them for everything.

Is project-based learning always better than direct practice?

No — it depends what's being learned. Projects are stronger for transfer (applying knowledge to a new, messy situation), motivation, and connecting ideas across subjects. They're a poor tool for drilling a fact or procedure to automaticity, which is what worksheets do well.

How do good KS3 teachers actually combine the two?

Typically fluency work first — short, regular practice on a specific skill — then a project that requires using that skill in a real context. The worksheet builds the tool; the project is where the student finds out the tool is actually useful.