Calculation notebook · use case

Combine Assignment Points Without Averaging Percentages

A 10-point quiz and a 100-point project do not carry equal influence in a total-points gradebook. Add earned points and possible points separately. The resulting fraction gives each assessment the influence implied by its possible points.

Prepare earned and possible points

List each assessment once, with earned points first and possible points second. Retain a zero earned score when the assignment counts. Excluding a missing assessment and counting it as zero are different gradebook policies; the calculator cannot infer which one the teacher uses.

Work through unequal assessment sizes

Consider 9/10 on a quiz and 60/100 on a project. The combined result is (9 + 60)/(10 + 100) × 100 = 69/110 × 100 = 62.727…%. Averaging 90% and 60% gives 75%, which answers a different equal-weight question. The project supplies 100/110, or about 90.91%, of the denominator.

Work through unequal assessment sizes
AssessmentEarnedPossiblePercentage
Quiz91090%
Project6010060%
Combined6911062.727…%

Estimate the effect of a new assignment

Adding 20/20 changes the total to 89/130, or 68.4615…%. The new score raises the average because its 100% rate is above the existing 62.727…%, but it does not replace the old denominator. Solving for an 80% overall result on that 20-point assignment would require 0.80 × 130 − 69 = 35 points, more than its 20-point maximum.

Do not merge weighted categories prematurely

If the syllabus weights homework at 20% and projects at 80%, compute the percentage inside each category first, then apply those percentages to the category weights. A points sum across categories is appropriate only when the instructor actually uses a common total-points denominator.

Make the grade reproducible

Save the individual rows and label excluded assessments. Confirm that the possible-point total matches the gradebook before comparing percentages. A displayed percentage may be rounded, whereas the gradebook may retain a fractional value; compare the underlying fraction when a result lies near a threshold.

Build a second record from raw fractions

A homework score of 20 out of 25 and a project score of 45 out of 75 combine to 65 earned points out of 100 possible points, or 65%. Averaging their individual percentages, 80% and 60%, would yield 70%. The five-point discrepancy arises because the project has three times the possible points and therefore three times the influence in a total-points model. Neither answer should be described as a generic average without its weighting rule.

In assignment-grade mode, choose the total-points option explicitly. Its explicit-weight mode gives equal influence only if you add equal weights in the third column, such as fifty for each row; that model reproduces the 70% result. The simpler grade calculator takes two-column earned/possible rows and can also accept one already summed row, 65 100. It has no separate equal-assignment selector and does not infer syllabus weights from an assignment name.

Compute a new assessment’s effect before averaging

Add an assessment worth forty points and earn 38. The new total is 103/140, or 73.571428…%. Its 95% individual score pulls the total upward, but the new result is not the average of 65% and 95%. The previous record contributes one hundred possible points and the new assessment forty. An independent check is (65 × 100 + 95 × 40)/140 = 73.571428… .

To reach 80% after that same forty-point assessment, solve (65 + x)/140 = 0.80. The requirement is x = 112 − 65 = 47 points, above the forty-point cap. At full marks, the best result is 105/140 = 75%. Keep the infeasible required count visible; converting it to forty would obscure the fact that the target remains unmet.

Separate a dropped assessment from a zero score

If the 20/25 homework is officially dropped, the remaining record is 45/75 = 60%. If the project is dropped instead, it becomes 20/25 = 80%. Dropping a row changes both sums; merely replacing its earned points with zero retains its possible points and lowers the grade. With a counted zero on the homework and the project unchanged, the total would be 45/100 = 45%, not 60%.

This distinction matters when a gradebook displays missing, excused and incomplete assessments differently. Make an explicit included-row record before calculating rather than deleting every low result. A dropped-score policy can also depend on percentage, point value or category rules. The arithmetic tool follows the selected rows; it does not decide which row the teacher’s policy is supposed to remove.

Audit marginal marks and rounding near a threshold

Once the denominator is 140 possible points, each additional earned point changes the percentage by 100/140 = 0.714285… percentage point. Two additional marks raise 103/140 to 105/140, or 75%. This marginal effect differs from adding a new assignment, which also enlarges the denominator. Distinguish a corrected mark on an existing assessment from a fresh assessment with its own maximum.

Keep earned and possible totals alongside the percentage when comparing with a gradebook. A result displayed as 74% may come from 73.571428… rounded for presentation, while the course threshold uses the original fraction. This tool requires earned points not to exceed possible points on each row; a syllabus bonus or extra-credit policy needs separate accounting. Category weighting, score replacement and the treatment of absent work should be documented separately rather than inferred from this fraction.

Questions and checks

Can I average assignment percentages?

That is valid only for an equal-weight model or equal possible-point totals. Total-points grading requires the two sums.

Can earned points exceed possible points?

Ordinary inputs must satisfy 0 ≤ earned ≤ possible. If a course permits extra credit, document that bonus and its policy separately rather than entering an unsupported ordinary score.

Does a zero earned score count?

If the assessment is included, its possible points stay in the denominator even when earned points are zero.

Sources and scope

The examples are illustrative calculations, not records of individual users. Check the policy or measurements that apply to your situation.

Try the calculations