Start with the Correct Specification
Find out whether the course follows OCR, AQA or Edexcel and use the current specification as a checklist. Divide it into areas such as algorithms, programming, data representation, computer systems, networks, cybersecurity and databases. Mark each topic red, amber or green based on how confidently you could explain it without notes.
This produces a realistic plan and stops revision becoming repeated reading of topics that already feel comfortable.
Replace Rereading with Retrieval
Close the book and try to recall an answer. Use short questions, flashcards, blank-page summaries and verbal explanations. Then check the answer and correct it. The checking stage matters: practising an inaccurate explanation simply makes the mistake more familiar.
For a topic such as networks, ask what a device does, why it is used and how two related terms differ. This is more useful than copying a full page of notes.
Keep Programming in the Plan
Programming is a practical skill. Read short programs, predict their output, trace variables and write small solutions regularly. A focused 20-minute task can be more useful than a long session completed once a month. When code fails, read the error message, isolate the smallest problem and test one change at a time.
Use Exam Questions Deliberately
Begin with topic questions before moving to mixed papers. Complete a question without notes, mark it carefully and record why marks were lost. Was knowledge missing, terminology vague or the question misread? The correction should address the cause.
Do not memorise a mark-scheme sentence without understanding it. Questions change, so students need to recognise the concept and apply it in a new context.
Build a Weekly Plan That Can Be Sustained
| Session | Focus | Example |
|---|---|---|
| 1 | Retrieval | Explain one theory topic without notes, then correct gaps. |
| 2 | Programming | Write or debug one small program. |
| 3 | Application | Complete a short set of exam questions and review errors. |
Short, regular sessions are easier to maintain than a large plan that is repeatedly postponed. A student can increase the time closer to assessments, but the balance between knowledge, practical work and exam application should remain.
Keep an Error Log
After each practice task, record the topic, the mistake, its cause and the action needed. “Lost two marks” is not specific enough. “Confused validation with verification; write and test two examples tomorrow” creates a useful next step.
What Parents Can Do
Help protect a regular revision time and ask your child what they retrieved or corrected, rather than how long they spent revising. Check that materials match the school’s exam board. If a plan is becoming overwhelming, reduce the number of tasks and make the next action more specific.
See GCSE tuition, explore a Computer Science Diagnostic Lesson when the gaps are unclear, browse the free revision resources, or read about improving exam technique.