The calendar knows the dates, not the surprises

What a release actually delivers

Almost nothing on a macro calendar moves a price on its own. Prices already carry a forecast of the number. What arrives on release day is the difference between the number and that forecast, and a date that delivers no difference passes like any other Tuesday.

That single sentence reorganises the whole calendar, so it is worth slowing down on it.

Before a scheduled release, the number is not unknown. Economists publish forecasts, those forecasts get collected into a consensus, and anybody with a position has already taken a view. The price on the screen is not waiting for the data. It is already a weighted guess at the data, held by everyone who has money on the outcome.

When the release lands, that guess is replaced by a fact. The portion of the fact that matched the guess was already in the price and changes nothing. Only the residual — the surprise — is new. An event's capacity to move a price is the size of that residual, not the size of the number.

Which produces the result that confuses people most about calendars: a release described as high-impact can pass almost unnoticed, while a remark nobody had scheduled reprices a great deal in minutes. Neither is irrational. The first was expected and the second was not, and expectation is the whole difference.

This article groups the fixtures by what each one actually reprices, explains why being on the calendar shrinks a release's information content, and covers the case that gets read backwards most often — the first estimate that moves more than the revision correcting it. The same idea applied to a central bank meeting specifically is its own article, and how the tiles on our Macro page fit together is the macro pillar.

Four things an event can reprice, and one that reprices nothing

A calendar sorts by date because that is the only field it can sort by. It is not the useful ordering. The useful question about any entry is which quantity does this change the market's estimate of, because the answer decides which channel it travels down to reach an Indian share price.

There are four such quantities, plus a category of fixture that carries no information at all and still moves prices — which is why it needs its own row.

Read the last row twice, because it breaks the article's own rule and does so legitimately. An index rebalance contains no news whatsoever: the rule is published, the additions and deletions are announced, and every passive fund tracking the index has to trade regardless of what it thinks. Flow can move a price without information doing any work. That is a different mechanism from everything else on the calendar and it should not be read with the same lens.

The flows article covers who is on each side of those trades. The rest of this piece is about the four groups that do carry information.

The policy path: the decision, the minutes, and the sentence nobody scheduled

The policy group is where the calendar's ordering misleads most reliably, because its highest-profile entry is usually its least informative one.

A rate decision is a single number that markets have been pricing continuously for weeks. By the morning of the meeting, most of the plausible range is already inside the curve. The statement, the vote split and the guidance carry what is left, and that division of labour is the subject of the decision-versus-surprise article — which also works through the arithmetic showing why a change in the expected path moves a bond yield far more than a single month at a different rate. India's own framework and meeting cadence are in the RBI article; why a decision taken in Washington reaches Mumbai at all is the Fed article.

Two entries in this group are worth separating out, because they behave unlike the decision they descend from.

Minutes are a second information event from a meeting that already happened. The decision is weeks old and fully priced; what the minutes add is the distribution behind it — how close the vote was, which arguments were made, what conditions were attached. A unanimous decision and a narrowly carried one look identical on the day and describe different starting points for the next one. That content had no consensus forecast attached to it, because there is nothing to forecast.

And then the entries that are not on the calendar at all. An unscheduled speech, an interview answer, a wire headline quoting an official. Here is the mechanism, and it is the spine of this article:

Being on the calendar is what shrinks a release's information content. A scheduled release attracts forecasters, and forecasts get priced. Positions are set against the expected range before the number lands, so the residual left over is small by construction — not because the topic is unimportant, but because the anticipation did the work in advance. An unscheduled remark has no survey, no consensus and no pre-positioning. Nothing about it was priced, so the entire content is residual.

That is a mechanical claim, not an empirical one: it follows from what a consensus does, and needs no market behaviour to be true. Its practical consequence is uncomfortable and worth stating plainly. The events most capable of repricing something are, by construction, the ones you cannot put in a diary. A calendar is still useful — it tells you when the room will be crowded and when a position faces a known binary — but it cannot be a list of what will matter, and no calendar anywhere can be.

The inflation path: why the core reading usually carries more

