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 record per student, from first enquiry to alumnus — family, documents, enrolment history, health flags and portal access, written once and read by every other module.
Bulk import with a validation preview · ID cards · duplicate merge with audit
The profile is the spine of the system. Attendance, marks, behaviour, health and communications all write back to it, so nobody has to ask three people to answer one question about a child.
A family is modelled once. Change a phone number and it changes for every child in that household, and a sibling view shows the whole family at a glance.
Bulk import runs as a preview first: it validates every row, shows you the counts, and hands back an error file for the rows it could not accept. Nothing is written until you accept the preview.
Status drives what the system does. Moving a student to withdrawn closes portal access, removes them from messaging audiences and triggers the leaving-certificate workflow — while every record they generated stays intact.
Constraints are the difference between a record system and a spreadsheet. These are enforced by the product, not by training.
A student cannot be enrolled in two sections of the same academic year, so class lists always reconcile with the roll.
A student with attendance or marks can only be withdrawn or archived. History stays auditable.
Guardian phone or email is required, because a student with no reachable adult breaks every alert the school depends on.
Where a national identifier is captured it must be unique, which is what makes duplicate detection reliable.
A court-order restriction on a guardian removes their portal access to that child rather than relying on staff memory.
Two duplicate records can be merged, but the merge is recorded with who did it and what was combined.
The record captures what your country actually asks for. These are not translations — the fields, labels and validation change with the education-system profile.
The student record is written into by almost everything. These three touch it most.
We configure a tenant with your education-system profile before the call, so the fields and labels are yours.