HomeDocs › Excused, Ungraded & Discarded

The short version

Sooner or later a piece of work should not count for a student. ProfDesk keeps four separate answers because they mean genuinely different things, and two of them behave differently in your outcome data.

  Counts towards the final grade? Counts towards CLO attainment? Shows in To Grade? Who decides
Excused No No No You, per student
Ungraded No, not yet No, not yet Yes Nobody; it just isn't marked
Dropped (lowest) No Yes No The assessment's rule
Discarded attempt No, that attempt only No, that attempt only No You, per attempt
The one row people miss. A dropped score still counts towards CLO attainment. The student sat the work and it was marked, so it remains evidence of what they can do. Dropping it is a kindness applied to the course total, not a statement that the measurement never happened. An excused item is different: they never sat it, so it is not evidence either way.

Excused

Excusing says this student is exempt from this work. Whatever the reason, such as illness, an approved absence, or a question that was misprinted on their paper, it stops counting.

The important part is what happens to the arithmetic: the item's weight leaves that student's denominator rather than scoring zero. Their percentage is worked out over everything else.

What you'll see

  • Any mark you already recorded is kept and shown struck through, so you can still see what they scored. Excusing never destroys a grade.
  • The student sees the item marked Excused on their results, with the mark struck through.
  • It disappears from your To Grade queue because there is nothing waiting for you.
  • AI grading skips excused students entirely, so a bulk run will not stamp a zero or AI feedback onto work somebody was exempted from.

Where to do it

  • ZenGrader: Excuse this sub-part or Excuse whole assessment on the grade-state bar.
  • Gradebook › Exclusions tab: see everyone who is excused from what, and lift an exemption from one place. In the grid itself, an excused cell is yellow with an EX tag and cannot be edited.
  • Student gradebook: an excused item is labelled Excused, with a link to where it can be lifted.
Excusing a whole assessment excuses every sub-part inside it in one action. Excusing them one at a time works too, but leaves the ones you forget still counting. ZenGrader tells you when an assessment is only partly excused.

Ungraded

Ungraded simply means not marked yet. It is the normal state of new work, and it is what the To Grade queue counts.

Ungraded work is left out of the final grade rather than counted as zero, so a percentage shown mid-term describes only what has been marked so far. Results & Outcomes shows a banner whenever anything is still outstanding, so a provisional figure is never mistaken for a settled one.

Putting something back to ungraded

You marked it, then decided you want another look. Setting it back to ungraded removes the score, rubric selections and AI feedback, and returns it to your To Grade queue.

  • ZenGrader: Set to ungraded, for one sub-part or the whole assessment.
  • Gradebook or student gradebook: clear the mark out of the cell. This works for typed and quiz scores. A rubric-marked score is greyed out there, so set it back to ungraded in ZenGrader.
Your annotations are safe. Setting work back to ungraded keeps your ZenGrader markup by default. The confirmation offers to clear it as a choice, not a side effect. And it never lifts an excusal: those are two different decisions, and only you can undo the one you made.

Dropping the lowest score

An assessment can be set to drop each student's lowest score, a common policy for a run of quizzes. It is worked out from the marks as they stand, so it re-decides itself every time a grade changes. You never mark anything as dropped; the rule does it.

Why it isn't the same as excusing

Because excusing happens first, and the drop then applies to what is left. That ordering is what stops an exemption from quietly eating the student's drop allowance. Four quizzes out of 10 each, drop-lowest switched on, a student scoring 9, 4, 7, 8:

SituationLeft outCountedResult
Nothing excused Quiz 2 (their lowest) 9 + 7 + 8 / 30 80%
Quiz 2 excused because they were ill Quiz 2 excused, then Quiz 3 dropped as lowest of the rest 9 + 8 / 20 85%

The ill student still gets their lowest sat quiz dropped, like everyone else. If the two mechanisms were the same thing, the exemption would have bought them nothing and they would have landed on 80%, the same as somebody who simply had a bad day.

Discarding an attempt

When resubmission is allowed, an assessment's marking policy decides which attempt counts: highest, latest, or the average. That policy is set for the whole class, which is a problem when the attempt you need to throw out is the one the policy picks.

The cases it exists for

  • Academic misconduct. A copied second attempt scoring 18/20 beats an honest first attempt of 11/20 under highest. Excusing the whole question would drop all 20 marks, which rewards the copying since they were doing badly on it.
  • Late work. Under latest, an attempt submitted after your window still wins.
  • The wrong file. Under average, one accidental upload drags the mark down permanently. If it used the student's last attempt, neither of you can fix it.

Discarding takes that one attempt, for that one student, out of the running. Every marking policy inherits it at once.

What discarding does not do

The file is never deleted. A discarded attempt stays openable in ZenGrader and stays in the student's own history, labelled as not counted. When the reason is misconduct, that file is your evidence. Removing it would be the opposite of what you need.

Reason and attempt quota

Discarding asks for a reason, such as academic misconduct, a wrong file submitted by the student, lateness beyond the accepted window, a technical problem, or another reason, plus an optional note. It is often an academic-integrity decision, so it goes on the record rather than being an unexplained flag.

You also choose whether the student gets the attempt back. The reason suggests an answer and you decide:

ReasonAttempt returned by defaultWhy
Wrong file / technical problemYesIt was never a real attempt
Late beyond your windowNoThey used their attempt
Academic misconductNoA refund would hand back another try at the work they were caught on

If you discard everything

Discard every attempt and the item goes back to not graded yet, returning to your To Grade queue. It does not become a zero. Any excusal on it survives.

Discards are reversible: Restore on the attempt row puts it back among the candidates and the grade recomputes.

Multiple attempts and your To Grade queue

Earlier attempts never appear separately in To Grade. The queue lists one item per student per sub-part, however many times they submitted. A resubmitted item simply carries an attempt count. Marking it clears it from the queue.

Most of the time you will grade the latest attempt and leave the earlier ones alone, and the gradebook then shows exactly the mark you entered: the marking policy only has a decision to make when two or more attempts have been marked.

Worth knowing. If you did mark an earlier attempt as well, the default policy is highest, so the gradebook may keep showing that earlier, higher mark rather than the one you just entered on the newest attempt. That is the policy working as configured. Change it on the assessment, or discard the attempt you don't want counted.

Related