← Back to blog

Short-Sale Volume Is Not Short Interest: A Squeeze Radar Workflow

A source-first workflow for separating reported short interest, daily short-sale volume, days to cover, float, liquidity, Reg SHO context, and squeeze-risk narratives.

Published 6/23/2026

Short-Sale Volume Is Not Short Interest: A Squeeze Radar Workflow cover image

Few market datasets create more confusion than short-sale volume and short interest. They sound similar, they both involve short selling, and both can appear beside squeeze narratives. But FINRA is explicit that daily short-sale volume and reported short interest are not the same. One is trading-flow activity for a day. The other is a position snapshot reported on a schedule.

A serious squeeze workflow starts by keeping those lanes separate. Short interest can help describe how much reported short positioning existed at a point in time. Daily short-sale volume can help describe intraday or daily trading flow, but it does not tell you how many shares remain short at the end of the day. Mixing the two creates false confidence.

FinMonkeys Squeeze Radar board showing reported short interest, daily short-sale ratio, setup scores, and freshness labels
Squeeze Radar keeps reported short interest and daily short-sale flow visible as separate fields, with freshness context before interpretation.

Understand the data before interpreting the setup

FINRA short interest reporting is collected on designated settlement dates, and firms report positions after those dates. That means short interest is delayed and point-in-time. It can still be useful, especially when combined with float and average volume, but it is not a live meter.

FINRA daily short-sale volume files aggregate short-sale trades reported to certain facilities during normal market hours. That flow may contribute to future reported short interest, but many trades can be closed, hedged, or part of market-making activity. A high daily percentage does not automatically mean a large short position exists.

  • Short interest: a reported position snapshot.
  • Short-sale volume: a daily flow measure, not an open-position count.
  • Days to cover: short interest compared with average trading volume.
  • Float: the share base that can make positioning more or less crowded.
  • Reg SHO threshold status: a separate market-structure flag, not a squeeze prediction.

Build the setup from independent ingredients

A squeeze-risk review should not rely on one metric. Reported short interest matters more when float is tight, borrow conditions are difficult, liquidity is thin, and price action starts moving against the short side. A high short-interest percentage in a very liquid mega-cap is a different situation from moderate short interest in a thinly traded small-cap.

Price action is also not optional. A crowded short can stay crowded for a long time if there is no catalyst, no liquidity pressure, and no buying interest. Conversely, a fast-moving stock with weak short-interest evidence may be momentum, not a squeeze setup.

  • Check reported short interest and its age.
  • Compare days to cover against realistic volume, not a one-day spike.
  • Review float, market cap, and liquidity together.
  • Separate news catalysts from social-media attention.
  • Check whether the setup depends on stale or missing data.

Use Reg SHO carefully

SEC Regulation SHO addresses short-sale practices, including locate requirements and threshold securities. Threshold-list status can be useful context because it points to securities with persistent fail-to-deliver conditions under the rule framework. But it does not by itself say a squeeze will occur.

Use threshold status as a flag for deeper review. Ask whether the company has real catalysts, whether liquidity supports the trade narrative, whether shares are hard to borrow, and whether price action confirms pressure. Without that context, threshold status becomes another headline term that can be overinterpreted.

  • Treat threshold status as a context flag, not a buy signal.
  • Check whether the flag is current.
  • Compare threshold status with price action and volume.
  • Avoid combining fail-to-deliver narratives with unrelated short-volume data.
  • Write down what evidence would invalidate the setup.

Avoid squeeze-story shortcuts

The most common shortcut is turning every heavily shorted stock into a squeeze candidate. Many heavily shorted companies are shorted for reasons that matter: weak balance sheets, dilution risk, poor operating trends, litigation, fraud concerns, or broken business models. Short interest can identify disagreement, but disagreement is not automatically opportunity.

The second shortcut is ignoring exits. A squeeze workflow should define what would make the setup less interesting: short interest falls, volume normalizes, catalyst fails, price breaks support, liquidity dries up, or data freshness deteriorates. Without invalidation rules, the story can survive long after the evidence changes.

  • Separate legitimate bearish fundamentals from crowded positioning.
  • Do not treat social attention as proof of forced covering.
  • Do not compare short-sale volume percentages across venues without understanding the source.
  • Do not ignore dilution, financing, or going-concern risk.
  • Do not keep a setup active after the evidence goes stale.
A squeeze workflow is strongest when it refuses to turn every short metric into the same story.

Keep short-volume, short-interest, and price evidence separate

A squeeze workflow fails when every bearish-looking datapoint is treated as the same signal. Daily short-sale volume is transaction-flow data. Exchange-reported short interest is a position snapshot reported on a schedule. Reg SHO threshold status is a settlement-related flag. Price momentum, borrow availability, float, and liquidity are separate pieces again. They may belong in the same research file, but they should not be blended into one vague pressure story.

The cleanest approach is to label the evidence by what it can and cannot prove. Short interest can indicate a large reported short position, but it is delayed. Daily short-sale volume can show short-sale activity in reported trades, but it is not the same thing as an outstanding position. Threshold status can highlight persistent settlement issues, but it does not explain motive by itself. Treating these categories precisely protects the research from sensational conclusions.

  • Record short interest with its settlement date and publication date.
  • Record daily short-sale volume as flow data, not as current short interest.
  • Track float, liquidity, and days-to-cover assumptions separately.
  • Use Reg SHO threshold status as a risk flag, not as a standalone thesis.
  • Write which evidence is current, delayed, estimated, or only suggestive.

Decide what would disprove the setup

Squeeze stories are sticky because they can always absorb another anecdote. A stronger workflow writes the invalidation conditions before the story gets emotional. Maybe short interest falls sharply, liquidity improves, the catalyst passes without pressure, price momentum breaks, or borrow conditions normalize. Whatever the case, the file should state what would make the setup less interesting.

  • Define the event or metric that would remove the name from the watchlist.
  • Avoid escalating a ticker only because social attention increased.
  • Compare new data with the original reason the setup was saved.
  • Use position-sizing and risk notes outside the data file; the data file is not a trade plan.
  • Archive expired setups so future research does not inherit an old narrative.

This makes the workflow less dramatic and more useful. The aim is not to predict a squeeze from one metric; it is to keep a precise evidence trail around a risky, often misunderstood setup.