Question bank software that lasts: tag questions, retire stale ones and reuse them across assessments. A practical system that keeps your bank organised.
A question bank is a set of questions you reuse across quizzes and exams. Each question is tagged by topic, difficulty and learning outcome. The value comes from the tags and the retirement rules rather than from the raw count. This guide explains how to build one that stays useful for years.
To support that work, Quest, Lectimax's question bank module, holds every question with its tags and lets you pull a balanced set for any assessment. The library stays in order, and the questions are yours to write and approve.
What tag scheme do you set before adding questions?
Decide the tags a marker needs before the first question lands. Use topic, learning outcome, difficulty and type. Add a fifth tag for item analysis once you have taught the term, so you can tell which questions worked. A question with no tags is a single use item and not part of a bank.
The scheme uses four tags with a defined vocabulary instead of a free text field. Topic pulls from the module outline, so "probability" and "probability distributions" stay separate because the syllabus treats them separately. Outcome comes from the numbered learning outcome the question tests. Difficulty is coarse, with three levels: recall, apply or evaluate. That is enough to build a fair quiz and fine enough to balance an exam. Type is MCQ, short answer or essay. It decides how the question scores and how long it takes a student. When every question carries these four, a query like "topic probability AND difficulty apply AND outcome 2" returns a usable set in seconds. Without the scheme, you search by the vague memory of what you wrote and get back whatever the string match finds.
Once the scheme exists, it only works if every question receives its tags at the moment you write it. Every time you write a question, add its tags and a correct answer note at the same sitting. Metadata added later is metadata that never gets added. Write the stem, the distractors, the correct answer and the tag line in one pass.
A question written on Tuesday and tagged on Friday is only two days from being a question never tagged. The Friday pass always gets dropped when marking and emails pile up. So treat the tag line as part of the question. For a multiple choice item, that means the correct option and a one sentence note on why it is correct. That note is what lets you reuse the item in a revision quiz without deriving the reasoning again. A bank where the answers carry a reason is a bank a colleague can use, while a bank of naked options is one that only the original author trusts.
Retire stale and ambiguous questions
Complete tags also make the next job possible, which is pruning. A bank stays useful when you prune it. After each assessment, mark questions students misread or that two markers read differently. Keep the ones that discriminated well and retire the rest. A live bank is smaller than a dead one, and easier to trust.
The retirement test rests on how students behaved, and your fondness for a question does not count. A question where the top of the class split evenly on the wrong option is ambiguous. A question that a whole weaker cohort got right but the strong cohort got wrong is miskeyed or testing the wrong thing. Both mean retire or rewrite it. Keep the questions where students who knew the material answered correctly and students who did not answered wrongly. That is the whole job of the discrimination tag from the first step, and it is why you record it at term end rather than guessing.
Pull a balanced set for an assessment
With a pruned and fully tagged bank, you can build assessments from it directly. For a quiz, draw questions by topic and difficulty so the set matches the syllabus coverage. For an exam, add the learning outcome and item tags so the paper tests the outcomes you promised. Pulling a balanced set by tag is where a bank pays for itself, because you assemble a defensible paper in minutes.
The balance rule is coverage first. Make the question mix mirror the syllabus weight. If the module spends a third of its time on statistics, a third of the exam should test statistics. The tags let you verify that in one view instead of reading every question again. Then check difficulty spread so the paper has some recall items early to settle students and the harder apply and evaluate items later. It also helps in moderation, since you can show the moderator the coverage by topic and outcome instead of asking them to trust your memory of half a term.
Let the bank grow by design
Moderation and pruning both depend on the bank being maintained steadily, so set a rhythm. Add a fixed number of questions after each tutorial and each assessment, and retire at least as many stale ones. The bank then grows a little every week instead of in a panic before the exam. Lectimax keeps the tags and the retirement notes together, so the bank stays organised across terms. See the full Lectimax feature set.
FAQ
How many questions make a useful bank? Enough that every topic has items at two or three difficulty levels. Cover each topic and outcome rather than chasing a target count.
Should every question be tagged by difficulty? Yes, because difficulty is the tag you use to build a fair quiz midway through the term. Add it when you add the question.
Can a department share a question bank? The same bank can be reused by a whole department when the tags and standards are agreed up front. Tagging discipline matters from the first term.
What happens to a question that fails item analysis? Retire it or rewrite it. The discrimination tag exists exactly so you catch the item that confused the strong students before it appears in another exam.
Where to go next
Since a bank is only as good as its link to your assessments, keep it tied to how you assess, and set the assessments from the same learning outcomes. See what AI grading in higher education really is, or review Lectimax pricing and the full feature set.