Open RadarPulse →
Options flow · June 28, 2026

Options flow alerts: how to set up and use unusual activity notifications

Monitoring a live options tape manually is not practical during a trading session. Flow alerts solve that problem by pushing a notification the moment a print meets criteria you define, so you can focus on other work and receive a curated signal rather than scanning a screen all day. This guide covers what to alert on, how to calibrate thresholds to reduce noise without missing important prints, and how to evaluate a notification before acting on it.

What an options flow alert is

An options flow alert is a real-time notification triggered when a trade on the tape matches criteria you specify. The most common triggers are a minimum premium threshold (filtering out small retail trades), an unusualness score above a set level, a specific ticker from your watchlist, or a combination of execution type and Vol/OI ratio.

The alert itself is not a trade signal, it is the notification that something worth evaluating has appeared on the tape. Whether it represents a directional conviction trade or a routine hedge depends on context you assess after the alert fires. The goal is to receive fewer, better notifications rather than a high-volume stream that demands constant attention.

What to alert on: the effective criteria stack

Alerts built on a single criterion tend to either over-fire (too many notifications, most of them noise) or under-fire (miss relevant prints). The most effective configuration combines at least two, ideally three, of the following:

Minimum premium threshold

The first noise filter. Set to $250,000 to eliminate retail activity. Set to $500,000 if you want to see only larger institutional-sized prints. A $1M minimum gives very few alerts per day, typically the most significant single-name moves on the tape. Start at $250K and adjust upward once you know the typical alert volume for your watchlist.

Unusualness score threshold

A composite score combining Vol/OI ratio, premium, DTE and aggressor side into a single 0–100 number. Alerting above 70 gives broad unusual coverage, many prints per day across the market. Alerting above 85 narrows to the highest-conviction outliers. Above 90 produces very few alerts, typically corresponding to EXTREME-tier prints. Set based on how many alerts you want to receive in a session.

Execution type: sweep

Restricting alerts to sweeps filters out block trades, which are often prearranged and carry less urgency signal. Sweep-only alerts fire on prints where a participant routed across multiple exchanges at the ask, the clearest urgency marker on the tape. Combine with the premium and score thresholds for the cleanest institutional-urgency filter.

Ticker watchlist

Ticker-specific alerts fire when any unusual print in a name you follow meets your criteria. Useful for stocks you already have a position in, names you've been researching, or tickers where you've seen prior unusual flow that hasn't resolved yet. Broad-market alerts (no ticker filter) complement this by surfacing names you weren't already watching, a common way to discover new setups from the institutional tape.

Confluence alerts: flow + congress overlap

A confluence alert fires when unusual options activity in a name overlaps with a recent congressional disclosure in the same stock. These cross-domain alerts are rarer but represent the highest-context signals, two separate public data streams pointing in the same direction simultaneously. The combination requires no additional work to surface; a scanner that tracks both data sources can fire the alert automatically.

Avoiding the most common alert calibration mistakes

Setting the premium floor too low. A $25,000 minimum premium alert fires on retail-sized trades constantly. On an active day, that is hundreds of notifications, the signal-to-noise ratio approaches zero. Start at $250,000 and only lower it for a specific ticker where you're watching for smaller accumulation over time.

Not filtering by DTE. Zero-DTE options (same-day expiry) generate enormous volume on market open and close, most of it mechanical and retail-driven. Requiring a minimum DTE of at least 7 days removes the 0DTE noise floor without discarding meaningful near-term catalyst plays.

Alerting within earnings windows. The five trading days before a company reports earnings flood the tape with protective puts and pre-announcement positioning. These prints look like directional bets but are often systematic hedges. Automatically excluding the earnings window, or treating earnings-proximity prints as a separate, lower-confidence category, keeps non-earnings alert quality high.

Including sector ETF flow in single-name alerts. Large sector ETF prints (SPY, QQQ, XLK, XLE) can trigger alerts that look like sector-wide conviction but are often index rebalancing or risk management by funds tracking benchmarks. Treat ETF prints separately from single-name prints in your alert routing if possible.

