IB Computer Science IA Guide: Structure & Success Tips

The IB Computer Science Internal Assessment (IA) is a solution-based project that asks students to identify a real client, design a product, implement it, and evaluate the outcome. It carries significant weight toward the final IB grade and is graded against IBO's official criteria, so understanding its structure early saves months of rework.

What the IA Actually Is

Unlike a typical school project, the IA is framed around a genuine client relationship. You (the student) act as a developer solving a problem for someone else—a teacher, a local business, a club, a family member—who has an actual need. The IB does not want a generic "build an app" exercise; it wants evidence that you can gather requirements, design a solution, build it, and critically assess whether it worked.

The final submission usually includes:

• A written report (typically capped around 2,000 words for the criteria sections)
• Supporting documentation: record of tasks, product design overview, development record
• The actual product (code, application, or system)
• A video demonstration for HL/SL students showing the product functioning

The Five Assessment Criteria

IB grades the IA against five criteria, each contributing marks toward the total:

1. Planning (Criterion A) — Defining the problem, client needs, and success criteria. This is where you justify why the project matters and what it must accomplish.
2. Solution Overview (Criterion B) — Records of tasks completed, time management, and evidence of iterative development (often shown via a Gantt chart or task log).
3. Development (Criterion C) — Technical documentation of how the solution was built: algorithms, data structures, key code excerpts, and design decisions. This is usually the most technically demanding section.
4. Functionality (Criterion D) — Demonstrated through the video, this shows the product actually working against the success criteria defined in Criterion A.
5. Evaluation (Criterion E) — Honest reflection on what worked, what didn't, and feedback from the client. Weak evaluations are one of the most common reasons IAs lose marks.

Choosing a Strong Project Scope

The biggest mistake students make is picking a project that's either too trivial (a basic to-do list app) or too ambitious (a full social network with real-time chat, authentication, and payments) for the time available. A well-scoped IA usually:

• Solves one specific, well-defined problem for a real client
• Uses technology appropriate to the course level (SL projects can be simpler than HL)
• Allows for meaningful technical depth—database design, algorithmic logic, or non-trivial data processing—without becoming unmanageable
• Leaves room for a clear