ZorantaGuides
Gradeleaf

Gradeleaf › Guides

Zero for Missing Assignments or a 50 Minimum? The Math and the Options

A zero for a missing assignment pulls an average down much further than a low score on work that was handed in. With scores of 85, 90 and 80 plus one zero, the average is 63.75. Record the missing work as 50 and it becomes 76.25; leave it out and it is 85.

Which of these is right is a policy decision, and many schools set it for you. This page shows the arithmetic behind each option, the main arguments for and against a 50 minimum, and ways to record missing work so the gradebook stays honest.

A teacher entering scores on a phone over a pile of handed-in papers

What a zero for missing assignments does to the average

Four assessments on a 0–100 scale, with the third one missing:

How the missing work is recordedCalculationAverage
Zero(85 + 90 + 0 + 80) ÷ 463.75
Minimum of 50(85 + 90 + 50 + 80) ÷ 476.25
Left out(85 + 90 + 80) ÷ 385

On the usual letter scale, those three averages are a D, a C and a B. The zero does the damage because of the shape of the scale: A, B, C and D each cover ten points, while F covers sixty (0 to 59). A single zero sits fifty or more points below the other scores.

How far one zero reaches

To bring that 63.75 back up to 80, the student would need a total of 400 over five assessments. They have 255, so the fifth score would need to be 145, which is not possible on a 0–100 scale. The zero still decides the letter grade after several more good scores.

Gradeleaf

In Gradeleaf you mark work as "Absent" (left out of the average) or "Not handed in", and choose for each class whether not-handed-in work is left out or counted as the lowest score. Get it on Google Play

The 50 minimum grading policy

Under a 50 minimum, the lowest score that can go into the gradebook is 50, including for missing work. Some districts apply it to every assignment; others only where the student made an attempt, and record no-attempt work differently.

Arguments for a 50 minimumArguments against
Keeps one missing task from making the course mathematically impossible to passGives points for work that was not done
Makes each letter band the same size on the scaleCan let a student pass while skipping a share of the work
Keeps the student working on later assignmentsWithout follow-up, missing work may simply stay missing
The report card still shows an F for that taskTeachers may feel it hides a real gap in learning

Edutopia's article The Problem with a 50 Percent Minimum Grade sets out the case against, and is worth reading alongside your own school's policy.

No zero policy alternatives

A no zero policy does not have to mean a free 50. Common alternatives keep the gap visible without letting the arithmetic take over:

Absent, excused and not handed in

These are three different things, and mixing them up is a common source of grade disputes.

SituationUsual treatment
Absent on the day, work excusedLeft out of the average
Absent, work to be made upMarked missing until made up, then scored
Present, work not handed inFollows your policy: zero, minimum score, or missing until a set date
  1. Write the rule for each case into your syllabus.
  2. Use a separate mark for "absent" and "not handed in" in the gradebook, rather than a blank or a zero.
  3. Decide when "missing" turns into a score, and tell students.
  4. Check the average with and without the missing work before report cards, so you know how much the rule is moving the grade.

The same rules apply inside weighted categories. A zero in a category worth 30% hurts less than a zero in a points-only gradebook where that task carries a large share of the points; total points vs weighted grades shows why.

Many schools and districts set how missing work must be graded. Where your school has a written policy, it takes priority over the options on this page.
Gradeleaf

Record missing work the way your policy says

Gradeleaf keeps "Absent" and "Not handed in" apart, and each student's average follows the rule you set for the class.

Get it on Google Play

iPhone version coming soon

More guides

All guides

Published by Zoranta, the developer of Gradeleaf.