Acting on the first alert without checking context. An alert that fires tells you a print occurred; it does not tell you whether the print is a directional conviction trade or a hedge. The 2-5 minutes spent checking earnings dates, stock chart, and prior 13F filings before acting is not optional, it is the process that separates useful signals from costly chasing.

The alert evaluation workflow

When an alert fires, run this sequence before making any decision:

  1. Read the full print. Check the strike distance from current price (OTM? by how much?), expiry (how many DTE?), total premium, execution type (sweep or block), and Vol/OI ratio. All five fields together determine the initial read.
  2. Check the earnings date. If the company reports in fewer than five trading days, the print is likely earnings-related. Discount the directional read accordingly.
  3. Look at the stock chart. Is the stock near a support or resistance level that would explain the strike choice? Is volume elevated on the equity side too, suggesting a broader institutional move?
  4. Check recent congressional disclosures and 13F filings for the name. A brief check on whether insiders or major institutions have recently disclosed activity in this name adds context in under two minutes.
  5. Look for spread structure. If the same name has multiple prints at different strikes in the same expiry session, you may be looking at spread legs. Confirm the directional read requires both legs to be net directional in the same way.
  6. Ask: what is the thesis? If you cannot state in one sentence why the stock should move in the direction the flow implies, and in what timeframe, the alert is not ready to act on. Wait for a setup you understand before committing capital.

Alert timing: real-time vs end-of-day

Two distinct use cases for options flow alerts exist depending on how and when you trade:

Real-time intraday alerts are useful if you are available during market hours to evaluate and act on prints as they appear. They are most valuable for EXTREME-scored sweeps in short-dated contracts, where the urgency signal is highest and the move, if it occurs, tends to happen quickly. The evaluation window on a real-time alert is typically minutes to an hour, acting later in the same day is usually still relevant, but the same-session window closes at 4pm.

End-of-day summary alerts, a ranked digest of the session's top prints, suit traders who cannot monitor during market hours. The delay is real: the print already happened and the initial price reaction may be partly embedded. The use case is research: reviewing what positioned heavily in a name, building a watchlist for the next session, and identifying confluence between flow and congressional data across the full day.

For most traders, a combination is most practical: real-time alerts filtered for only EXTREME-scored sweeps above $500K (low volume, high relevance), plus an end-of-day summary of the Top 25 for daily review.

Confluence alerts: the most signal-dense configuration

The highest-context option alert configuration, if a scanner supports it, combines unusual options flow with a secondary signal from a different data source in the same name:

Each combination takes the signal beyond options-only flow reading and into cross-domain pattern recognition, the direction both sources point in together carries more weight than either alone.

RadarPulse live confluence alerts. The in-app alert center fires when unusual flow in a name overlaps with a congressional disclosure or elevated institutional activity. The notification includes the flow print, the score, and the relevant cross-domain context, so the evaluation starts with the most relevant information already surfaced, not a blank print to research from scratch.

What to do when an alert fires during a position

If you already hold a position in a name that fires an unusual flow alert, the evaluation process is the same but the stakes are more immediate. Three scenarios:

Building a tiered alert system: three alert layers

Most traders make the mistake of running a single alert configuration and expecting it to serve every purpose, from catching the day's highest-conviction institutional event to monitoring familiar names to building tomorrow's watchlist. A single threshold cannot do all three well. Set it tight enough to catch only the most extreme prints and you miss the medium-signal names that become next week's trades. Set it loose enough to catch everything and you get dozens of notifications that numb the response to the most important ones.

The solution is three simultaneous alert layers, each with a distinct purpose and threshold calibration.

Layer 1, Immediate action layer (highest threshold)

Criteria: EXTREME-scored prints (score 90+) + premium above $1M + sweep at ask + minimum 14 DTE. Expected volume: 2–5 alerts per day on average. On quiet sessions, none may fire. On high-volatility events, you may see 8–10.

