How we build mock exams

People often ask why our mock exams feel harder than many other practice sets. The reason is simple: an easy mock can make you feel ready and then leave you unprepared on exam day. We prefer practice that feels close to the real exam, even if the score is lower at first.

Writing new question stems is only one part of the work. Most of the time goes into checking topics, making sure false statements are clearly false for a good reason, matching True/False keys to the solutions, and writing explanations that are still readable under time pressure. If we skip those steps, the mock becomes confusing instead of useful.

Below are the main checks we use before a task goes live. Any one of them can stop a draft from being published.

We also do not keep every draft. A larger task bank is not always a better one. In the last economics rewrite we drafted about forty task clusters, kept about eighteen in a form close to the first version, reworked eleven, and removed more than twenty that only looked difficult because the wording was unclear.

We add a statement when it reflects a real decision students face in the exam. In economics, that may be a definition next to a market-logic claim. In mathematics, it may be domains or discarded roots. In English, it may be vocabulary and grammar that still matter when you are tired. We leave things out when we already have several tasks teaching the same mistake.

After a hard practice exam, we look less at the total score and more at where points were lost for avoidable reasons. Mathematics usually shows the largest share. Economics often loses points through over-marking. English losses are usually smaller but still important. If a task only creates frustration without a clear lesson, we rewrite it.