Student progress tracker
Recorded the same day, after every session (~3 minutes) · Serves Domain 5: data use · Initials only — never full names, never photos of student work (privacy rules)
The tracker (printable — one sheet per group per month)
| Student (initials) | Ticket date | Item # | Tag (skill · M-code) | Mastery 1–4 | Note (one line, factual) |
|---|---|---|---|---|---|
| A.O. | Nov 3 | 8 | DIST · M3 | 1 | wrote 2x − 4 for 2(x − 4) |
| A.O. | Nov 4 | 12 | DIST · M3 | 3 | found 3 × −2 after probe |
| J.M. | Nov 3 | 8 | DIST · M3 | 4 | clean; wants harder |
| L.R. | Nov 3 | 2 | MOVE · M2 | 1 | added 4 when moving |
| L.R. | Nov 5 | 13 | MOVE · M2 | 1 | same error, second ticket → FLAG |
The flag column is the tracker’s real product. Two consecutive tickets below mastery (3 or lower) on the same tag → flag the site coordinator at the next check-in (D4). The flag travels with the tagged tickets, so the coaching conversation starts from evidence, not recollection.
Mastery scale (1–4, defined once — same words on the rubric)
| Score | What it means | Observable |
|---|---|---|
| 1 | Not yet | The step fails even with a ladder rung; misconception intact |
| 2 | Attempted | Right move attempted; execution or sign slips |
| 3 | Solved with support | Correct after a ladder hint (L1–L3) or after a probing question |
| 4 | Independent | Correct with zero hints, including the check-by-substitution |
Score the tag, not the item. Item 12 exists to carry the DIST tag; the ticket date and item number are provenance. This is what makes “two in a row on MOVE·M2” computable at a glance.
Privacy rules (non-negotiable)
- Initials only. Not first names, never surnames. If two students share initials, add a scheme digit (A.O.₁) — not a name.
- No photos of student work, ever. If you need the artifact, keep the paper in the site folder per the school’s agreement.
- No grades that could identify a child outside the group. The tracker lives with the tutor (paper) and, if digital, only in the organization-managed account — never a personal phone, personal email, or personal cloud.
- Aggregate up, never student-level. What the coordinator and the measurement plan receive is tag-level counts (e.g., “4 flags on MOVE·M2 this month”), not rows.
- When in doubt, stop and ask. Safeguarding and data rules are set by the school and your organization’s own training — that placeholder outranks anything written here.
Why paper-compatible
The fictional program’s tutors work in school corridors and spare rooms, not at desks. The tracker is designed to survive: a printed sheet on a clipboard, filled in the three minutes after the session while the session plan’s “after” line is fresh. Digital versions (a spreadsheet per group) are fine if they stay inside the organization-managed account — the rules above don’t change with the medium.
What the coordinator does with it
- Checks flag counts by tag at each coaching cycle — flags are coaching topics, not performance accusations.
- Aggregates tags across tutors for the simulated dashboard’s leading indicators.
- Watches tracker discipline itself: same-day recording (D2) is a fidelity metric precisely because a tracker filled on Friday from memory is a diary, not data.