Start with the benchmark
What did markets expect before the release? Without consensus, you cannot measure the surprise.
A terrible jobs report should be bad for stocks — right? Not always. Markets react to what changed versus expectations, and to what that change means for growth, inflation, and the Fed. We’ll start with a real U.S. release and see what actually happened.

On August 7, 2026, the U.S. jobs report landed far below expectations. Nonfarm payrolls fell by 23,000 in July, while economists surveyed by Reuters had expected a gain of about 80,000. June was also revised down from +57,000 to +20,000. If all you saw was the headline, 'U.S. economy loses jobs,' the bearish case would sound obvious.
The U.S. economy unexpectedly lost 23,000 jobs in July, versus an expected gain of about 80,000. If that were all you knew, what would you expect U.S. stocks to do that day?
Commit to your first read. The actual market move appears after you choose.
This is the point of the exercise: the market is not grading the economy with a simple good-news/bad-news scorecard. It is repricing the future. To understand why stocks rose, we need to separate the raw number from the surprise and then ask what that surprise changed.
| Field | Value |
|---|---|
| Actual | −23,000 |
| Consensus | about +80,000 |
| Previous first estimate | +57,000 (June) |
| Revised June | +20,000 |
A useful framework is: data → surprise → growth / inflation / Fed expectations → yields, earnings, and risk appetite → stock prices. The important part is the middle. A weak report can hurt the earnings outlook and still help valuations if it lowers expected interest rates enough.
Five days later, on August 12, U.S. July CPI rose 3.4% year over year, exactly in line with the widely watched forecast and slightly below June's 3.5%. Core CPI was also in line. Compared with the payroll report, this release contained much less surprise.
Yet stocks still moved: the S&P 500 rose about 0.3%, the Nasdaq gained about 0.5%, and the Dow was nearly flat. That does not mean an in-line CPI 'caused' the rally. AI earnings, falling yields, oil, and positioning were all moving at the same time. The correct lesson is that a low-surprise release leaves more room for other information to drive the session.
The July payroll miss mattered because it changed expectations immediately. But one weak month does not by itself prove recession, just as one cool CPI print does not prove inflation is solved. Revisions, participation, wages, job openings, retail demand, and later releases can strengthen or overturn the first interpretation.
What did markets expect before the release? Without consensus, you cannot measure the surprise.
Which expectations changed — growth, inflation, the Fed, yields, earnings, or risk appetite? More than one can move at once.
A one-day reaction is evidence. A macro trend requires repeated releases and corroboration from other series.
Compare actual with consensus, previous data, and revisions before reacting to the headline.
Trace the surprise through growth, inflation, Fed policy, yields, earnings, and valuation instead of jumping straight to price direction.
Use later data and independent indicators to test the first interpretation. One print is evidence, not proof.
Submit your answers to see detailed explanations.
Checking sign-in status...
Explain why a news headline can't be directly converted into a trading direction, and understand that the price reaction depends on the gap between the actual result and market expectations.
Understand the expectation-gap framework behind macro data: inflation/employment/growth/rates are the macro variables the market watches continuously; market prices usually already reflect some expectation; the gap between the actual value and expectations (the surprise) and the resulting revision to future expectations matter more than the headline number itself. No 'data direction → asset direction' fixed rule is used.