Curriculum

Running Two Curricula on One Campus

Multi-curriculum campuses are ordinary in the UAE and awkward in most software. The problem is not capacity — it is that the assessment models genuinely disagree with each other.

7 min read

Running more than one curriculum on a single campus is ordinary in the UAE and awkward in most school software. Groups add a second programme to widen their intake, or a school offers an international track alongside its original one, and what was a single reporting calendar becomes two.

The difficulty is not capacity. It is that the assessment models genuinely disagree with each other, and a system built around one of them will quietly distort the other.

Where the models actually diverge

These are not stylistic differences. They are different answers to the question “what does a grade mean”:

  • Criterion-based assessment judges work against defined criteria with achievement levels and band descriptors. A final grade is determined from criterion levels. Averaging those levels into a percentage destroys the information the model exists to carry.
  • Credit accumulation with GPA tracks courses, credit values and graduation requirements, and maintains weighted and unweighted cumulative averages that must recalculate whenever a grade changes.
  • Scholastic and co-scholastic reporting grades subject marks alongside descriptive areas on one report card, with term weightings feeding a computed final result.
  • Attainment against expected standard, plus progress from a baseline, treats those as two separate measures rather than one grade.

A system that stores all four as a percentage in a differently-labelled field will produce reports that look plausible and are wrong in ways only a subject lead will notice — usually after they have gone to parents.

Reporting calendars run in parallel, not in sequence

Two curricula mean two sets of marking periods, two report cycles and two sets of deadlines, frequently overlapping. Practically this requires:

  • Report cycles configured per curriculum, not one calendar imposed on the school;
  • Different cycles for different year groups within the same curriculum, since early years and exam years do not report the same way;
  • Report templates that differ per programme, because a criterion-based report and a credit transcript share almost no structure;
  • The ability to run both without staff on one side waiting for the other side’s cycle to close.

Systems that assume one reporting calendar tend to handle this by making the second curriculum a workaround — a separate spreadsheet, a manual template, a parallel process. That works until it is audited.

One student directory, whatever the programme

This is the part schools get wrong most often, usually by adopting two systems.

Most of a student record is curriculum-agnostic. Names, families, guardians, contact preferences, documents and expiry dates, attendance, medical notes, inclusion plans, transport — none of that changes because a child follows a different programme. Only assessment and reporting differ.

Splitting the directory to accommodate that creates real damage:

  • Families with children on both sides exist twice, and are contacted twice;
  • Sibling links break across the divide, so household handling stops working;
  • Whole-school attendance or roll figures become a manual merge, and two sources will disagree;
  • A student transferring between programmes becomes a new record with no history.

The right shape is one directory with assessment configured per programme. See how the student record is structured for what that looks like in practice.

Transfers between programmes

A student moving from one curriculum to the other should keep one continuous record. Their prior attainment stays attached even though it was recorded on a different scale — it is still the best available evidence of where that child was.

What should not happen is an automatic conversion between scales. Criterion levels do not map cleanly onto percentages and a system that silently converts them is inventing precision it does not have. Recording prior attainment as a baseline on its original scale is honest; converting it is not.

Questions to ask a vendor

  • Can two curricula run on one campus with one student directory?
  • Are report cycles configured per curriculum and can they run in parallel?
  • Is criterion-based assessment held as criteria, or as a percentage with different labels?
  • What happens to a student who transfers between programmes mid-year?
  • Can whole-school reporting read across both without a manual merge?
  • If we add a third programme in two years, is that configuration or a project?

That last question is worth asking even if a third programme is not planned. The answer tells you whether curricula are a first-class concept in the system or something that was added once, under pressure, for a specific customer.

If you run one curriculum today

It is still worth asking. Retro-fitting a second assessment model into a system that assumed one is not a configuration change — it is frequently a migration, and it arrives at the exact moment the school is busy launching a new programme.

The curriculum pages set out how each model is handled individually: British, CBSE and Indian, IB and American. If you are earlier in the process, how to choose a student information system covers the broader set of questions.

Frequently asked questions

Can one student directory serve two curricula?

It should. Students, families, attendance and documentation are curriculum-agnostic — only assessment and reporting differ. Splitting the directory duplicates families and breaks sibling links across the divide.

What if a student moves from one curriculum to the other?

They should keep one continuous record. Prior attainment stays attached even though it was recorded on a different scale, because the alternative is a student who appears to have started school on the day they transferred.

Do we need two systems?

No, and two systems is usually the worse answer — it duplicates every student who has a sibling on the other side and makes whole-school reporting a manual merge.

See it against your own school

A walkthrough configured to your curriculum, run by someone who can answer migration questions rather than defer them.

Book a demo