This is the only layer that demands real-time attention. When Layer 1 fires, stop what you are doing and run the evaluation workflow immediately. A score-90+ sweep above $1M is a genuine institutional event by any definition of unusual, rare enough to treat as high-priority, rare enough that evaluating every one is manageable. Do not let these stack up to review later. The same-session window closes at 4pm and day traders who want to act on the implied thesis have to do so within hours of the print.

Layer 2, Research layer (medium threshold)

Criteria: score 75+ + premium $250K+ + sweep. Expected volume: 10–20 alerts per day depending on market conditions and how broad your ticker filter is.

Layer 2 alerts are not trade triggers, they are research candidates. Each one goes into a queue: at end of session (or during a quiet period if you are available), review the Layer 2 list and decide which names warrant follow-up. Check earnings proximity, look at the chart, pull the most recent 13F for institutional context, and assess whether the thesis makes sense. The output of this review is a watchlist for the next session, names with both a flow signal and a thesis you can articulate. Some Layer 2 alerts will resolve as noise; others become the setup that fires on Layer 1 the next day.

Layer 3, Watchlist layer (ticker-specific)

Criteria: any unusual activity in your specific watchlist tickers, minimum score 60+. No minimum premium filter, or a lower one ($50K–$100K) for names where smaller prints still carry information. Expected volume: depends entirely on your watchlist size and activity in those names.

Layer 3 alerts fire when something is happening in a name you already have a view on, regardless of absolute premium size. A $150K sweep in a small-cap you have been watching for three weeks may carry more signal than a $2M sweep in a mega-cap you know nothing about, because you have the existing thesis to evaluate against. This layer is what ties options flow to your existing research process rather than keeping flow as a separate, disconnected signal stream.

The three layers interact in a predictable and useful way. Layer 1 surfaces the session's institutional highlights. Layer 2 builds tomorrow's watchlist. Layer 3 monitors the names you are already in or following. The escalation pattern to watch for: a name appears in Layer 2 one day (moderate unusual flow, worth noting), then appears in Layer 1 the next (a stronger, higher-conviction follow-on print). That escalation sequence, two consecutive sessions with prints in the same name, the second stronger than the first, is the highest-conviction alert pattern a tiered system can surface.

Three-layer reference table

Layer Threshold settings Daily volume Review timing Action response
Layer 1 Score 90+ · Premium $1M+ · Sweep · 14+ DTE 2–5 Immediately Full 6-step evaluation; act if thesis confirms
Layer 2 Score 75+ · Premium $250K+ · Sweep 10–20 End of session Research queue; build watchlist for next session
Layer 3 Score 60+ · Watchlist tickers only Varies When convenient Evaluate against existing thesis; monitor for escalation

Alert fatigue: why too many notifications defeat the purpose

Alert fatigue is the state where so many notifications fire that traders stop evaluating them properly, or stop checking altogether. It is one of the most common and most underappreciated failure modes in options flow monitoring, and it sets in faster than most traders expect.

The psychological mechanism is straightforward. When an alert fires every ten minutes throughout a six-and-a-half-hour session, it no longer functions as a signal, it becomes background noise, indistinguishable from an email notification or a calendar reminder. The urgency the alert was designed to create fades. Traders begin skimming alerts rather than evaluating them. From there the behavior degrades in one of two directions: they start ignoring alerts entirely (capturing nothing from the system), or they start acting on them reflexively without evaluation (which is worse than ignoring them, because it produces impulsive trades with no thesis behind them). Both outcomes are worse than having no alert system at all, because the system is creating the false impression of an edge while delivering none.

How to know if you have alert fatigue. The signs are specific. If you received more than 40 alerts in a session and cannot remember what most of them were about, your threshold is too low. If you find yourself executing trades directly from the alert notification without first running the evaluation workflow, you have fatigue. If you have started dismissing alerts without reading them, swiping them away on mobile, clearing notification stacks without looking, you have developed a conditioned non-response to the system. At that point the alerts are consuming attention without producing any analytical benefit.

The recalibration process. When alert fatigue sets in, the fix is counterintuitive: raise the threshold rather than trying to read more carefully at the same volume. The instinct is to try harder, to commit to evaluating every alert properly going forward. The instinct is wrong, because the alert volume is a structural problem, not a discipline problem. Two weeks of receiving three thoughtfully configured alerts per day and evaluating each one completely produces better decision-making outcomes than thirty alerts per day with reflexive, uncritical responses. Raise the score threshold from 70 to 85, raise the premium floor from $250K to $500K, and let the volume drop. Fatigue clears within a few sessions.

The "three per session" target for the primary layer. Professional options analysts often configure their primary Layer 1 alert to fire no more than 3–5 times per session on average, fewer on quiet sessions, more on high-volatility event days. This is achievable by combining score 90+, premium $1M+, and sweep into the primary layer. Three well-constructed alerts that each get a careful 3-minute evaluation is a better information diet than twenty alerts that each get 30 seconds of pattern-matching.

End-of-day digests as fatigue prevention. One of the most effective structural choices for managing alert volume is routing medium-threshold prints to an end-of-day summary rather than real-time notifications. Instead of receiving a push notification for every score-75+ print as it happens during the session, receive a single ranked list at 4:15pm, the top 20 prints from the day, sorted by score. Reading and evaluating that list once, in one focused sitting, is cognitively different from absorbing a stream of interruptions across six hours of a trading session. It is easier to think clearly about ten prints at once than to evaluate ten prints across ten separate real-time interruptions. The only cost is the delay, but for swing traders who are not acting intraday anyway, the delay is irrelevant.

Alert configuration for different trader types

There is no single correct alert configuration, the right setup depends on when you are available, how you make trading decisions, and what you are trying to accomplish with the flow signal. The following profiles are generalizations, but they map to the most common trader situations.

The active day trader

Available during market hours, focused on intraday price moves, and willing to act within the session. Optimal configuration: real-time Layer 1 alerts (score 90+, premium $500K+, sweep, 7–30 DTE) for immediate evaluation during the session; end-of-day Layer 2 digest for next-session watchlist building. The day trader's window closes at 4pm, an unacted-on real-time alert from 10am is no longer actionable for intraday purposes by 2pm, and is research-only by close. The Layer 1 real-time filter should be tight enough that any alert that fires is worth stopping current work to evaluate. The Layer 2 digest is consumed once after the close as a planning session for the following morning.

The swing trader with a day job

Not available during market hours; reviews once per evening. Optimal configuration: end-of-day digest of all prints scoring 80+ for session review at 6–8pm; ticker-specific Layer 3 alerts for active positions delivered to mobile (the only real-time interruptions during work hours). The swing trader uses the evening digest to decide which names to place entry limit orders on for the next session, the price reaction has already happened, so the question is whether the thesis is strong enough to enter on the following day's open or intraday pullback. Ticker-specific Layer 3 mobile alerts serve a specific function: they notify the trader when a position they are already in is receiving new flow activity, which may warrant checking the position at lunch or break even when not actively monitoring markets.

The portfolio manager tracking macro

Interested in broad institutional positioning trends and sector rotation signals, not individual day-trade entry timing. Optimal configuration: end-of-day digest filtered to major ETF flow (SPY, QQQ, sector ETFs) plus single-name prints scoring 85+ with premium $1M+; weekly summary for portfolio strategy review. Uses flow alerts to monitor whether institutional money is moving toward or away from a sector, not to generate specific trade triggers. A sustained pattern of heavy call flow in energy names across five consecutive sessions carries more portfolio-level information than any single print. The weekly digest format allows pattern recognition across multiple sessions that is harder to see when reviewing prints one at a time.

The researcher (no live trading)

