I4.06.2extendable deadlinedesign

Deadlines should be extendable, or at least requestable

Aliases: request more time · session keep-alive · hold extension · extra time

What it is

The clock hits zero with work still open: one field left, the network hiccupped, the ID number is in the other room. Deadlines should be extendable, or at least requestable means zero is not only “wipe / fail”. People can still take another stretch, or ask someone who can grant one. Advance notice is what makes it possible to hurry. Extension is what keeps one missed sprint from writing off the time already spent.

Why it happens

A limit is an estimate of duration, and estimates run short. Filling, thinking, fetching a document all have a tail, and the tail often pokes just past the original clock. If zero only destroys, filled fields, a held seat, a half-written answer all become sunk, and the next attempt starts over. Extension turns zero from a cliff into a negotiable edge: keep the session locally, hold the ticket a few more minutes, ask an invigilator for time.

Extendable and requestable are not the same strength. What the system can grant safely (session still live, stock still held) should renew in one beat, without an approval path. What cannot be granted, or would harm someone else (the last ticket, exam fairness), goes to a request — and the request must still be sendable before zero. After zero, only “ended” remains, which is too late. Infinite renewal turns the limit into décor, so extensions need a visible cap on count or total length, shown in advance.

Where it stops holding

Limits whose constraint is fairness (a synchronous exam, an auction close, a vote) cannot be quietly extended for one person; that breaks the rule. Extra time must hold for everyone in the same sitting, or be a pre-announced accessibility allowance, not a bargain at zero. A security cut, a payment already submitted, a legal filing deadline: extending would change the facts, and must not be silent extra life. Once stock has been released to someone else, a hold cannot be extended; what is owed is not more time but “released, you may rejoin the queue”. Selling “watch an ad for one more minute” as the only extension is selling the limit, not rescuing duration.

Applying it

  • For sessions, drafts and holds, offer “need more time” before zero. Default to a visible extra stretch, and show how many renewals remain.
  • For resources that cannot be renewed, place “request an extension” where it can still be hit before zero. After zero, say why it ended and what can still be done.
  • Fairness-bound sittings do not offer per-person silent extra time. Accessibility extra time is configured before the sitting starts, not when the countdown hits zero.
  • How to check: fill a form halfway, let the session clock reach warning, extend; the draft should remain and the clock should run again. Hide the extension until after zero — it should be too late to hit. Offering a silent extra minute to one person in a synchronous exam is the counterexample: everyone else’s clock in that sitting must match.

Related

  • Same group: I4.06.1 Deadlines need enough advance notice · I4.06.3 Fake urgency timers are a dark pattern
  • Nearby: I1.06 Timeout strategy · I2.06 Cancel during wait
  • Search terms: extend deadline · session keep-alive · request more time

Cards in the same group

Quick Actions

Share

Share this page

ios_share

https://hci.top/en/handbook/I4.06.2