In this article
After this article, you can
- Derive bounds from incomplete lower-timeframe bars.
- Mark missing data rather than inventing final extremes.
Terms at hand: Trading Journal · Backtesting · Stop loss · Take profit (TP) · Long position (bullish position) · Major Pairs
Multi-timeframe analysis compares different aggregations of the same market. To use it correctly, align data sources and interval boundaries, then distinguish a candle’s opening timestamp from the time its final values become available. A shorter candle can rise inside a falling hour without contradiction or a guaranteed future reversal.
What changes when the same data is aggregated?
Different timeframes aggregate the same underlying price observations. Higher intervals provide broader context, while lower intervals reveal detail. A top-down trading rule is one framework, not a law that a higher timeframe controls prices or guarantees continuation.
A top-down plan can assign context to a longer chart and an entry condition to a shorter one. That is a chosen framework, not a rule that the higher timeframe controls price. Define how you identify structure and when each pivot is known; background: market structure through higher highs and higher lows.
Top-down analysis — the three steps
Step 1. The higher timeframe — establish the trend
The following D1/H4/H1 sequence is an example of assigning roles, not a universal three-chart requirement. Any daily-close filter uses the most recently completed and supplied D1 value. A still-open candle is a different input.
- Price holds above the SMA200 on D1 — the dominant bias is bullish, and on the lower charts you look for long positions only.
- Price holds below the SMA200 on D1 — the bias is bearish, so only short positions are of interest.
- If price moves across the selected average, define how your rule handles that state. It is not by itself proof that the market has no trend or that one action is universally best.
Step 2. The middle timeframe — mark the entry zone
In this example, the middle chart supplies a predefined price area. Define its selection and invalidation rule before evaluating the next move; an EMA or retracement does not establish a probability of a reversal.
- Support and resistance levels visible on H4 — places where price has already stalled at least twice.
- A selected H4 EMA50 can be a reference level. Its relation to current price does not guarantee support or resistance.
- A Fibonacci retracement between 38.2 and 61.8 percent of the last distinct move.
- Specify the zone width in price units and its derivation. A 30–50-pip width would be a chosen hypothetical parameter, not a universal Forex range.
Step 3. The lower timeframe — the entry signal
The lower chart can supply a condition, but order execution is separate. Specify completed candles, actual entry side, volume, stop and exit conditions.
- If the rule requires price to enter the H4 zone first, record that event and its timestamp. Entering earlier is a different rule, rather than a formula-proven loss of all advantage.
- Look for a candlestick pattern aligned with the daily trend: a pin bar or an engulfing candle.
- Open the position after the candle that forms the pattern has closed, not while it is still forming.
- Choose the stop and buffer in advance and calculate their monetary effect from the actual entry. An ordinary stop may fill beyond its requested level.
Which combinations suit which trading style?
A four-to-six ratio between intervals is a convention, not a required spacing. Choose intervals for the actual holding period and data availability, then test the complete rule. Different aggregation intervals can reveal different details without an objectively correct universal ratio.
Three M15 bars give bounds, not final H1 extremes
The hour has ended but the export still has a gap. Record what can be established instead of treating three known bars as complete.
Scroll sideways to see the full diagram
Fictional completed M15 periods, one source, common scale and aligned H1 boundaries. Preserved OHLC:100/103/99/102,105/108/104/107,107/110/106/109. The second quarter is missing, not a documented session break. A possible missing bar102/115/98/105 fits surrounding opens and closes; it is not asserted to have occurred. The document MQL5 — MqlRates defines separate time, open, high, low and close fields in history records.
The first O and final C are preserved. Full-hour H cannot be below110 or L above99, but either can extend further. Record these as partial-data bounds and mark the gap. Do not substitute a convenient completion into a detector requiring the full range.
What does a complete set of three timeframes look like?
The trade table assumes one lot means 100,000 EUR and a USD account, with one pip = 0.0001 USD per EUR. At the stated actual fills, 40 pips means USD 400 gross loss and 120 pips USD 1,200 gross gain; reward/risk = 3. Costs are omitted. A requested ordinary stop is not a guaranteed fill, so USD 400 is planned gross risk rather than a maximum loss. Position sizing also needs the account-currency conversion, costs and provider volume increment; a 1% budget is a chosen rule, not a universal requirement.
What goes wrong most often?
- Using final data before it was available. After 09:30 in the synthetic hour, only two M15 bars have closed. The in-progress H1 has O = 1.1020, current H = 1.1030, current L = 1.0990 and last price 1.0995. Its final C = 1.1010 is still unknown.
- Confusing the candle label with availability. After 09:45, the latest completed M15 rises 10 pips, while the incomplete hour is 15 pips below its opening. For a completed-H1 rule, the latest eligible context remains 08:00–09:00. “After” includes receiving and finalising the provider’s data, not zero transmission delay.
- Assuming a fixed number of charts is optimal. Two views suffice for the aggregation check here. Add a third or fourth only if it answers a specified question; chart count alone does not establish accuracy or paralysis.
- Mixing candle boundaries or price sources. Match provider, Bid/Ask/Last convention, session and timezone. A display-timezone change does not rebuild bars or change Pine’s calculation timezone automatically.
- Replacing selected observations with all observations. Synthetic M15 closes 100, 100, 100, 100, 100, 110, 100, 110 give H1 closes 100 and 110. SMA2(H1) = 105; SMA8(M15) = 102.5. Raise the six other closes by 20 while preserving indices 4 and 8: H1 SMA stays 105 but M15 SMA becomes 117.5. Equal time coverage does not mean equal weights.
Different timeframes aggregate the same prices and can describe different horizons without guaranteeing a direction.
What to do tomorrow
- Record availability. For every used bar, keep start, end and provider availability time, source and price type. A bar beginning at 09:00 is not its final 09:00–10:00 result at 09:00.
- Check missing intervals. If a quarter-hour is missing, retain known first O, final C and observed bounds, but do not present the remaining three bars as complete hourly OHLC.
- Specify each chart’s role. A context, zone and trigger sequence is one possible framework. Document how conflicting or missing observations affect it before comparing results.
- Keep the full decision record. Record prices, times, input availability, fills and costs. A month of notes can document examples but does not by itself establish which timeframe combination will work in future.
If you want to take the subject further, the technical analysis section on ForexMechanics works through the same top-down sequence in long form, with worked examples on the major pairs.
Check your understanding
One short exercise
About 2 min · you can try again
Three preserved M15 bars have largest H110 and smallest L99; one quarter is missing. What follows for H1?
- Definitely H110 and L99.
- Nothing is known, even with first O and final C preserved.
- H≥110 and L≤99; exact values need missing data.
Check the answer and explanation
H≥110 and L≤99; exact values need missing data.
Missing data can extend the range but cannot remove observed extremes.
Frequently asked
Why is MTF important?
Different aggregations can reveal different details and availability times. In the synthetic example, the last two M15 candles rise while H1 closes 10 pips below its opening. That is arithmetic, not a contradiction or evidence of the next direction. MTF helps check inputs and context when a rule assigns those tasks; it does not automatically remove half of signals or guarantee better performance.
Which timeframe combinations are most common?
D1/H4/H1, H4/H1/M15 and H1/M15/M5 are possible role assignments, not a demonstrated popularity ranking or universal optimum. Their adjacent ratios are not all 4–6: M15/M5 is 3. Before aggregating, verify actual provider/session boundaries; one D1 does not necessarily contain six full H4 bars from another feed.
Always 3 timeframes — or fewer/more?
No fixed chart count is required. Two charts suffice for the M15-to-H1 aggregation check. Add another view for a defined task, not an assumed accuracy gain. The same observations shown in several charts do not become independent evidence; evaluate a complete method with costs before comparing variants.
Can I use same indicators on different tf?
Yes, but the inputs differ. SMA2 of the model’s H1 closes is 105 while SMA8 of its M15 closes is 102.5 despite the same two-hour coverage. Recovering the hourly mean requires selecting the fourth and eighth M15 closes with weight one half each, not giving all eight equal weight. MACD or another indicator can be used on several charts; disagreement is possible, not inevitable, and it does not provide independent data.
Sources & bibliography
-
Investopedia Multiple Time Frame Analysis · An introduction to analyzing markets across multiple timeframes. www.investopedia.com ↗
-
Brian Shannon Technical Analysis Using Multiple Timeframes · A book explaining technical analysis across multiple timeframes. www.amazon.com ↗
-
CFA Institute CFA Institute research portal · The CFA Institute research portal provides access to investment research. www.cfainstitute.org ↗
-
MetaQuotes MQL5 Reference — MqlRates · Distinct period-start time and OHLC fields. The aggregation tables use hypothetical aligned Bid intervals from one source. www.mql5.com ↗
-
TradingView Pine Script documentation — Other timeframes and data · Higher-timeframe confirmation and future-data leakage, plus differences between input feeds. No universal chart-count or performance rule follows. www.tradingview.com ↗
-
TradingView Pine Script documentation — Time · Opening and closing timestamps and chart-display versus calculation timezones. A display change does not itself rebuild session bars. www.tradingview.com ↗
