The complete module catalogue
Academic core, portals, operations, staff, inclusion and compliance — grouped into six clusters with what each one actually does.
Browse every moduleMatric and O Level, side by side
A school running a national stream and a Cambridge stream runs both in one CampusFlo tenant — separate ladders, separate grading, one student record.
See how it worksConfiguration, never a fork
A profile sets the level ladder, term structure, grading scheme, attendance model and the vocabulary itself. Every value stays editable afterwards.
One product, every countrySee it on your own scenario
A screen-share run against your levels, your grading scheme and your board — not a slide deck. Bring your student count and campuses.
Schedule a demoOne place for every message the school sends: notices, absence alerts, the daily diary, results and emergencies — targeted by class, section or child, with a delivery log for each one.
Audience picker · templates · quiet hours · delivery reports
Audiences are built from live school data — this campus, this level, this section, this house, the guardians of these students — so a message reaches the current cohort rather than whoever joined a chat group two years ago.
The messages that matter most are triggered by events elsewhere — a register closing, homework being set, a result publishing, an incident being logged. Rules and templates turn those into messages without anyone composing one.
Notices carry an audience, a publish window and optional acknowledgement, so you can see exactly who has not responded — which is the difference between having sent a consent form and having it back.
Closures, weather and security events go out on every channel at once with confirmation tracking, so the question “did the message reach them” has an answer rather than an assumption.
Messaging is where a school can do real damage quickly. These are the guards.
External sends require an active, configured channel and respect its daily limits, so nothing silently fails to leave.
A message to a student below a configurable age is routed to their guardians instead.
A guardian who has opted out of a category is excluded from those audiences automatically.
Non-emergency messages queue outside the configured window rather than arriving at midnight.
Parent-teacher conversations are retained per policy and can be escalated to a head.
Recipient, channel, template, time and delivery status — per student and per guardian.
Which channel a school actually uses is one of the sharpest differences between markets.
Communication is the output channel for most of the rest of the system.
It takes about a minute on the call, and it is the clearest way to see how targeting and delivery logging actually work.