A Principal’s Daily Dashboard: 10 Numbers to Watch

A dashboard answers one question quickly: where do I need to be today? Whether you read it on a phone at 7.45 a.m. or on the office screen at 8.30, it should point you towards the classroom without teachers, the bus that is late, the fee deficit that is growing, the pile of unanswered parent queries.

The test of every number is whether it changes a decision. A figure that is nice to know but never triggers anything belongs in a monthly report, not the daily view. The list below is a starting point; adjust it to the size of your school.

You will notice a mix of academic, financial and safety items. That is deliberate; a principal who sees only marks misses the bus, and one who sees only money misses the child.

Attendance and marking (1, 2, 9)

Attendance is the earliest signal of trouble. A gap in one class on Monday might be a cricket match; a gap in a dozen classes might be a rumour or an illness. The unmarked-class count is a discipline check: if the principal sees it every day, teachers mark on time.

Chronic absentees deserve their own line because individual children are lost in averages. A child absent four days in two weeks should trigger a call home, not a note at the year-end.

Staff coverage (3)

Uncovered periods mean children sitting without a teacher, and parents notice. Seeing them at 8 a.m. gives you time to arrange substitutes.

Money (4, 5)

You do not need accounts-level detail. Know whether collection is on track and whether old dues are growing. The cause of a problem is for the accountant to investigate; your job is to notice it early. For practical steps once you do, see reducing fee defaulters without upsetting parents.

Safety and service (6, 7)

A late bus is a parent calling the office. A complaint older than your promise is a parent posting online. Both are easy to see if the data is in one place.

Growth and planning (8, 10)

In admission season the enquiry funnel is a second heartbeat; out of season, keep the deadlines list visible so nothing sneaks up.

A dashboard is only as good as its inputs. If teachers mark attendance late, the number is wrong at 9.30. If receipts are entered at the end of the week, the fee figure is stale. Before you build any dashboard, agree the data-entry rules: attendance marked by 9.15, receipts posted the same day, queries logged when received.

Insist that every number can be drilled into. If attendance in Class 7B looks low, one click should show the students. A number that cannot be traced will be argued with. That is how you know a dashboard is computed from live records and not typed into a presentation. Takshiva’s school analytics and the principal’s view are built on this idea, with figures taken from the school’s own records.

1. 7.45 to 7.50: staff and uncovered periods. Arrange substitutes.
2. 7.50 to 7.55: bus status and any overnight parent messages.
3. 9.30: attendance marked or not. Ask coordinators for missing classes.
4. 9.40: attendance by class, one look at the lowest and the highest.
5. Before lunch: fee collection versus target, new enquiries, open queries.
6. Friday: weekly numbers 5, 8, 9 and 10, then decide what you will say on Monday’s briefing.

Hold a ten-minute huddle with the coordinators twice a week where each person reports on their number and on one action. The dashboard should drive a conversation, not replace it.

• Too many tiles. Twenty indicators means none gets attention. Keep the daily view to ten, and put the rest behind drill-downs.
• Red-green without context. A red number needs a threshold you chose, and a note of why it matters.
• Naming and shaming. Showing a teacher’s late marking to the whole staff breeds resentment. Use it privately first.
• Averages that hide problems. School-wide attendance of 94 per cent can conceal one class at 70.
• Ignoring the unmeasured. Culture, bullying and teacher morale do not show on tiles. Walk the school too.

If you lead a group of schools, the same ten numbers per branch make a useful central view; see running a multi-branch school.

The scenario below is invented to show how the numbers work together; your own thresholds will differ. On Monday the dashboard shows two classes unmarked at 9.30. The principal asks the coordinator to follow up, and both are marked by 9.45. Tuesday begins with three periods uncovered because two teachers are on leave; the vice-principal assigns free teachers before first bell.

On Wednesday collection against the monthly target is behind the usual pattern. The principal does not chase parents; she asks the accountant for the overdue list by age and finds that the oldest band belongs to a single class whose instalment date was changed mid-term without a clear notice. A short message to those parents clears most of it within days.

On Thursday, bus 4 shows no signal for twenty minutes in the afternoon. A call to the driver reveals a puncture; parents are told and a replacement vehicle is sent. On Friday the weekly review shows one student absent on six of the last ten days. The class teacher calls home and learns of a family illness. The school arranges notes and a gentler schedule rather than waiting for the year-end.

None of these needs a sophisticated tool. They need numbers that are current, a habit of looking, and people who know what to do next. That is the whole value of a dashboard, and it is why the first improvement most schools should make is not a new screen but quicker data entry.