Waits that take days

The parcel

Once it is handed over it moves through a system with its own working days and its own sorting, and that system has no interest in your evening. See a parcel moving.

The escrow window

This one counts down on its own and ends in a decision whether or not either party has said anything. See escrow running down to auto release.

The dispute queue

Opened by you, worked through by somebody else, at a pace set mostly by how many were opened before yours. See a dispute being looked at.

Somebody else's week

Silence in this band is far more often a schedule than a decision. See a vendor gone quiet.

Why tomorrow is the right time to look

A wait reaches this band when its mechanism runs on a calendar instead of on a session. Something physical has to travel. A queue has to be worked through by people who work through it during their own hours. A window has to expire. None of those are shortened by checking, and none of them care which tab is open.

More importantly, none of them produce partial progress you can see. A parcel in motion and a parcel that has not moved look identical from a screen. A dispute being read and a dispute waiting to be read look identical too. Absence of change in this band carries almost no information, which is the exact reverse of the seconds band, where a still screen that stays still long enough is the entire signal and there is nothing else to read.

There is a further reason to keep away from the screen here, and it is about what you will do with what you see. In the shorter bands the screen at least reflects your own request, so a change on it is connected to something you did. In this band the screen reflects somebody else's record keeping, updated when they update it, which may be nowhere near when the thing itself happened. A status that has not moved is not the same as a situation that has not moved, and treating the two as identical is how a normal week starts to look like a problem.

The practical consequence is that the right interval for looking is a day, not a refresh. Checking more often does not gather information, because there is no information to gather between one day and the next. It only gathers worry, and worry in this band tends to convert itself into actions that make things worse rather than into actions that help.

The deadline you did not know was running

The mistake that defines this band is missing your own deadline while your attention is fixed on somebody else's silence. Most of the waits here are passive. You are waiting to be told something, and there is nothing to do but wait. But not every clock in this band is passive. At least one of them counts down towards an outcome and reaches it without needing you to take part.

The shape of the mistake is always the same. Attention goes to the thing that is quiet, which is usually a vendor or a parcel, because quiet things are what people worry about. Meanwhile the window that would have let you say something closes without announcing itself. By the time the silence finally breaks, the option that mattered has expired, and every remaining option is worse than the one that just went.

• Waiting for a reply before opening a dispute, when the dispute window is the thing with the deadline on it and the reply has none.
• Letting escrow run down while a conversation is still going, so the decision gets made by a clock rather than by either of the people involved.
• Reading a slow reply as rudeness rather than as a schedule, and answering in a way that makes the next reply slower still.
• Losing track of what was agreed, because it was agreed a while ago, in a message thread, and nothing was written down anywhere else since.

Two habits deal with all of it. Know which of the clocks in your situation are counting down rather than merely waiting, and write down what was agreed at the time it is agreed rather than when you need it. Both cost a little attention now and save the whole argument later. A refund being agreed and a support ticket both go noticeably better for people who did the second one.

Waits that run on the calendar

Each card says what is moving out of sight, what would delay it further, and which of your own clocks is running while you wait for it. Read the one that applies, note the date you read it, and set the next look for another day rather than another hour.

The two edges of this band

Below is an evening, above is a wait with no honest end. The lower edge is easy to draw and the upper edge is the one that matters, because crossing it changes what you should do rather than only how long you should wait.

Downward, towards <a href="/evening">an evening</a>

The wait ends in one event that either happens today or does not. If coming back after supper is a reasonable test of whether it is done, the card belongs in the evening band and not here.

Upward, towards <a href="/open-ended">no honest end</a>

A wait leaves this band when nothing in its mechanism sets a ceiling any more. A parcel has a delivery system behind it, and delivery systems end in something. An order that never arrives has run out past the end of that system, and no further stretch of waiting puts it back inside.

The one that drifts

The published set changing sits here because the change itself, when it comes, is a discrete event. The waiting for it is not discrete at all, which is why that card is careful about what it claims and what it declines to claim.