Intraday Stock Trading Playbook: From Premarket Plan to Review
Build an intraday stock trading playbook covering candidate selection, opening conditions, entries, sizing, daily loss limits, execution, and review. A useful strategy is a written, falsifiable operating procedure — not a prediction engine. The purpose of this page is to help a reader define what is being tested, what can invalidate it, how implementation changes the result, and what evidence should be reviewed before risking capital.
Key Takeaways
- Premarket context is preparation, not prediction: Use overnight index moves, scheduled macro events, issuer filings, earnings releases, premarket volume, and large price gaps to describe the day's environment.
- Candidate quality should be rule-based: A watchlist becomes testable only when eligibility is explicit: minimum price and dollar volume, maximum spread, catalyst type, relative volume, gap size, sector, and exclusions.
- The opening range needs a definition: Five-minute, fifteen-minute, and thirty-minute opening ranges are different variables.
- Entry needs a trigger and a no-trade condition: A complete rule states what must happen to enter and what prevents entry.
- Size from adverse price, not confidence: Define the invalidation level, estimate realistic slippage beyond it, calculate dollars at risk per share, and size the position from a predetermined risk budget.
- Time-of-day is a strategy variable: Liquidity, volatility, volume, and participant mix change across the session.
What This Page Is — and Is Not
The page is intentionally built around decisions that can be observed and audited. For an intraday trading plan, that means the reader should be able to trace a decision from the information available at the time through the order, risk limit, exit, and later review. The page answers the intent to build a repeatable intraday trading process without turning a historical pattern into a recommendation.
Three boundaries keep the page distinct from Swoopr's existing foundations. First, premarket context is preparation, not prediction — treated as part of the method rather than re-teaching its underlying indicator or market definition. Second, candidate quality should be rule-based — connected to the canonical risk/execution lessons instead of being presented as a shortcut around them. Third, the opening range needs a definition — tested as an explicit condition so winning examples cannot redefine the strategy after the fact.
The expected output is a research-ready playbook: a reader can write the eligible universe, timing, trigger, order assumption, risk logic, event handling, and exit in advance. A reader who cannot do that has learned an interesting market observation, but has not yet defined a strategy that another person could reproduce.
Build the Research Record for This Method
Instead of copying a generic strategy template, build the record around the decisions that are unique to an intraday trading plan. The table below turns this page's eight core concepts into fields that can later be reviewed against actual trades or a historical test.
| Research field | What must be decided before evaluation | Evidence to save |
|---|---|---|
| Premarket context is preparation, not prediction | Use overnight index moves, scheduled macro events, issuer filings, earnings releases, premarket volume, and large price gaps to describe the day's environment. | Record the exact variable, timestamp, threshold or exception used. |
| Candidate quality should be rule-based | A watchlist becomes testable only when eligibility is explicit: minimum price and dollar volume, maximum spread, catalyst type, relative volume, gap size, sector, and exclusions. | Record the exact variable, timestamp, threshold or exception used. |
| The opening range needs a definition | Five-minute, fifteen-minute, and thirty-minute opening ranges are different variables. | Record the exact variable, timestamp, threshold or exception used. |
| Entry needs a trigger and a no-trade condition | A complete rule states what must happen to enter and what prevents entry. | Record the exact variable, timestamp, threshold or exception used. |
| Size from adverse price, not confidence | Define the invalidation level, estimate realistic slippage beyond it, calculate dollars at risk per share, and size the position from a predetermined risk budget. | Record the exact variable, timestamp, threshold or exception used. |
| Time-of-day is a strategy variable | Liquidity, volatility, volume, and participant mix change across the session. | Record the exact variable, timestamp, threshold or exception used. |
| Daily stop rules manage serial error | Intraday losses can cluster when market conditions are incompatible with the playbook or the operator is making repeated execution mistakes. | Record the exact variable, timestamp, threshold or exception used. |
| Review the decision trail | Record the information available before entry, intended order, actual fills, spread, slippage, rule adherence, exit reason, and screenshots or structured market state. | Record the exact variable, timestamp, threshold or exception used. |
This record should be versioned. If one of these fields changes, give the revised strategy a new version identifier and evaluate it separately. That prevents a losing period from quietly rewriting the method while retaining the track record of the older rules. For the same reason, record exclusions: a trade removed because it violated a pre-existing eligibility rule is different from a trade removed because its outcome was inconvenient.
A practical implementation should also distinguish the research definition from the execution implementation. The research definition says what exposure the method wants; the implementation states what order, delay, liquidity threshold, and fill model make that exposure realistically obtainable. That distinction is especially important when premarket context or candidate eligibility changes the cost of acting.
Core Concepts and Design Choices
1. Premarket Context Is Preparation, Not Prediction
Use overnight index moves, scheduled macro events, issuer filings, earnings releases, premarket volume, and large price gaps to describe the day's environment. The goal is to identify what could alter liquidity or volatility, not to make a confident forecast before continuous trading begins.
What this means in practice: Write one observable rule for premarket context and one condition that would make that rule invalid. Save both before examining the next block of data. This converts an attractive explanation into a falsifiable research decision.
Common research error: Treating premarket context as descriptive commentary in winning examples while omitting it from losing examples. A reproducible strategy applies the same definition to every eligible observation.
2. Candidate Quality Should Be Rule-Based
A watchlist becomes testable only when eligibility is explicit: minimum price and dollar volume, maximum spread, catalyst type, relative volume, gap size, sector, and exclusions. A short list produced by consistent filters is easier to evaluate than discretionary scanning that changes after every result.
What this means in practice: Write one observable rule for candidate eligibility and one condition that would make that rule invalid. Save both before examining the next block of data.
Common research error: Treating candidate quality as descriptive commentary in winning examples while omitting it from losing examples. A reproducible strategy applies the same definition to every eligible observation.
3. The Opening Range Needs a Definition
Five-minute, fifteen-minute, and thirty-minute opening ranges are different variables. Specify when the range starts, how auction prints are handled, whether extended-hours data is included, and what constitutes a break. Changing the window after seeing price action destroys testability.
What this means in practice: Write one observable rule for the opening range definition and one condition that would make that rule invalid. Save both before examining the next block of data.
Common research error: Treating the opening range as descriptive commentary in winning examples while omitting it from losing examples. A reproducible strategy applies the same definition to every eligible observation.
4. Entry Needs a Trigger and a No-Trade Condition
A complete rule states what must happen to enter and what prevents entry. Examples of no-trade conditions include a spread widening above threshold, a halt, a failed retest, a macro release inside the next few minutes, or price moving too far from the planned level before the order is submitted.
What this means in practice: Write one observable rule for the entry trigger and one for the no-trade condition. Save both before examining the next block of data.
Common research error: Treating entry conditions as descriptive commentary in winning examples while omitting them from losing examples. A reproducible strategy applies the same definition to every eligible observation.
5. Size from Adverse Price, Not Confidence
Define the invalidation level, estimate realistic slippage beyond it, calculate dollars at risk per share, and size the position from a predetermined risk budget. Confidence ratings can be recorded for research, but increasing size because a setup "looks perfect" introduces an unmeasured variable.
What this means in practice: Write one observable rule for position sizing and one condition that would make that rule invalid. Save both before examining the next block of data.
Common research error: Treating size from adverse price as descriptive commentary in winning examples while omitting it from losing examples. A reproducible strategy applies the same definition to every eligible observation.
6. Time-of-Day Is a Strategy Variable
Liquidity, volatility, volume, and participant mix change across the session. A setup profitable near the open may not behave similarly at lunchtime. Segment results by decision time and avoid combining dissimilar session regimes into one average.
What this means in practice: Write one observable rule for time-of-day eligibility and one condition that would make that rule invalid. Save both before examining the next block of data.
Common research error: Treating time-of-day as descriptive commentary in winning examples while omitting it from losing examples. A reproducible strategy applies the same definition to every eligible observation.
7. Daily Stop Rules Manage Serial Error
Intraday losses can cluster when market conditions are incompatible with the playbook or the operator is making repeated execution mistakes. A daily loss limit, maximum number of failed attempts, or mandatory review trigger can cap the damage from continuing to trade the same broken assumption.
8. Review the Decision Trail
Record the information available before entry, intended order, actual fills, spread, slippage, rule adherence, exit reason, and screenshots or structured market state. Then distinguish strategy loss, execution loss, and process violation. This makes later analysis actionable.
Worked Example
Hypothetical example — for education only.
A trader flags a liquid stock after a company filing creates an 8% premarket gap with unusually high time-adjusted volume. The plan waits for the first 15 minutes, requires the spread to remain below a preset threshold, enters only after price breaks and holds above the opening range, and sizes from a structural invalidation plus a slippage allowance. If the stock already extends two risk units before the trigger, the setup is skipped rather than chased.
The example is deliberately hypothetical. It shows the structure of a decision, not a recommended trade. A valid research record would preserve the inputs as they existed at the decision timestamp, model fills conservatively, include all eligible observations, and retain losing as well as winning cases. The preserved fields should match the intraday trading plan research record above rather than a generic trading checklist.
Turn the Example Into a Falsifiable Test
The worked example should now be decomposed using the page-specific concepts rather than judged by whether the hypothetical trade made money. The analyst should preserve the source data and write a pass/fail condition for each of the following research questions.
Test 1: Premarket Context Is Preparation, Not Prediction
Premise to freeze: Use overnight index moves, scheduled macro events, issuer filings, earnings releases, premarket volume, and large price gaps to describe the day's environment.
How to challenge it: Create at least one comparison in which the premise is weakened, removed, delayed, or measured a different reasonable way. The goal is to identify what could alter liquidity or volatility, not to make a confident forecast before continuous trading begins. Save both the original and challenged result; do not replace the weaker version merely because one outcome looks cleaner.
Implementation check: Note how this choice changes data requirements, order timing, liquidity exposure, position sizing, event treatment, or portfolio aggregation. If the choice cannot be represented with information that was actually available at the decision time, the result belongs in exploratory research rather than a claimed backtest.
Test 2: Candidate Quality Should Be Rule-Based
Premise to freeze: A watchlist becomes testable only when eligibility is explicit: minimum price and dollar volume, maximum spread, catalyst type, relative volume, gap size, sector, and exclusions.
How to challenge it: Create at least one comparison in which the premise is weakened, removed, delayed, or measured a different reasonable way. A short list produced by consistent filters is easier to evaluate than discretionary scanning that changes after every result. Save both the original and challenged result.
Implementation check: Note how this choice changes data requirements, order timing, liquidity exposure, position sizing, event treatment, or portfolio aggregation.
Test 3: The Opening Range Needs a Definition
Premise to freeze: Five-minute, fifteen-minute, and thirty-minute opening ranges are different variables.
How to challenge it: Create at least one comparison in which the premise is weakened, removed, delayed, or measured a different reasonable way. Specify when the range starts, how auction prints are handled, whether extended-hours data is included, and what constitutes a break. Save both the original and challenged result.
Implementation check: Note how this choice changes data requirements, order timing, liquidity exposure, position sizing, event treatment, or portfolio aggregation.
Test 4: Entry Needs a Trigger and a No-Trade Condition
Premise to freeze: A complete rule states what must happen to enter and what prevents entry.
How to challenge it: Create at least one comparison in which the premise is weakened, removed, delayed, or measured a different reasonable way. Examples of no-trade conditions include a spread widening above threshold, a halt, a failed retest, a macro release inside the next few minutes, or price moving too far from the planned level before the order is submitted. Save both the original and challenged result.
Implementation check: Note how this choice changes data requirements, order timing, liquidity exposure, position sizing, event treatment, or portfolio aggregation.
Test 5: Size from Adverse Price, Not Confidence
Premise to freeze: Define the invalidation level, estimate realistic slippage beyond it, calculate dollars at risk per share, and size the position from a predetermined risk budget.
How to challenge it: Create at least one comparison in which the premise is weakened, removed, delayed, or measured a different reasonable way. Confidence ratings can be recorded for research, but increasing size because a setup "looks perfect" introduces an unmeasured variable. Save both the original and challenged result.
Implementation check: Note how this choice changes data requirements, order timing, liquidity exposure, position sizing, event treatment, or portfolio aggregation.
Test 6: Time-of-Day Is a Strategy Variable
Premise to freeze: Liquidity, volatility, volume, and participant mix change across the session.
How to challenge it: Create at least one comparison in which the premise is weakened, removed, delayed, or measured a different reasonable way. A setup profitable near the open may not behave similarly at lunchtime. Save both the original and challenged result.
Implementation check: Note how this choice changes data requirements, order timing, liquidity exposure, position sizing, event treatment, or portfolio aggregation.
Test 7: Daily Stop Rules Manage Serial Error
Premise to freeze: Intraday losses can cluster when market conditions are incompatible with the playbook or the operator is making repeated execution mistakes.
How to challenge it: Create at least one comparison in which the premise is weakened, removed, delayed, or measured a different reasonable way. A daily loss limit, maximum number of failed attempts, or mandatory review trigger can cap the damage from continuing to trade the same broken assumption. Save both the original and challenged result.
Implementation check: Note how this choice changes data requirements, order timing, liquidity exposure, position sizing, event treatment, or portfolio aggregation.
Test 8: Review the Decision Trail
Premise to freeze: Record the information available before entry, intended order, actual fills, spread, slippage, rule adherence, exit reason, and screenshots or structured market state.
How to challenge it: Create at least one comparison in which the premise is weakened, removed, delayed, or measured a different reasonable way. Then distinguish strategy loss, execution loss, and process violation. Save both the original and challenged result.
Implementation check: Note how this choice changes data requirements, order timing, liquidity exposure, position sizing, event treatment, or portfolio aggregation.
Risk, Execution, and Evidence Should Fail Differently
For this method, a losing outcome can arise from at least three different sources. A hypothesis failure means the relationship implied by premarket context or candidate quality did not behave as expected. An implementation failure means the signal may have existed but spreads, slippage, borrow, latency, a gap, a halt, or order mechanics made it materially less tradable. A process failure means the operator did not follow the pre-written eligibility, size, or exit rule. These should be tagged separately in a journal or research database.
Risk analysis should follow the same decomposition. Planned loss is based on the written invalidation and modeled fill; stress loss uses a worse but plausible execution or gap; portfolio loss asks what happens if multiple exposures move together. The strategy should not label the planned stop as a maximum loss. The relevant stress scenario must be specific to this method's mechanism — for example, deterioration in the size-from-adverse-price discipline or a break in time-of-day conditionality — rather than a generic percentage applied to every method.
Execution assumptions also need to match the horizon implied by the strategy. The analyst should show gross results, the specific cost model, and net results. Then increase the cost assumption until expectancy reaches zero. That break-even level shows how much room exists for model error. If a small, realistic change in cost eliminates the result, the page should describe the method as implementation-fragile even when the frictionless backtest looks attractive.
Evidence Package to Retain
- Premarket context is preparation, not prediction: save the input data, the transformation or written rule, the eligibility decision, and one counterexample where the condition did not produce the hoped-for outcome.
- Candidate quality should be rule-based: save the input data, the transformation or written rule, the eligibility decision, and one counterexample.
- The opening range needs a definition: save the input data, the transformation or written rule, the eligibility decision, and one counterexample.
- Entry needs a trigger and a no-trade condition: save the input data, the transformation or written rule, the eligibility decision, and one counterexample.
- Size from adverse price, not confidence: save the input data, the transformation or written rule, the eligibility decision, and one counterexample.
- Time-of-day is a strategy variable: save the input data, the transformation or written rule, the eligibility decision, and one counterexample.
- Daily stop rules manage serial error: save the input data, the transformation or written rule, the eligibility decision, and one counterexample.
- Review the decision trail: save the input data, the transformation or written rule, the eligibility decision, and one counterexample.
The final evidence package should include the complete eligible sample, not a gallery of representative winners. It should also record how many variants were explored. For an intraday trading plan, a stable cluster of reasonable settings is stronger evidence than one isolated best parameter. Reserve later data or a genuinely separate universe for validation, and write the pause/retirement conditions before live performance creates pressure to reinterpret them.
When the Method No Longer Deserves the Same Label
A strategy should be paused or reclassified when the premise behind one of its core concepts changes materially. For this page, a change to the daily stop rules, the review process, market rules, data availability, or realistic execution can make old evidence non-comparable. At that point, preserve the historical version and start a new research version rather than splicing incompatible regimes together.
Common Failure Modes
- Allowing premarket context to remain subjective. Convert the idea into a timestamped, auditable variable or label the result as discretionary rather than quantitative.
- Treating candidate quality as a descriptive story instead of a field that must be recorded before entry. The tell is that the rule changes when a losing example appears.
- Optimizing the opening range window against the full historical sample. The safer design preselects a plausible range, records every variant tested, and validates on untouched observations.
- Ignoring how entry conditions change implementation. A theoretically correct signal can still be unusable when the related fill, liquidity, borrow, gap, or timing assumption is unrealistic.
- Allowing size from adverse price to remain subjective. Convert the idea into a timestamped, auditable variable or label the result as discretionary.
- Treating time-of-day as a descriptive story instead of a field that must be recorded before entry. The tell is that the rule changes when a losing example appears.
- Optimizing the daily loss limit against the full historical sample. The safer design preselects a plausible range and validates on untouched observations.
- Ignoring how the review process changes implementation. A theoretically correct signal can still be unusable when the related fill, liquidity, borrow, gap, or timing assumption is unrealistic.
- Reporting performance without the excluded observations, cost model, and version history. This prevents readers from distinguishing genuine robustness from selection bias.
Practical Operating Checklist
- Document premarket context. Write the decision before evaluation and save the data needed to reproduce it.
- Segment candidate eligibility rules. Write the decision before evaluation and save the data needed to reproduce it.
- Validate the opening range definition. Write the decision before evaluation and save the data needed to reproduce it.
- Version the entry trigger and no-trade condition. Write the decision before evaluation and save the data needed to reproduce it.
- Review size from adverse price calculation. Write the decision before evaluation and save the data needed to reproduce it.
- Define time-of-day eligibility. Write the decision before evaluation and save the data needed to reproduce it.
- Timestamp daily stop rules. Write the decision before evaluation and save the data needed to reproduce it.
- Stress-test the review process. Write the decision before evaluation and save the data needed to reproduce it.
- Calculate planned, stressed, and portfolio-level loss using assumptions appropriate to intraday trading.
- Model gross and net results separately, then identify the implementation cost that would erase the historical edge.
- Reserve an untouched validation sample or period and do not redesign the rule while looking at it.
- Set a dated review trigger for data, market-structure, broker-rule, or mechanism changes.
Questions to Resolve Before Treating the Method as Ready
What would falsify the premarket context rule?
Name an observable condition that would contradict the premise rather than merely produce one losing trade. Then decide whether that condition stops a single position, pauses new entries, or forces a new strategy version. The answer should reference the actual data and timing used, not a generic market opinion.
What would falsify candidate quality being rule-based?
Name an observable condition that would contradict the premise rather than merely produce one losing trade. Then decide whether that condition stops a single position, pauses new entries, or forces a new strategy version.
What would falsify the opening range definition?
Name an observable condition that would contradict the premise rather than merely produce one losing trade. Then decide whether that condition stops a single position, pauses new entries, or forces a new strategy version.
What would falsify the entry trigger and no-trade condition?
Name an observable condition that would contradict the premise rather than merely produce one losing trade. Then decide whether that condition stops a single position, pauses new entries, or forces a new strategy version.
What would falsify size from adverse price?
Name an observable condition that would contradict the premise rather than merely produce one losing trade. Then decide whether that condition stops a single position, pauses new entries, or forces a new strategy version.
What would falsify time-of-day as a strategy variable?
Name an observable condition that would contradict the premise rather than merely produce one losing trade. Then decide whether that condition stops a single position, pauses new entries, or forces a new strategy version.
What would falsify daily stop rules?
Name an observable condition that would contradict the premise rather than merely produce one losing trade. Then decide whether that condition stops a single position, pauses new entries, or forces a new strategy version.
What would falsify the review process?
Name an observable condition that would contradict the premise rather than merely produce one losing trade. Then decide whether that condition stops a single position, pauses new entries, or forces a new strategy version.
What should a reader do if the evidence is mixed?
Narrow the claim. A method can be useful in one universe, horizon, liquidity regime, or event context without being a general rule. Mixed evidence is a reason to state the boundary and uncertainty, not to add filters until the backtest becomes attractive. For an intraday trading plan, preserve the failed conditions because they are part of the information gain of the page.
Summary
Good work on an intraday trading plan starts with specification: universe, timestamp, signal, order, sizing, exit, costs, event treatment, and portfolio constraints. The reader should be able to explain why the behavior might exist, how it could fail, and what evidence would cause the method to be changed or retired. This is the standard that turns a trading idea into an educational research process.