Usually feels like
Days
Tomorrow is the right time to look, not tonight.
It sits in days because the work is done by people at their own desks, in an order you did not set and cannot see.
The wait, in plain words
Filing a dispute does not start a process that runs by itself. It puts a case in front of a person, and that person has other cases. Everything after the filing is queue time: your case waiting its turn, then being read, then being decided.
Queue position is not published, and it would not help much if it were, because queues of this kind are rarely first in, first out. Cases get sorted by age, by category, by which ones are waiting on somebody else, and by whatever the reader opening the list decides to clear first. From outside, all of that looks the same as nothing happening.
The part worth understanding is that most of the outcome was fixed when you pressed submit. The reader works from what is in front of them. A clear account with the right details attached is quick to decide. A vague one is not, and the usual consequence of a hard case is not a bad decision but a slower one.
Underneath, while nothing moves
The reader is reconstructing an order from records rather than witnessing it. They have the order page, the message thread, and whatever each side wrote when filing. They do not have your memory, your other conversations, or any way of inspecting anything outside the market.
| What the reader has | What the reader does not have |
|---|---|
| The order record: what was bought, when it was placed, what state it is in now. | Any way to see the thing the order refers to. |
| The message thread between the two of you, in the order it was written. | Anything either of you said anywhere else. |
| Both filings, side by side, including the parts that contradict each other. | Any sense of which of you is more upset, and no reason to weigh it. |
| Whatever the market itself records about the order. | Spare time. This is one case in a list of cases. |
That table is the whole reason filing quality matters. Anything missing from the left column has to be inferred, and inference is slow. A reader who has to work out what you meant will set your case down and clear two that are already clear, and yours rejoins the list.
Funds are generally held while this runs, which is the mechanical reason the countdown on escrow running down to auto release stops being the thing to watch once a dispute is open. The deadline that mattered was the one for filing. After that, the clock belongs to the queue.
Adding messages during the wait feels like pressure and works like dilution. Every addition lengthens what has to be read, and additions written days apart tend to contradict each other in small ways. A reader who finds two versions of one detail has to decide which you meant, which is a worse position for you than having said it once.
Behaving, and not behaving
A dispute that is progressing looks exactly like one that has been forgotten, so the distinction has to be drawn from your own conduct rather than from the screen.
A case you have left alone
You filed once, completely, with the details attached, and you have not touched it since.
You know what you asked for, so if a partial settlement is offered you already know whether you would take it.
A case you are damaging
You have added a message a day, each slightly different from the last, and the case is now longer than the order it describes.
You opened a support ticket about the dispute as well, so two queues hold two versions of one complaint.
The difference is not attitude. It is the length and consistency of what a stranger has to read. Short and consistent gets decided. Long and drifting gets deferred, and deferral is the only real penalty a queue can hand out.
If you genuinely have something new, one message saying what it is, and then stopping, is fine. New evidence is not the same as a restatement in stronger words.
Safe to do meanwhile
This is a wait where doing nothing is an active choice, and usually the right one.
- Re-read your own filing onceNot to improve it, but to know what the reader sees, so a later offer can be judged against it.
- Decide your floor nowThe smallest outcome you would accept, settled while you are calm rather than while you are being offered something.
- Leave the message thread aloneMessages written during a dispute are read by more people than you were writing to.
- Do not open a second channelA ticket about a dispute is a third account of the same order, written by you.
What makes it longer
Disputes stretch for structural reasons far more often than for suspicious ones.
- A filing that describes how you feel rather than what happened has to be translated before it can be decided.
- A case where both sides keep writing never reaches a stable state, and readers work on stable cases first.
- A partial offer that neither side answers leaves the case open with nobody waiting on the reader.
- Duplicate reports of one problem split its history across two places.
- A counterparty who has stopped replying stalls the case exactly where their answer was needed: a vendor gone quiet.
What this card is not. This card does not tell you how a decision will go, because nobody outside the case is in a position to know that.
Questions people ask about this wait
Does adding more evidence speed a dispute up?
Genuinely new evidence, added once, does no harm. Repeating what you already said in stronger language lengthens the case without adding anything to decide on, and long cases get read later than short ones.
Can you see how far along the queue is?
No. Queue position is not published, and this site contacts nothing, so it has no view of any queue at any market.