Trading Macro Events With Agents: Fed Days, CPI, NFP
FOMC, CPI and NFP move markets on a known schedule. Three agent patterns that respect that volatility instead of gambling on it, with worked rules.
Most volatility ambushes you. Macro releases are the exception: CPI prints, Fed decisions and the jobs report land at published times, on published dates, every month. That predictability is what makes fed announcement trading such a trap for automation. Your agent knows exactly when the storm hits, yet most bots sail straight into it with the same size and the same stops as on any quiet Tuesday.
This piece covers what actually happens to markets around FOMC, CPI and NFP, then three agent patterns that treat scheduled volatility as a design input rather than a surprise.
Fed announcement trading: what actually happens at 2pm
Take a Fed decision day. The statement drops at 2:00pm Eastern, the press conference starts at 2:30. In the minutes before release, market makers pull quotes and books thin out; spreads on liquid index products can widen to multiples of their normal width. The first move after the statement is often violent and often wrong: an initial spike in one direction, then a full reversal once the press conference reframes the message. Traders have a name for the pattern because it recurs so reliably.
CPI (8:30am ET) and nonfarm payrolls (8:30am ET, typically the first Friday of the month) behave similarly with one difference: they hit before the US equity open, so the reaction plays out first in futures, FX and crypto, and equities gap at 9:30.
Three mechanical facts matter for anyone running automations:
- Liquidity evaporates around the release. A market order that normally costs you 0.02% of slippage can cost ten times that in the release window.
- The first move frequently reverses. Machine-read headlines trigger the initial burst; the considered interpretation arrives minutes later and sometimes points the other way.
- Stops become tripwires. A stop-loss sitting 1.5% away, sensible all month, is well inside the range of a normal CPI whipsaw on a volatile asset. You can be stopped out and watch price close the day exactly where it started.
None of this requires forecasting anything. It is the terrain, and agents can be built for terrain.
Pattern 1: stand aside, automatically
The simplest defensible pattern is also the most underused: don't trade the window at all, and make abstention automatic rather than a thing you must remember at 8:25 on a Friday.
A concrete implementation: pause the agent 30 minutes before CPI and resume 60 minutes after the print. Thirty minutes ahead clears you before liquidity thins; sixty minutes after lets the initial whipsaw and the first reversal resolve. For FOMC, extend the resume time past the press conference, since the 2:30 Q&A regularly undoes the 2:00 move.
Variants scale with how much risk the event poses to your specific book:
| Exposure | Stand-aside rule |
|---|---|
| Unleveraged swing positions | Pause new entries only; existing positions hold with untouched stops |
| Leveraged or short-dated positions | Reduce or flatten before the release; re-enter on your normal signals after |
| Tight-stop intraday agents | Full pause, entries and exits, through the window |
This is where the plumbing matters. On Obside, macro events are available as triggers an automation can subscribe to, so "pause my momentum agent 30 minutes before CPI, resume 60 minutes after" is one condition on the agent, stated in plain language and restated back to you before it runs. No calendar-watching, no 8:25am phone alarm, no forgetting during a vacation week.
The cost of standing aside is honest and small: you occasionally miss a clean trend that starts on the print. The benefit is that you never donate a leveraged position to a spread that widened for ninety seconds.
Pattern 2: react to the print, not to your guess
The second pattern trades the event, but only after the number is public. The logic is conditional on data that exists, never on a forecast: compare the released figure to the consensus estimate, and act on the gap with strict limits.
A worked example for a jobs report: "If NFP misses consensus by more than 100,000 jobs in either direction, alert me with the print, the revision figures and my current exposure. If the miss exceeds 150,000, cut my index-tracking position by a third; otherwise do nothing." Every branch references a known number against a known benchmark. Nothing in the rule requires being right about the economy.
What separates a reaction rule from a gamble:
- It waits. No positions opened before the release in anticipation. Entering ahead of the number, however strong your conviction, is guessing with a countdown attached.
- It reads the actual-versus-expected gap, not the raw figure. Markets price the consensus in advance; an "objectively good" number below expectations routinely trades like bad news.
- It uses limit orders or delays. Reacting in the first seconds means paying the worst spreads of the day. A rule that waits even five minutes forgoes very little and pays far less.
- It caps its own size. Same principle as everywhere in agent guardrails: no single scheduled event should be able to move your account more than a pre-chosen fraction.
Reaction rules pair naturally with condition stacking: print gap AND a confirming price move AND a position-size ceiling is a textbook case for multi-condition automations, and the AND-logic is exactly what filters out acting on a number the market immediately shrugs off.
Pattern 3: sizing that respects the calendar
The third pattern never pauses and never reacts. It simply gets smaller when the calendar says risk is higher than usual.
Implementation is arithmetic. Suppose your standard risk per trade is 1% of the account with a stop 2% below entry. On an event day you halve the risk budget to 0.5%: either half-size positions with the usual stop, or full-size with double the stop distance, chosen by whether you'd rather be shaken out less often or lose less when you are. An agent applies the adjustment automatically from the events calendar; a human applies it until the third busy week, then forgets.
A reasonable schedule looks like: normal sizing on quiet days, half risk on CPI and NFP days for affected assets, half risk from the evening before FOMC through the press conference. If you want sizing to respond to measured volatility itself rather than the calendar, that generalization — ATR-based sizing and regime filters — is the subject of volatility-aware agents.
Sizing rules are the least dramatic pattern and arguably the best risk-per-effort trade in this whole article. They cannot be faked out, since they don't interpret the release at all. Their only cost is smaller wins on days a trend runs from the print.
Why "guess the number" is not a strategy, and other failure modes
The seductive version of macro trading is predicting the print or the Fed's decision and positioning beforehand. Set aside whether you can outforecast thousands of professionals whose entire job this is. Even a correct forecast fails two ways: the market may have priced it already (right number, no move), and the reaction may invert on a detail you didn't model. A cooler headline CPI with a hot core figure can rally for four minutes and close deeply red. You predicted the number, and the trade still lost.
The failure modes that hit agents specifically:
The headline fake-out. Algorithms read the headline figure first; humans read the composition minutes later. First-wave moves reverse often enough that any rule acting inside the first minute needs a size small enough to be wrong comfortably.
Revisions. Jobs numbers are notorious for material revisions in later months. The "shock miss" your agent traded may effectively cease to exist in the next release. Reaction rules should treat the print as a market event to respond to, never as a durable fact about the world.
Spread-widened stops. During the release window your stop executes at the prevailing quote, which may be far worse than the trigger price. This is why pattern 1 pulls tight-stop agents entirely rather than trusting stops through the window.
Correlated exposure. One CPI print moves your index position, your tech names and your crypto simultaneously. Sizing per position while ignoring the shared macro trigger understates event-day risk substantially. Event-aware rules should look at total exposure, not individual trades.
Unscheduled news, meanwhile, is a different problem with a different toolkit; that pipeline is covered in news-based trading with AI.
Where to go from here
Start defensively and earn complexity. Put pattern 1 on your existing automations this week: a pause window around CPI and FOMC costs you almost nothing and removes the ugliest tail outcomes. Add pattern 3's reduced event-day sizing once you've seen a release window play out in your own positions. Save pattern 2 for last, run it alert-only first, and let it place orders only after its logic has proven itself on paper through several releases.
The macro calendar is one of the few things in markets you get to know in advance. An agent that respects it is doing something you already believe in but won't reliably do by hand at 8:25 every first Friday. If you'd rather state the rule once than remember it monthly, Obside lets you attach macro-event conditions to any automation in a sentence, test it in paper mode, and keep your own limits on everything it does.
Educational content only. This is not investment advice. Trading involves risk, including possible loss of capital.
FAQ
If you trade with leverage, tight stops or short timeframes, standing aside through the release window is usually the highest-value rule available: spreads widen, liquidity thins and whipsaws trip stops that were sensible all month. Long-term unleveraged positions generally don't need to flatten; pausing new entries and leaving existing stops alone is a reasonable middle ground. The key is making the pause automatic instead of relying on memory.