Question Bank Overview

A high-level introduction to the Question Bank — what it is, why it matters, and what you can do with it.

Updated 2026/08/04

The Question Bank is your organization's central library of reusable questions. Instead of recreating questions every time you build a test, you write them once, store them here, and pull them into as many tests as you need. Every question you create — whether directly in the bank or while editing a test — lives here and can be reused, updated, and organized over time.

Why Use a Question Bank?

The bank is not just storage. It is the foundation of a scalable assessment program:

Reuse across tests — the same question can appear in multiple tests without duplication. Update it once and all tests that reference it reflect the change.

Organize at scale — folders, sub-folders, tags, labels, language, and status keep your library structured and filterable even when it contains thousands of questions.

Measure competencies — assign scoring dimensions to questions so test results show not just a total score but a breakdown by skill or competency area.

Collaborate safely — the Question Author role lets external contributors propose questions through a dedicated submission interface, while Question Bank Supervisors review, approve, revise, or reject them before any question enters the live bank. See Roles & Access and Question Submissions.

Analyze quality — question-level analytics (difficulty index, discrimination index) help you identify which questions are working well and which need revision.

What's Inside the Question Bank

The Question Bank is organized into four tabs:

Questions

The main library. All questions your organization has created live here. The Question Bank Navigator at the top of the tab lets you scope the view by folder, and filter by question type, status, language, tags, labels, and scoring dimensions. You can create, edit, copy, bulk-update, import, and export questions from this tab.

Content Blocks

Reusable bundles that group questions together with supporting content — for example, a reading passage followed by five comprehension questions. Content Blocks let you assemble test pages from pre-built units rather than individual questions.

Question Submissions

A moderated inbox for questions proposed by external contributors (Question Authors). Supervisors review each submission here and can approve, revise, or reject it before it enters the live bank. See the Question Submissions page for the full workflow.

Media Library

A centralized store for images, audio files, video files, and documents that you embed in questions. Uploading media to the library first makes it easy to reuse the same asset across multiple questions without re-uploading.

Every question created inside a test is automatically saved to the Question Bank.

Good to know

Every question carries a set of organizational properties, set when you save it and used by the Question Bank Navigator to filter, sort, and browse your library:

Folder — the question's single, structural home. Every question belongs to exactly one folder, and folders nest into sub-folders to any depth.
Tags — key-value metadata like difficulty: hard or topic: algebra. A question can carry several tags, enabling precise multi-condition filtering.
Labels — free-form strings with no key, such as needs review or exam-ready, for lightweight ad-hoc classification.
Language — an ISO 639-1 code (e.g. en, tr, de) marking what language the question is written in.
Status — a question's readiness: Draft, Review, or Ready for use in tests.

See Question Metadata for when to use each one and how they differ.

TestInvite supports a wide range of question types to suit different assessment needs:

Multiple Choice — one or more correct answers from a list of choices
Short Answer — single-line text input with optional validation rules
Long Answer — multi-line or rich text response, manually graded or rubric-scored
Numeric — number entry with format control and validation
Code — code editor supporting 17+ programming languages with AI evaluation
Audio — voice recording or audio file upload with AI evaluation
Video — video recording or upload with AI evaluation
File Upload — any file type submission
Photo — photo capture or image upload
Tabular — spreadsheet-style table input
Match — pair items from two columns with four layout options

Each question type is covered in detail in its own page under Question Types.

A Scoring Framework is your organization's shared list of competency dimensions and sub-dimensions — things like Communication, Problem Solving, or Technical Skills — that questions can be scored against. Defining them once, centrally, means every question author draws from the same vocabulary instead of inventing their own labels for the same competency.

It's most useful once a single overall score isn't enough — once you want test results to show a per-competency breakdown, so a candidate who looks average overall might turn out to be strong technically but weak on communication. That breakdown is also what powers dimension-based filtering in the Question Bank, analytics comparisons, and step prerequisites gated on a dimension score.

See Scoring Framework for how dimensions get assigned to questions and the difference between associated and scored dimensions.

By default, question authors can save a question to any folder and attach any tag with any value — there's no restriction. A Schema is for organizations that need more control: it lets you define exactly which folders exist, which tags are required, and which values are allowed, then enforces those rules at save time.

Strict folders — only folders defined in the schema are allowed
Required tags — certain tags must be present before the question can be saved
Strict tag values — tag values must match a predefined list

See Metadata Rules & Schema for when it's worth setting up, how to enable it, and how each rule works.