How to Write a Unit Test That Matches What You Actually Taught

You know the feeling. You hand back a test, the class average is a 62, and half the kids look at you like you swapped in a different unit. You taught the material. You made the study guide. And still, something did not line up. Usually the test drifted from the lessons without you noticing, one question at a time.

Here is how I stop that from happening, without turning test writing into a weekend project.

Write the test before you finish teaching, not after

Draft the test right after you finish planning the unit, before you teach day three. I know that sounds backward. It works because the test becomes your target. When you write it early, you can see the gap between what you planned to teach and what you plan to assess, and you can close it while you still have time.

Do not polish it. A rough draft with the question stems and answer key is enough. You will revise as you go.

Tag every question to a specific lesson

Next to each question in your draft, write the date or lesson number where students first saw that idea. If a question has no lesson attached, you have two choices. Teach it, or cut it. That is the whole rule.

This is where surprise questions sneak in. The stoichiometry problem you meant to demo but skipped when the fire drill hit. The vocabulary word that only appeared in a reading you never discussed. Tagging catches these before students do.

Match the format, not just the content

If you spent the unit doing whiteboard problems in pairs, a test full of multiple choice will feel foreign, even if the content is identical. Students are not just learning content, they are learning a format. Ask yourself:

• Did I practice free response? Then at least half the points should be free response.
• Did we do data tables and graphs in class? One should appear on the test.
• Did I use a specific sentence stem for explanations, like claim, evidence, reasoning? Use it on the test too.
• Did we work with a reference sheet or periodic table? Give them the same one.

Do a five minute reverse audit

Before you print, open your lesson slides or notes and skim them in order. For each day, ask, is this represented on the test? If a whole lesson has zero questions, either it was not important enough to teach, or your test is missing something. Usually it is the test.

Then flip it. Read your test top to bottom and ask, where did we practice this exact skill? If you cannot point to a specific day, that question is the surprise. Rewrite it or cut it.

Weight the points the way you weighted the time

If you spent four days on Newton's second law and one day on units, do not make units worth 20 percent of the test. Rough rule, points should track class minutes. It is not a perfect science, but it keeps a topic you barely touched from tanking a grade.

One honest note

All of this assumes the unit itself is coherent, with lessons that actually build toward the assessment. When the unit is a patchwork of stuff you pulled together at 10pm, no amount of test tuning will save it. That is the part I got tired of doing by hand, so I built Rested Teacher to plan a full year of aligned lessons and assessments in one place. Use it or do not, but do the alignment work somewhere.

A test should feel hard, not unfamiliar. If your students walk out saying it was tough but fair, you nailed it.