Article / Prediction markets / 3 min read
The question before the price
A prediction market turns an uncertain event into a specific contract. Understanding the difference is where useful analysis begins.
Two people can agree about what is likely to happen and still disagree about the value of a prediction-market contract. They may be answering different questions without realising it.
Consider a hypothetical market asking whether a city will record a temperature above 30°C by Friday. That sounds straightforward. But which weather station counts? Is the threshold strictly above 30°C, or at least 30°C? Does the deadline use local time? Is the result based on the first published reading or a subsequently corrected figure?
None of those details changes the weather. Each can change what the contract pays.
A forecast needs a defined outcome
Prediction markets are often discussed as forecasts with prices attached. That is a useful starting point, but it leaves out an essential step: the event has to be translated into a rule that can resolve a contract.
Polymarket's public documentation distinguishes a market's title from its resolution rules. Those rules specify the source used to determine the outcome, the relevant end date and the handling of edge cases. The platform's documented structure makes a broader point: a readable headline is a summary of an instrument, not a complete description of it. Polymarket: Resolution
In the temperature example, a weather forecast answers a question about the world. The contract adds a measurement procedure, a source and a deadline. Research needs to keep all of them in view.
Three separate questions
A useful way to read an unfamiliar event contract is to separate three questions:
- What event is being considered?
- What evidence will count as establishing that event?
- When must the event, or the evidence, exist?
The third question is especially easy to blur. An announcement, an effective date and a publication date can refer to different moments. A policy might be announced in one month and implemented in another. A statistic might describe one period and be released during the next. Those are ordinary features of public information, but they need to be made explicit when an outcome has a deadline.
This is also why apparently similar market titles should not be treated as interchangeable. “Announced by Friday” and “in force by Friday” ask different things. Before comparing their prices, it is necessary to establish what is being compared.
Make ambiguity visible
A strong piece of analysis should say where interpretation enters the argument. It should distinguish a fact established by the stated source from a reasonable expectation about what that source will eventually report.
Suppose the forecast strongly favours a hot day, but the named weather station is temporarily unavailable. The meteorological view may be unchanged while a question about measurement has appeared. Writing down that distinction gives readers a more accurate account of the uncertainty than quietly treating the missing reading as a routine detail.
An unresolved question does not always have a clever answer. Sometimes the honest research output is that the contract cannot yet be interpreted with enough confidence. Precision includes recognising that limit.
A more useful conversation about probability
Much commentary about prediction markets concentrates on the latest percentage or a dramatic change in price. There is also value in explaining the question that sits behind the number.
A market number travels easily. It fits a chart, a headline or a conversation. Its meaning is less portable: the source, the deadline and the treatment of an unusual outcome can disappear when the number is repeated.
When those details are explicit, disagreements become easier to locate. One reader may expect different weather; another may be interpreting the measurement rule differently. Those disagreements require different evidence to resolve. A good forecast begins with a question that two people can read the same way.