Deadlines need enough advance notice
Aliases: deadline notice · countdown warning · session timeout warning · lead time
What it is
Five minutes left on an exam, a session about to log out, an offer closing, a ticket held in the basket for ten minutes — if those clocks appear only on the last beat, there is no time to change plan. Deadlines need enough advance notice: before the constraint starts to bite, people must know there is a clock, how long it is, and what happens when it hits zero. A request the system abandons after waiting too long is a different timeout. This is about a person having to finish something before a moment.
Why it happens
Plans need a horizon. Knowing forty minutes remain, people drop low-priority checks and submit first. Not knowing there is a clock, they write as if there were no cap, until they are kicked out, wiped, or scored. A countdown that appears from nowhere is coded as an ambush, not as a rule. Notice has to cover three things: existence, length, consequence. “Please hurry” has no actionable length; a length with no consequence leaves people unsure whether the draft dies or they are merely signed out.
“Enough” tracks remaining work, not a global thirty seconds. Telling someone after they have filled a long form that the session logs out in two minutes is a real clock with a fake preview: remaining work already exceeds remaining time. Real advance means the limit is visible at the start of the task, with one more reminder before the irreversible tail.
Where it stops holding
A session that must cut immediately for security (account takeover detected) cannot wait long out of politeness; after the cut it must still say what happened, to distinguish from a silent expiry. A public clock in a live exam or at the end of an auction is the rule; advance notice is the rule being public, and cannot be hidden. Administrative deadlines measured in days are the wrong grain for a second-level countdown; notice belongs on a calendar and a reminder, not a ticking corner. A wait the user cannot speed up (the system is computing) turns a countdown into a promise about system duration — a different estimate, not a deadline on the person.
Applying it
- State the limit and the consequence at the start of the task. Remind once more before the irreversible window, still carrying remaining time and consequence.
- For clocks that discard work (session, seat hold, exam), notice must land before remaining work exceeds remaining time.
- Do not replace an actionable length with “please hurry”. Do not let the countdown appear for the first time in the last few seconds.
- How to check: start a form that takes several minutes, give no hint, then pop a countdown with under a minute left — that is the failing control. Make the limit visible at start, remind before the end; people should be able to submit or save after the reminder, not learn of the clock after being kicked out.