Direct answer
Swing Timeframes does not have one universally fixed list of inputs, because “inputs” depend on how a specific method defines its rules. In general, any Swing Timeframes approach uses (1) time-horizon settings that decide the intended holding window and (2) data fields from which conditions are computed, such as price values. If indicators are included, they add derived calculations as additional inputs. A reader can independently verify this by writing down the method’s explicit rule set: every decision point should reference specific data fields and parameters.
Mechanism or definition
A clear way to think about Swing Timeframes is as a rules-based way to relate a decision to a time horizon. “Swing” refers to looking for movement over a multi-day to multi-week span (exact length varies by method), rather than intraday. That time horizon is an input in practice because it constrains what data points are considered relevant.
Most Swing Timeframes implementations use three input layers:
-
Time-horizon parameters: These include the intended holding period (for example, the number of bars/days the method expects a trade to remain open) and the “decision cadence” (how often conditions are evaluated). Even if no explicit numbers are stated, the chart timeframe acts like an input because it changes which candles or bars exist.
-
Market data fields: Common fields are open, high, low, close, and sometimes volume. If the method uses only price levels, then price fields are the only inputs. If it uses derived levels, those levels become additional inputs.
-
Derived features (optional): If the method mentions indicators, it usually converts market data into derived values (for example, averages, momentum measures, or band levels). In that case, the indicator’s calculation settings (such as lookback length) are additional parameters, and the indicator output values are additional inputs.
Important modeling assumption: when you interpret a “Swing Timeframes” rule set, treat inputs as exactly what the rules reference. If the rule says “use the most recent close” then “last close” is the input. If the rule says “use a 20-period average,” then both the “20” and the underlying price series used by that average are inputs.
Evidence or example
Here is an example of how to list inputs without assuming live prices.
Assume a hypothetical rule set that evaluates conditions once per bar and is designed for swing holding.
- Time-horizon input: hold for a fixed number of bars (parameter) on the chart timeframe chosen by the user (implicit parameter).
- Decision inputs: at each evaluation, read the bar’s close (market data field) and maybe high/low (additional fields).
- Optional derived input: if the rule uses a moving average, then the moving average lookback length is a parameter, and the moving average value is a derived feature input.
To independently verify, you can do a paper check: for each decision, point to one referenced variable (such as “close of bar N” or “indicator output at bar N”). If a rule references something not derivable from the declared inputs—such as “market will turn next week”—then it is not an explicit input; it is an unsupported claim.
Limitations and risks
A key limitation is that “inputs” are not the same as “guarantees.” Even with the same inputs and parameters, outcomes can vary because:
- Market conditions change: Historical relationships between price and derived features may not persist.
- Costs and execution matter: Spreads, commissions, slippage, and order handling change realized results compared with simplified calculations.
- Timeframe dependence: Changing the chart timeframe changes which bars exist and therefore changes the inputs feeding the rules.
- Failure modes: A common failure mode is rules that fit one regime (for example, trending behavior) and underperform in another (for example, range-bound behavior), even though the inputs and parameters remain the same.
Also note a verification constraint: without real-time data, you can only validate that the rule set is internally consistent (inputs are well-defined and computable), not that it will work in the future.
Verification or next question
To verify which inputs Swing Timeframes uses for a particular method, rewrite its rule set in a checklist form:
- List every parameter (time horizon, lookbacks, evaluation frequency). - List every data field referenced (open/high/low/close, volume).