Skip to content
For Teachers

Diagnostic Quizzes: Using Pre-Assessment to Plan Better Lessons

May 2, 20267 minJames Okafor
Share:XLinkedIn

TL;DR. A diagnostic (pre-assessment) quiz reveals what students already know — and what misconceptions they bring — before you teach. Use the data to skip what they have, accelerate what's familiar, and front-load what's missing. 5 minutes of pre-assessment can save a week of misaimed instruction.

The cost of teaching what students already know

Walk into a 7th-grade classroom and start a unit on simple machines. Half the class learned this in 4th grade. They're bored. The other half is hearing it the first time. By Friday, the first group is checked out and the second group is still lost.

This is a teaching problem with a measurement solution: find out what they know *before* you plan the unit, not after.

What a diagnostic quiz isn't

It's not a graded assessment. Students should know that — explicitly. The pre-assessment exists to inform your teaching, not to evaluate them.

Telling students "this doesn't count" matters because anxiety degrades the signal. A nervous student answers worse than they actually know.

Phrase it as: *"I want to know what you already know about [topic] so I can teach you the parts you don't know yet, instead of the parts you do."* Most students appreciate this once they realize it's about respecting their time.

What to put on a diagnostic

Three categories of questions:

1. Prerequisite knowledge

Do they have the foundations the unit assumes? If you're teaching factoring, can they expand (x+2)(x+3)? If they can't, factoring won't land — go back and shore up the prerequisite.

2. Target content

The actual unit objectives, asked at the level you'll eventually expect. Some students will already meet some objectives. That's not bad data — it's permission to skip those parts.

3. Common misconceptions

This is the one most teachers skip and it's the most valuable. Bake the textbook misconceptions into wrong-answer choices on multiple choice questions. If 60% of your class picks the misconception, you know what your unit's biggest hurdle will be.

Example. Pre-quiz on evolution:

> Which of the following best describes how species evolve?

> A) Individuals adapt to their environment over their lifetime, and pass those changes to offspring

> B) Species change because they need to in order to survive

> C) Random variations in offspring lead to differences in survival, which over generations changes the species

> D) Species are designed to fit their environment

A and B are common misconceptions (Lamarckian evolution; teleology). D is a specific misconception about agency in evolution. C is the modern-synthesis answer.

If 70% of the class picks A or B, you know to start the unit by explicitly addressing the Lamarckian misconception. If most pick C, you can move faster.

Length and timing

  • 5–10 questions for a one-week unit pre-assessment
  • 15–20 questions for a multi-week or end-of-grade-level pre-assessment
  • Anything longer becomes its own assessment with its own anxiety. Keep it short, keep it ungraded, keep the message clear.

    Run it on Day 0 of the unit, ideally a class period or two before instruction begins so you have time to adjust your plans.

    Generating a diagnostic quickly

    Building a high-quality diagnostic from scratch can take an hour. AI cuts this dramatically:

  • In an AI quiz generator, paste the unit's standards, your old end-of-unit quiz, or the textbook chapter outline
  • Set difficulty to "medium"
  • Choose 10 questions, all multiple choice
  • Generate
  • Then *edit aggressively*. For each question:

  • Rewrite one wrong-answer choice to match a known misconception
  • Cut any question that's too easy (everyone will get it right — wasted slot)
  • Add at least 2 questions probing prerequisite knowledge
  • In 15 minutes you have a usable diagnostic. After 3–4 cycles you'll have a library of pre-assessments you can reuse with minor edits each year.

    Reading the data

    Once students have taken the diagnostic, look at three things:

    1. Which questions did most students get right?

    Anything above ~85% correct is a topic you can move past quickly or skip entirely. Don't spend a full lesson on something the class already knows; pivot to a brief review.

    2. Which questions did most students get wrong?

    Below ~30% correct is the unit's central challenge. Plan your most engaging, multi-modal lesson on this topic. It's where you'll create the most learning per minute of class time.

    3. Which wrong answers were popular?

    If a single wrong-answer choice is picked by 40% of students, that's a misconception you need to address explicitly. Plan a lesson that contrasts the misconception with the correct understanding directly — don't just teach the correct version and hope it overwrites.

    Using the data with students

    Be transparent. Many teachers share the class-level results (anonymously) at the start of the unit:

    > *"On the pre-quiz, 22 of you got question 4 right — you all already understand why species evolve. We're going to spend less time on that. But only 6 of you got question 7. That's where we're going to slow down and make sure everyone gets it."*

    This builds trust (you're respecting their time) and primes attention for the hard parts.

    Pairing pre and post

    The pre-assessment by itself is a planning tool. Pair it with a parallel post-assessment for the most powerful evidence of learning:

  • Same number of questions, same Bloom's levels, **different specific items**
  • Run identical analysis after teaching
  • Growth = post-score minus pre-score
  • Class-level growth scores are far more meaningful than absolute scores. A class that starts at 30% and ends at 80% has demonstrated more learning than a class that starts at 75% and ends at 85% — even though the second class has the higher final score.

    This evidence is also gold for parent-teacher conferences, administrator observations, and your own reflection.

    When pre-assessment isn't worth the time

    Don't pre-assess for:

  • Lessons that build on yesterday's lesson (you already have data — yesterday's exit ticket)
  • Unit lengths under 3 days (the prep cost outweighs the benefit)
  • Highly procedural skills that almost no student will have prior knowledge of
  • Save the diagnostic for new units, longer units, and content where prior knowledge varies wildly.

    A working teacher's annual rhythm

    A pattern that scales: pre-assess once at the start of each unit (4–8 times a year), reuse and refine the same pre-assessment each year, and let the cumulative data show you which prerequisite topics keep failing — those are the gaps in your earlier units, not just this unit's problem.

    Over 3 years, your pre-assessment library becomes a curriculum diagnostic for the whole grade.

    Related reading: [Formative vs Summative Assessment](/blog/formative-vs-summative-assessment) · [Standards-Aligned Quiz Design](/blog/standards-aligned-quiz-design) · [Student Data Tracking for Teachers](/blog/student-data-tracking-teachers)

    Get weekly study & quiz tips

    Join teachers and students who get practical tips on quizzing, active recall, and AI-powered learning.

    Share:XLinkedIn

    James Okafor

    EdTech Researcher & Instructional Designer

    Practice with AI-generated quizzes

    Ready to create your first quiz?

    Use AI to generate quizzes from your own study materials in seconds.

    Try SimpleQuizMaker Free