Introduction
The IB Computer Science IA can be the difference between a 6 and a 7. It’s your chance to show practical skills, but many students lose marks because they fall into avoidable traps. The IA isn’t just about writing code — it’s about designing, documenting, testing, and evaluating a solution for a real client. If you miss key requirements, even a working program can score poorly.
This article highlights the most common IA mistakes students make, explains why they cost marks, and shows how RevisionDojo helps you avoid them.
Quick Start Checklist
Here’s a fast overview of what not to do in your IA:
- Don’t invent a fake client.
- Don’t pick an idea that’s too simple or too complex.
- Don’t focus only on coding — documentation is key.
- Don’t ignore the testing and evaluation sections.
- Don’t submit without matching your work against the rubric.
The Biggest IA Mistakes
1. Choosing the Wrong Client
Students often pick a client who isn’t real, isn’t available, or doesn’t provide feedback. Examiners can tell, and it undermines your documentation.
Solution: Choose a reliable client like a teacher, librarian, or small business owner. Document every interaction.
2. Picking a Weak Project Idea
A calculator, to-do list, or basic converter may work but won’t score well because it lacks depth. On the other hand, projects that aim to be “the next Instagram” are impossible to finish.
Solution: Aim for a moderately complex project — something with meaningful data handling, but achievable in scope.
3. Over-Focusing on Coding
Many students spend 90% of their time coding and leave documentation for the last week. The result? Weak design diagrams, rushed evaluations, and missing criteria.
