01HANDOFF CLOCK
Move this sample order through a short journey.
Current statePacked00:00elapsed in this state
Resets at each handoff · illustrative onlyA future category, explained clearly
Every order has
time you can’t see.
Timesup™ is exploring a simple future: make elapsed time easier to notice at the moments where e-commerce work changes hands. Until launch, this is a field guide to the hidden minutes between picked, packed, dispatched, delivered and returned.
WEB EXPLAINER
00:00:00since this page opened
start!
still waiting?
next action →
This is an illustration of the idea—not a picture of the product.
ONE ORDER✦SEVERAL HANDOFFS✦TIME BETWEEN EACH
A useful distinction
A timestamp tells you when.
Elapsed time tells you how long.
Both matter.
Different questions.
Different questions.
Three ways to notice time
One clock.
Three useful questions.
These are web explainers—not product simulations. They show why elapsed time can be easier to understand when it is attached to an event and a next action.
02THREE QUESTIONS
TimestampWhen did it happen?14:05
Elapsed timeHow long since?23 min
ActionWhat happens next?Review →
03QUEUE SKETCH
Same status. Different ages.
A4 min
B11 min
C19 min
“Ready” alone does not show which item has waited longest.
The order journey
Where does the
waiting happen?
The useful question is rarely “what time is it?” It is “how long has this order, item or return been in its current state?”
Picked
A basket is complete; the next dependency begins.
Packed
The parcel may be ready, but not yet moving.
Staged
A physical order waits for the next person.
In transit
An exception can pause the real-world journey.
Returned
Receipt begins a second sequence of decisions.
Why this category matters
Digital systems record events.
The physical world still has gaps.
An order-management system may know that an order was marked “packed.” A person at the handoff point may still need a simple way to notice how long it has remained there. Timesup™ is being developed around that human-scale problem.
Read our public principles ↗support the system — don’t replace it
Application field notes
Built around
moments, not industries.
The pre-launch notebook
What we can explain
before launch.
Timesup™ is still in research and development. The public work now is to build clear language around the problem, its applications and its responsible boundaries.
- 01The problem
Where physical workflows contain invisible intervals.
- 02The applications
Which handoffs may benefit from clearer elapsed-time awareness.
- 03The boundaries
What elapsed time can—and cannot—tell a person.
- 04The evidence
Validated product specifications will come only after testing.
Field notes
Useful now.
Product later.
We publish the operational thinking around elapsed time without publishing the confidential product architecture behind Timesup™.
Browse all 8 notes ↗01Foundations
What does “elapsed time” actually mean?
Timestamp, duration, deadline and cue—separated in plain language.
6 min read↗
02Fulfilment
Where orders wait—even when the system says “ready”
The quiet gaps between pick, pack, staging, collection and delivery.
7 min read↗
03Quick commerce
The five handoffs inside one fast order
One customer countdown, several operational clocks.
8 min read↗
04Reverse logistics
Returns have a clock, too
Receipt, inspection and disposition are three different events.
6 min read↗
OUR PUBLIC PROMISE