Direct answer
Scalping timeframes do not have one single, universal rulebook. In practice, the “rules” usually mean a small set of repeatable conditions that determine (1) what time window you use to make decisions, (2) how you measure time inside that window, and (3) when you exit. A useful way to verify your own rule set is to express it as a clear checklist with assumptions, then test it on historical data under consistent cost and execution assumptions.
A key idea: the shorter the timeframe you trade, the more your results depend on mechanics you can measure—execution timing, transaction costs, and how your observed candles or ticks relate to fills—rather than on any single chart pattern.
Mechanism: define scalping timeframe “rules” you can test
A testable rule set for scalping timeframes is best written as separate parts. Each part should state inputs, decisions, and measurable stop conditions.
1) Decision timeframe and holding-time window
Start by defining the timeframe you use for signals (for example, the timeframe of the chart bars that your rule refers to) and the holding-time window your rules permit.
- Decision timeframe: the granularity you observe to decide whether to act.
- Holding window: the maximum duration you allow the position to remain open.
If you do not specify holding time, “scalping” becomes too vague to test. If you specify it, you can measure whether an entry followed by an exit always respects your window.
2) Timing logic inside the window
Time-based rules should explain exactly what happens next. Examples of rule types you can define without claiming profitability include:
- Candle-close decision rule: you only evaluate conditions at the close of each bar on your decision timeframe.
- Fixed-duration exit rule: you exit after a set duration (for instance, after N seconds or N bars).
- Bar-count rules: you enter on bar k and exit no later than bar k+M.
These are “mechanics” because they describe timing behavior, not market prediction.
3) Entry and exit conditions as measurable filters
Instead of using an indicator or pattern as a standalone “signal,” write entry and exit as conditions that can be checked numerically. For instance:
- A rule can require that a specific condition remains true for a defined number of consecutive observations.
- A rule can include a time-based cancellation: if the market does not reach your required state within your holding window, you exit.
To keep rules testable, define the condition using observable quantities you can record in backtests.
4) Cost-aware constraints (part of the rules)
Scalping timeframes typically mean more frequent trading and tighter time windows, so costs matter. A rule set should include assumptions about at least:
- Transaction costs: spread, commissions, and any recurring fees.
- Execution slippage: the difference between the observed price at decision time and the fill price.
Make these assumptions explicit. Without them, two tests can disagree simply because their cost models differ.
Evidence or example: a rule set expressed as a checklist
Here is a sample rule set structure written in a testable way. It is not a guarantee of results; it is meant to show what “rules of scalping timeframes” can look like when expressed clearly.
Example rule checklist (with explicit assumptions)
Assumptions (state these in your test):
- You use a decision timeframe of X minutes.
- You evaluate entry only at bar close.
- Your holding window is no more than M bars.
- You include a fixed cost model with spread + commission and a slippage assumption of S.
Entry rule (measurable):
- On each bar close, if condition A is true and condition B is true, open a position.
Exit rule (measurable timing):
- Exit at the first bar close when exit condition C is true or exit no later than the end of bar k+M.
Failure control rule:
- If execution cannot occur within a defined time after the decision (for example, due to a delayed fill), mark the trade as failed and do not assume the ideal fill.
Why this is “evidence-like”
The “evidence” is in the structure: every decision is tied to a specific time reference (bar close), a specific limit (M bars), and specific cost/execution assumptions (spread/commission/slippage). Anyone can verify whether your rules are consistently applied.
If your backtest results change materially when you adjust cost or slippage assumptions, that is an important finding about the strategy’s sensitivity—even if you do not know the future.
Limitations and risks: what can make scalping timeframe rules break
A rules-based approach still has failure modes. At least three are common when time windows are short.
1) Execution mismatch
Backtests often assume you can enter or exit at the observed price at a bar close. In reality, fills may occur later, at different prices, or not at all. When the holding window is short, even small delays can dominate outcomes.
2) Spread and cost sensitivity
Costs are typically a larger fraction of the potential move in short timeframes. If your rule set does not model costs realistically, it can appear to work during testing but fail when costs increase.
3) Market regime changes
Historical relationships do not ensure future behavior. Conditions such as volatility spikes, liquidity changes, or news-driven moves can make the same timing rules behave differently.
4) Data and definition risk
Your rules depend on definitions: what counts as a bar close, which timestamps are used, and how missing data is handled. Two platforms can produce different candles or timestamps, leading to different rule evaluations.
Verification and next questions
To independently verify your understanding of scalping timeframe rules, you can check whether your checklist is unambiguous:
- Can you explain the holding window in units of time or bars?
- Do your entry and exit rules reference a specific moment (for example, bar close)?
- Do you explicitly include costs and an execution assumption?
- Do you define what happens when execution fails or is delayed?
If you can answer “yes” to all four, you have a ruleset you can test and audit.
As a next question, consider: how would your rule set behave if you changed the decision timeframe (without changing other rules) or if your slippage assumption doubles? Large changes suggest your rules are sensitive to the mechanics of execution and costs.