Why most events get a PASS
CONSENSUS looks at far more matches than it publishes. Most get no pick: the case for one is not strong enough, or the price is not worth taking. Why that filter exists, what it costs, and why volume is the wrong product metric.
CONSENSUS publishes a pick only when a match clears its own bar. Most matches do not, so most matches produce nothing. The filter is the product: a short list of picks we stand behind is worth more than a daily quota of picks we do not.
What a reader sees
| Outcome | What it means | What happens |
|---|---|---|
| 1 u | The odds are clearly better than our own number | Published at full stake |
| 0.5 u / 0.2 u | The pick stands, but the price is closer to fair or short | Published at a smaller stake |
| PASS | Nothing convincing, or no price worth taking | Nothing sent. The most common outcome |
What the price does and does not decide. Whether there is a pick at all is decided by our criteria; the gap between our number and the market sets the size of the stake. A price that works against us produces the smallest stake, not a pass — and the expected value is printed next to the pick, negative included.
Why is volume the wrong metric?
A prediction service optimising for published volume has to find something to say about every fixture. Most fixtures are efficiently priced, so forcing output on them means publishing signals with no edge — which drags the aggregate towards the break-even rate and adds margin costs on top.
The arithmetic is unforgiving. Adding coin-flip signals to a set of good ones does not dilute the edge proportionally; it destroys it, because each added signal pays the bookmaker margin. A service that publishes ten signals a day is telling you it has found ten edges a day, which is a much larger claim than it sounds.
This is also why the number of published signals will never be a target here. A quota converts a filter into a content schedule, and the filter is the only thing worth paying for.
What does the filter cost?
Honesty requires stating the downside. A strict bar reduces sample size, and a smaller sample takes longer to demonstrate anything statistically. It also means some genuinely good opportunities are passed over. The filter trades coverage for precision, and that trade is a choice rather than a free win.
It also makes the record slower to build. A service publishing thirty signals a week reaches a thousand settled results in eight months; at our rate it takes considerably longer. We accept that, because a thousand results from a forced quota would not answer the question a hundred honest ones do.
How do you read a PASS?
A PASS is not a prediction that nothing will happen, and it is not a hedge. It means the method did not produce a scenario stable enough to publish, and that the event stays in the log without a signal.
From the reader's side, the value of a PASS is the events it removes from consideration. You are paying for the events we talk you out of as much as the ones we talk you into — and unlike a published signal, the value of a skipped event never appears in any performance statistic.
Check any of this against our record
Every signal CONSENSUS publishes carries the bookmaker odds fixed before the event starts and the settled result afterwards — including the drawdowns and the losing runs. The running total is on the front page and every entry is in the log.