How to read a full event, start to finish

This session pulls everything together. What happens in the days after per the research, how to read a fresh release in the order that matters, and two real cases from the public archive told start to finish — one that hit and one that didn't.

What the evidence says about the days after

A 1968 finding uncovered something that shouldn't happen if markets were perfectly efficient: after an earnings surprise, the price doesn't only move on announcement day — it keeps drifting in the same direction for weeks.

The finding and its confirmation

Ball and Brown documented that post-earnings drift for the first time in 1968. Rather than adjusting at once when the information became public — which is what the efficient market hypothesis covered in the chart chapter predicts — the price took weeks to fully absorb it.

Bernard and Thomas confirmed the pattern's persistence in 1989, over 1974-1985 data: the return spread between companies with the best and worst surprises was positive in 41 of the 48 quarters studied.

It's one of the most studied anomalies in recent decades of finance research, precisely because it's hard to explain without qualifying the strictest version of market efficiency.

The mechanism connecting it to the call

Something from this chapter's first session fits here. The National Bureau of Economic Research (NBER) work on management tone found that after a call with a worrying tone, the price keeps falling for days because the initial reaction fell short: the market responds faster to enthusiasm than to concern.

That's drift, measured from another angle. It isn't that the information arrives late: it's that it gets processed at different speeds depending on what it says.

And here it's worth being precise about what this means

A phenomenon being documented in academic literature, over historical data and large samples, doesn't make it an actionable certainty about a specific company's next report.

Caution is warranted for three reasons. Documented anomalies tend to erode as more people learn and exploit them, as the chapter on technical analysis covers. Studies measure averages across thousands of cases, not what one company will do next Tuesday. And Volatly hasn't validated this pattern on its own dataset yet.

Until that validation exists, it's treated here as exactly what it is: a real academic phenomenon, with sources, and nothing more. If something else ever gets claimed, it'll be with proprietary data and its sample in plain view.

How to read an earnings report in five minutes

A release can run twenty pages and nobody reads it end to end in the five minutes after it drops. You don't need to: there's a reading order that captures almost everything that moves the price, and it isn't the order it's written in.

The five steps, in order of importance

First, guidance. Not the quarter. We saw why: it's the only part speaking about the future. Find what the company says about next quarter or the year, and compare it against expectations. If guidance changes, almost everything else is secondary.

Second, revenue and earnings against consensus. Now the figures. And remember the two things from the previous session: beating is normal, so what informs is by how much; and beating on revenue outweighs beating only on earnings.

Third, the margins. Revenue rising with margins narrowing tells a very different story from revenue rising with margins intact. It's the difference between growing and buying growth.

Fourth, where the profit came from. Is it the core business, or is there a one-off factor — an asset sale, an accounting adjustment, a tax effect — that won't repeat? The headline doesn't distinguish.

Fifth, management's tone. It comes last because it arrives later, on the call, and it's what adds the most nuance. Cautious, confident, or evasive on a specific question.

Why this order and not the document's

If you start with the "beat or miss" headline and stop there, you miss exactly what this chapter has explained: that beating is normal, that guidance weighs more, and that the quality of the result matters as much as the result.

Reading in this order lowers the risk of reacting to the wrong headline, which is the most expensive error in the whole process.

The five most repeated mistakes

Worth having them together, because each corresponds to something this chapter has already covered.

One: reading the "beat or miss" headline and stopping. Around 78% of companies beat every quarter. The headline almost never contains information.

Two: comparing the result against the previous quarter rather than against expectations. The price doesn't compete against the company's history, it competes against what was already priced in.

Three: looking at the closing price on an event published after the close. The reaction happened afterwards, and the call was still to come.

Four: interpreting a move without knowing how much that asset normally moves. A 6% drop is enormous in a company that moves 2% and routine in one that moves 9%.

Five: reinterpreting the reading after knowing the outcome. It's the quietest of the five and the subject of the next section.

Anatomy of a case that hit

The two cases that follow are always told in the same six-step order, because that order is what allows you to learn from them rather than just read them.

The opening contrast — the most striking figure, first, before any explanation. Before the event — what the market expected and what detail sat outside the headline. The reading — the scenario, optimistic or pessimistic, and why it read that way before anything was published. What happened — the facts, as a sequence. The verdict — whether the scenario hit or missed, stated plainly. What can be learned — which part of this chapter explains what happened.

The opening contrast. Almost every analyst covering Zscaler had it on "buy", and the company had not missed an earnings expectation once in its recent record. The stock fell 31.5%.

Zscaler · 26 May 2026Pessimistic reading · right

Reports26 May 16:00 ET+0.30%26 May 16:02 ET−32.50%27 May 13:37 ET−31.52%27 May 16:00 ET

Starting price $184.60Window 26 May 16:00 → 27 May 16:00 ET

It rose 0.3% for two minutes. That was all it rose.

Before the event. Zscaler reported on 26 May 2026, after the close. The stock arrived off a very strong run and traded at $184.60. The expected headline was good: solid growth, a clean record and price targets above the market price. What the headline left out was how much of all that the market had already paid for during the run-up.

The reading. Pessimistic, at the highest conviction on the scale. Not because a bad result was expected, since a good one was, but because the prior run left little room for a good result to surprise anyone. It is the mechanism this chapter calls selling the news.

