Reports nobody has to assemble

Attendance, fee, payroll and communication reporting from the same records the institution runs on, plus the custom ones you define.

Book a demo

What this usually looks like today

The 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.

What it handles

Grouped by the job it does rather than listed as one long set of features.

Attendance reporting

By class, section, student or period, including the percentages certificates and boards need.

Fee and collection

Outstanding by class and campus, collection against expectation, and the defaulter view as it stands now.

Payroll and cost

Salary cost by department and campus, from the runs already processed.

Enrolment and progression

Headcount, admissions, withdrawals and movement between classes over time.

Communication logs

What was sent, to whom and whether it was delivered, which matters when a family says they were never told.

Custom reports

Definitions you build and save, so the report your board asks for every term is produced rather than rebuilt.

Multi-campus roll-up

Each campus on its own and the group consolidated, from the same entries rather than from campus summaries.

Print-ready output

Formatted for the pack rather than exported as a grid somebody has to lay out.

Current, not compiled

A report run on Thursday reflects Thursday, which is the whole point.

How reporting fits the year

The same reports, current whenever they are run.

  1. Every day

    Attendance, collections and messages sent, as they stand now.

  2. Every month

    Outstanding fees by class and campus, and salary cost from the runs already processed.

  3. Every term

    Enrolment, admissions, withdrawals and progression over time.

  4. For the board

    Saved definitions produce the pack rather than rebuilding it, formatted for print.

  5. For the group

    Each campus on its own and the group consolidated, from the same entries.

The cases most systems get wrong

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.

Who touches it, and what they see

The same records, presented differently depending on the job.

Leadership and trustees

Run the standing reports themselves rather than requesting a pack and waiting.

The office

Produces operational reporting without exporting and reconciling first.

Heads of department

Their own subject or section, not the whole institution.

Access follows the role

A report shows what that role is permitted to see, so reporting does not become a way around permissions.

What it shares records with

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.

An institution that did this

What changed when group reporting stopped being a manual roll-up.

School system · 2,400 students · PK

Bringing several campuses into one set of numbers

A school system replaced a manual month-end roll-up with reporting that reads every campus from the same records.

Same day
Group reporting
One record
Across campuses
Read the full story

Setting it up

Standing reports work as soon as the modules feeding them are live, because they read the records the institution is already keeping. There is nothing to configure for attendance, fees or payroll reporting.

Custom reports are built once with your definitions, usually starting with the pack your board asks for every term, and then run whenever they are needed.

Questions we get asked

Are reports current or do they need building first?
Current. They read the live records, so a report run on Thursday describes Thursday rather than whenever somebody last had time to assemble the exports.
Can we save a report definition?
Yes. The custom breakdown your board asks for every term is defined once and produced thereafter, rather than rebuilt from scratch each time.
Can leadership run reports without asking the office?
Yes, within what their role is permitted to see. Reporting follows the same access rules as everything else, so it cannot be used to see around a permission.
Do reports consolidate across campuses?
Yes - each campus on its own and the group together, from the same entries rather than from campus summaries somebody prepared.
Can we see whether a message was actually delivered?
Yes. Communication logs record what was sent, to whom and the delivery result, which is what settles a conversation with a family who says they were never told.
Is the output ready to put in a board pack?
Yes, formatted for print rather than exported as a grid somebody then has to lay out.

Bring your board pack

The report you assemble every term and how long it takes. That comparison usually makes the argument without us saying anything.

Book a demo