Multiple Timeframe Analysis for Journaling

Most traders who use multiple timeframe analysis (MTF) record only their entry timeframe in their journal — leaving out the higher-timeframe context that drove the decision. That gap turns alignment errors into noise. This guide is for active traders who already use MTF setups and want to build a journal structure that captures all three layers, scores alignment on every trade, and produces data-driven rules about when to trade and when to pass.

Step 1: Choose Your Timeframe Stack

Before you can journal MTF trades, you need a fixed stack. The industry-standard recommendation from Elder, Raschke, and Carter methodologies is a 4:1 to 6:1 ratio between each layer. Three common stacks:

Style	Trend (HTF)	Setup (MID)	Entry (LTF)
Day trader	60-min	15-min	5-min
Scalper	15-min	5-min	1-min
Swing trader	Weekly	Daily	4-hour

The most popular retail combination is the 5-15-60 stack based on broker education content and trading community surveys. Avoid mixing non-proportional timeframes such as 3-min and 60-min — the gap creates blind spots where the mid-level context is missing entirely.

Pick one stack and commit to it for at least 50 trades. Switching stacks mid-sample makes your alignment data incomparable across periods.

Step 2: Define Your Three Journal Fields

Every trade entry needs exactly three MTF fields, recorded at trade open — not after the trade closes:

1. HTF Bias — the higher timeframe directional label: Bullish, Bearish, or Neutral
2. MID Pattern — the setup-timeframe pattern name: bull flag, VWAP rejection, inside bar, etc.
3. LTF Trigger — the entry-timeframe event that caused execution: break of HOD, 5-min candle close above resistance, etc.

Recording these at open is critical. Post-trade reconstruction introduces confirmation bias — traders unconsciously align their memory of the higher timeframe with the outcome of the trade. If you lost, the HTF “seemed mixed.” If you won, it “was clearly bullish.” Lock in the read before you know the result.

Alexander Elder formalized this three-layer approach in his Triple Screen system, first published in Trading for a Living (1993), and it remains the canonical reference for structured MTF trading.

Step 3: Score Alignment on Every Trade

After filling in the three fields, assign an alignment score:

• Full — all three timeframes agree with your trade direction
• Partial — two of three agree; the third is neutral or unclear
• Against — your entry opposes the HTF trend

This single label turns qualitative analysis into a filterable dataset. A trader who shorts a 5-min pattern while the 60-min chart shows an uptrend should tag that trade Against — not “bad execution.” The distinction matters because bad execution is a process problem you fix by slowing down. Trading against the HTF is a setup-selection problem you fix with a rule.

Step 4: Tag Entries for Machine-Sortable Review

Narrative journal notes are useful for context, but they are not searchable. Use a structured tag string in a dedicated field:

HTF:Bear / MID:BearFlag@VWAP / LTF:FlagBreak / Alignment:Full

This format lets you filter all “Alignment:Full” trades in seconds, regardless of which journal tool you use. It also makes pattern recognition faster — searching “MID:BearFlag” across 200 trades reveals your win rate on bear flags specifically, separated from other setups.

Here is a concrete example. On May 1, 2026, SPY showed a clear 60-min downtrend — lower highs, price below the 20 EMA. A 15-min bear flag formed near a VWAP rejection at $527. On the 5-min chart, price broke the flag low at $526.40. A short entry at $526.40, stop at $527.20, risked $40 (0.8R on a $5,000 risk budget). The trade hit target at $524.50 for a $95 gain, or 2.4R. Journal entry: HTF:Bear / MID:BearFlag@VWAP / LTF:FlagBreak / Alignment:Full / Result:+2.4R.

Compare that to a trade earlier the same day — a 5-min short pattern taken while the 60-min chart was still in an uptrend. Tag: Alignment:Against / Result:-1R. The trade was stopped out. Without the alignment tag, both trades look like independent losses and wins. With the tag, they are data points in a pattern.

Step 5: Run a Monthly Alignment Breakdown

At the end of each month, filter your journal by alignment category and calculate three metrics for each group:

• Win rate (% of trades profitable)
• Average R-multiple (average gain/loss relative to initial risk)
• Average hold time (minutes or days)

After 40 trades using the example above, the data showed: Full alignment — 62% win rate, 1.8R average; Against alignment — 38% win rate, 0.9R average. That 24-point win rate gap and 2x R-multiple gap is not a coincidence — it is a repeatable structural pattern that most traders discover in their own data after 30 to 50 trades per category.

Use this breakdown to set concrete rules. Common outputs: halve position size on Partial alignment trades, skip Against alignment trades entirely, or require a specific minimum HTF signal strength before sizing up.

See how to find trading patterns in your journal and converting journal data to trading rules for the broader review framework.

Pro Tips

• Lock in HTF bias before the market opens. Mark the daily HTF direction in your pre-market notes so you are not re-reading the chart after you are already in a position.
• Treat “Neutral” as a separate bias, not a default. A sideways HTF is a genuine condition — it does not confirm any direction. Tag it Neutral and score the alignment accordingly rather than leaving the field blank.
• Track alignment separately for long and short trades. Many traders have a directional bias (better at longs than shorts, or better in downtrends than uptrends). Splitting the alignment breakdown by direction surfaces this asymmetry faster.
• The 4:1 ratio matters most at the top. The gap between HTF and MID is more important than the gap between MID and LTF. A 60-min trend versus a 5-min setup creates a 12:1 ratio that misses too much context — always have a middle layer.
• Review your Against trades first. Sorting by Alignment:Against and reading only those entries each month is the fastest way to identify recurring setup-selection errors.

Common Mistakes to Avoid

1. Reconstructing HTF bias after the trade closes. Post-trade memory is unreliable — traders fit the narrative to the outcome. Record all three layers before entering the position; otherwise the alignment data is corrupted.

2. Using inconsistent timeframe stacks across different setups. If you journal some trades on the 5-15-60 stack and others on the 1-5-15 stack without labeling which is which, your alignment categories are not comparable. Pick one stack per instrument or strategy and apply it consistently.

3. Logging alignment as Full when the HTF is actually Neutral. Neutral is not bullish or bearish — it does not confirm alignment. Treating a sideways 60-min chart as “not opposed” inflates your Full confluence sample and hides poor setup selection.

4. Waiting until 100+ trades to review alignment data. Waiting too long delays actionable insights. Run your first alignment breakdown after 30 trades per category — the sample is small but directionally useful, and you can refine rules as the sample grows.

5. Skipping the MID layer entirely. Some traders journal only the HTF and LTF. Without the setup-timeframe pattern, you cannot distinguish between different entry types within the same HTF condition — a flag breakout and a reversal at support both look like “HTF:Bull / LTF:BO” without the middle label.

How JournalPlus Helps

JournalPlus supports trade tagging with custom tag fields that accept structured strings like HTF:Bear / MID:BearFlag / Alignment:Full, making every entry filterable without manual spreadsheet work. The tag filtering in the analytics dashboard lets you isolate any alignment category and view its win rate, average R-multiple, and P&L contribution in seconds. For traders building out their trade plan template, the notes field can be templated to enforce the three-layer recording habit on every trade. If you trade across multiple styles — both day trading and swing trading — multi-account support keeps each timeframe stack’s data separate while still allowing cross-account pattern reviews.