You notice a unit test isn't actually measuring what you're teaching, so you rebuild it, better alignment to the standard, a rubric that separates the skills you actually care about, cleaner questions. That's real instructional growth. It's also the kind of work that quietly disappears into a normal week unless you deliberately capture it as evidence before your next review, at which point you're stuck trying to reconstruct what changed and why from memory.
Why this kind of growth evidence gets lost
Most performance reviews ask for evidence of growth, and most teachers default to citing a workshop attended or a course completed, because that's easy to point to after the fact. A genuine improvement to your own assessment practice is often stronger evidence of actual instructional growth, but it's harder to cite months later if you didn't capture the before-and-after and the reasoning while it was fresh.
What to capture at the time, not months later
1. Save the original assessment before you touch it. You need the "before" to make the case for the "after." A redesign only reads as growth if there's something concrete to compare it against.
2. Write down the specific problem you noticed, in the moment. "Question 4 was answered correctly by students who clearly hadn't mastered the standard, guessing patterns suggested it was testing test-taking skill more than content" is evidence. "I felt the old test wasn't great" isn't.
3. Document what specifically changed and why. Not just "new rubric," but which criteria moved, what each one is now checking for that it wasn't before, and how that maps back to the standard.
4. Note the actual outcome once you've used the new version. Score distribution shifts, clearer differentiation between students who mastered the content and those who didn't, fewer re-grading disputes, whatever changed is the part that turns "I redesigned something" into "here's what improved."
Why this reads stronger than a generic PD credit in a review
A reviewer looking at a stack of certificates sees compliance. A reviewer looking at a specific before-and-after assessment redesign, with your own reasoning attached, sees judgment, the kind of instructional decision-making that a review is actually supposed to be evaluating in the first place. It's also just true, in a way a checklist of completed trainings sometimes isn't.
Our [assessment blueprint tool](/assessment-blueprint) helps you map the redesigned version explicitly back to the standards and skills it's meant to check, which gives you the documented "why" behind the change instead of just the new document itself. Our [rubric generator](/grading-rubric) builds the scoring criteria alongside it, so the finished redesign and its rationale are ready to present as a matched pair when the review conversation comes up.
What still needs your judgment
- Choosing which redesign is actually review-worthy. Not every small tweak needs to become a growth artifact. Save this level of documentation for changes that reflect a real shift in your thinking, not routine maintenance.
- Framing the story honestly, not retroactively inflating a minor fix. A reviewer can tell the difference between genuine growth evidence and a small edit dressed up to look bigger than it was.
- Timing when to bring it up. Some redesigns are worth mentioning as they happen, in a check-in with an administrator, others are better saved whole for the formal review where the full before-and-after tells the complete story.
