Databus Logo
Blog Login →
The Live Single-School Dashboard for Principals & Trustees

"Get me the figures." Three days later, a report that's already out of date. Or: open the dashboard, now.

This is the live single-school picture a Principal runs the school on — fee-collection rate, period-wise attendance, exam-result trends and syllabus pacing, current this morning — instead of waiting on a hand-compiled month-end report. Reporting on what's happened, not prediction.

For Principals, vice-principals & trustees · live rate/trend/pacing · single school · routes to prediction, forecast & cross-campus where needed.

See the live dashboard →
In plain English

School analytics & reporting is the live single-school dashboard a Principal opens to see where the school stands right now — fee-collection rate against target, period-wise attendance, exam-result trends, and syllabus pacing across sections — instead of waiting for the office to compile a month-end report. It's reporting on what's already happened, drawn live from the fee, attendance, exam and lesson-planning modules. The forward-looking at-risk early warning on individual students is the student-performance-AI feature; the fee-default forecast is fee-prediction; the cross-campus comparison across several schools is the multi-branch use case; the change trail is audit-logs. This page reports; those predict, forecast, compare and record.

Live, not month-end
current this morning,
not a stale PDF
Rate · trend · pacing
on what's already
happened
Single school
the deep drill-down,
not cross-campus
Reporting
not prediction —
that's its own page
A real morning · K-12 school · the Principal's live dashboard

Four numbers a Principal actually runs the school on — and where each one sends you next.

Mr Verghese opens the dashboard at 09:00 instead of asking the office for a report. Most of it is steady; the value is that the one metric drifting is visible now, and the dashboard hands him to the module that can act on it.

Live dashboard · single school · this morning Reporting, not prediction
MetricWhat it reportsReadingIf it's off, go to
Fee-collection rate% of term target collectedon trackforecast → fee-prediction
Attendanceperiod-wise & class-wisesteadyper-student → at-risk warning
Exam-result trendacross terms, by classone class dippingindividual → student-performance-AI
Syllabus pacingsection vs expected2 sections behindplans → lesson-planning
The dashboard's job is to make the two amber rows — a class whose result trend is slipping, two sections behind on syllabus — visible at 09:00 rather than at month-end. But notice the last column: this page reports the state and then routes — the individual at-risk student to student-performance-AI, the fee forecast to fee-prediction. It tells the Principal where to look; it doesn't predict who'll fail.
Where a Principal flies blind on their own school

Four ways the numbers reach a Principal too late to use.

The three-day-old report

The Principal asks the office for the figures, waits days for a formatted report, and by the time it lands the situation has moved. Decisions get made on last month's reality.

Four systems and a spreadsheet

Fees in one place, attendance in another, marks in a third, syllabus in a teacher's diary — assembling one picture means opening everything and stitching it by hand, so nobody does it weekly.

The dip noticed at term-end

A class's results slide, or two sections fall behind on syllabus, and it's only visible when the term's over — when there's no time left to do anything about it.

Office hours lost to compiling

Staff spend days each month assembling routine reports by hand for the Principal and trustees — time that should go to running the school, spent formatting numbers that a live dashboard would just show.

How a Principal reads the school live

Open the dashboard, read the state, route the question.

1

Open the live dashboard, not a month-old PDF

Instead of asking the office to compile a report, the Principal opens a dashboard that's already current — drawing live from the fee, attendance, exam and lesson-planning modules of the same school. The numbers are as of this morning, not last month.

2

Read the fee-collection rate against target

See what proportion of the term's fees is collected against target, and how that rate is moving, so a collection falling behind is visible while there's still term left to act — the action itself happening in the fees and reminders modules.

3

Read attendance and result trends

See period-wise and class-wise attendance and exam-result trends across terms — what's actually happened, as rates and trends, so the Principal knows which class or subject is moving the wrong way without reading every mark sheet.

4

Read syllabus pacing across sections

See how far each section has progressed through the syllabus relative to where it should be. The pacing data comes from the lesson-planning module; this dashboard surfaces it alongside the rest.

5

Send the right question to the right module

When the dashboard shows something off, the Principal goes to the module that owns it — an individual student who may need intervention to the at-risk early-warning, a fee-default forecast to fee-prediction, the cross-campus comparison to the multi-branch use case. This dashboard reports; those pages predict, forecast and compare.

