Multi-Timeframe Analysis and Risk–Reward
A framework for separating horizons, calculating reward relative to risk and avoiding false precision.
Why short-, medium- and long-term scenarios require different data, models and invalidation logic. This article explains the reasoning framework used by Trading.Red and the limitations a reader should keep in view.
Three horizons, three questions
Short-term analysis asks whether intraday momentum and liquidity support a near-term move. Medium-term analysis asks whether multi-session structure is building acceptance around meaningful support or resistance. Long-term analysis asks whether daily and weekly trend, regime and major averages agree. Copying one score into all three horizons hides these differences.
Trading.Red calculates the horizons independently. This allows the short-term model to be bearish while the long-term model remains bullish. That disagreement is useful information: it may describe a pullback inside a larger advance rather than a broken system.
Risk–reward is a relationship, not a promise
For a bullish scenario, potential reward is the distance from the observed entry reference to the target, while defined risk is the distance from that reference to the stop or invalidation area. The scenario ratio divides potential reward by defined risk. A bearish scenario mirrors the distance calculation so the sign does not reverse the meaning.
The ratio says nothing about the probability of reaching either level. A large theoretical reward can be paired with a very low likelihood, poor liquidity or a stop that gaps. Model score and scenario ratio must remain separate fields.
Position risk belongs to the user
A platform cannot infer suitable position size without knowing a person's finances, objectives, existing concentration, time horizon and ability to absorb loss. Trading.Red does not collect enough information to make that suitability decision and does not place trades.
Users who choose to trade should independently decide the maximum capital they are prepared to lose, consider fees and slippage, and understand that a stop reference does not guarantee execution at that value. FINRA notes that stop orders become market orders and can execute materially away from the trigger during volatile conditions.
Why deterministic levels matter
Language models are useful for translating computed facts into readable explanations, but they should not invent prices. Trading.Red's level engines use market data and fixed formulas; narrative generation is restricted to describing those outputs and their limitations.
Before a scenario is displayed, its levels are checked for directional consistency. If an ordering rule fails, the safest outcome is to recalculate from deterministic inputs or return an unavailable state—not silently rearrange labels to create an attractive chart.
Questions to ask before acting
Is the data timestamp current enough for the selected horizon? Is the final candle complete? Are the target and stop derived from the same scenario? Does the broader market agree? Is a scheduled event likely to change volatility? Can the loss exceed the displayed distance because of a gap or execution delay? If any answer is unclear, more apparent precision does not solve the uncertainty.
Worked example: reward is not probability
- Observed entry reference: 100
- Bullish target: 112
- Invalidation reference: 96
Reading: The hypothetical reward is 12 and risk is 4, producing 1:3. The ratio describes distances only; it does not mean the target is three times more likely than the invalidation level.
Key takeaway
A technical label is a compressed description of market data, not knowledge of the future. Use the label to organize questions: which timeframe produced it, what confirmed it, which observation would invalidate it, and what data might be missing?
Further reading
These independent investor-education resources provide additional context about market and execution risk.