All articles
For institutes 10 min read

How to run IELTS mock tests for a whole batch without chaos

Running mock tests for thirty students: timing, exam conditions, marking Writing and Speaking at scale, and turning results into the next week's teaching.

A mock test is the highest-value thing an IELTS institute does and the most commonly botched. Done properly it predicts a band, exposes exactly which skill is holding a student back, and gets a nervous candidate used to the clock. Done as a worksheet handed out in class, it teaches almost nothing.

The difference is entirely in the conditions and the follow-up.

The conditions that actually matter

  • The clock, strictly. IELTS is a time-pressure exam before it is a language exam, and a mock without a hard stop measures the wrong thing.
  • No transfer time in Listening on the computer-delivered test — only two minutes at the end to check. Students trained on the paper version's ten minutes get a shock on test day.
  • Reading straight after Listening with no break, because that is the real thing, and stamina is a skill.
  • Writing with a live word counter, since hand-counting words burns minutes students cannot spare.
  • Speaking recorded, always. A student cannot hear their own hesitation while they are producing it.

How often, and when

A full four-section mock every week is too often — students stop taking them seriously and you generate more marking than you can turn around. Once a fortnight, with sectional practice in between, is the pattern most institutes settle on.

Schedule the first mock in week one, before you have taught anything. It feels counterproductive and it is the most useful test you will run: it gives every student a baseline band, tells you which skill each one needs, and makes your final mock a number they can see themselves having earned.

The marking problem, stated honestly

Listening and Reading mark themselves. Writing and Speaking do not, and that is where a batch of thirty becomes unmanageable.

Thirty students, two Writing tasks each, ten to fifteen minutes per task marked properly against the four criteria, is ten to fifteen hours. Add Speaking and the mock you ran on Saturday is still being marked on Wednesday — by which point the feedback has lost most of its value, because the student has forgotten what they were thinking when they wrote it.

Three ways institutes solve it

  • Cap the batch. Works, limits your revenue, and is the most common unspoken constraint on an institute's growth.
  • Mark a sample. Mark five essays properly, teach the common errors to everyone. Efficient, but the students you did not mark know it.
  • Automate the first pass. Let the platform score every script against the four criteria immediately, then have the trainer review, correct where they disagree, and add the one comment that matters. Every student gets same-day feedback and the trainer's time goes to teaching rather than to counting linking words.

Turning results into next week's lesson

The mock is only half the exercise. Before the next class, sort the batch by which section scored lowest and look for the pattern — if eleven students lost the same marks on True/False/Not Given, that is a lesson, not eleven individual conversations.

Then give each student one instruction, not a report card. "Your Task 2 essays are losing a band on Coherence because you never signpost your second body paragraph" changes behaviour. "You got 6.5, work on writing" does not.

Running mocks on IELTSVega

Full timed mocks across all four sections in both Academic and General Training, delivered in a computer-delivered exam format with the real timing behaviour, a Writing word counter and recorded Speaking. Writing and Speaking come back with instant AI band scores against all four official criteria, so a Saturday mock is marked by Saturday.

From the partner panel you create each student's account yourself, buy their plan on their behalf, and see one roster with every student's attempts, mocks and average band — which is the sorting exercise above, already done.

There is no joining fee and no minimum, so you can run a first batch through it before committing to anything.

Run your classes on IELTSVega.

Wholesale rates, a student roster and instant AI band scores. No joining fee, no minimum.

Become a partner

Frequently asked questions

How often should students take IELTS mock tests?

A full four-section mock every fortnight, with sectional practice in between, is the pattern that works for most institutes. Weekly full mocks generate more marking than an institute can turn around quickly and students stop treating them seriously. Always run one in the first week, before teaching anything, to establish a baseline band for every student.

How do I mark thirty students' IELTS Writing every week?

Realistically, you do not do it by hand. Ten to fifteen minutes per essay marked properly against the four criteria means thirty students produce ten to fifteen hours of marking a week. Institutes either cap batch sizes, mark a representative sample and teach the common errors, or have a platform score every script immediately and use trainer time to review and correct rather than to mark from scratch.

Should mock tests be on computer or paper?

On computer, unless you know your students are sitting the paper-based test. The computer-delivered format is now the majority and it behaves differently in ways that cost marks: there is no ten-minute Listening transfer time, only two minutes to check, and Writing is typed with a word counter. Practising on paper for a computer test trains the wrong habits.

What should I do with mock test results?

Sort the batch by weakest section and look for shared errors — if a third of the class lost the same marks on True/False/Not Given, that is next week's lesson rather than eleven separate conversations. Then give each student one specific instruction tied to a criterion, not a band number. A score tells a student where they are; only a named error tells them what to change.

Related articles