How to Revise Properly

What actually works in revision, based on evidence rather than on what feels productive, plus exam technique worth several grades.

Most students revise by reading their notes again, highlighting things, and copying work out neatly. All three of those feel productive and almost none of the effect survives to the exam. This page describes what actually works, and it is based on decades of evidence from cognitive psychology rather than on what feels comfortable.

The one idea that matters most

Retrieval beats review

Trying to recall something from memory strengthens that memory far more than reading it again does. This single finding is the most robust result in the whole of learning research, and almost nobody acts on it.

Practically, that means: read a page once, close it, and write down everything you can remember. Then open it and see what you missed. The gap between what you read and what you can produce is the only thing that matters, and rereading never shows it to you.

This feels much worse than rereading, because you are confronted with what you do not know. That discomfort is the mechanism working.

The five techniques that are worth your time

1. Retrieval practice

Test yourself, from memory, without your notes.

  • Do the ten question check on every topic on this site
  • Write exam answers before looking at the mark scheme
  • Cover a definition, say it out loud, then check
  • Use flashcards, but say the answer before flipping

2. Spaced practice

Revisit material after a delay rather than all at once.

A workable schedule for any topic:

  • Learn it today
  • Retrieve it after one day
  • Retrieve it after three days
  • Retrieve it after one week
  • Retrieve it after one month

Each retrieval takes a few minutes. Four spaced sessions of ten minutes beat one session of forty by a very large margin, and the difference grows the longer the gap to the exam.

3. Interleaving

Mix topics rather than blocking them. Instead of two hours on networks, do forty minutes on networks, forty on algorithms and forty on data representation.

Blocking feels smoother because you stay in one mode. Interleaving is harder and produces better retention and better ability to tell similar problems apart, which is exactly what an exam demands.

4. Elaboration

Ask why and how, not just what.

  • Why does virtual memory make a computer slow?
  • How does a firewall differ from anti malware, and why do you need both?
  • Why is RISC used in phones rather than CISC?

Answers to why questions stick because they connect to things you already know. Isolated facts do not.

5. Concrete examples and practice questions

Do questions. Then do more questions. Then mark them honestly against the mark scheme.

What to stop doing

  • Rereading notes. It produces a strong feeling of familiarity and very little recall.
  • Highlighting. It feels like processing and is close to passive.
  • Copying work out neatly. This is handwriting practice.
  • Watching videos without pausing to answer anything.
  • Making beautiful revision materials you never use.
  • Revising the topics you like. Your comfort is not a good guide.

Building a plan that survives contact with reality

  1. List every topic on the specification. This site is organised by specification point precisely so you can use it as a checklist.
  2. Rate each one honestly, red, amber or green, based on whether you could explain it to somebody now.
  3. Start with red. Not with what you enjoy.
  4. Book specific sessions, not vague intentions. "Tuesday 5 to 5:40, networks" happens. "Do some revision this week" does not.
  5. Every session ends with retrieval. Close everything and write what you remember.
  6. Re-rate weekly, and let the ratings decide next week's sessions.

Exam technique, which is worth several grades

  • Underline the command word first. Describe, explain, compare, evaluate and justify all want different things.
  • Count the marks. Four marks means four separate creditworthy points. Write four.
  • Explain means because. Every point needs a reason or a consequence attached.
  • Compare means both. Say what each one is like, not just what one is like.
  • Discuss and evaluate mean both sides plus a conclusion. A one sided answer is capped in the mark scheme however correct it is.
  • Show working in calculations, with units on every line. Method marks are real marks.
  • Answer the question in front of you, not the similar one you revised.
  • Leave nothing blank. A blank is a guaranteed zero and a rough attempt frequently is not.
The single biggest improvement available to most students

Write answers out fully, from memory, and mark them against the real mark scheme. Recognising a correct answer is a completely different skill from producing one, and only the second is tested.

A realistic weekly pattern

You do not need four hours a night. You need consistency.

WhenWhatHow long
Monday to ThursdayOne topic: read, then ten question check, then five exam answers40 minutes
FridayRetrieval only, on the topics from the past week and the past month20 minutes
SaturdayOne full past paper, timed, or half a paper45 to 90 minutes
SundayMark the paper, list every dropped mark and why30 minutes

That is under five hours a week, and done from January it is worth more than any amount of panic in May.

If you are behind

Do not try to cover everything. Cover the highest value things:

  1. The topics that appear on every paper: data representation, algorithms, programming fundamentals, networks
  2. The command words, so you stop losing marks you already know the content for
  3. Past paper questions rather than notes, because they show you what is actually asked

Fixing the way you answer questions is faster than learning three more topics, and it applies to every question on the paper.