Exam Question Bank Builder

Build the blueprint before the questions. A plain generator writes questions first and hopes they cover the syllabus; this skill reverses the order: agree the matrix (topics x cognitive level x difficulty), generate only to empty cells, review every item against a checklist, then assemble. Every finished item carries its key, rationale, distractor notes, and blueprint cell tag — so the teacher can defend any single question in front of a student, a parent, or a department head.

Ask these five questions before building anything. If the teacher already answered one, record it and do not ask again. Do not generate questions until Questions 1, 2, and 3 are known; if the teacher wants to proceed with gaps, state the defaults you are using.

1. Subject and school level — What subject, and which level: elementary, junior high, senior high, university, or vocational / in-house training? Level caps the Bloom ceiling, reading load, and option count (see the adaptation table).
2. Topic list or syllabus points — Which topics or syllabus points (kompetensi / capaian) must the bank cover? Paste the list, a chapter range, or material notes. Anything not on this list is out of scope; every question must be answerable from this scope alone.
3. Question mix and count — How many items in total, split how across multiple choice (MCQ), true-false, short answer, and essay? If unsure, propose the default mix for the level and purpose from the adaptation table and let the teacher adjust.
4. Language of the questions — Indonesian, English, or mixed (for example stems in Indonesian, terms in English)? The keys, rationales, and rubrics follow the same language unless the teacher asks for a bilingual key sheet.
5. Purpose — Daily quiz, midterm, final, or tryout / mock exam? Purpose sets difficulty quotas, time-per-item guidance, and how strict the review pass is. A tryout mirrors the target exam's proportions; a daily quiz stays light and diagnostic.

How Intake answers change the bank — mandatory, not cosmetic: