Strategies

Formative Assessment Cycles

Strategy · All strategies
Evidence · 9 claims (4 for, 2 mixed, 3 against) · 18 studies (9 quant-synthesis, 6 causal, 2 review, 1 associational), q2–q4 · 9 of 18 report an effect size · 1 claim rests on one study

Description

A formative assessment cycle is a short instructional loop with four moves: elicit evidence of what students currently understand, interpret that evidence against where they need to get to, adjust the next stretch of teaching in response, and elicit again to check whether the adjustment worked. The cycle can run in ninety seconds, with a show-of-hands question mid-explanation, or across a fortnight, with a diagnostic task driving a re-teaching plan. What makes it a cycle rather than a check is the third move: if the evidence never changes what happens next, the assessment was monitoring, not formative.

Design Implications

The evidence for assessment for learning is strong in aggregate but heterogeneous in the way that always signals an implementation-dependent effect Assessment for learning improves achievement [+S]. Wiliam's framing explains why: formative assessment is not an instrument but a set of practices, and the classroom gains come from the responsiveness — the teacher and the learner both doing something different because of what the evidence showed. Programmes that install the instruments (exit tickets, mini-whiteboards, traffic lights) without changing what follows them produce little.

Two design consequences follow. The eliciting move has to be diagnostic rather than merely performance-revealing: a question that most students get right tells you nothing you can act on, and a question whose wrong answers all look alike tells you nothing about why Eliciting Student Thinking. And the adjustment has to be feasible in the time available, which means the cycle's length must match the size of the adjustment it can support — a mid-lesson check can support a re-explanation, not a re-planned unit.

Context

Requirements

Constraints

Implementation Variability

Target Learners

Target Learning Goals

Instructions

  1. State the target for this cycle. One thing students should be able to do by the end of it, specific enough to write a diagnostic question about.
  2. Design the eliciting task to be diagnostic. Build it so that each wrong answer implicates a particular misunderstanding, and so that guessing right is unlikely (Formative Assessment).
  3. Collect from everyone at once. Mini-whiteboards, all-student response, or written responses — anything that samples the whole class rather than the volunteers.
  4. Interpret against the target, not the average. Ask what the wrong answers have in common; the pattern, not the percentage, is what tells you what to do.
  5. Decide and act before moving on. Choose from a prepared set — re-explain differently, run a worked example, pair students, move on with a note to revisit (Demonstration, Scaffolding).
  6. Tell students what you saw and what you changed. This is what converts the cycle from surveillance into shared work, and it models the self-assessment you eventually want them doing.
  7. Re-elicit on the same target. Verify the adjustment worked before treating the target as met; an unverified adjustment is an assumption (Feedback).
  8. Keep it ungraded. Record what you need for planning, not for the gradebook, so students have no incentive to conceal confusion.

Examples

Mid-explanation diagnostic questions: A teacher pauses an explanation, poses a multiple-choice question whose distractors each encode a known misconception, reads the whole-class response on mini-whiteboards, and either re-explains or proceeds — a cycle of under two minutes.

Exit ticket driving the next lesson's starter: Students answer two questions on leaving; the teacher sorts the responses into three piles that evening and opens the next lesson with the error that dominated.

Unit pre-assessment in mathematics: A short diagnostic before a fractions unit identifies which students already hold the prerequisite, allowing the first two lessons to be re-planned around the specific gaps rather than taught to the middle.

Draft-conference-redraft in writing: The cycle runs over a text — draft, targeted feedback on one criterion, redraft, check on that criterion — rather than over a concept. - Dylan Wiliam's "hinge questions" — multiple-choice items with distractors mapped to specific misconceptions; the whole class answers simultaneously and the teacher chooses one of several pre-planned instructional responses. - Kahoot! / Poll Everywhere — anonymous whole-class response systems that make the misconception distribution visible to instructor and learners alike. - ASSISTments — online math homework platform that gives immediate task-level feedback to students and error-pattern reports to teachers, who adjust the next lesson.

Key Sources

Page metadata
Field Value
type strategy
id formative-assessment-cycles
aliases formative-assessment
title Formative Assessment Cycles
description Running instruction as a repeating loop — elicit evidence of learning, interpret it, adjust teaching, then re-elicit — so that what happens next is decided by what students actually understood.
status review
generated by claude/unspecified on 2026-08-30
trust unverified — no one has confirmed this page's content
sources 3 — black-wiliam-1998, wiliam-2011, hattie-timperley-2007

Frontmatter is the page's machine-readable record — see the Schema & Guide.