An inflation release rarely reaches a share price directly. It reaches the policy path, and the policy path reaches the share price. That indirection explains most of what looks odd about how these prints are read.

Start with what the reading is. A consumer price index tracks the cost of a fixed basket of goods and services; the headline number is the change in the cost of the whole basket. Inflation itself is its own article, so take the definition as read and go to the part that matters for a calendar: the basket contains two kinds of thing, and only one of them tells you anything about the future of the basket.

Food and fuel move on their own supply. A bad monsoon, a shipping disruption, an oil producers' decision — the resulting price change says a great deal about vegetables or diesel and very little about whether demand across the economy is running hot. It is also partly visible before the release: the fuel component follows a crude price anyone can watch on a screen, which is one reason crude matters to India ahead of any inflation print at all.

The rest of the basket moves on demand and on wages, which are persistent. Strip out food and fuel and what remains is the measure most policymakers watch: the core reading. The term arrives last on purpose — core is not a more important number, it is the same basket with the noisiest and most externally-driven parts removed.

So the mechanism runs: core is the part that carries into future readings, the policy path responds to what carries, and the policy path is what discounts an equity cash flow. That last leg is the yields article.

Here is the specific mistake this produces, and it is common enough to name. A headline print that surprises can be an inflation event with almost no policy content. If the whole miss sits in vegetables after a poor harvest, the number that moved is one the central bank cannot influence with an interest rate and knows will reverse when the harvest normalises. Reading the headline surprise as a policy surprise is reading a supply shock as a demand signal. The reverse case is worse and quieter: a headline that lands exactly on consensus while its composition shifts — food falling, core firming — is a release with a surprise in it that the headline number hides completely.

The honest limit on all of this: the split is a convention, not a law. Which items count as core, and whether a given food or energy move is genuinely temporary, are judgements that reasonable people contest, and a supply shock held long enough starts showing up in wages and in the rest of the basket anyway. Core is the better signal of persistence, not a clean separation of it.

The growth path, and the two signs it arrives with

Growth releases are the group where the transmission genuinely runs both ways at once, and where saying so is more useful than picking a side.

A share price is a claim on future earnings, discounted. A stronger-than-expected growth reading is news about the numerator — earnings — and, in the same instant, news about the policy path that sits in the denominator. One release changes the estimate of both halves of the same fraction, and the two changes work against each other. Which half moves more is not determined by the mechanism, and this article does not claim to know. What the mechanism does tell you is that a growth print is capable of being read either way without anybody being confused, and that a market reaction which looks perverse may simply be the other half winning. The discounting side of that fraction is the time-value article.

The three fixtures in this group are not interchangeable, and the differences are entirely about timing.

• Purchasing-manager surveys are the fastest. Purchasing managers are asked whether activity is better or worse than last month, and the answers are combined into a diffusion index — a reading built so that a level of 50 separates a majority reporting improvement from a majority reporting deterioration. That construction is worth understanding before reading one: it measures the breadth of a direction, not the size of it. A reading can rise while output falls, if more firms saw a smaller improvement.
• Industrial production is a measured quantity rather than a survey, arrives later, and covers only part of an economy that is mostly services.
• GDP is the most complete and the slowest. It describes a quarter that ended weeks or months ago, and it is published as an early estimate that is revised as fuller source data arrives.

That last point deserves its own section, because the standard reading of it is backwards.

Why the first estimate can move more than the revision that corrects it

A statistical agency publishes an early estimate of a quarter built on partial source data, then revises it as fuller data comes in. Two things are true at once, and holding both is the whole point:

The revision is closer to the truth. The first estimate carried more news.

That is not a contradiction and it is not a criticism of anyone. It falls out of what information means. A release's capacity to reprice something depends on how much of the underlying quantity was still unknown at the moment it landed — and by the time a revision arrives, most of that quantity has already been described by other releases.

So the calendar entry that says revised GDP is describing a number that is better and news that is staler. A market that repriced on the first estimate and barely reacted to a sizeable revision was not being inconsistent — it had already learned about that quarter from three months of subsequent data, and the correction told it something it had mostly worked out.

