IA Templates

Starter templates for IA documentation. These give you a structure to build on; they are not the only way to present the work. Customise them for your specific project.

These templates are aligned with the 2027 syllabus (first assessment May 2027). The previous IA’s Record of Tasks template has been retired; the 2027 IA does not require a Record of Tasks.

IA Proposal Form

A school-level planning form to complete before you start drafting Criterion A: Problem specification. It walks you through a full problem specification (problem statement, what the product must do, constraints, inputs and outputs), success criteria (with a worked example and a coverage check), the computational context with alternatives and a requirements list, a planned techniques and features checklist (core features, plus optional advanced algorithms and extensions), wireframe sketches, a scope-and-risk and self-check section, and a teacher review and approval table. A mapping table shows how each part feeds Criteria A to D.

Download IA Proposal Form (.docx)

Use this in: the planning stage, before Criterion A. Once your teacher has approved the proposal, the content here becomes the starting point for Criterion A in your final documentation.

The IB does not prescribe an IA proposal format; this is a school-level tool. Its job is to let your teacher review feasibility, scope, and the quality of your success criteria before you commit 35 hours of work to the project.

Testing Strategy Template

Use this to draft the testing strategy for Criterion C: System overview. Cover typical inputs, boundary cases, and abnormal inputs for every success criterion.

Download Testing Strategy Template (.docx)

Use this in: Criterion C: System overview (where you design the strategy) and Criterion D: Development (where you deploy it and report results).

How to use these templates

Download the template.
Customise the structure to match your project.
Fill in project-specific details: the generic text is a scaffold, not content.
Review with your teacher before finalising.
Update as the project evolves: success criteria and testing rows will change as you learn what is actually feasible.

What’s not in the templates

Decomposition / Gantt (Criterion B): every project decomposes differently; a template would be generic enough to be unhelpful. Use any diagramming tool (draw.io, LucidChart, paper-and-pen, or a built-in word-processor table).
System model diagrams (Criterion C): class diagrams, ERDs and wireframes depend on your product’s shape. Tools: draw.io for UML / ERD, Figma or paper for wireframes.
Record of Tasks: retired in the 2027 syllabus. If your school still uses an internal RoT-style tracker for personal accountability, that is fine, but it is not part of the IA submission.