Guide
A mock test series is a schedule, not a pile of papers. Most of the work is decided before the first sitting: what each paper measures, when it opens, and what a student is told afterwards.
A blueprint is the distribution each paper must hit: how many questions per topic, at what difficulty, worth what marks. Write it before authoring, because assembling questions and deciding coverage at the same time reliably produces a paper that over-tests whatever the author finds interesting.
It also makes the series comparable. If paper three has the same shape as paper one, a student’s improvement means something. If it does not, you have measured two different things and called it progress.
Do not release scores until the whole batch has sat the paper. Once a score is out, discussion of the paper follows it, and the last students to sit are taking a different exam from the first.
A useful pattern: every student gets a copy of their own answers on submission, with no correctness or scoring — enough to review what they did while it is fresh. The scored breakdown goes out to everyone at once, after the window closes.
Papers that get harder because the author is getting more ambitious, not because the syllabus says so. Reusing a question a batch has already seen and reading the improvement as learning. Publishing a series without a decided answer-key challenge process, then improvising one under pressure.
Fewer than you are tempted to schedule. Each paper needs review time to be worth sitting; a fortnightly paper that is fully discussed beats a weekly one that is not.
Usually not, if the batch sits the paper across a window. Give them a copy of their own answers on submission and release scores together once the window closes, so the last students are not sitting a discussed paper.
More answers on the full FAQ.