Macro event thesis revalidation checklist

Most setups fail because the trader treats release validation as the same thing as follow-through validation.

Do this first:

Pre-release confirmation is about preparation. Revalidation confirmation is about survival.

In macro events, survival is often about a data sequence changing under your feet. Your revalidation list should be short enough to be executed in real time.

• Pre-release checkpoint: confirm schedule, liquidity baseline, and planned position size
• Revalidation checkpoint: define the exact facts that can invalidate the thesis in the next 5 to 15 minutes

Too many rules reduce execution quality. Choose only the conditions that flip the risk structure.

Use exactly these four categories:

Document each category with one number:

If any one condition is met, your trade is not “wrong”; it is **invalidated** and the process should switch branch.

• thesis contradiction from the actual print
• spread and depth failure
• stop-window mismatch
• financing or assignment surprise
• what print level means directional assumption is broken
• what spread width means the position is too expensive to hold
• what clock means your adjustment window is no longer valid
• what account state means settlement/assignment risk moved outside control

When the first invalidation fires, you should already know the exact next move.

Set your revalidation branches:

Example:

These are execution maps, not narrative plans. A plan becomes usable only when the branch is tied to a specific size and rule.

• immediate scale-down branch
• branch for partial close and wait
• branch for full disarm and re-entry later
• if print confirms thesis but spread doubles, move to reduced-size continuation
• if print breaks the thesis and spread stays normal, close or rotate quickly to defined hedge
• if spread also spikes in the invalidation window, close exposure and stand down

Risk logic written without your account reality will not work.

Before the event:

During revalidation, if any account capacity limit is reached, the invalidation logic is no longer hypothetical. You must execute the conservative branch immediately.

• include the minimum buying power needed for forced adjustments
• include the available credit line for overnight funding friction
• include the hard cap for short-side assignment path if it can occur
• include the broker rule that can reject or delay late adjustments

Revalidation is not complete when the first 5 minutes pass.

At the end of the event reaction period, record:

This log is what turns one-off event trading into repeatable strategy learning. Without this, every event feels like a new start. With it, every event becomes a cleaner version of the previous one.

• whether each invalidation category was hit
• whether the branch action executed as planned
• which branch was fastest to trigger and why
• what to keep for the next iteration