The decision-relevant version, which is the part worth carrying away: when scanning a calendar, the entries capable of carrying information are the ones describing a period nobody has measured yet. Entries that correct a period already covered by later data are, on this reasoning, the low-information end of the list even when their headline looks dramatic. That is a judgement about how to read a calendar, offered as a reading rather than a rule — a revision large enough to change the character of a period is a genuine exception, and revisions to a series everyone uses as an input are a second one.

The same asymmetry is why a first print of any series — a new index, a first estimate, a preliminary reading — sits differently on a calendar from a confirmation of something already published. One is a measurement. The other is mostly a formality that occasionally is not.

India's own fixtures, and why the Budget is a different shape

Everything above applies to Indian releases as written. Two domestic fixtures are structurally different enough to need their own treatment.

The Union Budget is not one number with a consensus. Every other entry on this calendar reprices a single macro quantity against a single expectation. A budget is a bundle of many decisions landing simultaneously — tax rates, duties, spending allocations, borrowing plans, sector-specific measures — and there is no survey that produces one consensus figure to be surprised against. The expectation is diffuse, which changes the shape of the day rather than its size: the surprise is distributed across sectors rather than concentrated in one variable, and dispersion between sectors can be the larger part of what happens even when the index-level move is unremarkable.

One component of a budget does behave like a conventional macro release: the government's borrowing figure. That is a single number, closely forecast, and it lands in the bond market — where a change in expected supply of government paper reaches yields, and yields reach every discounted cash flow behind them.

Index rebalances are the mechanical case, and India sees them from both sides. A global index provider's review changes which Indian names sit in portfolios that track it; a domestic index reshuffle does the same inside the country. Neither carries information about a company's business. Both create trades that must happen at a known time, which is exactly the flow-not-information distinction from the table above — and it is why our Macro page's events card keeps index reviews alongside macro releases while leaving company results out.

Two further points specific to reading India, both of which are other articles' to own in full. First, a large share of what reprices an Indian share is not on an Indian calendar at all: the dollar, the US rate path and global risk appetite arrive overnight, which is the subject of how global indices lead the Indian open. Second, a domestic event lands on top of whatever the global backdrop is doing that morning, and separating the two afterwards is guesswork — what a risk-off day looks like describes the pattern to check against. The currency leg of both is the rupee article.

Where this framing is thinner than it looks

Four honest limits, because a framework that only ever confirms itself is not teaching you anything.

The consensus is an estimate of an estimate. "The market expected X" is a survey of forecasters, or a level backed out of instruments that carry premia of their own. It is not a measurement of what anyone believed, and two careful readers can disagree about what was priced. Everything in the surprise framing rests on that input.

Positioning can matter more than the number. A small surprise landing on a crowded position and a large surprise landing on a flat one are not comparable, and positioning is not observable in advance. This is the commonest reason a release is read correctly and the reaction still looks wrong.

Attribution on the day is not measurement. A release lands in a market simultaneously absorbing flows, earnings, the overnight session and everything else. Saying an index moved because of a print is an attribution, and a same-session move is consistent with several explanations at once.

A first-round reaction is not the economic effect. The repricing happens in seconds; the thing being repriced — borrowing costs, corporate behaviour, actual output — moves over quarters and can turn out smaller or larger than the price move implied. The two are related and are not the same object.

Reading this on the Macro page

FNOTrader's Macro page carries an Upcoming Macro Events card as its last block, below the cross-asset correlation heatmap. How it is built is worth stating plainly, partly because one of its choices is a deliberate omission that goes to the heart of this article.

What it shows. It reads the same shared events feed as the standalone Events page, filtered to the next 30 days in IST from today, sorted by date and then time, and capped at the first eight rows. Only two categories survive the filter: macro releases and index reviews. Company results and corporate actions are excluded by design — this is a market-wide calendar, not an earnings diary. When nothing qualifies, the card says so rather than showing an empty box, and a link takes you to the full calendar where the per-company entries live. The central-bank card higher up the page points here for meeting dates.

