On one bank
Every branch running the weekly mock from the shared bank by the end of the second batch cycle, including eleven franchise branches.
An institute that stopped setting forty separate mocks a week and started setting one — then found out which branches were actually teaching.
40 branches · four states · weekly mocks. Measured across two batch cycles, against the institute’s own prior year.
Every branch wrote its own weekly mock. Comparing branches meant comparing papers of different difficulty, which meant not comparing them at all.
One mock, generated from the shared bank, sat on the same evening in four states — and the first honest branch conversation they had ever had.
“Forty branch heads each thought their mock was the hard one. They were all right, which is the same as all being wrong.”
Director of academics
Not a plan — what they did, including the parts that were not the plan. Pick a moment.
Eight years of questions across four states, in nine formats, most of them in Word documents on individual faculty laptops. Near-duplicates were flagged rather than merged, because two similar questions are often deliberately different.
The first shared mock ran at two branches on the same evening. The gap between them was nine marks, which nobody had expected and nobody could explain by the paper.
Twelve branches on the shared bank. The weekly cycle held — generating a mock took minutes rather than an evening per branch, which is what made forty feasible at all.
The eleven franchise branches were given the bank without export, and their own results scoped to themselves. Head office sees all forty. This took one conversation and no custom work.
Every branch on one bank, one mock a week, and a branch comparison that is finally about teaching rather than about who set the easier paper.
Measured across two batch cycles, against the institute’s own prior year. A figure without a method is a figure you cannot check, so each one says what it counted and what it did not.
Every branch running the weekly mock from the shared bank by the end of the second batch cycle, including eleven franchise branches.
Faculty time across the institute, per weekly cycle: setting forty papers against generating one. Measured by the institute from their own timesheets, not estimated by us.
How many times the average approved question appears in a paper across a year, without repeating on any batch that has already seen it. Before the shared bank it was under 1.2.
Across two cycles of weekly mocks at forty branches. Answers save on the device, so a dropped line costs the seconds it lasted.
Every rollout has one, and a case study without it is marketing. These are theirs, in their own account.
Two branches, same paper, same evening, nine marks apart. Before the shared bank that gap was invisible, and every branch head could reasonably believe their own mock was the demanding one. Making it visible was the point of the project and it was still an unpleasant fortnight.
The institute’s own view afterwards was that the number was always true and they had simply been unable to see it. That is the right reading, but it is worth knowing it lands that way before you start.
Tagging eight years of questions by chapter and difficulty is not a weekend. It took a working month with two faculty members on it part-time, and roughly one question in nine turned out to be a near-duplicate that somebody had to decide about. We flag them; we do not merge them, because that decision is not ours to make.
Two branches with long-tenured faculty preferred their own mocks and sat the term out. They joined in the second cycle after seeing the branch comparison — not because they were told to, which the director considered the only sustainable way it could have gone.
If any of that would be a problem where you are, it is worth raising on the first call rather than in the second term.
All six are measured the same way. See all six
The ones that come up almost every time.
It means every branch can. The bank is shared; whether a branch draws from it or sets its own is a branch decision. The nine-mark gap only became visible because they chose to run one common mock.
Six weeks, and most of that was not technical. Agreeing a common blueprint across forty academic heads was the work; importing batches from their existing spreadsheets took an afternoon.
It was not closed and nobody was sacked, which was the fear. The gap turned out to be two chapters taught in a different order, and it closed over the following term once that was visible.
Book a free 30-minute demo. We’ll build the same breakdown from a paper you already ran, so the first number you see is your own.