Students and records

Your roster identifies the students whose papers you mark. Committed results belong to those students, so check roster entries and paper assignments before recording a class set.

Check roster entries before a run

Keep names recognisable and check for existing entries before adding a student. When a paper needs someone who is missing from the roster, you can add that student from the matching dropdown without leaving the marking run.

The name written on the paper is used for matching. A suggestion is something to check against the work, especially when students have similar names. The identification guide explains how to assign and correct matches.

Distinguish drafts from recorded results

A run in progress is a draft. Resolving a flagged answer does not by itself write a mark to a student’s record. You check the digest and confirm every mark when you commit the results.

After commit, the student’s record carries their results across tests. Open the run for the class’s question-by-question results, or the student record to look at that student’s work across tests. See reviewing and committing.

Read the context behind a total

Two equal totals can represent different strengths and gaps. Look at which questions lost marks and what those questions assessed. When comparing tests, consider differences in content and available marks before interpreting a change in the total as progress or a setback.

For practical examples, read using question-level results to plan reteaching.

Export or correct results

You can export a run or student record to CSV. Check the destination’s expected columns before importing the file into your usual markbook; AutoMark does not sync marks directly into an LMS.

Individual committed marks can be corrected, and a paper assigned to the wrong student can be reassigned. The record keeps those actions as your changes rather than silently replacing what happened.