Reporting, honestly framed

It shows you what is — it doesn't claim to know what will be.

Reporting, not prediction

This dashboard reports rates, trends and pacing on activity that's already happened. It does not forecast or score the future — the forward-looking work is owned by separate, explainable features. Keeping that line clear is what makes the numbers trustworthy.

No invented benchmarks

The dashboard shows your school's own figures against your own targets — it doesn't manufacture an industry "score" or a comparative percentile out of thin air. A real number against a real target beats a flattering invented one.

Live from the source modules

Every figure is drawn live from the module that owns it — fees, attendance, exams, lesson-planning — so the dashboard is a view, not a second copy of the data that can drift. Each number stays owned by its module; this page reads it. Data handled under DPDP Act 2023.

Framework references: DPDP Act 2023 (school data, role-governed access). This is operational reporting on completed activity, not prediction — the at-risk early-warning is owned by the student-performance-AI feature (an explainable model, reviewable by the academic head, never a black-box verdict), and the fee-default forecast by the fee-prediction feature. Figures shown here are illustrative of metric types, not performance claims.

Reporting vs prediction vs forecast vs cross-campus vs audit · what this page owns

Live single-school reporting ≠ at-risk prediction ≠ fee forecast ≠ cross-campus comparison ≠ the change trail.
This page owns the live picture; the rest are their own pages.

SchoolDeck keeps the live operational dashboard distinct from the forward-looking prediction features and from the cross-campus group view on purpose — so this page ranks for the Principal's "where do we stand now" and never competes with the prediction or multi-campus pages.

This page owns

  • The live single-school dashboard — where the school stands this morning.
  • Fee-collection rate, attendance, result trends, syllabus pacing as live reporting.
  • The "stop waiting for month-end reports" Principal outcome.
  • Reporting on completed activity — rate, trend, pacing, not a forecast.
  • Routing the Principal to the module that can act on what's off.

This page defers to

  • Forward-looking at-risk early warning on individual students (explainable model, confidence interval) — lives in Student-Performance-AI. This page reports; that page predicts.
  • Fee-default forecast — which families may slip before the due date — lives in Fee Prediction. This page shows the rate; that page forecasts the slip.
  • Cross-campus comparison across several schools for a Trust head — lives in the Multi-Branch use case, which routes into this page for the per-school detail.
  • The forensic change trail — who edited which number and when — lives in Audit Logs. This page shows the state; that page shows the history.
Three reading-the-school realities

The same live dashboard, three readers.

The dashboard is the same; what each reader watches for shifts with the role.

Principal

The Monday-morning read

A Principal opens the dashboard each morning to see fees, attendance, results and pacing at a glance, and catches the class slipping or the section behind while there's term left to act — then routes the specific case to the module that owns it.

Trustee (single school)

Oversight without the wait

A trustee of one school gets the same live picture for governance, instead of a monthly pack — with a view set by role-based access. For a trustee across several schools, the cross-campus view is the use case above this one.

Academic coordinator

Watching the academic side

A coordinator watches the result trends and syllabus pacing most closely, spotting the subject moving the wrong way — and takes an individual student to the at-risk warning when the live trend suggests a closer look.

From the field

Thrissur, Kerala · CBSE senior secondary school · Principal.

"For most of my years as Principal, 'how is the school doing' meant sending a note to the office and waiting two or three days for a report that was already out of date by the time it reached me — fees from one register, attendance from another, marks from a third. What I wanted was simply to open one screen in the morning and see where we stand today. Now I do. Last month it showed me one class whose result trend had dipped and two sections that had fallen behind on the syllabus, and I could see it in the first week, not at the term-end review. I'll be precise about what it is, because I asked the team this directly: it shows me what has happened, it doesn't pretend to predict who will fail — when I want to look closely at a particular child, it sends me to the proper early-warning tool for that. And it's my school's numbers against my school's targets, not some invented score. That honesty is exactly why I trust the screen."
Mr. George Verghese Principal · CBSE senior secondary school · Punkunnam, Thrissur-680002, Kerala
Live single-school dashboard · fee-collection rate / attendance / result trends / syllabus pacing · reporting on completed activity, not prediction · routes individual cases to the at-risk and forecast features
Quick answers

