Using formative data to change teaching (teacher moves)

• Short cycle: collect → interpret → act → check again.
• Use exit tickets to decide the start of the next lesson (reteach, practice, or extend).
• Group students intentionally: mixed ability for peer tutoring; similar needs for targeted instruction.
• Adjust pace and select exemplars based on common misunderstandings.
• Keep track of trends (not just single errors): if many students miss the same concept, plan a mini‑lesson.

From the book’s example: many teachers check averages and spread (standard deviation) to see if teaching matched assessment. You don’t need complicated stats — look for patterns and clusters of misunderstanding.

---

Sample mini‑lesson plan with built‑in formative checks

Before class

• Quick diagnostic: 3 question Google Form to check prior knowledge (5 mins).
• Prepare 1 targeted multiple‑choice and 1 open explanation question.

During class

• Quick check after direct instruction: mini whiteboard question (2 mins).
• Think‑pair‑share on one problem (5 mins). Listen for misconceptions.

End of class

• Exit ticket (3 mins): 1 correct problem + 1 reflection (“What strategy worked? What am I still unsure about?”)

Next class

• Use exit ticket results: reteach misconception (10–15 mins) and then give targeted practice.

---

Sample exit ticket prompts (pick one per lesson)

• “One thing I learned today is… One thing I’m stuck on is…”
• Short problem + “How confident are you in your answer? (1–4).”
• “Explain the strategy you used in one sentence.”
• “If you could ask the teacher one question about today’s lesson, what would it be?”

---

Practical rubrics & success criteria (short example)

Success criteria for a short written explanation:

• Clear statement of the main idea (1)
• Logical steps with evidence or reasoning (1)
• Correct use of vocabulary (1)
• A concluding sentence summarising result (1)

Use checklists students self‑tick before submitting. This builds ownership and reduces repetition in teacher feedback.

---

Common pitfalls and how to avoid them

• Over‑grading formative checks: they should be low stakes — grade for participation only.
• Flooding students with feedback: prioritize 1–2 key fixes per student.
• Using rewards that undermine intrinsic motivation: be careful with external incentives for formative tasks.
• Only testing facts: include metacognitive prompts and strategy checks.
• Publicly shaming errors: keep formative feedback private or constructive to protect self‑esteem.

If you’re ever unsure how to respond to a struggling student, err toward encouragement and a clear plan — small wins rebuild confidence.

---

Quick ways to assess metacognition (ready to use)

• Confidence meter (1–5) next to answers.
• “How did you get there?” one‑line rationale.
• Error analysis prompt: “What went wrong and how would you fix it?”
• Learning plan: “One specific thing I’ll practice this week is…”
• Strategy reflection: “Which strategy was most helpful and why?”

---

Fast checklist for implementing formative assessment this week

• Day 1: Start with a 3‑question diagnostic (5 mins).
• Every lesson: end with a 2–3 question exit ticket (3 mins).
• Twice a week: use a 1‑minute paper on key concept (inform teaching next day).
• Weekly: pick 4 students for short 1:1 conferences (2–3 mins each) to check progress and set goals.
• Teach peer‑feedback norms in one lesson and apply in group work.

---

Formative assessment is not a separate add‑on. It’s woven into your lesson cycle: before (diagnose), during (monitor), after (reflect & act). The payoff is huge — clearer decisions, better student confidence, stronger metacognition, and teaching that actually responds to what learners need.

You can ask AI (ChatGTP, Gemini, etc.):

• Draft a 5‑lesson micro‑sequence on the topic of the lessons with formative checks built in,
• Create printable exit ticket templates you can use in class,

Please take the quizs to proceed: