Late Work Penalty Calculator

Original score:

points

Maximum score:

points

Due date and time:

Submitted date and time:

Grace period:

duration

Grace period unit:

Late-unit rule:

Weekend and no-school exclusions in Advanced apply only to calendar-day counting.

Penalty method:

Percent deduction:

% / unit

Percentage base:

Point deduction:

points / unit

Penalty tiers:

Format each line as minimum units, amount, for example 1, 10.

Tier amount:

Maximum-score reduction:

% of max / unit

Weekend exclusion:

Only affects the calendar-day rule.

{{ params.exclude_weekends ? 'Weekends excluded' : 'All calendar days counted' }}

No-school dates:

Use one YYYY-MM-DD date per line. Only the calendar-day rule uses this list.

Total deduction cap:

Enter zero to disable the cap. Choose how a positive cap value is measured.

policy amount

Deduction cap basis:

Points, percent of effective original score, or percent of assignment maximum.

No-mark cutoff:

Enter zero to disable the cutoff. A positive threshold is exceeded only by a larger counted total.

counted units

Minimum score floor:

Enter zero to disable the floor. Choose points or percent of assignment maximum for a positive value.

policy amount

Score floor basis:

Use points or percent of assignment maximum.

Final-score rounding:

Choose no model rounding to preserve full precision; the direction applies only to a selected increment.

Rounding direction:

Nearest, down, or up at the selected increment.

Checkpoint	Value	Policy meaning	Copy
{{ row.label }}	{{ row.value }}	{{ row.detail }}

Calculation trail

Audit the counted lateness, deduction basis, and final safeguards against the written course policy.

Late-work policies often sound precise until a submission falls between the examples. “Ten percent per day” leaves several questions open. Does a partial day count? Is the percentage taken from the earned score or the assignment maximum? Do weekends count? Does a grace period move the deadline? Does a score floor survive a no-mark cutoff? Different answers can produce different grades from the same timestamps.

A reproducible adjustment begins by turning the written policy into an ordered set of rules. Due and submission times establish lateness, the grace period moves the effective deadline, and the late-unit rule converts elapsed time into a count. Only then can the penalty method determine a deduction or maximum score.

Rolling days count elapsed 24-hour blocks and round any partial block up.
Calendar days count local dates after the effective deadline; configured weekends and no-school dates can be omitted.
Hours count elapsed hours and round any partial hour up.

The penalty itself may be a percentage per counted unit, points per unit, the highest matching fixed tier, or a declining maximum-score cap. Percentage policies need a declared base because 10% of an 80-point earned score removes 8 points, while 10% of a 100-point assignment removes 10. The percentage deduction is non-compounding: each unit uses the same selected base.

Caps, floors, cutoffs, and rounding are not interchangeable. A deduction cap limits how many points can be removed. A floor protects the adjusted score from ordinary deductions. A no-mark cutoff sets the score to zero when counted lateness is greater than its threshold and overrides the floor. Rounding changes the final score only after deduction and floor rules have been applied.

The result is useful only when it matches the published course policy and the institution's official timestamp. Daylight-saving changes, time zones, reopened attempts, excused lateness, accommodations, and manual overrides can require an authoritative gradebook review rather than arithmetic alone.

How to Use This Tool:

Translate the policy in the same order it would be applied to a real submission. Do not choose a familiar-looking preset unless its wording matches the course rule.

Enter Original score, Maximum score, Due date and time, and Submitted date and time. The earned score is limited to the assignment maximum before deductions.
Set Grace period and Late-unit rule. Choose calendar days only when the policy is based on local dates; weekend and no-school exclusions affect that mode alone.
Choose Penalty method and enter its rate, percentage base, tier rows, or maximum-score reduction. Fixed tiers use one minimum counted-unit threshold and amount per line.
Configure the optional cap, cutoff, floor, and rounding rules in Advanced. Zero disables the deduction cap, no-mark cutoff, or score floor.
Review Counted late units, Applied penalty, and Adjusted score. Check Policy notes for exclusions, the selected tier, a cap, a floor, or a cutoff before transferring the result to a gradebook.

