All field notes
AssessmentAugust 2, 2026·6 min read

Writing a Pre-Assessment That Actually Tells You Where to Start the Unit

Most pre-assessments get skipped because they feel like extra work before the real teaching starts. Here's how to build one that actually changes where you begin, in under twenty minutes.

By Mr. Tran, 7th grade math
Teacher reviewing a short student pre-assessment quiz at a desk with a unit planning notebook, warm natural light

Most teachers know they're supposed to pre-assess before a unit starts. Most teachers also skip it, because building a real diagnostic on top of everything else on the to-do list before a unit begins feels like extra work that delays the "actual" teaching. The irony is that skipping it is what causes the wasted time, you spend the first three days of the unit re-teaching a prerequisite half your class already knew, or moving too fast for the half that didn't.

A pre-assessment isn't a test, it's a map

The goal isn't to grade what students don't know yet, it's to find out where the actual starting line is for this specific group of kids, which is rarely exactly where the curriculum map assumes it is. A good pre-assessment is short, five to eight questions, ungraded, low-pressure, and it targets the prerequisite skills the unit depends on, not the unit content itself.

Build it backward from what the unit assumes

1. List the two or three prerequisite skills the first lesson assumes students already have, not the skills the unit will teach, if the first lesson assumes fraction fluency, that's what you check, not decimal operations that come in week three
2. **Ask one question per skill that reveals the *method*, not just the answer**, "show your work" on a single problem tells you more about a misconception than ten multiple-choice items that can be guessed
3. Give it the day before, not the morning of, you need time to actually look at the results and adjust day one before you walk in, not react live in front of the class

Turning results into an actual starting point

Our [assessment blueprint tool](/assessment-blueprint) helps you map exactly which prerequisite skills a unit depends on before you write a single diagnostic question, so the pre-assessment tests the right three things instead of a scattershot review of everything from last year. Once you know your learning target for day one, our [learning objectives tool](/learning-objectives) helps you write it at the right level of specificity for where your students are actually starting, not where the pacing guide assumes they are.

What the data should actually change

  • If most of the class is solid on the prerequisite, skip the planned review day and start the new content immediately, that's a real day of instruction you get back
  • If a third of the class is shaky on one specific piece, build a 10-minute warm-up reteach into day one instead of a full review lesson that bores the two-thirds who didn't need it
  • If the gap is wide and split roughly in half, that's your differentiation plan for the first week, not a problem to solve with one whole-group lesson

The twenty-minute investment

Writing the pre-assessment takes maybe twenty minutes once you know the two or three prerequisites to check. What it buys back is not spending the first three days of a three-week unit guessing at the room's actual starting point. The unit goes faster overall because it starts in the right place, not because any single lesson was rushed.

Keep reading