How to Use Past Papers for Computer Science Revision

A past paper only helps if you mark it against the official mark scheme and use the lost marks to decide what to study next. The method I recommend has four steps: attempt a paper under timed conditions, mark it line by line, log why each mark was lost, then redo those questions a few days later. Doing ten papers without marking them honestly teaches less than doing three with this loop.

Key takeaways

Mark every paper with the official mark scheme, because it shows exactly what earns credit and what the examiners accept.
Log each lost mark with a reason, such as misread the question or wrong loop bound, since the reasons show patterns that topics do not.
Redo the weak questions after a few days. Re-reading the model answer is not the same as being able to write it.
Use examiner or chief reader reports where they exist, because they list the errors real students made.
Do some papers under exam timing and without notes, and others untimed to study a topic.

Why do past papers often not improve your grade?

The usual mistake is treating a paper as a test to finish, not as feedback to use. A student does a paper, glances at the answers, feels they "get it" and moves on. The next paper repeats the same errors. A paper is only useful if it changes what you do afterwards.

Official mark schemes are the key. For IGCSE Computer Science 0478, Cambridge publishes a past papers page with question papers and mark schemes. A mark scheme from the May/June 2024 Paper 2 shows how marking works: examiners award credit for correct or valid answers, marks are not deducted for errors, and pseudocode and programming answers are generally credited for logic rather than strict syntax.

What is the four-step method?

Attempt it properly. Use the time limit, no notes, and the same tools you will have in the exam. Stop when the time is up and mark the unfinished part separately.
Mark it line by line. Use the official mark scheme and be strict. Give yourself a mark only for what is written on the page, not for what you meant.
Log every lost mark. In a table, write the question, the marks lost, and a short reason. Use the same category names each time so patterns show up.
Redo after a gap. After two or three days, rewrite the weak answers from a blank page. If you can do them cold, they are learned.

Here is an example of an error log, with made-up entries to show the format:

Question	Marks lost	Reason	Fix
Q6	2	Loop ran one time too many	Check the loop bounds with the first and last value
Q9	3	Did not read "state and explain"	Underline command words before answering
Q12	1	Did not know the term	Add to the vocabulary list and test it on Friday

How do examiner and chief reader reports help?

They tell you which mistakes are common, so you can avoid them before you make them. The College Board's 2025 Chief Reader report for AP CSP lists errors per question, for example describing a syntax error when the question wanted a logic error. The scoring guidelines then show what earned the point.

Read the report after you have attempted and marked the matching paper, not before. The errors will make more sense once you have made a few of your own. Check whether your exam board also publishes examiner reports for your course, and read them the same way.

How many papers should you do, and when?

Quality matters more than count, and the right number depends on how many papers exist for your course and how much time is left. As a guide, here is an example schedule of mine for the last six weeks before an exam. It is a suggestion, not an official figure.

Weeks 1 and 2: do individual questions by topic, untimed, to learn the patterns.
Weeks 3 and 4: do one timed paper a week and run the full four-step loop.
Weeks 5 and 6: do two timed papers a week, redo the weak questions, and stop learning new topics three days before the exam.

Keep a few of the newest papers back until the end, so your last timed attempt is a fresh one. If you want help marking and building your error log, my school computer science lessons include it, and you can book a free call to try one.

What mistakes should you avoid with past papers?

Looking at the mark scheme while you work. You will recognise answers instead of recalling them.
Marking generously. If the scheme needs a specific word and you wrote a vague one, that is a lost mark.
Doing only your favourite topics. Papers should show you where you are weak.
Using an old specification without checking. Courses change. For 0478, check the syllabus years on the paper against the one your school teaches, since rules like calculators and language use can differ between syllabuses.
Skipping the redo step. This is where learning happens.

Frequently asked questions

How many past papers should I do before an exam?

There is no official number. Do enough to cover every topic and to run the full marking and redo loop several times, and use the newest papers last. Three papers done carefully beat ten that were never marked.

Should I time every past paper?

No. Do some questions untimed to learn a topic, then move to timed, no-notes papers closer to the exam so you practise pacing.

Where do I find official mark schemes?

For Cambridge IGCSE Computer Science 0478, the Cambridge International website has a past papers page with question papers and mark schemes. For AP courses, the College Board publishes scoring guidelines and reports on AP Central.

How to Use Past Papers Properly: A Revision Method for Computer Science Exams