Book a lesson
HomeAcademicExam Strategy
GCSE Computer Science · Exam Technique

Exam Strategy Sessions

Learn how to approach GCSE Computer Science exam questions — structuring answers, avoiding common mark-losing mistakes, and using your time effectively under pressure.

Book an exam sessionGCSE Exam Rescue

What this covers

How OCR GCSE papers are structured and timed
Command words: what evaluate, explain, and describe actually mean
Long answer technique for 4, 6, and 8-mark questions
How to approach pseudocode and algorithm questions
The most commonly lost marks — and how to avoid losing them
Miss ICT Academic Pathway · Learn Practise Apply Master

Why exam technique matters as much as content knowledge

Students who know the content but do not know how to answer the questions lose significant marks. GCSE Computer Science exam questions have a very specific structure — knowing the pattern gives you a systematic advantage.

Command words change everything

Explain is not the same as describe. State is not the same as justify. OCR mark schemes reward specific types of response for each command word. Using the wrong approach loses marks even when the knowledge is correct.

Structure before writing

For questions worth 4 marks or more, plan your answer before writing. 30 seconds of planning prevents the most common mistake — writing too much irrelevant content and too little focused content.

The answer method — use this every time

How to answer any GCSE CS questionRead the command wordState · Describe · Explain · Evaluate · CompareCount the marks available1 mark = 1 point. 4 marks = 4 separate points.Plan before writing30 seconds planning saves minutes rewritingPoint + developmentMake the point, then explain WHY or HOWCheck: do you have enough points?Count your distinct points vs marks available

How to answer longer questions

Questions worth 4 marks or more need a structured approach. Unstructured writing scores poorly regardless of how much you know.

1
Identify the marks available.
4 marks usually needs 4 distinct points or 2 well-developed points. 6 marks needs 3 developed points. Plan before writing.
2
Use the mark scheme language.
OCR mark schemes use very specific vocabulary. Using terms like "overflow", "decomposition", "ASCII" precisely — where relevant — earns marks.
3
One point per sentence.
Write clearly. "The system uses encryption [point]. This means data is converted into a form that cannot be read without a key [development]." Point + development = 2 marks.
4
Conclude evaluate questions.
For evaluate questions, always state which option is better (or neither) and justify your conclusion. An unsupported conclusion earns 0.

Pseudocode and algorithm questions

These questions are high-value and very predictable. Approach them methodically.

Trace table questions

Create a table with column headings for each variable. Fill in values row by row, one instruction at a time. Never skip a line. Show every intermediate value — partial marks are available.

Write your own pseudocode

Read the question carefully. Plan the logic before writing. Use IF, FOR, WHILE, FUNCTION, RETURN correctly. The examiner cares about logical structure, not perfect syntax.

Common pseudocode mistakes

Using = instead of ← for assignment · Missing ENDIF · Confusing FOR and WHILE · Not showing the RETURN in a function · Using Python syntax instead of OCR pseudocode

Time management in the exam

GCSE Computer Science papers are time-pressured. Spending too long on early questions leaves insufficient time for higher-mark questions.

Paper 1: 1h 30m

90 marks. 1 mark per minute. Do not spend more than 3 minutes on a 2-mark question.

Start easy.

Complete questions you are confident about first. Return to uncertain ones later with remaining time.

Marks per minute.

A 6-mark question deserves 6 minutes. A 1-mark question deserves 1 minute. Keep watching the clock.

Leave nothing blank.

Even a partially correct answer may earn a mark. Never leave a question unanswered — especially definition and identify questions.

Ready to put this into practice with an examiner?

Knowing the technique is one thing. Applying it under exam conditions, with an examiner watching and correcting in real time, is what builds the habit. One session can change how your child approaches every question on the paper.

Book an exam sessionGCSE Exam Rescue Intensive
✔ OCR GCSE examiner  ·  ✔ DBS checked  ·  ✔ UK wide online  ·  ✔ Evenings & weekends

Frequently asked questions

How long is the GCSE Computer Science exam?

Paper 1 (computational thinking) and Paper 2 (written exam) are each 1 hour 30 minutes. Both are worth 80 marks.

What topics are on each paper?

Paper 1 focuses on computational thinking, algorithms, programming, and problem solving. Paper 2 covers computer systems, networks, databases, ethics, and data representation.

Can I use a calculator?

No. GCSE Computer Science exams do not allow calculators. Binary and hex conversions must be done by hand — which is why practising the method is essential.

My child has left revision late. Is exam technique still worth focusing on? +

Yes — genuinely. Exam technique can be improved in a single focused session. Students who learn the command word method and the point-plus-development structure in their final weeks consistently feel more in control in the exam room, even when content knowledge is incomplete. One session is worth it.

Does this help if my child hasn't finished revising all the content? +

Yes. Many students lose marks on topics they have revised because they don't answer the question correctly. Learning how to read command words and deploy the marks-available strategy improves scores across every topic — including ones where knowledge is still developing.

Related resources

Theory

Algorithms Explained

Algorithms for the exam — with trace table practice.

Practice

Mock Exam Walkthroughs

Apply your strategy to full past-paper style questions.

Intensive

GCSE Exam Rescue

Small group intensive — final preparation before the real papers.

1-to-1

GCSE CS Tutor

Personal exam technique coaching from an OCR examiner.