EducateAIBlog
Exam Prep

How to Study From Past Papers: a Cited Q&A + Weak-Topic Deck Workflow

EducateAI Editorial TeamEducateAI Editorial Team
··7 min read·Updated
Printed exam paper, annotated notes, and laptop on a study desk

Past papers are useful because they do two jobs at once.

They show you what the course actually asks, and they show you what you still cannot retrieve when time pressure is real.

That makes them better than generic revision when the exam is close. Generic revision keeps the course broad. Past-paper work makes it narrower.

The strongest workflow looks like this:

past paper → source check → cited answer → weak-topic deck → retest

Exam feedback loop

The past-paper diagnosis loop

Each attempt should produce a smaller, better-targeted set of topics to review.

  1. Source pack

    Keep the relevant papers, notes, slides, and model answers together.

  2. Question patterns

    Label recurring tasks, traps, and topics across papers.

  3. Cited answer check

    Verify each missed answer against the assigned course material.

  4. Weak-topic deck

    Turn recurring misses into small, source-linked prompts.

  5. Timed retest

    Try a similar question again and feed remaining misses into the next loop.

Next cycle: return to Source pack

A repeated miss returns to the source pack instead of becoming an unverified card.

Figure: A past paper is most useful when every miss becomes a verified correction and a later retest.

Step 1: Build one source pack before you start

Gather the material you will use to verify answers:

  • lecture slides
  • textbook chapters or PDFs
  • your notes
  • sample solutions if they exist
  • the past papers themselves

Do not jump between ten folders while you are trying to diagnose weak areas. Put the relevant files in one course workspace first.

Step 2: Use the past paper to find patterns, not just marks

As you read through past papers, label the questions by type:

  • definition or rule recall
  • process explanation
  • comparison
  • application or worked example
  • interpretation of a case, graph, or passage

This matters because weak topics often hide behind weak question types. You may not be bad at “the chapter.” You may be bad at explaining a process from memory or applying a rule under time pressure.

Step 3: Check answers against your own course files

Once you miss a question, do not jump straight to a generic explanation.

Go back to the notes, slides, or PDF your course is built on and answer:

  • where is the relevant explanation?
  • how is the concept phrased in the source?
  • what example or rule does the course keep using?

If you use a cited Q&A workflow here, the goal is simple: keep the explanation tied to the assigned material instead of drifting into a general answer that sounds right but does not match your course.

Worked example: an error log for average speed

The question and attempted answer below are original illustrations, not a past-paper extract or a real student's work. Use your own question number and course reference when filling in your log.

Question A: A runner covers 120 m in 30 s, then another 120 m in 60 s, without pausing. What is the average speed for the whole journey?

Time spent on each 120 m leg

  • First 120 m leg30 s
  • Second 120 m leg60 s
Question and source
Practice question A below Step 3. Definition check: OpenStax, University Physics Volume 1, section 3.2, equation 3.5, linked below. No exam marking scheme is supplied.
First attempt
First part: 120 / 30 = 4 m/s. Second part: 120 / 60 = 2 m/s. Then: average speed = (4 + 2) / 2 = 3 m/s.
Failed step
I gave both speeds equal weight, although the runner spends twice as long on the slower part. The two part-speeds are correct; combining them this way is the error.
Checked correction
Average speed = total distance / elapsed time = 240 m / 90 s = 8/3 m/s, approximately 2.67 m/s. At 3 m/s for 90 s, the runner would cover 270 m, which contradicts the stated 240 m.
Next practice
Attempt question B below without looking at this entry. Write total distance and total time before calculating.
Unresolved check
I have not attempted B yet. Record its working and check whether I again averaged the two speeds directly.
The bars show elapsed time from zero to 60 seconds, not speed. The slower leg lasts twice as long.

The definition comes from OpenStax section 3.2, equation 3.5. The numerical questions here are our own examples.

Question B: A runner covers 120 m in 20 s, then another 180 m in 60 s, without pausing. Find the average speed for the whole journey. Try it before opening the answer.

Check question B

Total distance = 300 m. Elapsed time = 80 s. Average speed = 300 / 80 = 3.75 m/s. Averaging the part-speeds, 6 and 3 m/s, would give 4.5 m/s. That would imply 360 m in 80 s, not 300 m.

If you remembered the definition but chose the wrong calculation, practise another checked problem. If you forgot the definition, add a small recall card for it. Check the reasoning in your next attempt before deciding what belongs in the deck.

Step 4: Turn misses into a weak-topic deck

Your deck should not become a second copy of the whole course.

It should become a compact record of what still breaks.

Good weak-topic cards usually come from:

  • questions you missed completely
  • answers that were vague or incomplete
  • recurring traps across multiple past papers
  • definitions or examples you keep mixing up

What to put on a card:

  • one clear prompt
  • enough context to know what the question is asking
  • a concise answer you can actually check
  • a source reference or example if that helps you stay anchored

Step 5: Re-test under exam conditions

The point of the deck is not to feel organized. The point is to improve retrieval under constraint.

So after you build the weak-topic deck:

  1. review the cards
  2. run a timed block of past-paper questions again
  3. see which weak topics still fail
  4. tighten the deck again

If the same topic keeps failing, the problem is often the card design. Split it. Add the missing example. Make the question more specific.

A Simple Weekly Version of This Workflow

If your exam is still a few weeks away, one weekly loop is enough:

  • Day 1: run one past-paper section
  • Day 2: verify misses against notes and PDFs
  • Day 3: create weak-topic cards
  • Day 4: review the cards
  • Day 5: retest on a similar question set

If the exam is very close, use a shorter cycle and focus only on the highest-yield topics.

Common Mistakes

  • doing past papers without checking the source material afterward
  • building a huge deck from everything instead of from weak topics
  • reviewing answers passively instead of answering again from memory
  • treating every mistake as equal instead of prioritizing recurring misses
  • switching tools constantly instead of keeping one clear exam loop

Bottom Line

Past papers are not just for self-testing at the end.

They are one of the best ways to decide what deserves review in the first place.

Use them to expose weak topics. Check those topics against your course files. Then build a smaller deck from what still breaks.

If you want to connect this workflow to the rest of your exam system, continue with:

Past-paper workflow

Turn exam mistakes into a tighter review loop

Use your own notes, slides, and PDFs to verify answers, then build weak-topic decks that reflect what still fails under pressure.

See study workflows
Last Updated:

Was this article useful?

One click helps us improve future guides.

Exam PrepPast PapersStudy WorkflowsFlashcardsPDF Study

Related Articles