School analytics & reporting, asked and answered.

What every Principal, vice-principal and trustee asks before they swap month-end reports for a live dashboard.

What does school analytics & reporting do?
It gives a Principal a live, single-school dashboard of the numbers that run the school — the fee-collection rate against target, period-wise and class-wise attendance, exam-result trends across terms, and syllabus-completion pacing across sections — so they can see where the school stands this morning instead of waiting for a clerk to compile a month-end report. It is operational reporting on what has already happened, drawn live from the fee, attendance, exam and lesson-planning modules. It reports; it does not predict.
How is this different from student-performance AI?
This page reports what has happened — rates and trends across the school. The student-performance-AI feature is forward-looking: it flags an individual student who may be at risk before exam season, using an explainable model with a confidence interval per flag. Reporting and prediction are different jobs: this dashboard tells the Principal where attendance and results stand now; the at-risk feature points at a specific student who may need intervention next. They connect — but one is the live picture and the other is the early warning, and they live on separate pages.
Does it predict fee defaults?
No — it shows the current fee-collection rate and how it is trending, which is reporting on what has happened. The forward-looking forecast — which families are likely to default before the due date, so reminders can be targeted — is owned by the fee-prediction feature, not this dashboard. This page tells the Principal "collection is at this rate and moving this way"; fee-prediction tells them "these specific accounts are likely to slip next." Keeping reporting and forecasting on separate pages stops "where we are" from being confused with "where we are heading."
Can it compare several schools in a Trust?
This page is single-school analytics — the deep drill-down into one school's numbers. The cross-campus comparison, where a Trust head looks across several schools at once to see which campus needs attention, is the multi-branch group-oversight use case, which routes into this page for the per-school detail. So the two work together at different altitudes: the group view surfaces the campus, and this dashboard explains what is happening inside it. For one school, this is the page; for the group, start at the multi-branch use case.
How live is the data really?
It draws directly from the operational modules — fees, attendance, exams, lesson-planning — so the figures reflect what those modules hold as of now, rather than a snapshot someone exported last month. When a fee is collected or attendance is marked, it flows into the dashboard. The whole point of the page is to remove the lag between something happening in the school and the Principal being able to see it, which is exactly the gap a manually compiled monthly report leaves open.
Which numbers does the dashboard actually show?
The operational ones a Principal runs the school on: fee-collection rate against the term target, period-wise and class-wise attendance, exam-result trends across terms, and syllabus-completion pacing across sections. These are rates, trends and pacing — the live state of the school. The dashboard surfaces them in one place from the modules that produce them, so the Principal is not opening four systems and a spreadsheet to assemble the picture each morning.
Does it show the audit trail of who changed a number?
No — it shows the numbers, not the forensic history of edits. The complete, immutable record of who changed which fee record or mark and when is owned by the audit-logs feature, which exists for financial audits and CBSE inspections. This dashboard reads the current figures; if a Principal needs to see who altered a value, that is the audit-logs page. Keeping the live dashboard and the change trail separate means each does its job cleanly — one shows the state, the other shows the history.
Can a trustee see it, or just the Principal?
Both, governed by role-based access. A Principal sees the operational dashboard for their school; a trustee can be given a reporting view appropriate to their oversight role. What each person sees is set by the role-based-access model, so the dashboard respects who should see what. For a trustee overseeing several schools, the cross-campus view is the multi-branch use case; for the single school, this dashboard is the shared live picture for the Principal and the trustee of that school.
Does the Principal still need to wait for the office to make reports?
That is exactly the problem this page removes. The point is that the dashboard is already compiled and current, so the Principal does not send a request to the office and wait days for a formatted report that is out of date by the time it arrives. The numbers are there to open. The office staff are freed from assembling routine reports by hand, and the Principal makes decisions on this-morning's figures rather than last-month's — which is the whole reason a live dashboard beats a monthly compilation.

Stop sending the office for figures and waiting three days.
Open the school, live, this morning.

We'll show you the live single-school dashboard — fee-collection rate, attendance, result trends and syllabus pacing — and how it routes you to the right module when something's off, in a demo on your school's actual data.

Book the Dashboard Demo →