5 Common Mistakes Students Make in IB Computer Science Paper 1

IB Computer Science Paper 1 tests core theory across both Theme A and Theme B — but strong subject knowledge alone doesn't guarantee a strong score. Most lost marks come from a handful of avoidable habits. Here are the five that show up most often.

1. Not matching the command term

"State," "describe," "explain," and "discuss" all ask for different depths of answer. A one-line answer to a 4-mark "explain" question will never earn full marks, no matter how correct it is — the mark scheme is built around the command term, not just the content.

Fix: before writing anything, check the command term and the mark allocation. A 4-mark question needs roughly 4 distinct, developed points.

2. Vague or generic answers

"It makes it faster" or "it's more secure" are common phrases that rarely earn marks on their own. Examiners are looking for answers tied specifically to the scenario in the question — not general statements that could apply to any system.

Fix: always refer back to the specific context given in the question. If it's about a hospital database, your answer should mention the hospital's data, not databases in general.

3. Drawing diagrams but not labelling them properly

For topics like network topologies, logic circuits, and data structures, the diagram itself is often only half the answer — the labels are what actually earn the marks. A correct-looking diagram with missing, vague, or incomplete labels frequently scores far lower than students expect.

Fix: label every component clearly, using the exact terms from the syllabus, and add labelled arrows or annotations wherever the mark scheme is likely to expect them — don't assume the diagram speaks for itself.

4. Running out of time on early questions

Paper 1 is tightly timed, and it's tempting to spend extra time perfecting an answer you feel confident about. That time often comes out of the questions at the end of the paper — sometimes ones worth more marks.

Fix: do a timed practice paper before the real exam so you know your natural pace, and stick to roughly one minute per mark as a rule of thumb.

5. Using everyday language instead of correct computer terminology

Answers written in casual, everyday phrasing — "the chip," "the internet thing," "it saves the info" — rarely earn marks, even when the underlying idea is correct. Mark schemes are built around precise subject vocabulary, and examiners can only credit what's actually stated in those terms.

Fix: learn the exact terminology for each topic — processor, not "chip"; secondary storage, not "memory stick"; copper cable , not "the wire" — and use it consistently, even in short answers.

None of these mistakes are about knowing less content — they're about how that content gets presented under exam conditions. Fixing them is often the fastest way to move up a grade boundary.