Report Cards Without Losing the Weekend

Ask a head of year where report card time actually goes and the answer is never "writing the comments." It is chasing four teachers who have not submitted, reconciling a spreadsheet where someone typed a grade into the wrong column, discovering that two teachers used different mark schemes for the same subject, and formatting the whole thing into a document that prints correctly.

The writing — the part that requires professional judgement and is the only part with any value to a parent — is a fraction of the elapsed time.

This matters because most attempts to speed up reporting target the wrong step. Templates and comment banks make the writing faster, and the writing was never the bottleneck. The bottleneck is that the inputs live in fifteen places and have to be assembled by hand before anyone can write anything.

Consider what a single report actually needs. Grades for every subject, from every teacher, on a consistent scale. Attendance for the period, which lives in a different system. Behaviour records, which may live in a third. Effort or attitude ratings, usually collected on a separate form. A subject comment per teacher. A tutor or form comment that summarises across all of it. And a headteacher line on some reports but not others.

In most schools at least four of those are collected separately and merged manually. That merge is where the weekend goes, and it is also where the errors come from — a grade transposed between systems is invisible until a parent queries it.

When grades, attendance and behaviour are already in one system, most of the assembly disappears. The report is a view over data that already exists rather than a document compiled from submissions. The teacher’s job reduces to the part only they can do: the comment.

A few things worth getting right whatever you use. Set the mark schemes centrally rather than per teacher, or you will spend the reconciliation time regardless. Make submission status visible to heads of department in real time, so chasing is targeted rather than a broadcast email to everyone. And generate the parent-facing document from the same data as the internal one — schools that maintain a separate "nice version" for parents eventually publish a version that disagrees with the record.

On AI-drafted comments, which every vendor now offers including us: they are genuinely useful and they are not a substitute for the teacher. A model that can see a student’s grades, attendance and behaviour record can produce a competent first draft in the school’s register and language, and that saves real time on the fortieth report of the evening. What it cannot do is know that a student’s grade dropped because of something happening at home. The right use is a draft a teacher edits, never a comment that ships unread — and any school adopting this should say so explicitly to staff, because the failure mode is a teacher who stops reading.

Multilingual schools have a specific version of this problem. A report that must exist in French and English, or Arabic and English, is usually produced twice and diverges. Generating both from one source, with correct typography and right-to-left layout where needed, removes an entire class of embarrassment.

Skoolia’s gradebook holds grades, attendance and behaviour in one place, so report generation is a view over current data rather than a compilation exercise — with AI-drafted comments a teacher edits, and documents produced in English, French or Arabic from the same source. The comment is still the teacher’s. Everything around it does not need to be.