Page 1 of 1
NZDUSD M1 structure: higher-timeframe bias workflow
Posted: Sun Oct 04, 2026 11:32 pm
by LondonScalper
NZDUSD is a pair I trade occasionally, mostly during the overlap of the Wellington afternoon and the London morning. It's thin enough that M1 structure on its own misleads me constantly, so I lean heavily on a higher-timeframe bias first.
My workflow, which takes about five minutes at 06:45 London:
H4 chart: is price above or below the last clear swing high or low? That gives the broad direction. If there's no clear swing within the last three days, the bias is neutral and I trade smaller.
H1 chart: where are the last two H1 swing points? These are the levels I'll respect on M1. A long on M1 just under an H1 swing high is a trade I don't take.
M15: what did the Asian session do? If NZDUSD trended in Asia in the direction of the H4 bias, I look for continuation in London. If it went against the bias, I wait for London to show its hand.
Only then do I go to M1, and only to time entries. I'm looking for a higher low in an uptrend bias, or a lower high in a downtrend bias, ideally after a pullback to an H1 level.
The pair's thin liquidity means stops on M1 structure alone get taken out by noise. I place mine beyond the M15 swing, which means bigger stops and smaller size.
I take maybe four NZDUSD trades a week. Without the higher-timeframe step, it was eight trades a week, and noticeably worse.
Re: NZDUSD M1 structure: higher-timeframe bias workflow
Posted: Mon Oct 05, 2026 8:49 am
by PTScalper
LondonScalper wrote: Sun Oct 04, 2026 11:32 pm
NZDUSD is a pair I trade occasionally, mostly during the overlap of the Wellington afternoon and the London morning. It's thin enough that M1 structure on its own misleads me constantly, so I lean heavily on a higher-timeframe bias first.
My workflow, which takes about five minutes at 06:45 London:
H4 chart: is price above or below the last clear swing high or low? That gives the broad direction. If there's no clear swing within the last three days, the bias is neutral and I trade smaller.
H1 chart: where are the last two H1 swing points? These are the levels I'll respect on M1. A long on M1 just under an H1 swing high is a trade I don't take.
M15: what did the Asian session do? If NZDUSD trended in Asia in the direction of the H4 bias, I look for continuation in London. If it went against the bias, I wait for London to show its hand.
Only then do I go to M1, and only to time entries. I'm looking for a higher low in an uptrend bias, or a lower high in a downtrend bias, ideally after a pullback to an H1 level.
The pair's thin liquidity means stops on M1 structure alone get taken out by noise. I place mine beyond the M15 swing, which means bigger stops and smaller size.
I take maybe four NZDUSD trades a week. Without the higher-timeframe step, it was eight trades a week, and noticeably worse.
Hi LondonScalper,
Great breakdown. I completely agree with your emphasis on establishing a higher-timeframe bias first—skipping that step is how most traders get chopped to pieces in the lower timeframes.
However, our execution workflows diverge significantly at the final step. Personally, I don’t touch the M1 charts at all. From my perspective, the 1-minute chart is entirely too full of noise, especially on a thinner pair like NZDUSD.
Here is why I stripped
M1 out of my workflow completely and stick strictly to raw price action on the Daily and 15-minute charts:
The Illusion of Precision
M1 charts often give a false sense of control. What looks like a "lower high" or a "structural break" on a 1-minute chart is frequently just random order book turbulence, algorithmic ping-pong, or momentary spread widening. On a pair like NZDUSD during the London open, liquidity gaps can create M1 candlesticks that look like major reversals but are actually just routine tick fluctuations.
Re: NZDUSD M1 structure: higher-timeframe bias workflow
Posted: Mon Oct 05, 2026 8:49 am
by PTScalper
If Your Stop is on M15, Your Entry Should Be Too
You mentioned a great point: you place your stops beyond the M15 swing because M1 structure gets taken out by noise. I found that if my risk parameters and invalidation levels are based on the M15 chart, zooming into the 1-minute chart to optimize the entry by a pip or two isn't worth the psychological friction. Watching M1 often tempts you to micromanage the trade, close early, or get shaken out by a 60-second fake-out before the true M15 move plays out.
Waiting for the 15-Minute Close
Instead of dropping to M1 for a trigger, I execute directly on the M15. I use the Daily chart for my overarching market structure and bias, and then wait for price to reach those key zones.
Re: NZDUSD M1 structure: higher-timeframe bias workflow
Posted: Mon Oct 05, 2026 8:49 am
by PTScalper
Once there, I let the M15 chart do the work. I want to see a clean liquidity sweep or definitive candlestick structure (like a strong rejection or engulfing candle) close on the 15-minute timeframe. A 15-minute close confirms that institutional volume has actually accepted or rejected a level, rather than just poking through it for 60 seconds to hunt stops.
You noted that adding your higher-timeframe filter cut your trades from eight to four per week, but noticeably improved your results. I experienced the exact same leap in quality when I deleted the M1 timeframe entirely. It forces you to be patient, wait for the noise to settle, and trade the actual structure rather than the static.
Re: NZDUSD M1 structure: higher-timeframe bias workflow
Posted: Wed Oct 14, 2026 1:00 pm
by FXS Prop Desk
For readers comparing the two workflows, the difference is mostly about cost per trade. On NZDUSD the typical spread is wider than on EURUSD, so on M1 the stop is usually only a few multiples of the spread, while on M15 it's many multiples.
A quick way to check which fits: calculate spread divided by stop distance for your last 50 trades. If it's regularly above 10%, the lower timeframe is costing more than the precision is worth. Below 5%, M1 entries can make sense as long as the bias is set higher up, as LondonScalper describes.