Usually feels like
Days
Tomorrow is the right time to look, not tonight.
It sits in days rather than higher up because the market clock attached to the order does have an edge, even though the movement underneath it has none.
The wait, in plain words
Dispatch and movement are two different events, and almost all of this wait sits in the gap between them. Marking an order as sent is something a person does in the market interface. Whatever it refers to may have happened before that, after it, or not yet. The two are related. They are not the same event, and only one of them is visible from where you sit.
So the thing you are waiting for is a record, not an object. The record changes when somebody or something updates it, and long flat stretches are the ordinary texture of such records rather than a signal about them. A page that has not changed since yesterday has told you nothing. It has simply not been written to.
The honest description of most of this wait is that you know nothing new. That is uncomfortable to read on the third refresh, but it is accurate, and it is why this card spends more time on the clock than on the wait. There is a deadline running underneath, and it is the only part of the situation you can act on.
Underneath, while nothing moves
A tracking record is a claim about a label. A label can exist before anything is carried, because creating one is a keystroke. Scans are events attached to that label by whoever handles it, so a gap between scans is a gap in reporting. Handling and reporting are separate systems that touch each other occasionally, which means the record can sit still while things happen and can also sit still while nothing happens. From outside, those two look identical.
That is the mechanical reason nothing about the wait tells you the state of the thing waiting. The record is downstream of handling, handling is downstream of dispatch, and dispatch is downstream of a decision somebody made about their own working day. Each link adds delay of its own, and none of them reports to you.
Meanwhile a second clock is running, and this one you can see. Order pages of this shape generally carry a window after which the order settles by default, described on escrow running down to auto release. That window knows nothing about labels or scans. It has been running since the moment covered in the order going through.
Those two clocks are the whole of the situation. One you cannot see and cannot influence. The other you can see, and it has an edge. Missing that edge while staring at the first one is the characteristic mistake of this band.
Behaving, and not behaving
Since you cannot inspect the thing itself, the only useful distinction is between a wait that still has room around it and a wait that is quietly running out of one.
A wait that is behaving
The record is flat or moving slowly, a direct question gets an answer eventually, and the settlement window still has room in it. Nothing here needs a decision today.
You have looked at where the countdown sits, so you know when the next decision point arrives without having to watch for it.
A wait that has stopped behaving
The settlement window is near its end and you have taken no position, so whatever happens next will be decided by the default rather than by you.
The vendor has stopped replying and you are reading the silence as reassurance. That has its own card: a vendor gone quiet.
The distinguishing feature is not the record. It is whether the deadline is still an option or is about to become a fact. A flat record with plenty of window left is an ordinary day. The same flat record near the edge of the window is a decision you are declining to make.
Nothing in the record will tell you which of those you are in, because the record was never about the window. You have to open the order page for that, and it takes a moment.
Safe to do meanwhile
Most of what is useful here takes a few minutes once, and then leaves you alone for a day.
- Find the settlement windowOpen the order page and see where the countdown sits before doing anything else.
- Read your own order record onceWhat was agreed, what was said, and in what order. Reading it later under pressure is worse.
- Write one question, or noneA direct question can be answered. A stream of updates cannot, and it costs the other side the time they would spend on you.
- Keep the addresses you already haveA wait is a poor moment to go looking for a new way in.
- Draft the filing you may never sendIf the window closes in on you, the case already exists and was not written in a hurry.
What makes it longer
The wait stretches for reasons that mostly have nothing to do with you, and for one or two that do.
- Dispatch happens in batches, so an order placed just after a batch waits for the next one before anything at all becomes true.
- Records are written by handlers who have no relationship with you and no reason to write more often than their own system requires.
- A question sent as several messages is read as several messages, and the reply comes after all of them have been read.
- Opening a dispute starts a second wait alongside the first, and the second one is a queue with people in it.
- Checking many times a day makes the wait feel longer without changing anything about it.
What this card is not. This is not a way of finding out where anything is, and it is not advice about anything physical.