Run four campuses without four versions of the truth
The hardest part of running a group is not any single campus it is that every campus reports differently. One school counts attendance monthly, another weekly; one sends fee summaries in a spreadsheet, another on WhatsApp. KIDUART puts an organisation layer above the schools so definitions are shared, each campus keeps its own data boundary, and the group sees a rollup it can actually act on.
Roles this covers
- Organisation owner
- Organisation admin
- Group manager
- Trustee
Challenges and answers
What school groups tell us goes wrong and what replaces it
Each row names the manual problem, what it costs, and the module that removes it. Follow the module link to see how that module is built.
- Challenge 01
Each campus reports in its own format
Board meetings start with reconciling numbers instead of deciding anything.
In KIDUARTConsolidated and custom cross-school reports read the same fields from every campus, so comparisons are structural rather than negotiated.
- Challenge 02
No clear record of who can do what, where
Access spreads through informal permissions and leftover logins.
In KIDUARTSchool admin account management delegates each campus explicitly, and org member roles control the group layer itself.
- Challenge 03
Separate software bills and renewal dates per campus
Finance chases invoices instead of planning the year.
In KIDUARTOrg-level subscription and billing keeps plans, add-ons, invoices and payment methods in one place for the whole group.
- Challenge 04
New campuses take a term to set up
Growth is limited by admin capacity, not demand.
In KIDUARTMulti-school administration adds a campus with the group's session, branding and preferences already defined.
A typical day
How the day runs for school groups
- Monday morningOpen the organisation dashboard and read the health score per campus.
- MidweekCompare attendance and collection across campuses on the same definitions.
- Month endGenerate a consolidated report for the board from live data.
- Quarter endReview subscription usage, invoices and add-ons at group level.
What you get on day one
- Organisation dashboard with campus health analytics
- School list with comparison and headcounts
- Delegated school admin accounts per campus
- Consolidated and custom cross-school reports
- Group subscription, invoices and billing portal
- Organisation-level support tickets
Panels this role signs into
Module areas behind this role
Questions we get
School groups and trusts straight answers
Does each campus see the other campuses' data?
No. Data is isolated per school, and the organisation layer only reads what it is entitled to for reporting. School staff continue to work inside their own campus.
Can campuses keep different fee structures and sessions?
Yes. Fee structures, classes and sections are configured per school, while the organisation defines shared preferences such as branding, reporting scope and subscription.
How is billing handled for a group?
Subscription and billing can be managed at organisation level with one plan, add-ons and consolidated invoices instead of separate agreements per campus.
See KIDUART from the school groups point of view
We will run the demo in the panel this role uses, on a scenario you bring from your own school.
30-minute walkthrough
Booked around your school hours
Run on your own data
Your fee heads, classes and staff roles
No card, no lock-in
Nothing is charged to see the product