How to Make a Test Blueprint (Table of Specifications), Step by Step

Most of us have written a test the night before, then realized halfway through marking that half the questions were about one chapter and nothing checked whether students could actually apply anything. A test blueprint fixes that before it happens. It takes about twenty minutes and makes the test itself faster to write.

Quick answer: To make a test blueprint, list the topics you taught and weight each by teaching time, decide what share of points goes to each cognitive level (for example remember, understand, apply), choose the item types, and fill a grid with the number of questions and points for each topic and level. Then write questions to match the grid, not the other way round.

What a test blueprint is (and why it matters)

A test blueprint, also called a table of specifications, is a plan of your test. It crosses two things:

• Content: the topics or learning objectives you're testing.
• Cognitive level: what students have to do with that content, usually based on Bloom's taxonomy (remember, understand, apply, analyze, evaluate, create).

Each cell says how many questions, and how many points, go to that topic at that level. The point is validity: a test should sample what you taught, in roughly the proportion you taught it, at the levels you expect. Without a plan, tests drift toward easy-to-write recall questions on whatever topic is freshest in your mind.

Step 1: Decide the purpose and the format

Before drawing anything, answer three questions:

• What is the test for? A unit test, midterm, final, or a quick check.
• How long is it?
• What item types? All multiple choice, or a mix with short answer and written responses.

Purpose drives everything else. A final exam should lean more toward understanding and application than a five-minute check after one lesson.

Step 2: List topics and weight them by teaching time

The simplest fair rule: topics you spent more time on get more points. Divide each topic's class time by the total.

Say the unit took 20 lessons and the test is out of 50 points:

• Topic A: 4 lessons, 20%, so 10 points.
• Topic B: 8 lessons, 40%, so 20 points.
• Topic C: 8 lessons, 40%, so 20 points.

Adjust if one topic is especially important for what comes next, but don't let a topic you covered in one lesson take over the test.

Step 3: Choose your cognitive levels and their weights

You don't need all six Bloom levels on every test. Three columns work well for most classroom tests:

• Remember: recall facts, terms, definitions.
• Understand: explain, compare, classify, give examples.
• Apply (and beyond): use a procedure in a new situation, solve, analyze.

A common split for a unit test is roughly 40% remember, 30% understand, 30% apply. A final might shift toward 30/40/30 or more application. These are starting points, not rules. What matters is deciding on purpose rather than discovering afterwards that 80% of the test was recall.

Step 4: Fill the grid with questions and points

Now combine Steps 2 and 3. Here is a worked example for a 50-point test, written as rows (one per topic):

• Topic A (10 points): 6 remember questions at 1 point, 2 understand questions at 1 point, 1 apply question at 2 points.
• Topic B (20 points): 7 remember at 1 point, 5 understand at 1 point, 4 apply at 2 points.
• Topic C (20 points): 7 remember at 1 point, 4 understand at 1 point, 1 understand short answer at 2 points, 3 apply at 2 points.

Totals: remember 20 points (40%), understand 15 points (30%), apply 15 points (30%). Topic weights match Step 2 too. Always add up both directions, by topic and by level, before you write anything.

Match item types to levels. Multiple choice handles remember and understand efficiently. Short answer, where students must produce a number or a word, is better for application because guessing doesn't help.

Step 5: Write a specification for each cell

For every cell with questions, write one line saying exactly what is tested, starting with a measurable verb:

• Remember: identify, list, name, define.
• Understand: explain, compare, classify, summarize.
• Apply: calculate, solve, use, predict.

Avoid vague verbs like "know" or "appreciate"; nobody can tell what question would test them. With good specifications, writing questions becomes translation, and a colleague could write a comparable test from your blueprint.

Step 6: Write the questions and check them against the blueprint

Only now write the test. When you're done, count again: questions per topic, per level, points per section. Fix any drift.

If you draft questions in rayQuiz with Draft with AI, the Difficulty section has a Suggested matrix with presets such as quick check, midterm and final. The default scale is Know, Understand, Apply, and you can switch to Use the 4-level matrix (Recall · Comprehend · Apply · Advanced). Set the ratios to match your blueprint, describe the topics, and attach your unit notes. The draft shows a level tag on each question plus a count per level, so checking it against your plan takes seconds. The AI can still misjudge a level, so read every question before you use it.

Common blueprint mistakes

• Filling it in after writing the test. Then it's paperwork, not a plan.
• Judging level by length. A long question can still be pure recall. Level depends on the thinking required.
• Putting every application question in one topic. A student weak in that topic loses all the hard points at once.
• Skipping specifications. Without them, nobody can check whether a question really sits at the intended level.

FAQ

Is a test blueprint the same as a table of specifications? Yes, the terms are used interchangeably. Some schools also say assessment blueprint or test matrix.

Do short quizzes need a blueprint? Not a full grid, but a one-line plan helps: how many questions, which objectives, how many at each level. It takes a minute and makes even a ten-question quiz more balanced.

How do I tell understand from apply? Ask what the student has to do. Restating or explaining what was taught is understand. Using it on a problem or situation they haven't seen before is apply.

Once your blueprint is ready, make each question count with our guide to writing good multiple-choice questions, or try the AI quiz generator with your own level ratios.