Choose the decisions the meeting should support
Start with the work the principal and coordinators can influence during the coming week. Examples include clearing unresolved office requests, arranging class cover or addressing repeated timetable conflicts. A report belongs in the review when it helps identify a decision, a question or an action that needs leadership attention.
Keep routine information available as background rather than reading every total aloud. Ask each department to bring a short explanation of its important exceptions. “Four requests need approval by Tuesday” is a more useful opening than a lengthy account of all the requests successfully handled during the week.
Use the same reporting period and definitions
Confirm the period covered by each report and when the information was last updated. A Monday-to-Friday total should not be compared casually with a figure that includes the weekend or only part of Friday. Small differences in timing can create an apparent problem that disappears when the reports describe the same period.
Check what a label actually counts. An incomplete register is different from an absent student, and an unanswered enquiry is different from a request waiting for the family to reply. Write down the definitions used in the review so departments can prepare consistent information and avoid spending the meeting disputing terminology.
Separate a signal from its explanation
A change in a number is a reason to ask a question, not an automatic explanation of what happened. Fewer completed requests may reflect more complex cases, a staff absence or a data-entry delay. Ask the responsible person to describe the underlying work before assigning a solution.
Use a small sample of relevant records when a total is unclear, with access limited to authorised participants. Avoid displaying personal student details simply to make a report feel more concrete. The aim is to understand the process well enough to decide what needs to change, not to expose every case to the whole meeting.
Agree actions that someone can complete
For each decision, name the next action, its owner and a realistic due date. “Improve communication” is too broad to check next week. “Office coordinator to confirm the collection instructions and update the standard reply by Wednesday” describes work that can be completed and reviewed.
Check whether the owner needs an approval, another department’s help or time away from routine duties. A task can remain open because a dependency was never resolved, even when the named person is willing to do it. Record the dependency and who will remove it rather than repeatedly extending the same deadline.
Carry forward exceptions instead of repeating the meeting
At the next review, begin with actions that are overdue, blocked or have produced an unexpected result. Completed routine work can be acknowledged in the record without taking over the discussion. This leaves time for new issues and helps staff see that the meeting is intended to move work forward.
When an action has not helped, reconsider the original explanation. Extra reminders will not solve a confusing form, and another spreadsheet may not fix unclear ownership. Ask what changed after the action and what evidence is still missing. Adjust the approach rather than keeping the same item open with a new date each week.
Keep the review small enough to sustain
Use a consistent short agenda and a simple action record. Invite the people needed for the decisions, and share the relevant outcomes with colleagues who were not present. Avoid turning the review into a general announcement session that requires every department to sit through issues outside its responsibilities.
After several weeks, check whether the process is helping the school close work and spot recurring problems earlier. Remove reports that are never used, refine unclear definitions and keep the actions visible between meetings. The value of a weekly review is the work it enables during the following week, not the thickness of the report pack.
What schools should check
Choose the decisions the meeting should support
Start with the work the principal and coordinators can influence during the coming week.
Use the same reporting period and definitions
Confirm the period covered by each report and when the information was last updated.
Separate a signal from its explanation
A change in a number is a reason to ask a question, not an automatic explanation of what happened.
Agree actions that someone can complete
For each decision, name the next action, its owner and a realistic due date.
Related questions
How many reports should a principal review each week?
Use the smallest set that supports the week’s decisions. The appropriate number depends on the school, but each report should have a clear purpose and a person who can explain its exceptions.
What should the action record contain?
Record the agreed action, owner, due date, relevant dependency and current status. Keep sensitive case details in the authorised source record rather than copying them into general meeting notes.
Explore the school software behind these workflows
Review the product workflow with your school team, then bring your current records and questions to a live demo.
Explore SkoolMatic school workflowsBook a Demo