Five copy-paste templates for the most common assignment reminder situations: group project, classmate, TA-to-class, last-call urgency, and your own self-reminder. Each one explains the tone choice behind it, so you can adapt without losing the calibration.
Done in seconds. No sign-up required.
Most reminder emails fail in the same three ways: they bury the deadline, they over-apologize for sending, or they make a vague ask. The reminders that get fast, friendly responses share three traits.
"Friday at 11:59 PM" beats "this week" every time. Specificity is respect for the reader's time.
"So we can submit on time" lands better than "I need this from you." Same content, different relationship.
End with one specific yes/no question. "Is the intro section on track?" gets a reply. "Let me know" does not.
When to send: 3 to 4 days before deadline, before things get tight.
Subject: Quick check-in — [Project name] due [Friday]
Hey [Name],
Quick check-in on the [project name] due [Friday at 11:59 PM]. I'm working on the [your section]
and want to make sure we have time to integrate everyone's parts before submission. Could you send
your [section] by [Wednesday EOD]? If anything is blocking you, happy to take a piece off your
plate.
Thanks,
[Your name]
Why it works: shared goal (we), specific ask (Wednesday EOD), offer to help. Not a chase.
When to send: 24 to 48 hours before deadline, casual register.
Subject: [Class] HW due tomorrow at midnight
Hey [Name] — heads up the [class] homework is due tomorrow at midnight. I'm aiming to start
tonight around 8. Want to compare notes when you start, or are you good?
[Your name]
Why it works: drops the formal preamble, names a specific time you'll start, offers collaboration not pressure.
When to send: 3 days before assignment, then 24 hours before as a last-call.
Subject: [Course] — [Assignment] due [Friday] at 11:59 PM
Hi everyone,
A reminder that [Assignment Name] is due this [Friday at 11:59 PM]. The submission portal is open
on [Canvas / Blackboard] under the [Module 4] folder.
A few common questions from office hours:
• [Question 1]: [short answer]
• [Question 2]: [short answer]
If you are stuck, post in the [forum / Slack] or reply here. We're holding extra office hours
[Thursday 3–5 PM] in [room].
Best,
[Your name], TA
Why it works: deadline in the subject line, FAQ pre-empts emails, clear escalation path.
When to send: 24 hours before deadline, when you have not heard back.
Subject: 24 hours — [Project name] due tomorrow
Hey [Name],
Following up on the [project] due tomorrow at [11:59 PM]. Have not heard back on your section
yet — are you in a place where you can send what you have by [tonight at 9 PM]? If something
came up, let me know and we can figure out a plan B.
[Your name]
Why it works: urgency without panic, names the deadline twice, offers an out ("if something came up").
When to send: when you find out about an assignment, set this once.
The self-reminder is the one situation where you should automate instead of write. Type the assignment name and due date into the reminder form once, and you will get an email at 7 days, 3 days, 1 day, and the day-of — with follow-ups if you do not click "I did it." No email composing, no scheduling, no future version of you forgetting to send it.
Automate the reminders for yourself. Save the writing energy for the team emails that actually need a human touch.
Lead with the shared goal, name the specific deadline, and end with a low-friction question. "Hey, just checking in on the lit review draft due Thursday at 11:59 PM. Is your section on track or want me to take a piece?" works because it offers help rather than demanding action.
"Quick reminder," "Just flagging," "Looping back on," "Wanted to make sure this stays on the radar," and "Heads up" all work. Avoid "gentle reminder" in professional contexts — it has been overused to the point of sounding passive-aggressive.
The best opening names the specific assignment in the first sentence so the reader knows immediately what the email is about. "Quick check-in on the bio lab report due Monday" beats "Hi, hope you are doing well, just wanted to follow up." The first version respects time. The second one wastes it.
Frame it as a check-in, not a chase. Acknowledge that everyone is busy. Make a specific ask with a clear deadline. "Hey, want to make sure the Friday draft happens — could you send your section by Wednesday EOD so I can integrate?" Specific timeline + offer of help = professional, not pushy.
For group projects: 3 to 4 days before the deadline (gives time to recover if someone is behind), then 24 hours before as a last-call. For your own self-reminders: 7 days, 3 days, and 1 day before. Day-of reminders fire too late for anything that needs work, but they are useful for submission-only tasks.
For your own deadlines, yes. Set up an automatic email reminder once and skip writing the email at all. For nudging others, an automated reminder feels impersonal and is usually a worse fit than a one-line manual check-in. Automate the self-reminders, write the team ones.
For your own deadlines, automate it. Type the assignment, pick the date — the reminder writes itself.
Set My Auto-ReminderLast modified: