Definition: what “inputs” means in Multi Day Holding
Multi Day Holding is a forex trading approach defined mainly by holding positions across multiple days, rather than intraday timing. “Inputs” are the specific data choices and parameters you plug into the rules that determine when a position is opened, how long it is held, and when it is closed. In this informational explanation, we focus on stable mechanics: the kinds of inputs that an implementation must specify, and which parts are variable.
Mechanism: the core inputs and their dependencies
A self-contained Multi Day Holding model typically needs four input groups.
1) Time-horizon inputs
These specify the intended duration across days. Common examples of time-horizon inputs are:
- Holding window length (e.g., number of days the plan allows)
- Weekend handling (how the plan treats periods when liquidity and spreads can differ)
- Evaluation timing (whether rules are checked using end-of-day values, timestamps, or another convention)
Dependency: The practical meaning of “multiple days” depends on the market’s daily schedule and on how your data labels “day” (timezone, candle close time, and broker server time).
2) Entry and exit rule inputs
These define decision points. Inputs here include:
- Entry condition variables (what observable facts you use at the decision time)
- Exit condition variables (time-based exit, rule-based exit, or both)
- Order type assumptions (how entry and exit are actually executed: market vs limit, and whether stop orders are used)
Dependency: Even if the entry/exit logic is fixed, real fills depend on execution quality, spreads, and slippage.
3) Price measurement inputs
Implementations must define how price is measured and compared.
- Price source (bid, ask, mid, or another convention)
- Comparison method (thresholds compared to close values vs intraday extremes)
- Data granularity (daily bars vs higher-resolution data)
Dependency: Changing these measurement choices can materially change outcomes, even when the “strategy idea” is the same.
4) Cost and sizing inputs
To evaluate or implement the approach, you need assumptions that translate price moves into net results.
- Trading costs model (commission and spread treatment)
- Slippage assumption (if not using realistic execution data)
- Position sizing rule (how size relates to account size or to stop distance, if stops are part of the plan)
Dependency: Without consistent cost and fill assumptions, comparisons between tests and live trading can be misleading.
Evidence or example: a concrete checklist of inputs
Because there are many variants, it’s hard to name “the” universal set of inputs. Instead, use this checklist to make a Multi Day Holding implementation independently explainable:
Assume a rule set with:
- A holding window of N days (your chosen parameter)
- An exit rule that triggers either when an observed condition is met or when the window ends
- A price convention (for example, using a specific price field consistently)
- A cost model that specifies how spreads and fees affect profit calculation
- An execution rule for how fills are determined (or an assumption used during backtesting)
Verification step: if you can’t state each item above as a parameter or assumption, then your “inputs” are not fully specified, and two people may implement different versions while using the same label.
Limitations and risks: what can break the inputs
At least one material limitation should be explicit.
- Execution mismatch: A backtest can assume fills at ideal prices while live trading can experience slippage, spread widening, or slower order execution.
- Data and timing mismatch: If the data source’s day boundaries or timestamps differ from the broker’s, “holding across days” may not mean the same thing.
- Cost sensitivity: Small changes in spread/fee assumptions can outweigh the underlying price movement over multiple days.
- Rule mismatch across timeframes: If your decision variable is computed from daily values but your execution uses intraday fills, the real path can violate the assumptions.
These are failure modes of the implementation, not proof that the concept is invalid. They show why outcomes vary with market conditions and operational details.
Verification and next question
To independently verify a claim about “which inputs Multi Day Holding uses,” ask for the exact list of: (1) time-horizon parameters, (2) entry/exit rule variables, (3) price measurement conventions, and (4) cost/execution assumptions. If a description omits any one group, it is incomplete.