Cutting your term reporting cycle from three weeks to one day

Ask a head of school how long reporting takes and you will get an answer in weeks. Ask what actually happens in those weeks and almost none of it is reporting. It is chasing marks, retyping them, recalculating totals somebody has already calculated, and correcting the errors that all of that introduced.

The reporting itself — the professional judgement, the comment that tells a parent something useful, the decision about whether a set of results is fit to publish — is perhaps a day of work. Everything else is logistics. This guide is about removing the logistics.

Where the three weeks actually go

Time a conventional reporting cycle and it divides fairly consistently into four activities:

• Collection. Marks exist, but on paper, in personal spreadsheets, and in the heads of teachers who are also teaching. Someone has to gather them.
• Transcription. Collected marks are typed into a second place — a master sheet, a template, a report card. Each retyping is an opportunity for error.
• Calculation. Weightings, totals, averages, grades and positions are worked out, often more than once, sometimes differently by different people.
• Correction. The errors introduced during transcription and calculation are found — usually by a parent, sometimes after publication.

Only the first is unavoidable, and even it is only unavoidable at the end of term because it was avoidable all term.

Fix the calendar before you fix the software

The single biggest lever is not a system feature. It is deciding that marks are entered when the work is marked, not when the deadline arrives.

A teacher who records a test the week it is sat spends a few minutes. The same teacher recording a term of tests in the last week spends an evening, under pressure, from notes — which is precisely the condition under which mistakes are made. Moving mark entry to the point of marking does not add work; it redistributes work that was always going to happen, out of the fortnight that cannot absorb it.

End-of-term crunch is not a reporting problem. It is a collection problem that has been deferred for eleven weeks.

This is a management decision, not a technical one. It needs the head of department to say that continuous entry is expected, and it needs mark entry to be quick enough on the day that the expectation is reasonable — including on a phone, in a classroom, without a reliable connection.

Compute what can be computed

Weightings, grade boundaries, subject averages and class positions are arithmetic. They are also where most published errors originate, because arithmetic done by hand across hundreds of learners will produce mistakes no matter how careful the person is.

Configure the rules once — per subject, per stage — and let them run. The rules are the part that deserves scrutiny at the start of the year; the arithmetic afterwards does not need reviewing, only the inputs do. A school that reviews its grade boundaries carefully in January and never recalculates a total by hand is in a better position than one that checks every total in November.

Keep the sign-off, drop the transcription

Automating the arithmetic sometimes raises a fear that professional judgement is being automated too. It is not, and it should not be. Two things must stay human:

• The comment. A generated remark that says nothing is worse than no remark. The value of a report card to a parent lives almost entirely in the sentence a form tutor writes.
• The release. Results should be held until a named person has looked at them and signed them off. A system that publishes automatically will eventually publish something that should have been questioned.

What disappears is the retyping between the mark book and the report card — the step that produced errors without adding judgement.

Print in your own format, in one batch

Schools are rightly attached to their report card format. It carries the crest, the house system, the subject ordering and the language the community recognises. A reporting cycle that requires abandoning it is trading one problem for another.

The format should be configured once and then generated for the whole cohort in a single run. If producing report cards involves opening a document per learner, the cycle cannot compress below a week regardless of what else is fixed.

What a one-day cycle looks like

When collection has happened continuously and calculation is automatic, the end of term looks like this: marks are already in; the head of department reviews subject results and queries anything anomalous; form tutors write comments; the head of school reviews and signs off; the batch is generated and released.

That is a day of concentrated, senior work — which is what reporting was supposed to be. The three weeks were never the reporting. They were the cost of not collecting as you went.

What to do this term

You do not need a new system to start. Pick one department and require entry within a week of marking. Write down your grade boundaries and weightings and check they are what you actually use. Count how many times a mark is typed between the script and the report card, and remove one of those steps. Then measure the next cycle against this one.