What happened. At 16:02 New York time, two minutes after publication, the stock was up 0.3%. That was all it rose. From there it fell through the rest of the extended session and all of the following one, hitting −32.5% at 13:37 on the 27th. It closed the evaluation window at −31.5%.

The verdict. Right. The pessimistic scenario played out, and with room to spare: at no point did the price rise more than 2% against the reading.

What it teaches. That a good result and a good reaction are different things, and that the difference sits in what the price already carried. Getting the number right was not required here: reading what expectation it competed against was enough.

Anatomy of a case that missed

A course teaching only cases that hit would be hiding half the information, and it would be exactly what the rest of the industry does.

This second case is told with the same respect and the same detail as the first. The scenario had reasonable logic before the event, and it still didn't play out. That doesn't invalidate the reading method: it invalidates the idea that a method exists which is always right, which is an idea nobody serious defends.

The opening contrast. Two days after the previous case, the same reading, on the same kind of setup and with even higher conviction. Dell rose 32.8%.

Dell · 28 May 2026Pessimistic reading · wrong

Reports28 May 16:00 ET−0.98%28 May 16:00 ET+39.34%29 May 04:12 ET+32.76%29 May 16:00 ET

Starting price $317.05Window 28 May 16:00 → 29 May 16:00 ET

The most it ever fell was 0.98%, and that was the opening instant.

Before the event. Dell reported on 28 May 2026, also after the close, trading at $317.05. It arrived on a 67% run over thirty days, well beyond the price targets analysts were carrying. On paper, the same picture as Zscaler: a run that seemed to have got ahead of the good news.

The reading. Pessimistic, at the far end of the scale. The argument was the one from two days earlier and it was reasonable: when a stock rises 67% in a month and leaves its coverage's targets behind, the reaction to a good result tends to be muted.

What happened. The opposite. The price barely dipped on publication, 0.98% at its worst, and by 04:12 the next morning, with the regular market still shut, it was up 39.3%. It closed the window at +32.8%, having run against the reading by as much as 41.9%.

The verdict. Wrong, with nothing to soften it. This was not a reading that fell short: it was a reading of the opposite sign.

What it teaches. That the same reasoning applied to two similar setups can produce opposite results in the same week. Dell's reading was not worse than Zscaler's; it was the same one. What differed was what the result carried inside, and that was not available before it was published.

That pair is this chapter's best defence against its own content. Reading an event well improves the odds. It does not turn them into certainties, and anyone selling you otherwise is selling you something else.

What to do when the scenario fails

This section is the one most missing from any material on this subject, because almost everyone writes about what to do when you're right.

First: separate process from outcome

A reading can be well made and turn out badly. It can be badly made and turn out well. Confusing the two is the fastest way to learn the wrong lesson.

A good process with a bad outcome is what happens when you gathered the available information, interpreted it reasonably, and something nobody had appeared. There's nothing in the method to correct.

A bad process with a good outcome is more dangerous, because it reinforces a bad habit. Buying without looking at anything and having it work out teaches precisely the opposite of what's worth learning.

This distinction is so central it has its own chapter later: the risk chapter opens on exactly this point, because being right and winning aren't the same thing.

Second: having written the invalidation point beforehand

The practical part, and the one that prevents self-deception.

If before the event you wrote down what would have to happen for your reading to be wrong, afterwards you only need to check whether it happened. If you didn't write it, what almost always happens is the reading gets reinterpreted after the fact so it fits what occurred — and then you're never wrong and you never learn anything.

That habit — writing the scenario and its invalidation point beforehand — is what the logbook in the method chapter is about.

Third: look at the sample, not the case

One miss says nothing about a method. Nor two, nor five. What says something is the proportion across a sufficiently large sample, with its confidence interval alongside, which is the range the real number reasonably sits in and narrows as cases pile up.

How large "sufficiently large" is, and why ten trades say absolutely nothing, is the content of drawdowns, streaks, and sample size, the risk chapter's final session. It's also why Volatly publishes its full archive with its misses included and its sample in view: an accuracy figure without the failures inside and without the number of cases alongside isn't data, it's an assertion.

What to remember

• Post-earnings drift has been documented since 1968 and confirmed in 41 of 48 quarters, but it's an academic phenomenon, not a certainty about any specific company's next event.
• The correct reading order starts with guidance, not with the "beat or miss" headline.
• A process can be well made and turn out badly: separating process from outcome is what allows you to learn anything.
• Writing the invalidation point before the event is the only thing preventing you from reinterpreting it afterwards.

Milestone reached

That closes Chapter 4, the heart of this course. You can read an event before it happens and explain the scenario in words: why it concentrates so much movement, what gets published and when, what expectation the company is really competing against, what the options market is saying, and how a full case is told start to finish.

You've just read two entire events, with a calculator and time on your hands. That same work, for every company you care about, every quarter, is what doesn't fit into a life with a job.

The chapters ahead go deeper into the pieces this one has been using: how to read a company from the inside, how to read a chart, and how much to risk on each decision.

Related: the dividend, start to finish · drawdowns, streaks, and sample size · what expectation a company is really competing against