Best Revision Timetable for Computer Science

Computer Science revision is different from most subjects because you need to balance two very different skills: memorising theory and practising programming. Here's a structured timetable that covers both.

The three pillars of CS revision

Every revision session should focus on one of these three activities:

• Theory recall — active testing of your knowledge (quizzes, flashcards, teaching it back)
• Programming practice — writing actual code, not reading about code
• Exam practice — past papers and mock exams under timed conditions

The biggest mistake is spending all your time on theory and neglecting programming, or vice versa. Both papers carry equal weight.

8-week revision plan

This plan assumes you're starting serious revision about 8 weeks before the exam. Adjust the timeline if you have more or less time.

Weeks 1–2: Audit and foundations

• Day 1: Go through the specification topic by topic. Rate each as green (confident), amber (shaky) or red (don't know). This is your revision map.
• Theory days (3 per week): Work through your red topics first. Use auto-marked quizzes to test yourself — not your notes.
• Coding days (2 per week): 20–30 minutes of Python challenges focusing on fundamentals (variables, loops, functions, file handling).
• Weekend: One past paper (untimed is fine at this stage). Mark it, note where you lost marks.

Weeks 3–4: Deepening

• Theory: Move to amber topics. Focus on understanding, not just recognition. Can you explain each concept without looking at your notes?
• Coding: Progress to harder challenges — string manipulation, 2D arrays, algorithms. Write complete programs, not just individual lines.
• Weekend: One past paper under timed conditions. Compare your mark to grade boundaries.

Weeks 5–6: Exam focus

• Theory: Rapid-fire quiz sessions. Cover 3-4 topics per session using flashcards or quizzes. Focus on precision — exact definitions, correct terminology.
• Coding: Practice writing code on paper (no IDE). This is how the exam works and it feels very different.
• Weekend: Full mock exam. Try a timed auto-marked mock for instant feedback.

Weeks 7–8: Refinement

• Theory: Review your past paper mistakes. Make a "last-minute" sheet of the facts you keep forgetting.
• Coding: Redo the challenges you got wrong earlier. If they're easy now, you've improved.
• Final weekend: One more full mock. Then rest — cramming the night before doesn't help.

Weekly template

Tips that make a real difference

• 30 focused minutes beats 2 distracted hours. Put your phone in another room.
• Don't re-read notes. If you're not testing yourself, you're not revising.
• Track your progress. Keep a simple log of topics covered and marks on past papers. Seeing improvement is motivating.
• Sleep matters. Your brain consolidates learning during sleep. Late-night cramming is counterproductive.