IB Computer Science IA 2027: Criteria, Format and Examples

9 min read

Oct 19, 2026

#IB Computer Science#IB Computer Science 2027#IB Internal Assessment#Computer Science IA
IB Computer Science IA 2027: Criteria, Format and Examples cover image

The IB Computer Science IA 2027 asks you to do more than build an attractive app. You must identify a meaningful problem, develop a working computational solution, and show how your decisions, code and testing solve that problem. For students entering the first assessment in May 2027, the updated rubric also changes how this work is documented and marked.

A July 2026 r/IBO discussion asked for accessible criteria and documentation examples. This guide draws on the IB curriculum update and official 2027 examiner instructions.

What Is the New Computational Solution IA?

The new internal assessment is called the computational solution. You individually select a real-world problem, apply computational thinking, and create software that addresses it. The project brings together Theme A, concepts in computer science, and Theme B, computational thinking and problem-solving.

The requirements are identical at Standard Level and Higher Level. The IA carries 30% of the final grade at SL and 20% at HL, with 35 teaching hours allocated. A named external client is not mandatory, but the problem and requirements must be credible.

A functional product alone is not enough. Your documentation must explain the decisions behind it.

IB CS IA Criteria and Mark Breakdown for 2027

CriterionMain focusMarksSuggested documentation words
A: Problem specificationScenario, requirements and success criteria4300
B: PlanningDecomposition and development plan4150
C: System overviewSystem model, algorithms and testing strategy6150
D: DevelopmentFunctional product, implementation decisions and testing121,000
E: EvaluationPerformance against success criteria and improvements4400
Total302,000

The word allocations above are recommendations, not separate compulsory section limits. Criterion D accounts for 12 of 30 marks, but technical ambition cannot automatically compensate for missing evidence. The IB uses best-fit assessment.

Do not use a pre-2027 rubric marked out of 34. The names, allocations and expectations have changed.

Criterion A: Problem Specification (4 Marks)

Your opening section establishes what is wrong, why a computational approach is appropriate, and what success will look like. Describe a specific scenario rather than starting with the programming language you want to use.

“I will make a booking website” describes a product, not a problem. Explain whose bookings fail, why and what the system must accomplish.

Use substantial, measurable success criteria. “Easy to use” is vague; “rejects overlapping reservations for the same room” is testable.

Check your section: Is the context credible? Are requirements precise? Can you later prove whether each success criterion was met?

Criterion B: Planning (4 Marks)

Decompose the problem into computational tasks, connecting requirements to components, dependencies and development stages.

For a booking solution, separate validation, availability checking, data storage, cancellation and user feedback. Show dependencies between components.

A timeline that merely lists dates is insufficient. Connect work stages to success criteria.

Check your section: Could another programmer understand what you planned to build and the order in which its components depend on one another?

Criterion C: System Overview (6 Marks)

Show your system model, relevant interface designs, algorithms and testing strategy.

Use diagrams where they clarify relationships. A data model could show Room, Reservation and User records. Pseudocode could demonstrate how two booking intervals are compared. A test table could identify normal input, boundary conditions and invalid input.

Avoid screenshots that reveal little about the underlying system or testing strategy.

Check your section: Do your designs explain the core logic, and can the test plan be traced back to your stated success criteria?

Criterion D: Development (12 Marks)

Development carries the largest allocation. Explain the functioning product and the algorithmic techniques you personally implemented. Select meaningful code excerpts and annotate the decisions that matter: why a particular structure was appropriate, what an algorithm achieves, what alternatives you considered, and how testing influenced revisions.

For a booking system, explain conflict detection rather than every button. Show a failed overlap test and the corrected logic.

A polished interface cannot replace demonstrated computational thinking. Credit external libraries and distinguish your own algorithms.

Your video of no more than five minutes must show functionality and testing, not a spoken code review. Examiners assess functionality from the video without running your software.

Check your section: Have you explained implementation choices and their effectiveness, not just described what the finished screens look like?

Criterion E: Evaluation (4 Marks)

Return to the criteria you defined at the start. Evaluate what the system demonstrably achieves, what it does not, and which improvements are justified by evidence. Unsupported claims that “all features work” are insufficient.

For example, a booking product might pass conflict detection but struggle when two users submit reservations at the same moment. An appropriate improvement might be a database transaction that prevents simultaneous updates from creating duplicate bookings. Justify the proposed change.

Check your section: Is every judgment supported by observed results, and are recommendations specific to genuine limitations?

An Original IB Computer Science IA Project Example

Illustrative project: Shared Study Room Booking System. This is a fictional teaching example, not an official IB exemplar or an assessed submission.

Problem: A small learning center coordinates two study rooms using messages and a spreadsheet. Duplicate reservations are occasionally entered, and staff have difficulty checking availability.

Proposed solution: A local web application stores reservations, validates time intervals, checks availability and produces a daily schedule. The core computer science problem is enforcing booking constraints, not simply displaying a calendar.

Success criterionEvidence you could collect
S1: Accept bookings only with a valid room, date and time rangeTests with valid, incomplete and reversed inputs
S2: Reject overlapping reservations for the same roomTests with partly overlapping, fully contained and adjacent intervals
S3: Allow cancellation and restore availabilityBefore and after reservation records
S4: Display the day's reservations in chronological orderOutput for a deliberately unsorted set of bookings

Example algorithm: Represent each booking as a start time and end time. Two intervals conflict when the proposed start is earlier than an existing end and its end is later than the existing start. Check only reservations for the same room and date. This permits adjacent bookings while rejecting overlaps.

Suggested documentation structure for this fictional project: A: scenario and S1 to S4. B: component breakdown and build sequence. C: reservation data model, overlap algorithm and test matrix. D: annotated implementation and development test results. E: success criterion results and justified improvements.

Development evidence: Annotate overlap checking, invalid input handling and a correction prompted by testing.

Evaluation evidence: Report S1 through S4 test results and address limitations such as simultaneous requests.

Choose your own independently developed problem; do not reproduce this example.

IA Documentation Format and Submission Limits

The official 2027 moderation instructions describe a ZIP file containing three components:

  1. Documentation: One PDF with five separate sections, A through E. The maximum is 2,000 words, and the word count must appear on its first page.
  2. Demonstration video: One video lasting no more than five minutes, showing functionality and examples of testing, in a common format such as MP4.
  3. Appendices: One PDF containing the full source code and other resources referenced in the documentation, with clear links from the main text to the relevant material.

The documentation word count excludes headings, success criteria, diagrams, captions, pseudocode, code excerpts, annotations and tabular evidence. Extended explanatory writing placed in these elements still counts.

The appendix is not marked directly. Nevertheless, without full source code, you cannot receive full marks for Criterion D. Examiners are not required to search the appendix for evidence missing from your main documentation. The software product itself is not submitted for the examiner to run.

How to Show Authentic Development and Testing Evidence

Preserve genuine design revisions, code versions, test inputs, expected and actual outputs, and corrections as you develop.

Include normal, extreme and abnormal data in your testing strategy where appropriate. For the booking example, normal data might be a valid midday reservation, boundary data might involve adjacent time slots, and abnormal data might include a missing room identifier or an end time before the start time.

Show what changed after failed tests. Attribute reused code, and explain your original contributions.

A Practical IA Planning Checklist

Before submission, ask whether you can answer yes to each question:

  • Is the problem real and sufficiently focused for independent development?
  • Can every success criterion be checked against observable behavior?
  • Does the plan break the solution into clear computational components?
  • Do the diagrams and algorithms match what you actually implemented?
  • Have you explained important code choices and test-driven corrections?
  • Does the video visibly demonstrate working features and relevant tests?
  • Does the evaluation distinguish demonstrated success from remaining limitations?
  • Are the documentation, word count, video and complete source appendix ready?

Frequently Asked Questions About the CS IA 2027

Do SL and HL students use different criteria? No. The computational solution requirements and 30-mark rubric are the same. Its grade weighting differs: 30% at SL and 20% at HL.

Do I need an external client? The 2027 task allows students to choose their own real-world problem without a mandatory named external client. Real user needs can still strengthen a well-grounded scenario.

Is a five-minute video optional? No. The video is a required part of the submission and demonstrates functionality and testing used for Criterion D.

Can I submit an existing template as my project? An unchanged template without evidence of meaningful modification is inappropriate. Your documentation must make your own algorithmic thinking and development work visible.

Final Advice for the First Assessment in 2027

Build evidence alongside your software. Select a computationally meaningful problem, measure success and demonstrate genuine functionality. Use the IB's updated Computer Science subject information and your teacher's access to the full subject guide for precise assessment descriptors.

Written By

Author Profile Picture

Aditi Sneha

Growth Strategist

Reviewed by Ayisha Shahani, IB Content Head at Koncepts.

Loading suggested posts