Why the IB Computer Science HL Paper 3 Option topic decides a 7
IB Computer Science Paper 1 and Paper 2 split the mark budget in a way most candidates misread. Learn the per-section weightings and how to allocate revision…
Most students preparing for IB Computer Science treat Paper 1 and Paper 2 as two versions of the same test. The mark budget tells a different story. Once you can see where the marks actually live, the choice between HL and SL, between Paper 1 drills and Paper 2 drills, and between the Case Study and the Option topic becomes a calculation rather than a feeling.
What the mark budget looks like across the IB Computer Science assessment
The IB Computer Science course ends with two written papers plus the Internal Assessment (IA). For HL candidates, Paper 1 carries roughly 45 marks over 2 hours and 30 minutes, Paper 2 carries 65 marks over 2 hours and 30 minutes, and the IA contributes 30 marks. For SL, the weights are smaller but the proportions follow the same shape. The papers together account for the bulk of the final grade, so any revision plan that spends more time on the IA than on Paper 2 is fighting the mark budget.
What most candidates underweight is the Case Study inside Paper 1. The Case Study is a single pre-released document, and around 24 of the 45 Paper 1 marks on HL sit on questions that quote it directly. Treat the Case Study as a third paper, not as a reading passage.
Why Paper 1 is not a theory exam
Paper 1 tests the syllabus content through the lens of the Case Study. The questions ask candidates to apply ideas from Topic 1 through Topic 7 to a real scenario such as a transport network, a hospital system, or a ticketing platform. The word apply matters. A candidate who can define a binary tree but cannot trace one through a hospital's patient record system will lose marks even with perfect recall of the definition.
The reliable Paper 1 move is to read each question, then go back to the Case Study excerpt at the end of the question and ask: which of the four or five syllabus ideas does this scenario activate. Most strong answers are 80% syllabus vocabulary and 20% scenario-specific re-statement. The 20% is what the mark scheme rewards; the 80% is what keeps the answer anchored.
Paper 1 tactical checklist
- Underline the noun in the command term: state, describe, explain, discuss, evaluate all have different mark ceilings.
- For every 4-mark discuss question, write two clear syllabus points and one short scenario link.
- Reserve the last 8–10 minutes of Paper 1 for the longest evaluate question; it is the only question where HL markers routinely give a 4 instead of a 3 because of a missing counter-argument.
Paper 2 is where HL and SL separate
Paper 2 is the technical paper. The first section tests the compulsory topics from the syllabus; the second section is the Option topic, where candidates choose one of four subtopics in advance. On HL, the Option topic is worth around 30 of the 65 Paper 2 marks. A student who has not pre-studied their Option loses about a quarter of the paper before they sit down.
The compulsory section is built around pseudocode, trace tables, data structures, and short constructed responses. The trap is grammar. Markers do not care whether the candidate writes Python, Java, or a slightly off IB pseudocode dialect, but they do care about indentation, variable declarations, and consistent loops. In my experience a 6/7 answer and a 5/7 answer often look identical in logic; the 6/7 answer uses a single, clean loop where the 5/7 answer uses a tangle of flags and breaks.
Common pitfalls and how to avoid them
- Confusing 2D array row/column indices. The Case Study and the exam swap between row-major and column-major conventions; always label the axes on the diagram you draw.
- Forgetting the IA scope constraint. A 30-mark IA cannot rescue a 40-mark Paper 2 collapse, so the IA is the third priority, not the first.
- Studying all four Option topics shallowly. A 2-mark gain on each Option is usually smaller than the 4-mark gain on one Option read deeply; pick one Option in the first month and stop re-deciding.
How the IA interacts with the papers
The IA is a 30-hour development project plus a write-up. The mark scheme rewards a working solution to a real client problem, a clear record of the development process, and a candid evaluation. A common IB Computer Science mistake is to treat the IA as a programming showcase, when the rubric actually weights the documentation and consultation evidence nearly as heavily as the code itself.
For most candidates, the IA is the only part of the course that is fully self-paced. Use that. A candidate who finishes the IA by the end of Year 12 has an entire Year 13 to drill Paper 2, which is the only way to absorb the Option topic and the trace-table questions that appear every November and May.
Allocating revision time: a 12-week block for HL
The mark budget suggests a clear time split. Across a 12-week revision block, I would personally put roughly 5 weeks on Paper 2, 4 weeks on Paper 1 including the Case Study, 2 weeks on the IA write-up, and 1 week on past-paper triage. SL candidates shift that to about 4 weeks on Paper 2 and 4 weeks on Paper 1, since SL has no Option topic but a shorter Case Study window.
The week-by-week logic matters. Weeks 1 to 4 should be syllabus-driven, with one paper per week. Weeks 5 to 8 should be past-paper-driven, with full papers under timed conditions. Weeks 9 to 12 should be error-driven: every wrong answer gets a one-line note in a single notebook, and that notebook is the only revision source in the final week.
Paper 1 versus Paper 2 at a glance
The table below summarises the structural difference most candidates miss. The numbers are taken from the official IB Computer Science subject guide and are stable across recent exam cycles, so the proportions will not surprise you from one session to the next.
| Feature | Paper 1 | Paper 2 |
|---|---|---|
| Core question type | Scenario-based, Case Study anchored | Technical, pseudocode and trace tables |
| Approx. HL mark weight | 45 marks | 65 marks |
| Pre-release material | Yes, the Case Study | No, but the Option topic must be pre-studied |
| Highest-leverage revision move | Re-read the Case Study three times | Drill one Option topic to 80% accuracy |
| Common mark-losing habit | Generic answers that ignore the scenario | Sloppy pseudocode with inconsistent indentation |
Conclusion and next steps
The mark budget is the single most useful object in IB Computer Science preparation. Once you know that Paper 2 carries roughly 60% of the written mark and that the Case Study inside Paper 1 carries roughly half of that paper, the revision plan writes itself. Use the syllabus guide as a scoring reference, not as a reading list, and time-box your Option topic in the first month of revision.
IB Courses' one-to-one IB Computer Science programme drills each student's Paper 2 pseudocode fluency against the official rubric and turns the Case Study into a timed 4-week module, so a 7 target becomes a concrete week-by-week plan rather than a wish.