Click to upload or drag and drop
PDF, DOCX, PPTX, TXT, JPG, JPEG, PNG, HEIC, ODP, ODT, BMP, or TIFF
up to 20MB
Uploading...
A test bank should hold roughly three to five times the number of questions that appear on a single exam, per topic you assess. If a midterm has 50 questions drawn evenly from five units, you want about 30 to 50 questions per unit, so 150 to 250 in the bank. That ratio lets you generate several unique exam versions, support retakes, and rotate items across terms without repeating the same test. Smaller banks work for low-stakes quizzes; high-stakes or heavily proctored courses need the larger end.
The right size depends on what the bank is for. A bank exists to give you more questions than any one exam needs, so you can pull a fresh, balanced test every time instead of reusing the same 50 items until they leak. Too small and every version looks alike; too large and you spend effort writing questions you never use. The three-to-five-times rule is the practical middle.
People fixate on a round number, like a thousand questions. The number that actually governs test security and variety is the ratio of bank size to exam size, per topic. If each exam pulls 10 questions from a unit and the bank has 40 for that unit, any two students share few items and you can run four distinct versions before repeating. Push the bank to 50 per unit and you can also retire weak questions after item analysis without dropping below coverage.
Coverage is the constraint, not raw volume. A bank of 2,000 questions that all test one chapter is worse than 200 spread evenly across the ten chapters an exam covers. Size each topic to the exam, then add the topics up.
| Assessment type | Questions per exam | Suggested bank size | Why |
|---|---|---|---|
| Weekly low-stakes quiz | 10 | 20 to 30 | Two to three versions is plenty; stakes are low |
| Unit test | 25 | 75 to 125 | Enough for retakes and two exam forms |
| Midterm or final | 50 | 150 to 250 | Multiple versions plus room to retire weak items |
| Large intro course (100+ students) | 50 | 250 to 400 | Reduces overlap across many simultaneous test-takers |
| Certification or licensing practice | 75 | 400 to 750 | Broad blueprint coverage and heavy reuse over time |
These are starting points, not laws. Adjust up if the exam is proctored remotely, retaken often, or worth a large share of the grade, because those raise the incentive to share answers. Adjust down for formative quizzes where a leaked question costs nothing.
A good bank is balanced three ways. First by topic, matching the weight each unit carries on the exam. Second by difficulty, with a mix of recall, application, and analysis questions so every generated version has a comparable spread. Third by format, if your exams use more than multiple choice. Tag each question by topic, difficulty, and type as you build, so pulling a balanced 50-item version is a filter, not a manual hunt.
Writing 250 calibrated questions by hand is why most instructors never build a real bank. The faster path is to generate the pool from source material and then curate it. Upload your textbook chapters, lecture notes, or course packet to a question bank generator, which reads the material and drafts questions across formats and cognitive levels. You get to the target volume in minutes, then spend your time on the high-value work: checking answer keys, strengthening distractors, and tagging by topic and difficulty. Generation gives you quantity; your review gives it quality.
Corporate and training teams size banks the same way, sometimes larger, because compliance modules get taken by the whole company and reuse constantly. Many run the pool inside a platform that delivers and tracks training across a whole workforce, pulling a randomized set for each employee so no two people see an identical check.
Aim for three to five times the number of questions on a single exam, counted per topic. For a 50-question exam drawn from five units, that means roughly 30 to 50 questions per unit, or 150 to 250 total. The multiple matters more than a round number because it determines how many unique versions you can build and how much room you have to retire weak items. Raise it for high-stakes or heavily reused exams.
No. Coverage and balance matter more than raw size. A large bank concentrated on a few topics gives worse exams than a smaller one spread evenly across everything the exam tests. Beyond a point, extra questions you never use just add maintenance. Size each topic to match its weight on the exam, keep a mix of difficulty levels, and stop once you can generate the versions you need without repetition.
Roughly the bank-to-exam ratio per topic. If each exam pulls 10 questions from a unit that has 40 in the bank, you can build about four versions with little overlap before items start repeating. Randomizing question and answer order stretches that further. If you need many simultaneous versions, such as a large lecture course, size the bank toward the higher end of the three-to-five-times range.
Generate the questions from your source material, then curate them. Upload textbook chapters, lecture notes, or a course packet to a question bank generator, which drafts questions across formats and difficulty levels in minutes. That gets you to the target volume fast, so your effort goes into reviewing answer keys, improving distractors, and tagging by topic and difficulty rather than writing every item from scratch.
Yes. Tag each question by topic, difficulty, and format as you add it. Tags are what let you pull a balanced exam version with a filter instead of hand-picking items, and they make it easy to retire or replace weak questions after item analysis. Without tags, a large bank becomes hard to use, and you lose the main advantage of having one in the first place.
Ready to build one? Upload your course material to the question bank generator and reach a properly sized, balanced pool in minutes instead of a weekend.
From the same family of tools