Building a predictive model, backtesting flow signals, or studying the relationship between unusual options activity and subsequent price moves. Optimal configuration: all prints above $1M (no score filter, or a very low floor of 40+) for raw data capture; end-of-day digest for daily review. Deliberately avoids heavy score filtering to prevent confirmation bias in the signal they are studying, the scoring model's prediction is what is being tested, not something to rely on as a filter. Focuses on the raw tape: execution type, strike distance, DTE, premium, and subsequent price outcome. This configuration produces the most data and the most noise simultaneously, which is the correct tradeoff for model-building rather than real-time trading.

Trader-type configuration reference

Trader type Primary alert layer Threshold Review frequency Primary use
Day trader Real-time L1 Score 90+, $500K+, sweep Immediately + EOD digest Intraday execution
Swing trader EOD digest Score 80+; L3 ticker-specific Evening review Next-session watchlist
Portfolio manager EOD + weekly digest Score 85+, $1M+; ETF flow Evening + weekly Macro / sector rotation
Researcher Raw tape capture Premium $1M+, no score filter EOD review Model building / backtesting

The alert + technical analysis workflow

Options flow alerts tell you that institutional activity is occurring in a name, the size, direction, and urgency of positioning. They do not tell you where the price is, whether it is at a favorable entry point, or whether the technical setup supports the implied thesis. Flow without technical analysis leads to entries at arbitrary prices relative to structure; technical analysis without flow lacks the conviction context that unusually large positioning provides. The two work best in sequence.

Why flow without technicals leads to poor entry timing. A call sweep can appear in a name that is 15% extended above its 50-day moving average, in overbought RSI territory, with no recent consolidation or pullback. Buying calls at the current price means riding the same institutional positioning, but at a price 15% higher than the institutional participant paid to establish their position. The risk-reward is asymmetrically worse even if the institutional thesis is correct. The name may ultimately move in the direction the flow implies, but the entry has significantly reduced the expected return. Conversely, a bearish flow print in a name that is already at a major technical support level may fail to follow through, because the technical floor is being defended by buyers who do not care about options flow.

The three-step confirmation workflow. After an alert fires and evaluation passes, apply this sequence before committing capital:

  1. Alert fires → run the evaluation workflow. Check the print details (score, premium, DTE, strike distance, execution type). Confirm no obvious earnings-window or spread-leg explanation. Form a preliminary thesis.
  2. If evaluation passes → check the technical setup. Look at the chart: where is the stock relative to its 50-day and 200-day moving averages? Is it near a defined support or resistance level? What does relative volume on the equity side look like today? Has there been a recent pullback from a high, or is the stock extended? The technical picture tells you whether a favorable entry exists now or whether waiting improves the trade setup.
  3. If technicals confirm → size and structure the position. Identify your entry price, stop level, and target based on the contract DTE and strike distance from current price. A 30-DTE contract with a strike 5% OTM needs a different position size and stop placement than a 60-DTE contract with a strike 2% OTM in the same name. The DTE determines how much time decay works against you; the strike distance determines how much the stock needs to move for the position to be profitable.

Technical confirmation patterns after a bullish flow alert.

Technical confirmation patterns after a bearish flow alert.

When flow and technicals conflict. The most common conflict is a bullish sweep in a technically overbought name, or a bearish sweep in an oversold name that is at major support. In these cases, the technical condition is the timing filter, not the veto. The institutional positioning may be correct on a 30–60 day horizon while the technical condition resolves on a 5–10 day horizon. Wait for the technical overbought condition to work off through time (consolidation) or price (pullback to moving averages) before entering based on the flow signal. The thesis does not expire because you waited a week for a better entry. If the stock breaks down technically while you are waiting, the flow print may have been a hedge rather than a conviction trade, which is additional information.

Tracking alert performance: measuring your process over time

The only way to know whether an alert configuration is generating value, and whether your evaluation process is producing accurate assessments, is to measure outcomes systematically over time. Most traders skip this step entirely. They configure alerts, act on some, ignore others, and never close the feedback loop between what the flow implied and what subsequently happened. Without that feedback loop, there is no way to improve the calibration or identify which alert types are actually predictive for the names and sectors they trade.

