Skip to main content
skodle
All IB Engine areas

IB Engine · Coordinate

Whole-school oversight, and evidence that is already there

Coordinators see coverage, gaps and programme health across the school, and the evidence an authorisation or evaluation visit asks for is the same evidence teachers created while working — not a folder assembled the month before.

Why it matters

  • A gap detector that reads the actual curriculum graph finds concepts never taught and standards never assessed.
  • Evidence is linked to units, students and requirements once, then read from many angles.
  • Coordinator roles are designations on top of normal accounts, so a PYP coordinator approves PYP without becoming an administrator.
  • Detected gaps become tasks somebody owns, rather than a dashboard nobody acts on.

What's included8 capabilities

Whole-school oversight, evidence and accreditation.

Academic years

The year axis new IB records are stamped with, so past years stay reproducible.

IB command centre

Exceptions-first, read-only whole-school health dashboard.

Unit mappings

Typed unit → objective/standard edges — approved, versioned, the graph coverage is measured from.

Gap detector

Unmapped & under-assessed objectives, under-taught & overused elements, units missing evidence.

IB roles

Coordinators and supervisors — with real approval powers.

Accreditation

IB practices → linked evidence → gaps → actions → readiness.

Student submissions

Work learners added to their own IB portfolio, awaiting review.

Evidence graph

The one evidence store every subsystem links into.

What this does not claim

Being accreditation-ready is a claim about your school, not about software. skodle keeps the evidence in order; the practice behind it is yours.

Read next

Other IB Engine areas