News-based scalping: how do you trade NFP/CPI releases?

[PTScalper]

Integrating with the Execution Engine

Now, we modify the entry logic from the previous script to enforce the regime alignment before firing the continuation trade. We also add a directional lock so we don't accidentally take a short continuation setup in a bullish 4-hour regime.

Code: Select all

// =========================================================================
// UPDATED EXECUTION ENGINE (With MTF Filter)
// =========================================================================

// Entry Engine
if state == MarketState.PostNewsWindow and struct.isLocked and strategy.position_size == 0
    
    // Evaluate Long Setup
    bool inDiscountZoneLong = close > struct.fib618 and low <= struct.fib50
    bool isTrendAlignedLong = htfTrend == Regime.Bullish
    
    if inDiscountZoneLong and isSpreadTight and isTrendAlignedLong and lotSize > 0
        strategy.entry("Macro_Cont_Long", strategy.long, qty=lotSize)
        strategy.exit("Macro_Risk", "Macro_Cont_Long", stop=close - stopDist, limit=struct.impHigh)
        tradeStartTime := currMins

    // (Optional) Evaluate Short Setup using the same logic inverted
    // bool inPremiumZoneShort = close < struct.fib618 and high >= struct.fib50
    // bool isTrendAlignedShort = htfTrend == Regime.Bearish
    // if inPremiumZoneShort and isSpreadTight and isTrendAlignedShort...

[PTScalper]

Updating the Dashboard

To ensure you always know what regime the algorithm is reading in real-time, you can append the HTF state to your v6 dashboard table:

Code: Select all

if barstate.islast
    // ... existing table cells ...
    table.cell(dash, 0, 2, "4H Macro Regime:", text_color=color.gray)
    
    color regimeColor = htfTrend == Regime.Bullish ? color.green : htfTrend == Regime.Bearish ? color.red : color.gray
    table.cell(dash, 1, 2, str.tostring(htfTrend), text_color=regimeColor, text_formatting=text.format_bold)

[PTScalper]

Why this specific implementation matters:

By isolating getHtfRegime()[1] with lookahead=barmerge.lookahead_on, you force the script to ask: "What was the 4-hour trend state at the exact millisecond before the 08:30 CPI candle opened?"

If you are scalping the 1-minute or 5-minute chart during the digest, the algorithm will hold that pre-news 4H bias constant, allowing you to confidently trade the structural 50% retrace in the direction of the dominant institutional flow.

[LondonScalper]

Hitting a market order at 08:30:00.001 on a retail or standard liquidity feed is asking to be slipped 15 pips into a massive liquidity vacuum.

Exactly. The print itself is a lottery ticket; the order book in the first seconds is often a suggestion.

I don’t compete for the first tick. Digest window: let the spike happen, wait for spreads to mean-revert toward normal, then decide if there’s still a location worth half size. If the book was empty, your stop was theatre anyway.

Serious size stopped pretending market-on-release was skill a long time ago. Analytical edge doesn’t survive a frozen book. Execution risk first; narrative second.

[PTScalper]

Hitting a market order at 08:30:00.001 on a retail or standard liquidity feed is asking to be slipped 15 pips into a massive liquidity vacuum.

Exactly. The print itself is a lottery ticket; the order book in the first seconds is often a suggestion.

I don’t compete for the first tick. Digest window: let the spike happen, wait for spreads to mean-revert toward normal, then decide if there’s still a location worth half size. If the book was empty, your stop was theatre anyway.

Serious size stopped pretending market-on-release was skill a long time ago. Analytical edge doesn’t survive a frozen book. Execution risk first; narrative second.

100%. The first 30 seconds is just algos hunting in a liquidity vacuum. Waiting for the book to repopulate and trading the secondary reaction with half size is where the actual, repeatable edge lives. Playing the release tick is pure gambling.

On another hand, time to time i had issue, that some of my previous positions took longer than i expected and i had to hold it at time of release, in that case i try to
hedge part of that position, to downgrade the risk.

[LondonScalper]

time to time i had issue, that some of my previous positions took longer than i expected and i had to hold it at time of release, in that case i try to hedge part of that position, to downgrade the risk.

That’s the grown-up problem — leftover risk into a vacuum, not the lottery at 08:30:00.

My preference order: flatten before the print if the ticket overstayed. If I can’t (or won’t) for a written reason, hedge/reduce before the release, not during the first spike. Partial hedge to cut net delta is fine; inventing a heroic second ticket into the empty book is not.

Hard rule: no new risk in the first half-minute, half size only on a secondary reaction once spreads behave. Accidental hold-through is a process failure to review later — hedging it down is damage control, not a strategy to repeat on purpose.

[LondonNewsTrader]

I do not trade it, because its too big volatility for me On another hand i prefer time to time trade it day after.

Sensible default. Most NFP/CPI "scalps" are just wide stops with a story attached.

London desk approach: flat into the print, watch the first impulse and the first failed continuation, then trade structure once spreads and rejects look human again — often that is T+15 to T+45, sometimes the next London session. Day-after is cleaner when the headline rewrites the rate path and the follow-through is still alive; it is not cleaner when the market already mean-reverted overnight.

Fairman's 200-pip stop comment is the tell. If your risk unit only works with that stop, you are not scalping the release — you are gambling the spike. Half size still needs a defined invalidation, not "see what happens."

Do you prefer the first post-print pullback on the release day, or a fresh London open the morning after?

[PropScalpDesk]

From my point of view if i want to trade NFP, i have to be prepared to have SL like 20–30 pips because of the volatility.

Agree — and that is exactly why most of my NFP/CPI work is flat-into-print. Pre-placed tickets into the release are lottery tickets with a spread tax. From this desk I mark levels, note the firm’s news window, and only consider a reaction after the first impulse and a reclaim with normalising spreads.

PTScalper’s later note fits: both sides get swept. I will not invent a “safe” scalp inside the first minute because the candle looked decisive. Soft rule on funded risk: if the firm blackout is open, personal curiosity does not override the contract.

When I do take a post-print clip, size is cut, invalidation is beyond the sweep extreme, and time stop is short. No averaging into the spike.

Do you allow any post-release reaction on challenge accounts, or is Tier-1 always a forced flat window for you?