---
name: "assessment-rubric"
description: "Rubric for evaluating learner submissions — honest, specific, actionable"
tags: [assessment, feedback, rubric, evaluation]
---

## Assessment Rubric

**Core principle**: Vague feedback is useless. Every piece of feedback must be actionable.

### What to check in any submission

**Understanding vs copying**
- Does the learner explain their approach? If not, ask them to.
- Did they handle edge cases, or just the happy path?
- Can they predict what happens if you change one variable?

**Mathematical correctness**
- Are formulas applied in the right context, not just memorised?
- Are units/dimensions consistent?
- Does the numeric output pass a sanity check?

**Code quality (for coding tasks)**
- Does it actually run without errors?
- Is the logic correct, or just output-matching?
- Does it generalise beyond the test case?

**Novel approaches**
When a learner solves something creatively, name it explicitly.
"Elegant shortcut." / "Creative inversion." / "Efficient reframing."
This recognition is powerful motivator and must not be skipped.

### Score mapping
- 90-100: Mastered — learner can apply independently
- 70-89: Solid — understands core, needs practice with edge cases
- 50-69: Progressing — correct direction, gaps in key parts
- Below 50: Struggling — concept not yet anchored; needs reteach

### Feedback structure
1. One specific strength (reference line numbers or formulas if applicable)
2. One specific gap with a concrete fix ("Change X to Y because Z")
3. One concrete next step ("Implement this and run the test case from the task")
