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 demoAdmissions, attendance, timetables, exams, report cards and parent messaging — configured for your country's education system, not someone else's.
✓ 35 modules ✓ 9 education-system profiles ✓ One tenant, several ladders
Bilal was marked absent for this morning's register. Reply LEAVE to submit a leave application.
Delivered 08:13
A register book, WhatsApp groups, spreadsheet mark sheets, a fee ledger, a separate accounts package and a filing cabinet. Each one holds part of the same student, and nobody holds all of them.
Nothing reconciles, so every question becomes a phone call.
Written once, read by every module that needs it.
CampusFlo ships nine education-system profiles, and a profile is configuration rather than a separate build. It sets the level ladder, the term structure, the grading scheme, the attendance model and the words the screens use — and every value stays editable afterwards.
Nothing below is a translation layer. The ladder, the identifiers, the grading scheme and the vocabulary are the product's own data, which is why a school running a national stream and a Cambridge stream can run both in one tenant.
See the Pakistan profileStudent record · Pakistan (national)
Student record · United Kingdom
Student record · United States (K-12)
A parent walks in, or rings during break, or fills in the form on your site. Right now that enquiry lives on a diary page or in somebody's WhatsApp thread. Here it becomes a record with a counsellor, a stage and a date for the next call.
Fields for selling software to a business.
Fields for a family asking about a seat.
Every general-purpose CRM will happily hold a phone number. None of them know that the question is which child, for which class, starting when — or that a date of birth has to be checked against the intake cut-off before anyone promises a seat.
The record also carries the campus, the intake, the previous school, transport and hostel interest, the source it arrived from and whether the family agreed to be messaged. Those fields are not customisation. They are the reason the follow-up is useful.
The pipeline — seven stages, and yours if you want different ones
Stages are configurable — a school that runs a fee discussion or an interview round inserts its own and the reports follow it. “Not interested” keeps its reason rather than being deleted, so next year’s planning can see that eleven families walked because Class 4 had no seat.
The desk opens on Overdue, Today and Upcoming rather than on everything ever recorded. Any open enquiry nobody has touched for seven days is flagged, whether or not the counsellor remembered it. Assignment is manual, default or round robin.
A phone number that already exists surfaces the family’s earlier enquiries before a second record is created. Usually it is the same parents asking about a second child, and three children at one school is normal here — so it is linked as a sibling.
Convert to application opens the admission form already filled in, after checking that the intake is open, the class is offered and the child is old enough. Click it twice and you land on the same application — never a second one.
CampusFlo holds the enquiry
The record, the pipeline and the school’s own rules.
Foxaf talks to the family
Our sister product, and deliberately a separate one.
Every module writes into the same student record, so work done once is not done again. Eighteen of them make up the school core; the rest cover boarding, inclusion, safeguarding, statutory returns and the public-facing site.
Most school systems cover attendance, marks and fees, then stop. These are the ones inspectors, boards and parents ask about — and the ones a school discovers are missing after it has already bought something else.
Restricted concern records with a chronology, referral tracking and an access audit on every view.
Support plans with targets and reviews, and exam access arrangements that reach the seating plan.
Nurse visits, medication logs with consent, care plans and an emergency summary staff can see.
Board and government exports built from the same data — BISE and FBISE lists, the UK census, US state files.
CampusFlo runs on a production ERP, so accounting, payroll, purchasing and the canteen counter are part of the same system rather than something to integrate later. Schools buying elsewhere buy a school system, then buy accounts, then reconcile the two by hand.
It also connects to Foxaf for WhatsApp, campaigns and automation, so a school runs its admissions marketing without buying a separate tool for it — how the two divide the work.
Double-entry ledgers, vouchers, banking and financial reporting.
Teachers and staff are employees: leave, shifts, payroll, self-service.
A point of sale that keeps working through an internet outage and syncs on reconnect.
Uniforms, stationery, lab supplies and assets across campuses.
Admission enquiries with sources, follow-ups and conversion tracking.
WhatsApp, SMS, email and in-app, with templates and delivery logs.
Permissions are set per action and per role, so a subject teacher, a nurse and the principal open the same system and see different things. Sensitive records — health, inclusion, safeguarding, counselling — sit behind their own permissions with an access audit.
Today, across every campus, without asking anyone for a report.
Built for a phone between lessons, scoped to your own classes.
One login for every child, even across campuses.
Age-appropriate by policy — read-only or off for the youngest.
The record of truth, and the paperwork that comes out of it.
Medical notes, safeguarding concerns, custody arrangements and exam results are not ordinary data, and CampusFlo treats them accordingly. Access is granted per action, masked per field and audited on every view.
A role sees the fields its job needs. Others are hidden rather than merely read-only, and never appear in exports.
Health, inclusion, safeguarding and counselling each sit behind their own permission, separate from general staff access.
Opening a sensitive profile is recorded. Concerns cannot be deleted, only voided with a reason and an author.
Guardians choose channels and language, and consent is captured against the record rather than assumed.
Subject-access export and erasure workflows, with retention rules that run as scheduled jobs.
Education-records access is configurable per profile — FERPA in the US, GDPR in the UK and EU, and court-order flags on custody.
Setup is configuration rather than development, because the education-system profile does most of the work. You pick a profile, we import what you already have, and your staff train on your own data.
Pick your education system, confirm the ladder and vocabulary, add campuses, shifts and your print identity.
Students, guardians and staff from spreadsheets, with a validation preview and an error file before anything is written.
Sections, subjects, the curriculum map, teaching assignments and the timetable for the current year.
Role-based training on your own data, then registers, homework and parent messaging from day one.
Forty minutes, a screen-share, and your levels, your grading scheme and your board — not a slide deck.
Bring your student count, your campuses and whatever you use today.