Leadership Experience Case Study
Many school operational problems are not caused by lack of effort. They are caused by different teams working with different versions of the truth.
During one school leadership assignment, a review of transport and meal services exposed a significant mismatch between students recorded as opting for a service, students actually using it and families whose payment had been recorded.
In one snapshot, more than four hundred students were recorded as having opted for transport, while payment records covered only a little over half that number. Meal records showed a similar gap: registrations, approximate daily users and recorded payments were three different figures.
The problem was not simply unpaid fees. The first problem was that the school could not make a reliable decision until the datasets were reconciled.
Three Lists Can Describe Three Different Realities
Schools often maintain operational information across several systems:
- admission or ERP records;
- transport department lists;
- meal or cafeteria lists;
- accounts payment records;
- daily attendance or usage information;
- parent requests made through email, forms or WhatsApp.
If one system says a student has opted for transport, another says no payment is recorded and the bus attendant sees the student every day, which record should leadership trust?
The answer is not to choose one list. It is to reconcile them.
Do Not Begin With a Mass Reminder
When payment gaps appear, the fastest response is often to send the same reminder to every parent. That may be administratively easy but creates avoidable frustration for families who have already paid or never opted for the facility.
In this case, the immediate operational direction was to compare the opted list with the paid list and obtain name-level clarity. Parent reminders were then intended only for families whose payment remained outstanding.
This is a small example of a larger principle:
Communication quality depends on data quality.
Separate Registration, Usage and Payment
A robust service-control system should distinguish at least three statuses.
1. Registered
The family has formally requested the facility.
2. Active user
The student is actually receiving the facility.
3. Payment status
The required payment has been received, is pending, has been waived or has another authorised status.
These fields should not be assumed to mean the same thing.
A Practical Reconciliation Process
- Freeze the reporting date. Decide the date for which the comparison is being made.
- Export the registration list. Record every student formally opted into the service.
- Confirm actual usage. Validate who is currently using transport or meals.
- Match payment records. Reconcile accounts against student identifiers, not only names.
- Investigate exceptions. New admissions, withdrawals, concessions, temporary usage and recent payments may explain differences.
- Assign ownership. One responsible person should maintain the final reconciled list.
- Communicate selectively. Send reminders only to the relevant families.
- Repeat periodically. Service data changes throughout the year and cannot be reconciled once and forgotten.
Why This Matters Beyond Fees
Accurate service data affects much more than revenue.
Transport numbers influence route planning, bus capacity, staffing and safety. Meal numbers influence procurement, food preparation, wastage and supervision. Incorrect data can therefore create both financial and operational risk.
A school that prepares meals for registered students rather than realistic daily users may waste resources. A transport department using outdated lists may plan routes incorrectly. An accounts team working without service-usage information may chase the wrong families.
One Source of Truth Does Not Mean One Department
Different departments still need to own their work. The transport team should know routes and active users. Accounts should control payments. Admissions should maintain enrolment data.
But leadership needs a common reconciliation point where those records meet.
This can be a well-designed ERP workflow or a controlled master sheet. The technology matters less than the discipline: definitions must be clear, records must be current and someone must be accountable for exceptions.
The Leadership Learning
The case reinforced a principle that applies across school operations:
Before asking people to act, make sure the institution knows exactly who needs to act.
Mass reminders, route changes, facility suspension or procurement decisions should not be based on approximate data when name-level information is available.
Good school operations are often invisible. Parents notice them mainly when something fails. Behind that reliability is a simple but demanding habit: reconcile the data before making the decision.