Why mapping is harder in an international school
A school offering the IB, Cambridge, CBSE or a mix carries several structures at once, each with its own vocabulary: units and inquiry in one, syllabuses and assessment objectives in another, national scheme of work in a third. The tempting fix is one flat template, and it fails because it describes none of them properly.
The second difficulty is scale. Planning, assessment and evidence tend to sit in separate files, so duplicate work grows and coverage gaps hide.
What a strong map includes
Whatever the framework, a map earns its keep when it connects the following, and no more.
- Year groups and subjects or courses
- Objectives, standards or assessment objectives, in the framework's own terms
- Concepts and skills where the framework uses them
- Units and the learning experiences inside them
- Assessment tasks, linked to what they assess
- Evidence of what actually happened
Let the structure adapt to the framework
The right approach is a shared skeleton, year to unit to lesson, with framework-specific fields where a framework needs them. An IB unit carries a statement of inquiry and criteria; a syllabus-based course carries topics and assessment objectives. What matters is that both can be read in the same place, so leaders see the whole school.
Be wary of any claim that a tool is framework-agnostic without showing a real unit in each framework you teach.
From map to evidence
The value of a map rises sharply once it connects to assessment and student work. Then the question changes from what did we plan to what evidence exists that it happened, which is the question a governing body, an accreditor or a parent is actually asking.
That connection is also what makes a map cheap to maintain: evidence collected as a by-product of teaching, rather than assembled before a visit.
Where skodle fits
This section names our own product, so weigh it accordingly. The requirements above hold whatever you buy.
skodle connects maps, units and lessons, versions maps by cloning, and for PYP and MYP units reports overused and unused concepts and unmapped or unassessed objectives from approved mappings, with assessment, portfolios and accreditation evidence attached to the same records. For an IB school that is the IB Engine, built for the four programmes separately.
The limits matter more here than anywhere. The curriculum engine is built around the four IB programmes, and a Cambridge syllabus or CBSE scheme of work is not modelled the way an MYP unit is: maps, standards and the gap report are IB-programme structures. A Cambridge or CBSE school gets the school structure (stages, year groups, subjects), unit planning that can be tagged to its framework, and the shared assessment, attendance, reporting and intelligence layers, which are real and programme-independent, but not framework-specific curriculum maps or coverage analysis. Accreditation evidence is modelled against IB standards and practices, not every accreditation framework.
Choosing curriculum mapping software
Test these against a live demo of your own units, in every framework you teach.
- Framework fit: does a unit in each of your frameworks look right, in that framework's terms?
- Versioning: can you show last year's map as it stood?
- Permissions: who can change objectives, and is every change attributed?
- Coverage: does it count gaps and repetition, and from what?
- Assessment link: can a task be traced to the objective it assesses?
- Reuse: can a good unit be shared without being copied and left to drift?
A realistic way to start
Map one framework or one subject first, fix what the first review finds, then extend. Schools that try to map every framework at once produce a large document and lose the people who were meant to use it.
If your school is IB-only, the step-by-step process is in how to create a curriculum map for an IB school.
The multi-framework question to ask every vendor
Ask each vendor to show a unit, a year map and a coverage report in each framework you teach, and to say plainly which of those the product models natively and which it handles through generic fields. The honest answers differ, and the difference is worth knowing before you migrate.
