Macro event move reaction playbook
Set a predefined response ladder for first, opposite, and stale macro moves before the release, so a single trade idea does not become several unmanaged decisions
Direct answer
Macro moves after release can fail your strategy in three different ways: price moves too fast, the wrong direction for a moment, or movement stalls after a headline. Define all three before entry, not after the first filled order
Start with the "three branches" map, not one scenario
Before placing your order, define what you will do in each branch:
Most plans only define the first branch, then get rewritten at T+30 seconds.
Write a one-line branch map per branch with:
If you cannot write all three branches in one screen, the entry should be delayed or reduced.
- price moves in the expected direction and keeps volume
- price moves opposite to your thesis during the first liquidity wave
- price stays flat for several minutes despite headline data
- expected delta change by contract
- acceptable spread widening
- size reduction rule after branch activation
- stop or hedge path for each outcome
Build branch actions as percentage cuts, not opinion calls
Ambiguous words like "take profit" and "exit if weak" cause execution lag. Convert them into explicit percentage cuts before the event.
Example:
These are not recommendations for "maybe". They are commands. Commands should be repeatable across symbols and sessions without emotional interpretation.
- If the first directional move is confirmed but spread doubles, cut to 70% and remove deep liquidity-risky add-ons
- If opposite move appears immediately, remove 50% immediately and re-evaluate with reduced delta
- If price drifts and options fail to tighten, reduce 25% within the same minute and hold only the original thesis core
Separate reaction speed from entry thesis
The thesis is your reason to trade. Reaction speed is operational execution.
In event windows, they diverge:
So, define reaction timers:
Do not let window 2 overwrite window 1. Many losses come from waiting for certainty before reducing risk.
- You can be right on direction and still lose on execution if the reaction speed requirement is impossible
- You can be wrong on direction but keep the account safe if speed control is pre-approved
- You can be uncertain and still keep optionality if spread and liquidity caps are active
- reaction window 1: immediate print response (for protective adjustment)
- reaction window 2: confirm directional continuation
- reaction window 3: stale regime decision before normal liquidity returns
Close the loop with a post-event checkpoint
A macro release does not end when the initial spike ends. The account often gets worse in the next minutes, when spread normalizes slower than expected.
Add a short checkpoint routine:
Repeat the same checklist after every macro event. If the post-event process is weaker than the pre-event plan, the next iteration is where you improve, not the strategy idea.
- lock a snapshot of quote, spread, and remaining liquidity at release
- confirm assignment or settlement constraints for short legs
- verify whether your branch action executed at the intended size
- document why you held, cut, or closed in each branch
Common questions
Why does a thesis pass but the trade fail?
Because directional edge and execution edge are separate. The first one can work while the second fails from spread, depth, or cutoff timing.
How often should I rewrite these branches?
At least once per major macro cycle, and whenever liquidity conditions or broker cutoff rules change.
Is there ever a reason to keep full size if the initial branch fails?
Only if the branch plan explicitly keeps full size, includes explicit liquidity capacity, and still preserves the loss budget. That is rare.
Can I automate this in an order rule?
You can automate some alerts and prechecks, but branch decisions usually need human override because fills, spread shifts, and venue behavior are dynamic.