Behind it, the feed is a passthrough to our analytics service, which serves only rows marked enabled from a shared events table, ordered by date, then time with all-day entries last, then severity. The route is cached for five minutes.

Now the omission, which is the honest part. A row in that feed carries a date, a time, a title, a category, a severity label, an exchange, an optional description and an alert lead time; the card renders a subset of them. Nowhere in it is there a consensus forecast, a prior reading or a released actual. There is no number on that card to be surprised against.

Which is exactly the quantity this article says does the moving, so the limitation should be stated rather than glossed: the card can tell you that a day is crowded. It cannot tell you whether a release will contain a surprise. Nor could any card, because a surprise is by construction the part nobody forecast. What a calendar is good for is knowing which mornings carry a known binary and which do not — and that is a real use, just a smaller one than the highlighting implies.

A note on the severity label, since it is the field most likely to be over-read. It is a property of the row, not a measurement of the surprise the release will contain — it says this is the kind of fixture capable of mattering, which is a statement about the category and not about the day. Call the failure mode the marked-calendar illusion: treating a highlighted date as a high-information date. The highlight can only ever describe potential, because the residual is unknowable until the number is out.

Two more page conventions that trip people up. The dot on an events row encodes severity; the dot on a market tile encodes impact on Indian equities, which is why a falling dollar shows green and a rising USD/JPY shows green too. Those are two different colour schemes on one page, and the impact convention (including the wrinkle that an unweighted price tile falls through to the raw direction of its own number) belongs to the pillar. And the events list is fetched once when the page loads: the tiles refresh on a 60-second poll, the calendar below them does not, so a reload is what updates it.

Finally, the part that follows directly from this article's argument: no event carries any weight in the page's composite score. The score is built from the market tiles plus foreign institutional cash flow, and a calendar entry never enters it. That is the right construction. A scheduled date is not a measurement of anything; an event reaches the score only after it has moved a market instrument — a yield, the dollar, a volatility index — which is the same route by which it reaches a portfolio.

The score itself is score = 100 × Σ(w_ic_i) ÷ Σ(w_i), over 20 weighted tile inputs summing to 1.33 — the dollar index at 0.20, the US 10-year yield at 0.15, Brent at 0.12, and the yen cross and the US VIX at 0.10 each being the five largest — plus foreign flow folded in at 0.12 and saturating at ±₹5,000 crore, which is not in the tile table at all. That is 21 contributions, and a divisor of 1.45 on a day when every feed reports and the flow number is in. On such a day the flow input accounts for at most 100 × 0.12 ÷ 1.45, or about 8.3 points of the headline score, and the dollar for at most 100 × 0.20 ÷ 1.45, about 13.8.

Two properties of that average matter for anyone reading a score on an event day. When a feed fails, its weight leaves the numerator and the denominator — so 1.45 is the all-present maximum rather than a constant, and every input that did report takes a correspondingly larger share of the score. Two days carrying the same number can rest on different sets of inputs, and those 8.3 and 13.8-point ceilings are the crowded-day case, not a hard cap. And each input is clamped to ±1 before it is weighted, so a single instrument moving three times as far as its saturation point counts the same as one that just reached it. The composite measures agreement across channels, not severity within one — which is precisely why a single violent move has to be handled outside the average.

That is what the regime labels do. Boundaries sit at ±20, with a stress override at a score of −35 or lower, or a one-day US VIX rise of 20% or more, or a one-day USD/JPY fall of 1.2% or more. The stress test runs first, so either of those two one-day moves labels the day Stress even when the composite is positive. Every number in the last three paragraphs — each weight, the ±20 boundaries, the three stress triggers — is FNOTrader's design judgement — a considered view about what matters to Indian equities, not a measured constant and not a fitted coefficient. A different reasonable weighting produces a different score from identical inputs, and none of it forecasts anything.

Common questions

Continue reading

More in Macro & Markets · App: Options Analytics · Definitions: glossary · Free tools: calculators · All: every article