A topic in the Open Knowledge Graph — a free, open map of 15,290 topics and the order to learn them in.
Test specifications define the domain, item types, cognitive levels (Bloom's taxonomy), and desired difficulty distribution. Specification tables align test content with domain and specify items per content area and level. Rigorous specifications ensure content validity, guide item writing, and enable parallel forms. Essential for defensible, aligned assessments.
From your study of content validity, you know that a test is valid to the extent that its items representatively sample the domain the test claims to measure. But "representatively sample" is doing a lot of work in that sentence — how do you decide what counts as the domain, and in what proportions? Test specifications (also called a test blueprint) are the answer: a formal document that operationalizes the domain before a single item is written. The blueprint is the architect's plan; the items are the building materials. Without a plan, builders make locally sensible decisions that produce a structurally incoherent whole.
A typical specification table is a two-dimensional grid. One axis represents content areas — the topical sub-domains of the construct (e.g., for a certification exam in nursing: pharmacology, patient assessment, infection control). The other axis represents cognitive levels, usually drawn from Bloom's taxonomy: recall, comprehension, application, analysis, synthesis, evaluation. Each cell in the grid specifies how many items should target that content area at that cognitive level. A test with 100 items might allocate 20 to pharmacology, of which 5 test recall ("What is the mechanism of this drug?"), 10 test application ("Given these symptoms, which drug is contraindicated?"), and 5 test analysis ("Why might this drug combination cause adverse effects?"). This granularity ensures that the test measures the *right kinds* of thinking, not just factual recall dressed up as applied reasoning.
The specification table directly produces content validity — your prerequisite concept — but its value does not stop there. A rigorous blueprint makes it possible to construct parallel forms: two or more versions of the same test that are statistically interchangeable. Because both forms are built to the same specifications (same number of items per cell, same difficulty distribution), they measure the same construct with the same sensitivity. This is essential for licensure and high-stakes certification, where different test-takers receive different items but must be judged on a common standard. Without a blueprint, parallel forms are impossible to verify.
Blueprints also serve a legal and professional defensibility function that is easy to underestimate. In high-stakes contexts — board exams, employment screening, educational accountability — test developers may be asked to justify every item and the test's overall structure in legal or regulatory proceedings. A specification table created before item writing, reviewed by subject-matter experts, and documented formally demonstrates that the test was designed to measure the stated domain. It is evidence that the measurement was systematic rather than arbitrary. This is why rigorous specifications are not bureaucratic overhead — they are the foundation on which the validity argument rests.