October and November Mock Exams: Marking GCSE and A-Level Papers Without Losing Half Term

October and November are when two different mock seasons land on the same department at once. Year 13 sits A-level mocks that feed the predicted grades going out with UCAS applications. Year 11 sits GCSE mocks that are often their first proper exam-conditions paper of the course. Different purposes, different stakes, same six weeks, same marking pile. Treating them as one undifferentiated workload misses what actually matters about each.

Why the A-level mocks carry external weight

A-level mocks in this window are not purely internal. The marks and the teacher's professional judgement from them become the predicted grade that goes on a student's UCAS application, and for courses with earlier deadlines, such as Oxbridge, medicine, dentistry and veterinary science, that application goes in before Christmas. A predicted grade that is a full grade out, in either direction, has consequences a student cannot easily undo once the form is submitted.

That changes what the marking needs to deliver. It is not enough to be fast. The mark has to be defensible, because a department head or a tutor may be asked to justify it, and the student is relying on it to choose which universities to apply to at all.

Why the GCSE mocks are a different problem

Year 11's October or November mock is usually the first time that cohort has sat a full paper under real exam conditions. There is no UCAS form attached to it, and nothing about the mark follows the student beyond the school. What it does do is set the baseline: the target grade conversations with parents, the intervention groups for the spring term, and the student's own sense of where they stand, all start from this result. Get it back to students quickly enough and it changes revision before January. Get it back three weeks later, after half term has absorbed the urgency, and a lot of that value is already gone.

So the two problems are genuinely different: A-level mocks need a defensible mark because of what rides on it externally, GCSE mocks need a fast mark because of what the turnaround time costs internally. Both still need someone to read every paper against the scheme first.

Where GradeDrive fits into an autumn mock set

The workflow does not change for mocks. A department scans the completed scripts into one PDF, uploads it with the mark scheme, and GradeDrive suggests a mark for every question with the matched criterion shown beside it. A teacher reviews every suggestion before it counts, the same review step whether the mark is going on a UCAS predicted grade or a Year 11 tracking sheet.

GradeDrive officially supports Biology, Chemistry, Physics and Maths at both GCSE and A-level, including Combined Science and Further Maths. English is experimental. If your mock set spans a subject outside that scope, the marking stays with the department for that paper. See the full breakdown on AI marking for GCSE and AI marking for A-level, or the department-wide view on exam marking software.

How much to trust it on a mock set you cannot afford to get wrong

This matters more for A-level mocks than for most marking, given what is riding on the mark. Two independent case studies on SSRN compared GradeDrive against official AQA marks, on papers AQA itself picked as hardest to mark consistently: a quadratic-weighted kappa of 0.885 on GCSE Physics, and 0.864 on A-level Maths. Separately, across roughly 216,000 marks and 2,300 submissions last summer, teachers left 99.2% of GradeDrive's suggestions unchanged after reviewing every one, though that figure describes how GradeDrive's own users behaved, not an independent audit. The accuracy page has the full methodology and the limits of both. Review every mark on a predicted-grade mock the same way you would review any other marking: with the student's answer and the scheme in front of you, not just the number.

If this is your first mock season marking

Trainee and early-career teachers often sit their first full mock marking load in this window, frequently with a mentor to check against but without years of mark-scheme pattern-matching behind them yet. The review screen showing which criterion a mark was matched to is useful here for a reason beyond speed: it is a second check on your own reading of the scheme, not just the student's answer, while you are still building that judgement. It does not replace a mentor's feedback on your marking, and it should not be used as if it did.

Common questions

Do GCSE and A-level mocks need to be marked differently? The GradeDrive workflow is the same for both. What differs is how carefully you should review the output: an A-level mock feeding a UCAS predicted grade is worth the extra few minutes per borderline script that a purely internal GCSE tracking mock might not need.

Can it mark a mixed set of subjects in one mock week? Yes, upload each subject's scripts and mark scheme as a separate assessment. GradeDrive officially covers Biology, Chemistry, Physics and Maths at GCSE and A-level; anything outside that scope is marked by the department as usual.

Is this suitable for a PGCE student or ECT marking their first mock set? Yes, in the same way it is for any teacher: it suggests a mark and shows its reasoning, you decide. It is not a substitute for a mentor's guidance on your marking, particularly in your first year.

Will it work with whichever exam board we used for the mock? Yes, GradeDrive marks against whichever mark scheme you upload, so it is not tied to one board.

Related reading

• AI marking for GCSE
• AI marking for A-level
• Exam marking software for UK schools
• Mock Exam Season and the Marking Pile: What UK Secondary Teachers Are Doing Differently
• Is AI Marking Allowed in UK Schools? What the DfE's Guidance Actually Says