Interpreting Results:

Raw late units show the count before calendar exclusions. Counted late units drive the policy, and the difference appears as excluded units. When rolling days or hours are selected, configured weekends and no-school dates do not change either count.

Raw penalty is the deduction produced by the selected method. Applied penalty may be smaller when a positive deduction cap is reached. Points lost can differ from applied penalty after a score floor, rounding, maximum-score clamp, or no-mark cutoff.

A cutoff of 3 units does not apply at exactly 3. It applies only when counted late units are greater than 3. Check the policy wording carefully if it says “three days or more,” because that is a different boundary.

Technical Details:

Timestamps are parsed as nominal local wall-clock values in YYYY-MM-DDTHH:MM form. No timezone or daylight-saving offset is inferred. The grace duration is converted to minutes and added to the due timestamp before lateness is counted.

Formula Core:

For hourly and rolling-day policies, every positive fraction becomes a full counted unit.

u = ⌈ \frac{\max (0, t_{submitted} - t_{due} - g)}{q} ⌉

g is grace time in minutes. q is 60 for hours or 1,440 for rolling days. Calendar-day mode instead counts eligible local dates after the grace deadline.

The percentage and point methods produce a raw deduction in assignment points:

\begin{matrix} D_{percent} & = & B \times \frac{r}{100} \times u \\ D_{points} & = & p \times u \end{matrix}

B is either the effective original score or assignment maximum, r is the percent per unit, and p is points per unit. The effective original score is the smaller of the entered original and maximum scores.

After the raw deduction is converted to points, the policy order is:

S = cutoff ? 0 : clamp (round (\max (F, O - \min (D, K))), F, A)

O is effective original score, D is raw deduction, K is the optional deduction cap in points, F is the score floor, and A is assignment maximum. When the cap is disabled, raw deduction is used directly. Rounding may be disabled or applied to 0.01, 0.1, 0.5, or 1 point using nearest, down, or up.

Rule Core:

Fixed tiers and maximum-score caps replace the two linear deduction formulas but still enter the same cap-floor-rounding sequence.

Late-work penalty method rules
Method	Rule
Fixed tier	Select the highest tier whose threshold is ≤ counted late units; convert its amount from points, percent of original, or percent of maximum.
Maximum score cap	Available maximum = max(0, assignment maximum × (1 − rate × units ÷ 100)); deduction is the amount the effective original exceeds that cap.
Deduction cap	Applied deduction = min(raw deduction, cap converted to points). A value of 0 disables the cap.
No-mark cutoff	Apply 0 only when counted units > cutoff. A value of 0 disables the cutoff.
Score floor	Keep deduction-based results at or above the point floor or percentage-of-maximum floor; a cutoff overrides it.

With an 80-point original on a 100-point assignment, 40 hours late under rolling-day counting becomes 2 units. A 10% deduction based on the original removes 80 × 0.10 × 2 = 16 points, leaving 64 before any optional cap, floor, cutoff, or rounding.

Accuracy Notes:

The arithmetic is deterministic, but policy interpretation remains the main source of error. Verify the official due timestamp, accepted submission timestamp, local calendar, and written boundary language.

Calendar-day counting treats a submission later on the effective due date as one raw day late; that date may count as zero only if it is excluded.
Weekend and no-school exclusions do not pause rolling 24-hour or hourly elapsed time.
The model does not infer time zones or daylight-saving transitions.
Excused lateness, accommodations, resubmissions, extensions, gradebook overrides, and institutional appeal rules require separate review.

Worked Examples:

Weekend exclusion changes a calendar count

A deadline at 5:00 p.m. Friday and a submission on Monday can span several calendar dates. With calendar-day counting and weekend exclusion enabled, Saturday and Sunday are omitted; with rolling days, the same elapsed time is divided into 24-hour blocks and the weekend setting has no effect. The correct choice comes from the course policy, not from whichever result is more favorable.