Attendance, fee, payroll and communication reporting from the same records the institution runs on, plus the custom ones you define.
Book a demoThe board meets on Thursday. On Wednesday somebody exports four systems into a spreadsheet, reconciles the figures that disagree, and produces a pack that is accurate as of Tuesday afternoon.
A trustee asks a follow-up question in the meeting. Answering it means going back and doing the whole exercise again for one number.
When reports read the live records, the pack is current and the follow-up is a filter rather than another Wednesday.
Grouped by the job it does rather than listed as one long set of features.
By class, section, student or period, including the percentages certificates and boards need.
Outstanding by class and campus, collection against expectation, and the defaulter view as it stands now.
Salary cost by department and campus, from the runs already processed.
Headcount, admissions, withdrawals and movement between classes over time.
What was sent, to whom and whether it was delivered, which matters when a family says they were never told.
Definitions you build and save, so the report your board asks for every term is produced rather than rebuilt.
Each campus on its own and the group consolidated, from the same entries rather than from campus summaries.
Formatted for the pack rather than exported as a grid somebody has to lay out.
A report run on Thursday reflects Thursday, which is the whole point.
The pack that was accurate on Tuesday. Assembled on Wednesday for a Thursday meeting, from exports taken whenever each system was free. The numbers describe a moment that has passed.
The follow-up question. A trustee asks something adjacent to the report. Answering it means repeating the whole assembly exercise for one figure.
The two reports that disagree. Fee collection from one system, accounts from another, and a difference nobody can explain because the export times differed.
The report rebuilt every term. The same custom breakdown produced from scratch each time, because there was nowhere to save the definition.
These are the cases worth testing in a demo. Bring the messiest one you have.
The same records, presented differently depending on the job.
Run the standing reports themselves rather than requesting a pack and waiting.
Produces operational reporting without exporting and reconciling first.
Their own subject or section, not the whole institution.
A report shows what that role is permitted to see, so reporting does not become a way around permissions.
Reports read the same records every module writes to, which is why the fee figure in a report is the fee figure in the ledger. There is no export step and therefore no reconciliation step.
Multi-campus roll-up uses the same structure the institution already has. Permissions decide what a report shows, so reporting cannot be used to see around an access rule.
That is why a report is current rather than a snapshot of whenever somebody last had time to build it.
What changed when group reporting stopped being a manual roll-up.
School system · 2,400 students · PK
A school system replaced a manual month-end roll-up with reporting that reads every campus from the same records.
The parts of the institution this touches most.
The report you assemble every term and how long it takes. That comparison usually makes the argument without us saying anything.
Book a demo