Skip to main content
Build · Level B Senior school · portfolio track

The Build · Level B curriculum

A program is not magic — it is data, logic and structure a human designed. Build starts by making that structure visible: decompose a problem, choose the right data shape, then write code you can explain line by line and defend in review.

6 units410 guided hours12 monthsCambridge Levels 2–3
Apply to join

6 units · 410 guided hours

The full curriculum, top to bottom. Tap any unit to open its detailed record.

Reasoning before tools, evidence before opinion

A program is not magic — it is data, logic and structure a human designed. Build starts by making that structure visible: decompose a problem, choose the right data shape, then write code you can explain line by line and defend in review.

  1. Problem
  2. Understanding
  3. Reasoning
  4. Design
  5. Implementation
  6. Testing
  7. Reflection
  8. Improvement

Every unit runs the loop, then goes round again — deeper each time.

7 CBE core competencies

Assessed across every unit, not taught as an add-on.

Communication & collaborationCritical thinking & problem solvingCreativity & imaginationCitizenshipDigital literacyLearning to learnSelf-efficacy

Values

Threaded through projects and peer review.

IntegrityResponsibilityRespectExcellenceUnityPatriotism

Pertinent & contemporary issues

Deliberately built into the briefs learners tackle.

Digital citizenship & online safetyData protection & privacyAI ethics, bias & fairnessEnvironmental sustainability (compute cost)Financial literacy & entrepreneurshipInclusion & accessibilityMental well-being & healthy screen habitsCareer & life skills

6 units · 410 guided learning hours

Open any unit for its full record — learning outcomes, assessment criteria, competencies and grading.

Strand: Foundations of software & problem-solving 60 GLH Months 1–2 Portfolio + exam

Key inquiry: “When a problem looks too big to code, how do we break it down until each piece is obvious?”

You ship: A command-line tool that solves a self-chosen problem, with tests and a written design rationale.

LO1 · Data structures & algorithms

  • Choose an appropriate data structure and justify the choice
  • Analyse a solution’s efficiency in plain terms (time/space)

LO2 · Decomposition & OOP

  • Decompose a problem into functions/classes with clear responsibilities
  • Refactor working code to be simpler and explain each change

LO3 · Version control

  • Use Git to branch, commit and collaborate with a partner
Core competencies (CBE)
Critical thinking & problem solvingDigital literacySelf-efficacy
PCIs addressed
Data protection & privacyCareer & life skills
Hands-on practice
  • Solve a real problem two ways and compare which is clearer and faster.
  • Pair-program a tool and review each other’s commits.
  • Whiteboard the design before writing code; reflect on what changed.
Unit grading (Cambridge · Pass / Merit / Distinction)
Pass

Solves guided problems and uses Git.

Merit

Designs and refactors independently with sound choices.

Distinction

Delivers reusable, tested, well-documented tooling.

A portfolio of 6 real, shipped artefacts

Not certificates — working things you built. Every unit ends in a real artefact you own, assessed to standard and ready to show a school, an employer, or an investor.

Unit 1 · Level 2

A command-line tool that solves a self-chosen problem, with tests and a written design rationale.

Unit 2 · Level 3

A deployed full-stack app (frontend + API + database) with a live URL.

Unit 3 · Level 3

A tested feature merged through pull requests, with code review and CI passing.

Unit 4 · Level 3

A trained classifier with an honest evaluation and a short write-up of its limits.

Unit 5 · Level 3

An app with an LLM feature, guardrails, and an honest evaluation of where it fails.

Unit 6 · Level 3

A complete, deployed project (software, web or AI) with docs, and a portfolio-ready presentation.

One rubric, aligned across CBE and Cambridge

CBE performance levels and Cambridge grades describe the same evidence — a working artefact and the reasoning behind it.

CBE levelCambridge gradeWhat the evidence shows
Below expectationNot yet PassCannot yet demonstrate the outcome unaided; work is incomplete or does not run. Needs re-teaching and another attempt.
Approaching expectationPassMeets every assessment criterion with guidance. The artefact works for the happy path and the learner can explain what it does.
Meeting expectationMeritMeets all criteria independently, handles edge cases, evaluates the result, and justifies design decisions from first principles.
Exceeding expectationDistinctionShips a production-grade artefact to real users, critiques trade-offs (cost, latency, safety), and extends beyond the brief with original work.
Read the full document (print / PDF)

The complete curriculum in one printable, saveable document.

Follow it through with a mentor in your corner

Every unit ends in a real artefact — assessed to standard and added to your portfolio.

Apply to join Back to Build
// LET’S BUILD

Have a project? Send us the brief.

Tell us what you need — even a rough idea. You'll hear back within a day with an approach, a timeline, and a fixed quote. No pitch decks, no account managers.