Five Things That Slow Down Result Turnaround, and How We Removed Them

When we started tracking turnaround time by stage rather than end to end, five specific bottlenecks accounted for almost all of the delay between a student submitting a test and a university receiving a result.

The first was scheduling written and spoken grading in the same queue as objective marking, even though objective sections are scored instantly by the server. Separating the two meant a student's reading and listening scores were never held up waiting for an examiner to be free.

The second was single-examiner review with no defined escalation path for borderline scores, which meant close calls sat unresolved until someone happened to notice them. We fixed this with an explicit rule: any result within three points of the pass threshold is automatically routed to a second examiner, rather than waiting for a manual flag.

The third was report formatting done by hand per partner, which introduced both delay and inconsistency. A standard report layout, generated the same way for every partner and then adapted only in delivery format, removed a full day from the average case.

The fourth was unclear ownership when a partner's requirements changed mid-cycle — a rubric update or a pass mark change with no single person responsible for propagating it. Assigning one named account contact per partner closed that gap.

The fifth, and the hardest to fix, was treating every attempt as first-time-right rather than building in a scheduled second check before release. Counter-intuitively, adding a mandatory second review step reduced total turnaround, because it caught errors before they became a delay caused by a partner sending a result back.