What to track for each alert you evaluate. The tracking log should cover every alert you evaluate, not just the ones you act on. Alerts you dismiss as noise are as informative as alerts you trade, because they tell you whether your noise filter is accurate. For each evaluated alert, record:

Calculating signal quality (separate from trade win rate). Take all alerts where your evaluation concluded "genuine directional signal", regardless of whether you traded. Among those, track what percentage of the underlying stocks moved in the expected direction within the DTE window. This number, call it the signal quality rate, tells you whether the alerts you are classifying as directional are actually predictive. A signal quality rate above 55% is meaningful edge (50% is random). A rate below 50% suggests your score threshold or classification process needs adjustment. Critically, this rate is independent of your trading win rate, you may have a 60% signal quality rate and a 45% trade win rate if your entries are poorly timed. The two numbers diagnose different problems.

Calculating your evaluation accuracy. Track separately what percentage of prints you classified as "probable hedges" turned out to be non-directional, confirmed by the stock not moving meaningfully within the DTE window. And track what percentage of prints you classified as "directional conviction" moved in the expected direction within the DTE. The gap between your accuracy rate and random chance (50%) is your evaluation edge. Over time, you should see this improve as you develop pattern recognition for the specific false-positive types that appear in names and sectors you follow.

Monthly review cadence. Once per month, review 30 days of alert outcomes. The questions to answer in the review:

Sample alert tracking log

Date Ticker Score Direction Classification 14-day outcome Correct?
Jun 2 NVDA 94 Bullish Directional +8.3% Yes
Jun 3 AMD 81 Bearish Probable hedge +1.1% Yes
Jun 5 META 88 Bullish Directional -3.2% No
Jun 9 TSLA 76 Bullish Watchlist +5.7% Yes
Jun 11 XLE 83 Bearish ETF rebalance +0.4% Yes

Track every evaluated alert, including dismissed ones. The dismissed rows validate (or challenge) your noise-filter logic as much as the traded rows validate your signal read.

Frequently asked questions

What are options flow alerts?

Options flow alerts are real-time notifications triggered when an options trade meets criteria you define, minimum premium, unusualness score, specific tickers, or a combination of sweep execution and Vol/OI ratio. They surface high-conviction prints from the daily tape without requiring constant manual monitoring of a live scanner.

What should I set options flow alerts for?

The most effective configuration combines a minimum premium of $250,000 or more, a composite unusualness score above 70–85, and sweep execution. Adding a ticker watchlist narrows alerts to names you are actively following. Confluence alerts, flow plus congressional or 13F overlap, produce the fewest but highest-context notifications.

How do I avoid false alerts in options flow?

Raise the premium minimum to $500,000 or above; require Vol/OI above 2; restrict to sweeps rather than including blocks; set a minimum DTE of 7+ days to exclude 0DTE noise; and exclude the five-day earnings window for each underlying. Raising the unusualness score threshold to 85+ is the single most effective way to reduce alert volume while preserving the highest-conviction prints.

Can I set options flow alerts on specific tickers?

Yes. Ticker-specific alerts fire when any unusual print in a name you follow meets your configured thresholds, regardless of broad market activity. They are most useful for stocks you are actively researching or already hold a position in. Pair them with broad market alerts (no ticker filter) to also surface new names from the institutional tape.

How quickly should I act on an options flow alert?

An options flow alert starts an evaluation process, not an execution. Spend 2–5 minutes checking earnings proximity, stock chart, prior 13F filings, and whether a spread structure is visible before placing any trade. The most common mistake is acting on the first notification without this check, buying a print that was an institutional hedge, not a directional conviction trade.

Get options flow alerts from RadarPulse

Real-time alerts on EXTREME-scored prints, live confluence notifications when flow overlaps with congressional data, and a daily Top 25 digest for end-of-day review. Basic is $12/mo with a 14-day free trial.

Open RadarPulse →

Keep reading