SCHOOL MANAGEMENT · LEADERSHIP AND REPORTING
Which School Reports Should Management Review Every Week?
A decision-led guide to choosing a manageable weekly school review across attendance, admissions, fees and operational exceptions.
Conceptual product view · no customer records or performance figures
THE SHORT ANSWER
A useful weekly school review focuses on operational items that can still be acted on: incomplete attendance, admissions needing a next step, fee exceptions requiring verification and time-sensitive academic or administrative issues. Select reports based on the school’s actual workflow, define the period and owner, and confirm product availability before making a report part of the routine.
01 / SET THE WEEKLY QUESTION
Choose decisions that have a short enough horizon to act on.
A weekly meeting should surface work that can be resolved before it becomes a month-end issue: missing entries, pending hand-offs, upcoming admissions actions or a financial discrepancy that needs checking. Avoid loading the agenda with information that cannot change this week.
Define the reporting window and which role owns each question. Compare equivalent school days when holidays or examinations change the normal schedule.
02 / ATTENDANCE COMPLETENESS
Check whether expected sessions and records have been captured.
A weekly check may ask whether attendance is complete for the sessions that actually took place. Confirm the timetable and roster before treating a blank as absence or an unusual total as a pattern.
Keep follow-up private and supportive. Attendance records can prompt a conversation but do not explain an individual learner’s circumstances.
03 / ADMISSIONS & HAND-OFFS
Review requests that lack a clear next step or responsible person.
Where the school uses an admissions workflow, identify records that need a decision, document check or communication. Review status meaning and effective dates; an old or ambiguous status may not describe current work.
Do not count every enquiry as an admission opportunity without understanding the process. Use the review to clarify responsibility and resolve genuine bottlenecks.
04 / FEES & EXCEPTIONS
Focus on items that need verification rather than broad collection pressure.
A weekly finance review can surface unmatched receipts, unclear instalment context or an approved adjustment awaiting record completion. Check the underlying receipt and agreement before contacting a family.
Keep individual financial information within authorised roles. Totals need a defined period and should not be interpreted as a performance judgement without relevant context.
05 / UPCOMING OPERATIONS
Use the next week’s calendar to prevent avoidable surprises.
Review events that require staff coordination, such as examinations, schedule changes or planned communication, where those are part of the school’s established process. Confirm who will update affected teams and families.
A calendar or report does not prove a message was received. Check the communication channel and follow-up responsibility separately.
06 / CLOSE THE MEETING
Record decisions and defer anything that needs deeper monthly analysis.
Capture the decision, owner, due date and evidence to revisit. Leave unresolved causes as questions rather than implying certainty from an incomplete view.
Keep the weekly routine proportionate. If a topic requires trend analysis or policy discussion, schedule a separate review with the appropriate people.
A FIELD GUIDE FOR YOUR TEAM
A weekly school operations review
Keep the review short: focus on exceptions and upcoming decisions, not a full inspection of every record.
| Lens | Question to ask | What to record |
|---|---|---|
| SET THE WEEKLY QUESTION | Choose decisions that have a short enough horizon to act on. | A focused agenda with weekly owners and time window. |
| ATTENDANCE COMPLETENESS | Check whether expected sessions and records have been captured. | A session-completeness check and assigned exception owner. |
| ADMISSIONS & HAND-OFFS | Review requests that lack a clear next step or responsible person. | A next-step list with clear owners and due dates. |
| FEES & EXCEPTIONS | Focus on items that need verification rather than broad collection pressure. | A verified exception queue with an accounts owner. |
| UPCOMING OPERATIONS | Use the next week’s calendar to prevent avoidable surprises. | A short look-ahead with communication and readiness owners. |
| CLOSE THE MEETING | Record decisions and defer anything that needs deeper monthly analysis. | A brief decision log and a separate path for deeper review. |
CODEPEX IN CONTEXT
Useful guidance begins with clear scope.
School ERP reporting capabilities and specific report names should be checked against the current public registry and product demonstration. The examples below are decision categories, not a promise of a particular report or filter.
Product-specific statements are based on the current owner-controlled capability declaration. Ask CodePex to confirm any institution-specific configuration or unlisted requirement.