Late work, extensions, and resubmissions

What a missed due date actually does

Nothing automatic happens at the due date. Red Stet doesn't lock the assignment or refuse a submission. dueAt is a marker — it drives UI state and stamps submissions on-time or late, but never gates submitting.

After the date passes:

• The due chip in the student's left rail turns red.
• New submissions tag with a Late pill in your view.
• The dashboard counts the assignment as past-due for sorting.

For a hard deadline, use the maxAttempts cap plus a conversation.

What the student sees when work is past due

Almost identical to on-time. Same instructions, rubric, Submit button. Differences:

• The due chip in their list turns red until they submit.
• The header date still reads "Due May 28" — no "Overdue" relabel.
• Submission timestamp vs. dueAt drives the Late pill on your side.

The student isn't warned or scolded. To make them reflect on the delay, add a self-assessment prompt ("If this draft is past due, what made it hard to finish on time?") — the answer travels with the submission.

Submission limit maxAttempts

Set in the New Assignment form, edit panel, or as a classroom default. Blank means unlimited.

Server-enforced. Exceeding it rejects with "Submission limit reached (N attempts allowed)." Front end disables Submit at the cap; server check is authoritative.

Suggested values:

• High-stakes summative → 1
• Process essay with revision → 3
• Low-stakes practice → blank or 5+

Set a classroom default at Class settings → Default attempt limit. Override per-assignment.

The student's submission counter

With a cap set, the Submission panel shows the count ("Attempt 2 of 3") and a help line ("1 attempt remaining"). After the first submission, the button reads Resubmit.

At the cap, Submit disables and the help line reads "You've used all 3 attempts." To give another try:

• Raise maxAttempts for the class
• Return for revision without grading — doesn't burn an attempt (see below)

No per-student cap override — see Extending one student.

Extending the due date for the whole class

Open the assignment, click Edit assignment, change the Due field, save. dueAt is a substantive change — more than a date swap.

The server:

1. Snapshots student-facing state into versionHistory
2. Bumps currentVersion
3. Fires an assignment-update notification to every active enrollee
4. Drops an update banner into each student's view

Students must Acknowledge the banner before submitting. Version history keeps the last 20 snapshots.

Add a changeNote ("Pushing to Friday — snow day Tuesday means we lose a workshop class"). It lands in the notification body and history entry.

The substantive-change banner and version snapshots

When a substantive field changes (instructions, dueAt, targets, subTasks, rubric, peerReview, attachments, referenceLinks, maxAttempts, selfAssessmentPrompts), every student gets an update banner.

The banner gates submission. Students can keep writing but can't submit until they hit Acknowledge. See changes opens a diff against the version they last read.

Students can't miss the new date — they have to click through, and you have the server-side record.

1-click reminder pushes to students

The assignment carries a Remind dropdown next to Edit and Duplicate. One click fans an in-app notification plus email to the audience you pick. Students already submitted or graded are skipped.

Three audiences:

• Not yet submitted — submissions in not-started or in-progress. Mid-week nudge.
• Past due & not submitted — narrowed to students past dueAt. Morning-after follow-up.
• Past due, ungraded (you) — self-nudge to your bell feed. No emails.

Each notification reads "Reminder: Argument essay — draft 1" (or "Past due: …") with a deep link.

Capability: postClassMessages — owners, co-teachers, TAs can send. Read-only roles can't.

Extending one student

Open the kebab (⋯) on the student's gradebook row and pick Override due date. Takes a date + optional reason; replaces the class-wide dueAt for that student. They see the new date with an Extended pill (hover for reason). The Late pill clocks against the override.

Lighter-touch options:

1. Quietly accept the late submission. Submit isn't locked; ignore the Late pill. Right for short delays.
2. Direct message with the new date you've agreed on. Not enforced, but recorded.
3. Push the class date when the cause is shared (snow day, outage).
4. Override + a tag (IEP, extended-time) for recurring accommodations.

Returning work for revision

"Return for revision" is the absence of a final grade plus a message about what to fix:

1. Open the student's submission.
2. Leave inline feedback, rubric scores, comment-thread notes.
3. Leave status at submitted; don't mark Graded.
4. Message what to revise and that an attempt remains.

Status stays at submitted; attempt count holds. Resubmit increments the counter and starts a fresh round.

If you graded and want a revision: flip status back to submitted (teachers can), and the student can resubmit if attempts remain.

Resubmitting after a return

Mechanically identical to first submit. Cosmetic differences:

• Button reads Resubmit.
• Confirmation: "Resubmit this assignment? Your teacher will see the updated draft. You'll have N attempts left after this."
• submittedAt overwrites. The provenance log keeps the keystroke history; the row carries one timestamp.

An active substantive-change banner gates Resubmit too — acknowledge first.

The teacher view shows the latest submission. Prior content lives in the provenance recording — open the chain from the row.

The late pill in the teacher's grading view

Each row carries a status pill — On time, Late, or none. Computed from submittedAt vs. dueAt; no manual override.

Extending the class date leaves prior submissions on-time. Students who submit between the original and new dates also get On time.

To follow up on missing students, use the Remind dropdown with Past due & not submitted.

Sort and filter by Late

The gradebook header has a Sort by late toggle and three filter chips: All, Late only, On time only. Sort and filter are independent. The meta line shows the late total.

Per-row Nudge

Each missing-submission row has a Nudge button. Click, optionally type a custom message, and one in-app notification + email go to that student. Rate-limited to once per 24h per student per assignment. Mute-aware on the nudge kind.

Nudge is the one-student equivalent of Remind.

When late submission affects the grade

Red Stet never auto-deducts. Rubric scores are the score. A "10% per day late" policy is yours to apply.

The Late pill and submission timestamp give you what you need at a glance.

If your LMS handles late automation (Canvas penalties, Schoology deductions), the score that passes back is the raw rubric score; the LMS deducts downstream.

Some teachers add a self-assessment prompt asking the reason for late work. The answer rides with the submission.

Related

→ Creating an assignment — where dueAt and maxAttempts are first set.

→ Returning work and final grades — the grading-side picture, including how the final score crosses the line from draft to gradebook.

→ Grading workflow — rubric scoring, comment threads, and the moment a submission moves from Submitted to Graded.

→ Back to the help library for more topics.

Missing something? Email feedback.