Stock scanner alerts are most useful when they reduce a large market into a manageable watchlist rather than encourage automatic trades. This workflow shows how to configure pre-market and intraday scanners using liquidity, relative volume, gap size, volatility, catalysts, technical triggers, and alert timing, then evaluate each alert with repeatable assumptions before taking action.
Overview
A scanner searches a defined universe of stocks for conditions that match your rules. An alert is only an invitation to investigate; it is not proof that a trade is attractive. The central objective is to find symbols with enough liquidity, movement, and context to support a planned decision while filtering out avoidable noise.
A practical workflow has four stages:
- Discover: Run a broad pre-market or intraday scan.
- Validate: Confirm the data, catalyst, trend, spread, and trading session.
- Plan: Define the entry condition, invalidation level, position size, and exit logic.
- Review: Record whether the alert produced a valid setup, not merely whether the stock moved.
This distinction matters for both discretionary traders and automated systems. A news sentiment framework can help organize headline review, while a paper trading bot or scanner can test alert logic without sending live orders. Scanner alerts should not be treated as a substitute for risk management or as an automatic trading signal.
Use separate scans for different jobs. A pre-market scanner identifies unusual gaps and possible catalysts before the opening bell. An intraday scanner looks for fresh volume, range expansion, breakouts, reversals, or changes in market structure. A swing-trading scanner generally needs less immediate movement but more evidence of a multi-session trend or upcoming catalyst.
How to estimate
Start by translating your setup into measurable conditions. The goal is not to choose the highest number of filters; it is to choose filters that answer specific questions.
1. Define the trading universe
Set the market, exchange, security type, price range, and minimum liquidity before adding technical conditions. If your platform provides average daily volume, dollar volume, or bid-ask spread data, use those fields to avoid symbols that may be difficult to enter or exit. Dollar volume can be estimated as:
Estimated dollar volume = share price × shares traded
For intraday work, consider recent volume and the quality of the spread rather than relying only on a stock's historical average.
2. Add relative volume
Relative volume compares current or expected activity with a reference level. A simple estimate is:
Relative volume = current volume ÷ comparable average volume
The comparison should use a similar time of day when possible. Comparing the first several minutes of a session with a full-day average can produce misleading results. Set a minimum relative-volume threshold appropriate to your strategy, then review whether the threshold generates too many thin or already-extended names.
3. Measure the gap and volatility
For a pre-market scan, gap percentage is commonly calculated as:
Gap percentage = (pre-market price − prior close) ÷ prior close × 100
Gap size alone does not establish direction or quality. A large gap may reflect a meaningful catalyst, a temporary price dislocation, or a wide and unreliable market. Pair the gap filter with volume, spread, catalyst confirmation, and a defined technical level.
For volatility, choose a consistent measure such as average true range, percentage range, or the distance between recent high and low. A useful question is whether the expected range is large enough to reach your planned target while still allowing a stop that fits your risk limit.
4. Confirm the catalyst
Use a separate news or event check for earnings, guidance, filings, analyst actions, corporate announcements, sector developments, or other identifiable reasons for unusual activity. Do not assume that a headline explains the entire move. Check its timestamp, source, relevance to the company, and whether the price reaction has already occurred.
5. Add a technical trigger
Technical conditions should describe what must happen next, not simply what has already happened. Examples include a break above a defined pre-market high, a reclaim of a prior support level, a pullback that holds a moving average, or a range expansion accompanied by volume. Keep the scan broad enough to find candidates, then use the chart to determine whether the setup meets your trading plan.
6. Control alert timing and duplicates
Choose whether alerts should trigger once per symbol, once per bar, or whenever a condition becomes true. Repeated alerts can create the illusion of multiple opportunities when they are really one continuing move. Record the first alert time and suppress duplicates until the setup changes materially, such as a new breakout level, failed thesis, or fresh catalyst.
| Use case | Liquidity focus | Relative volume | Movement filter | Catalyst and trigger |
|---|---|---|---|---|
| Day trading | Prioritize consistent dollar volume and manageable spreads | Compare activity with the same time of day | Use a range or volatility measure that supports the planned stop and target | Fresh catalyst plus an intraday level or price-action trigger |
| Swing trading | Prioritize reliable multi-session liquidity | Look for accumulation or activity above a longer reference period | Use trend structure, recent range, and expected holding-period movement | Identifiable catalyst or trend change plus a daily or weekly confirmation |
Inputs and assumptions
Scanner results are only as dependable as their inputs. Before saving a scan, document the following assumptions:
- Session: Specify pre-market, regular session, or after-hours. Confirm that your platform actually supports the selected session.
- Data timing: Check whether quotes, volume, news, and technical fields are real-time, delayed, or updated at different intervals.
- Price basis: Note whether filters use last trade, bid, ask, midpoint, adjusted close, or another field.
- Universe: Exclude instruments that do not fit your plan, such as securities with unacceptable spreads, trading halts, or insufficient history.
- Thresholds: Write down the minimum price, dollar volume, relative volume, gap, and volatility values rather than changing them informally during the session.
- Risk limit: Estimate position size from the distance between entry and invalidation. The position-sizing formula is: shares = maximum account risk ÷ risk per share.
Thresholds are starting assumptions, not universal standards. A volatile market may make a previously moderate gap or range appear ordinary, while a quiet market may make the same filter too restrictive. Review alert quality using a sample of prior sessions. Track how many alerts became valid setups, how many failed because of liquidity or news, and how many arrived too late to act on responsibly.
For traders considering automation, keep scanning separate from order execution until the logic has been tested. A backtesting framework can help test historical rules, but live conditions may differ because of spreads, delays, halts, partial fills, and changing market behavior. Broker API permissions and order support should also be checked before connecting any automated trading bot.
Worked examples
Example 1: Pre-market day-trading scan
Assume a trader wants a short list of liquid stocks that may have enough movement for an opening-session plan. The scan begins with a defined minimum price and dollar-volume requirement, then adds a moderate gap range, elevated pre-market activity, and a confirmed company-specific or sector catalyst. The trader does not buy when the alert fires. Instead, each symbol is placed on a watchlist and reviewed for:
- Whether the news is current and relevant.
- Whether the spread remains acceptable near the open.
- Whether the pre-market high and low create clear reference levels.
- Whether the opening price is already too far from the planned invalidation level.
- Whether the expected reward justifies the risk after estimated slippage and fees.
If the gap is 8 percent and the planned stop is 2 percent below the proposed entry, the trader still needs to estimate position size from the account risk limit. The gap percentage does not determine the amount to invest.
Example 2: Intraday breakout alert
Suppose a symbol passes a liquidity filter and forms a narrow range during the session. The alert is configured to trigger only if price moves above the range high and current volume exceeds a chosen reference level. The trader then checks whether the move is occurring near a meaningful higher-timeframe level, whether the broader market supports the direction, and whether the distance to the next resistance area leaves enough room for the plan.
If the breakout fails immediately and returns inside the range, that event may invalidate the setup. A duplicate alert should not reopen the same idea unless a new structure forms. This prevents notification volume from becoming a substitute for analysis.
Example 3: Swing-trading scan
A swing trader may use a daily scan for stocks above a longer-term trend reference, showing improving volume and holding a defined support area. The catalyst may be an upcoming earnings event or a sector development, but the trader must decide whether holding through that event fits the plan. The alert creates a candidate list; the entry still depends on a daily close, pullback, or other prewritten trigger.
When to recalculate
Revisit scanner settings whenever market conditions, platform data, or your trading process changes. At minimum, review them during a weekly process check and after a sustained change in volatility, liquidity, or news-driven activity. Recalculate thresholds when you switch from day trading to swing trading, change the security universe, or adopt a different chart timeframe.
Platform updates are another reason to review the workflow. Feature names, session definitions, alert behavior, and data-delay notes can change. Confirm that each field still means what your rules assume, especially for pre-market volume, after-hours prices, relative volume, and news timestamps.
Use this daily checklist before acting on any stock scanner alert:
- Confirm the trading session and data freshness.
- Remove symbols that fail liquidity or spread requirements.
- Read and timestamp the relevant catalyst.
- Mark the key high, low, support, resistance, and invalidation levels.
- Estimate the entry, stop, target, position size, and potential execution costs.
- Decide whether the alert belongs on a watchlist, not whether it deserves an automatic order.
- After the session, record which alerts produced valid setups and why the others failed.
That final review turns alerts into a feedback loop. If too many alerts arrive late, adjust timing or suppress duplicates. If most candidates lack liquidity, strengthen the universe filters. If alerts identify movement but not repeatable setups, refine the catalyst and technical conditions. Recalculate the workflow when the inputs change, then keep the rules stable long enough to evaluate them fairly.