Overview
This series examines how deadlines and other temporal signals shape work in post-secondary computing education. It distinguishes late submission from earlier starts, distributed sessions, quality, support demand, and fairness; then compares final dates, milestones, calendar placement, feedback windows, reminders, task fit, and split deadlines. The evidence supports a conditional conclusion: supportive signals can make long, multi-step work more recoverable and redistribute course support, while a bare or punitive cutoff may relocate pressure. Findings come from a qualitative review of 19 mostly undergraduate computing studies published from 2015 through June 2025 and a bounded CS 124 case, not a universal formula or proof of lasting habit change.
Learning outcomes
- On-time submission shows that a boundary was crossed, not that procrastination or work compression disappeared.
- Long, multi-step tasks benefit more consistently from supportive milestones, scheduled feedback, or process-aware reminders than short routine work.
- In the studied CS 124 case, split deadlines reduced support peaks and improved measured efficiency without a detected Early/Later grade difference.
- Fairness depends on aligned time, information, support, and surrounding workload, not equal hours alone.
Keywords
Preview every chapter · Unlock full text, audio, and video from chapter 4
PlansFAQ
Do deadlines reduce procrastination in computing courses?
They reliably reduce late submission, but they do not automatically eliminate compressed work or establish lasting self-regulation.
What makes a deadline more than a cutoff?
A deadline becomes a useful temporal scaffold when it exposes a meaningful intermediate state early enough for feedback, revision, or recovery.
When are milestones or reminders most useful?
Milestones and process-aware reminders are most useful for long, multi-step work with pacing or process-visibility problems; generic reminders may be enough for short participation problems.
Can split deadlines improve course support without harming grades?
In the studied CS 124 case, split project checkpoints reduced one-day support peaks and improved measured efficiency without a detected Early/Later grade difference. The result depends on coordinated release, testing, due dates, and local monitoring.