Back To Computer Science

IA Playbook

Computer Science IA Criteria Guide

Turn your scenario, design evidence, and testing into a clean, defensible project record.

Use this guide to keep the client need, success criteria, implementation, and testing connected so the product reads as one coherent development story.

Criteria Breakdown

Did You Know? The easiest score jumps usually come from explicitly naming what the criterion rewards and supporting it with direct evidence.

Criterion A: Planning (6 marks)

Examiner Focus

The appropriateness of the scenario for investigation, rationale for product choice, and quality of success criteria.

Top-Band Move

An appropriate scenario for investigation for an identified client, providing evidence of consultation, is described. The rationale for choosing the proposed product is justified and includes a range of appropriate criteria for evaluating the success of the product.

Common Penalty

An appropriate scenario for investigation for an identified client is stated. The rationale for choosing the proposed product is identified. The criteria for evaluating the success of the product are generally inappropriate.

Criterion B: Solution Overview (6 marks)

Examiner Focus

Completeness and clarity of the record of tasks, design overview, and test plan.

Top-Band Move

The record of tasks and the design overview, including an outline test plan, are detailed and complete. From this information it is clear how the product was developed.

Common Penalty

The record of tasks and the design overview, including an outline test plan, are limited. From this information it is difficult to see how the product was developed.

Criterion C: Development (12 marks)

Examiner Focus

Complexity and ingenuity of techniques used, appropriateness of tools, and explanation of techniques.

Top-Band Move

The use of techniques demonstrates a high level of complexity and ingenuity in addressing the scenario identified in criterion A. It is characterized by the appropriate use of existing tools. The techniques are adequate for the task and their use is explained. All sources are identified.

Common Penalty

The use of techniques demonstrates a low level of complexity and ingenuity or does not address the scenario identified in criterion A. It is characterized by limited use of existing tools. There is no explanation of why the techniques are used or how they are adequate for the task. Sources are used but are not identified.

Criterion D: Functionality and Extensibility of Product (4 marks)

Examiner Focus

Product functionality (as shown in video) and potential for future expansion/modification.

Top-Band Move

The video shows that the product functions well. Some expansion and modifications of the product are straightforward.

Common Penalty

The video shows that the product functions partially. Some expansion and modification of the product is possible but difficult.

Criterion E: Evaluation (6 marks)

Examiner Focus

Evaluation against success criteria, incorporation of client feedback, and quality of improvement recommendations.

Top-Band Move

The product is fully evaluated against the success criteria identified in criterion A including feedback from the client/adviser. Recommendations for further improvement of the product are realistic.

Common Penalty

There is a limited attempt to evaluate the product against the success criteria identified in criterion A. There is limited evidence of feedback from the client/adviser and any recommendations for further improvement are trivial or unrealistic.

Markbands

Criteria point markbands to benchmark where your current draft sits and what a stronger band demands.

Criterion A: Planning (6 marks)

Points 0

The response does not reach a standard described by the descriptors below.

Points 1-2

An appropriate scenario for investigation for an identified client is stated. The rationale for choosing the proposed product is identified. The criteria for evaluating the success of the product are generally inappropriate.

Points 3-4

An appropriate scenario for investigation for an identified client, providing evidence of consultation, is stated. The rationale for choosing the proposed product is partially explained and includes some appropriate criteria for evaluating the success of the product.

Points 5-6

An appropriate scenario for investigation for an identified client, providing evidence of consultation, is described. The rationale for choosing the proposed product is justified and includes a range of appropriate criteria for evaluating the success of the product.

Criterion B: Solution Overview (6 marks)

Points 0

The response does not reach a standard described by the descriptors below.

Points 1-2

The record of tasks and the design overview, including an outline test plan, are limited. From this information it is difficult to see how the product was developed.

Points 3-4

The record of tasks and the design overview, including an outline test plan, are partially complete. They provide a basic understanding of how the product was developed.

Points 5-6

The record of tasks and the design overview, including an outline test plan, are detailed and complete. From this information it is clear how the product was developed.

Criterion C: Development (12 marks)

Points 0

The response does not reach a standard described by the descriptors below.

Points 1-4

The use of techniques demonstrates a low level of complexity and ingenuity or does not address the scenario identified in criterion A. It is characterized by limited use of existing tools. There is no explanation of why the techniques are used or how they are adequate for the task. Sources are used but are not identified.

Points 5-8

The use of techniques demonstrates a moderate level of complexity and ingenuity in addressing the scenario identified in criterion A. It is characterized by some appropriate use of existing tools. There is some attempt to explain the techniques used and why they are adequate for the task. All sources are identified.

Points 9-12

The use of techniques demonstrates a high level of complexity and ingenuity in addressing the scenario identified in criterion A. It is characterized by the appropriate use of existing tools. The techniques are adequate for the task and their use is explained. All sources are identified.

Criterion D: Functionality and Extensibility of Product (4 marks)

Points 0

The response does not reach a standard described by the descriptors below.

Points 1-2

The video shows that the product functions partially. Some expansion and modification of the product is possible but difficult.

Points 3-4

The video shows that the product functions well. Some expansion and modifications of the product are straightforward.

Criterion E: Evaluation (6 marks)

Points 0

The response does not reach a standard described by the descriptors below.

Points 1-2

There is a limited attempt to evaluate the product against the success criteria identified in criterion A. There is limited evidence of feedback from the client/adviser and any recommendations for further improvement are trivial or unrealistic.

Points 3-4

The product is partially evaluated against the success criteria identified in criterion A including feedback from the client/adviser. Recommendations for further improvement of the product are largely realistic.

Points 5-6

The product is fully evaluated against the success criteria identified in criterion A including feedback from the client/adviser. Recommendations for further improvement of the product are realistic.

Build Sequence

Did You Know? Most weak drafts fail from sequence chaos, not lack of ideas.

Step 1

Define the scenario

State the client need clearly and translate it into measurable success criteria before building anything.

Step 2

Document the design

Record the task list, design overview, and test plan so the development path is easy to follow.

Step 3

Explain the development

Show why your techniques and tools are suitable, and make the source of every technique clear.

Step 4

Test and evaluate

Use the video and test evidence to judge functionality, extensibility, and how well the product meets the criteria.

Submission Checklist

  • Client consultation and success criteria are clear.
  • The solution overview explains how the product was developed.
  • Development choices are justified, not just listed.
  • Evaluation is tied back to the original success criteria.

Quick Wins

  • Make success criteria measurable before coding.
  • Show why a technique was used, not just that it was used.
  • Use testing evidence to support every evaluation point.

Did You Know?

Get Faster Feedback On Your Computer Science IA

Marksy grades your project against IB criteria, flags missing documentation, and helps you tighten the link between implementation and evaluation. Marksy is built to grade faster with criterion-level precision, so you can improve before final submission.

1. Upload your IA draft PDF to Marksy.
2. Get criterion-by-criterion feedback fast.
3. Revise and resubmit with focused improvements.
Marksy grading results view

Instant Grading Results

See where your score is now, not just where it could be.

Marksy criteria-wise feedback highlights

Criterion-Level Feedback

Marksy explains feedback by rubric criterion, so revision is targeted.

Marksy actionable todo feedback list

Action List To Improve

Get concrete next edits instead of vague "improve analysis" advice.

Marksy AI detection and highlight review

Confidence And Integrity Signals

Review flagged sections and strengthen authenticity before submission.