What "Priced In" Actually Means, and Why It Gets Misused

"It's already priced in" is one of the most overused phrases in market commentary, deployed to explain both why an expected event caused no reaction and, confusingly, to wave away why an expected event caused a large one. The concept itself is sound. The problem is almost entirely in how loosely and how retroactively the phrase gets applied.

What "priced in" actually means. Saying an event is priced in means current prices already reflect some probability-weighted expectation of that event and its likely consequences, built from the range of outcomes participants see as possible, not a single forecast everyone agrees on. It doesn't mean every investor expects the same outcome, and it doesn't mean the market has assigned the expected case a certainty it doesn't deserve. When the realized outcome, and the details surrounding it, land close to the distribution markets had already embedded in prices, there may be little new information left to reprice, and prices can move only modestly even though the event itself is significant: a widely expected rate hike, telegraphed for weeks through communication and data, often produces little market reaction on the day it's announced precisely because the expectation was already built into prices well beforehand.

Where the concept breaks down. Markets price the full range of possible outcomes and how confident participants are in that range, not just a single expected case, so an event that matches the median or consensus expectation exactly can still move markets if it resolves uncertainty that had previously been priced as a wide range. The act of narrowing that range is itself new information, even when the central outcome doesn't change, which is why "the market got it right on direction" and "the market reaction was small" are two different claims that don't automatically imply each other.

The magnitude problem. Being broadly right about the direction of an event doesn't mean the market got the details right. A rate cut that was correctly expected can still surprise on its size, twenty-five basis points instead of the anticipated fifty, or on the accompanying language, and markets react to that specific mismatch even though the headline direction was exactly as forecast.

Consensus forecasts and market pricing aren't the same thing. A published economist consensus, a median forecast collected from a survey, is a different object from what's actually embedded in market prices. For a central bank decision, fed-funds or overnight index swap futures pricing reflects what traders are actually positioned for and willing to transact on, which can diverge from the survey median by a wide margin. For a scheduled event like an earnings release, options-implied volatility can give a read on the magnitude of move the market expects, without necessarily implying a clean view on direction. Treating a survey consensus as identical to market pricing is one of the more common ways "priced in" gets misapplied. It's also worth keeping in mind that market-implied probabilities are themselves an estimate extracted from prices, not a direct readout of what investors literally believe, they can embed risk premia and technical factors of their own, so even "the market's pricing" falls short of a clean survey of expectations.

Why the phrase gets misused after the fact. "It was already priced in" is frequently used retroactively to explain a muted reaction that actually had other causes, offsetting news arriving the same day, or a reaction that simply hadn't fully played out by the time commentary was written. Treating the phrase as an explanation rather than a claim that needs its own evidence is where most of the misuse comes from. Before concluding something was priced in, the more useful exercise is identifying what the market actually expected beforehand, futures pricing, the dispersion in a survey, options-implied volatility, or positioning data, and checking that against what happened. If you can't point to what the pre-event expectation actually was, "priced in" is explanation by hindsight, not an analysis.