CHAPTER 3
How to Take the Pain
Out of Report Season.
Report season doesn’t have to mean late nights, copy-paste errors, and frantic email chains. The schools that get it right aren’t working harder, they’ve built a better process. Here’s what that looks like.
Report season is the one time of year when the weaknesses in a school’s administrative infrastructure become impossible to ignore. The grade that has to be manually copied from a spreadsheet into a Word document. The comment that gets written twice because the markbook and the report template don’t talk to each other. The email chain that goes back and forth as someone tries to track down the one teacher who hasn’t submitted their section yet. Every school has a version of this. Most have accepted it as unavoidable. It isn’t.
Why report season is harder than it needs to be
Ask any school administrator what the most stressful period of the academic year is and the answer is almost always the same: the two or three weeks before reports go out. Not because the reports themselves are complicated, most teachers know their students well and can write a coherent comment in ten minutes. The stress comes from everything around the writing: the data that has to be pulled from separate systems, the formatting that breaks when a comment is too long, the version control problem when a report is edited after someone else has already reviewed it, and the distribution process that involves printing, or emailing individually, or both.
This is a systems problem dressed up as a workload problem. The teachers are not the bottleneck… the infrastructure is. When grades live in one tool, comments are written in another, and distribution happens through a third, the report production process requires a human being to act as the connective tissue between them. Every copy-paste is a moment where an error can enter. Every manual step is a moment where the process can stall.
For international schools, the complexity compounds. Reports may need to serve parents who read in different languages. Schools following multiple curricula may need different report formats for different year groups. The expectation of a bilingual or multilingual report becomes an enormous manual effort without one.
“We spent three weeks every term producing reports. Two of those weeks were logistics. Chasing submissions, fixing formatting, merging documents. The actual writing took three days.”
~ Deputy Principal, international secondary school
The irony is that the report itself (the document that matters, the thing parents read and students remember) is the smallest part of the process in most schools. The infrastructure swallows the time that should be spent on substance. Fix the infrastructure and you give that time back.
Â
The four specific places where report season breaks down
Most report season problems fall into four categories. Understanding which ones your school is experiencing is the first step toward fixing the right thing.
Data entry duplication. Grades are entered in the markbook, then manually re-entered into the report template. Every grade is typed twice. Every re-entry is an opportunity for a discrepancy and discrepancies in reports are the kind of errors that parents notice and remember.
Grades entered in the markbook flow directly into the report card template. Teachers see the data already populated when they open a student’s report. They write the comment; the system handles the data. Nothing is typed twice.
Submission tracking is manual. Someone (usually the admin team or a head of year) has to manually track which teachers have submitted their reports and chase the outstanding ones. This typically involves a spreadsheet, a series of reminder emails, and a great deal of time that could be spent on something else.
The system shows a live completion dashboard. Which reports are done, which are in draft, which haven’t been started. Visible to administrators at any time. Reminders can be triggered from the same view. The chase email becomes unnecessary because the information is always current.
Review and approval has no workflow. Once a teacher submits a report, someone needs to review it before it goes to parents. In most schools, this happens via email. The report is attached, commented on, sent back, revised, and sent again. Version control is a permanent problem. Knowing which version is the approved one requires careful attention to email threads that are easy to lose track of.
Reports move through a defined status workflow inside the system: draft → submitted → approved → published. Each status change is logged. Reviewers can annotate directly in the system. There are no email attachments and no version control problem because there is only ever one version.
Distribution is a manual process. Reports are printed, sorted, and sent home in bags. Or exported as individual PDFs and emailed to parents one by one. Or uploaded to a shared drive that parents may or may not know how to access. Each method is slow, unreliable, and leaves the school with no confirmation that the report was actually received.
One action distributes all approved reports to all parents simultaneously via the parent app, with read receipts logged per family. Parents can access the report permanently. Not just for one term, but for as long as their child is enrolled, and beyond. No printing. No email attachments. No shared drive links.
What a well-structured report process actually looks like
The schools that have the smoothest report seasons are not the ones with the most experienced admin teams. They are the ones where the process is built into a system that handles the logistics automatically. Here is what that process looks like, step by step.
1. Template configured once, used every term
What parents actually experience and why it matters for your school
The report card is one of the most significant communications a school sends to a family each term. It is the document that most concisely represents the school’s professional assessment of their child’s progress. The medium through which it arrives sends its own signal about the school’s level of organisation and care.
A report that arrives as a PDF attachment to an email — in a zip file, with a filename like “Report_2024_final_v3_APPROVED.pdf” — is not a professional parent experience. Neither is a report that gets lost in a spam folder, or printed on paper that comes home crumpled at the bottom of a bag, or uploaded to a shared folder that requires a login the parent has forgotten.
Caption: The report card experience in the Schooly Parent App. Clean, permanent, and delivered in the parent’s own language.
When a report is distributed through the parent app, the experience is different in every way that matters to a family. The parent receives a push notification that their child’s report is ready. They open the app, tap on the report, and see a clean, formatted document on their phone readable immediately, without downloading anything or logging into a separate system. The report is stored permanently in the app; they can return to it in six months, or two years after the child has left the school, and find it exactly where they left it.
For international schools, the distribution moment is also a multilingual moment. The notification that the report is ready arrives in the parent’s language. The app interface is in the parent’s language. The report content, written by teachers in the school’s language of instruction is accessible to parents who may need to share it with a family member who will help translate. All of this happens without any additional effort from the school.
The read receipt capability changes something else, too: it gives the school the ability to follow up with families who haven’t opened a report. In a school where reports go out by email or printed letter, there is no way to know whether a parent has seen their child’s report. In a school using Schooly, an administrator can check the distribution view the following morning and see exactly which families are yet to engage and send a follow-up notification with a single click.
How Schooly handles this
Schooly’s Report Cards module is fully integrated with the Assessments & Markbook module. Grades flow automatically into report templates with no manual data entry. Bulk distribution to all parents via the app takes a single action, with read receipts logged per family. Reports are stored permanently in the parent app accessible at any time, from any device.
What report season looks like when the process works
To make this concrete, here is what the report season timeline looks like in a school with a well-structured system in place compared to the manual process most schools currently run.
Six questions to audit your current report process
Work through these before your next reporting cycle. Any “no” is a process gap worth fixing, most of them point to the same root cause.
- Do your teachers type grades into a report template that already exist in your markbook? If so, every grade is being entered twice. The second entry is the one where errors appear and the one that creates discrepancies parents notice.
- Can you see, right now, how many of your teachers have submitted their reports for the current cycle without asking anyone or checking a spreadsheet? If not, your tracking process depends on a human intermediary who has better things to do.
- How does a reviewed report get returned to a teacher for amendment? If the answer involves an email with an attachment, you have a version control problem waiting to happen or one that's already happened and was quietly fixed by someone.
- How do you distribute reports to parents, and how do you know which parents have received and opened them? If the answer is "email" and "we don't," you are distributing into a void. Some of those reports are going unread.
- Can a parent access their child's report from three terms ago without contacting the school? If not, every historical report request is a manual admin task and a signal that your report storage is not working for families.
- How many hours did your admin team spend coordinating the last report cycle, i.e chasing submissions, managing versions, handling distribution? That number is your baseline. A well-structured system should reduce it by more than half.
The bottom line
Report season is one of the most reliable indicators of how well a school’s administrative infrastructure is working. A school where report season runs smoothly… where teachers submit on time because the process is easy, where administrators spend their time reviewing rather than chasing, where parents receive a polished, permanent document on the day reports are released is a school whose systems are working as they should.
A school where report season means late nights for the admin team, frantic emails across the two weeks before the deadline, and a distribution process that leaves nobody sure whether every parent actually received what they were supposed to receive. That school is not short of effort, it is short of infrastructure.
The fix is not a harder-working team. It is a system where grades flow automatically from assessment to report, where completion is tracked without manual effort, where review happens inside a single platform, and where distribution is one action followed by confirmation that every parent has been reached. That system exists. And the term after you switch to it, report season will feel like a different time of year.
CHAPTER 2
The Right Way to Communicate With Parents (Without WhatsApp or Personal Numbers)
Informal channels feel easy until they create a compliance problem, a pastoral incident, or a parent who simply didn’t get the message.
CHAPTER 4
Why Your Markbook Is Slowing Everyone Down And What to Do About It
When grade entry happens in one system and reports live in another, the gap between them costs your staff hours they don’t have.
