Why a well-organised question bank saves more time than any other exam feature
A question bank is a central store of questions, each labelled with its subject, topic, difficulty and type, so that tests can be assembled from it instead of being typed fresh every time. Built carefully, it lets a teacher put together a balanced paper quickly, create different sets for different batches, and see which questions need fixing. Built carelessly, it becomes a long list that nobody can search.
This guide is for academic coordinators, heads of department and coaching faculty who are moving question papers from Word files and registers into an online exam system. You will learn how to design tags, pick question types, set up a review process, use randomisation, and keep the bank secure and current.
Design the tagging scheme before anyone types a question
Tags are what make a bank searchable. If ten teachers add questions without agreed tags, you end up with "Trigonometry", "Trig" and "Trignometry" as three different topics, and random paper generation quietly breaks. Agree the list first, keep it in a shared sheet, and let only the coordinator add new values.
| Tag | Example | Why it matters |
|---|---|---|
| Subject | Physics | The basic filter for teachers and for section-wise papers. |
| Chapter and topic | Current Electricity > Ohm's law | Needed for topic-wise result analysis and for balanced papers. |
| Class, course or batch | Class 10, NEET foundation, DCA | Stops a Class 8 question from appearing in a Class 12 test. |
| Difficulty | Easy / Medium / Hard | Lets you control the mix in each paper. |
| Question type | MCQ, numeric, subjective | Affects marking rules and the time each question needs. |
| Marks and negative marks | 4 / -1 | Keeps scoring consistent wherever the question is reused. |
| Source and author | Own question, previous test, reference book; teacher's name | Helps with review, copyright care and accountability. |
Keep difficulty to three levels at the start. Teachers' first estimates of difficulty are often off, and you will correct them later using real results. Fewer levels make that correction easier.
Choosing question types for what you want to measure
Online exam systems usually support several question types. Each one measures something slightly different, and each has its own marking traps that are better settled before the first test than argued over after it.
| Type | Good for | Watch out for |
|---|---|---|
| MCQ (one correct option) | Quick checks of concepts and facts across a wide syllabus. | Weak wrong options that nobody would pick, which make the question easier than it looks. |
| MSQ (more than one correct option) | Testing whether a student knows all the conditions, not just one. | Decide and announce how partly correct answers are marked. |
| True/False | Quick revision quizzes. | A blind guess is right half the time, so use it sparingly in graded tests. |
| Numeric answer | Calculations in maths, physics and accounts. | Define acceptable rounding and units, or correct answers will be marked wrong. |
| Match the following | Pairs such as terms and definitions. | One wrong pair can disturb the rest; decide whether each pair earns marks separately. |
| Fill in the blanks | Key terms and formulas. | Spelling and spacing variants; list every acceptable answer. |
| Subjective / descriptive | Explanation, reasoning and writing. | Needs a teacher to evaluate and a marking scheme so different evaluators agree. |
Writing questions that read well on a screen
A question that works on paper can fail on a phone screen. Long passages need scrolling, small diagrams become unreadable and wide tables break. When writing new questions or converting old ones, keep these points in mind:
- Test one idea per question. If a question checks two things, a wrong answer does not tell you which one the student missed.
- Make every wrong option believable. The best wrong options come from mistakes students actually make in class.
- Keep options similar in length and style. The longest, most detailed option is often guessed as correct.
- Avoid "all of the above" and "both A and B" if options will be shuffled, because the letters will no longer match.
- Use images only when needed, and check them at phone size. Crop diagrams tightly and make sure labels can be read.
- Avoid double negatives such as "Which of these is not incorrect?"
- If you set papers in Hindi and English, keep both versions of a question together and review them side by side so the meaning does not drift.
A review workflow so errors are caught before students see them
Every question should be checked by someone other than its author before it is used in a graded test. A simple status flow is enough:
- Draft: the author adds the question with all its tags and the answer key.
- Reviewed: a second teacher checks the answer, wording, tags and difficulty, then approves it or sends it back with a comment.
- Approved: the question becomes available for test papers.
- Retired: the question is kept for records but no longer drawn into new papers.
If your system does not track these statuses directly, a tag or a separate category for each stage does the same job. What matters is that unreviewed questions cannot slip into a final exam.
Importing existing questions from Excel
Most institutes already have hundreds of questions in Word files and old papers. Moving them through an Excel import template is faster than typing each one into the system. Fill one row per question with columns for the question text, options, correct answer, tags and marks. Import a small batch first, preview it as a student would see it, and only then import the rest. Check maths symbols and images carefully, because they are the most likely to break during import.
Using randomisation to build many papers from one bank
Randomisation lets the system pick questions for each paper according to rules, instead of a teacher choosing every question by hand. A typical rule reads: from Chapter 4, draw five easy, eight medium and two hard MCQs. Each candidate or batch then gets a different set that still follows the same blueprint.
Random papers are only fair if the pools are deep enough and the difficulty tags are honest. If you draw two hard questions from a pool of three, almost every candidate sees the same questions. If some "medium" questions are really hard, one candidate's paper ends up tougher than another's. As a working habit, keep each pool several times larger than the number you draw from it, and use a blueprint so every paper covers the syllabus in the same proportion.
| Chapter | Easy | Medium | Hard |
|---|---|---|---|
| Chapter 1: Number systems | 3 | 4 | 1 |
| Chapter 2: Polynomials | 2 | 4 | 2 |
| Chapter 3: Linear equations | 3 | 5 | 2 |
| Total: 26 questions | 8 | 13 | 5 |
Shuffling the order of questions and options within a paper is a related setting, but it is mainly an integrity control. It is covered in our article on reducing cheating in online tests.
Reuse, revision and retirement
A bank only stays useful if someone maintains it. Questions get exposed when students talk about a test afterwards, syllabi change, and some questions turn out to be confusing once real students answer them.
- Track use: note when and in which tests each question appeared, so the same question does not come up in back-to-back tests for the same batch.
- Revise using results: after each test, look at questions that almost everyone got wrong, or that strong students got wrong more often than weak ones. These usually have unclear wording or a wrong key. Our guide to reading online exam results explains how to spot them.
- Correct difficulty tags: change the tag to match how students actually performed, not how hard the author expected the question to be.
- Retire exposed questions: once a question from a high-stakes paper is likely to be circulating, move it to the practice pool or retire it.
- Check against the syllabus every year: when the board or course syllabus changes, filter by chapter and retire or re-tag questions that no longer apply.
Protecting the bank from leaks
A question bank is valuable precisely because its questions are unseen. Leaks usually come from inside: a shared staff login, a paper downloaded to a personal laptop, or a final test assembled days early and visible to too many people.
- Give each teacher their own login and limit them to their own subjects through role permissions.
- Restrict bulk export and printing of questions to the coordinator.
- Keep separate pools for practice tests and graded exams.
- Assemble high-stakes papers close to the exam date and schedule them so they open only at the start time.
- Remove access promptly when a teacher leaves the institute.
For a broader buyer's view of access control, audit logs and backups, see our software security checklist.
How MATROP's question bank works, and when a spreadsheet is enough
In MATROP's online exam software, the question bank is a central store organised by categories, topics, difficulty levels and tags. It supports MCQ, MSQ, true/false, numeric, match the following, fill in the blanks and subjective questions. Teachers can import questions from Excel, and support for images and mathematical notation is available as an option. Admin, teacher and student logins carry separate permissions, and the topic tags feed the topic-wise performance figures in results.
If you set only a few tests a year for one class, a well-organised spreadsheet or folder using the same tags may be enough for now. A dedicated bank becomes worthwhile when several teachers contribute questions, when you run frequent tests or a mock series, or when different batches need different sets. Coaching institutes looking at exams as part of a wider system may find our coaching institute ERP guide useful.
Questions people ask
How many questions should a topic have before we use random selection?
There is no fixed number, but each pool should be clearly larger than the number of questions you draw from it. If the pool is barely bigger than the draw, most candidates get nearly identical papers and randomisation adds little.
Can we bring our old questions from Word files into the bank?
Yes, usually by first copying them into an Excel import template with one row per question and columns for options, answer and tags. MATROP's software supports Excel import; import a small batch, preview it, then do the rest.
Who should approve questions before they appear in graded tests?
A teacher other than the author, ideally the subject head or a senior colleague. The reviewer checks the answer key, the wording, the tags and the difficulty level.
Should practice tests and final exams draw from the same questions?
Keep them in separate pools. Questions used in practice are effectively public once students have seen them, so they should not decide a final grade.
