SEC Rule 10b5-1 Plans Explained — Why Pre-Scheduled Insider Trades Aren't Signals

How 10b5-1 plans work

Rule 10b5-1 was adopted by the SEC in 2000 to provide corporate insiders with an affirmative defence against insider-trading liability for transactions made pursuant to a pre-arranged trading plan. The logic: if an insider commits to a specific trading schedule at a time when they have no MNPI, the trades that later execute under that schedule cannot be "on the basis of" MNPI even if the insider subsequently acquires such information.

Plan adoption requirements

To qualify for the Rule 10b5-1 safe harbour, a plan must be adopted at a time when the insider is not aware of MNPI about the issuer or its securities. The plan must specify in advance either:

• The amount of securities to be purchased or sold and the price, OR
• A formula or algorithm for determining amount, price, and timing (e.g., "sell 5,000 shares on the first trading day of each calendar month"), OR
• Delegated discretion to a broker — giving the broker binding instructions that do not allow the insider to later influence timing or volume.

In practice, the vast majority of 10b5-1 plans use a formula-based approach, often tied to regular intervals (monthly) or price triggers (sell X shares when the price exceeds $Y). This makes the trade pattern visible in Form 4 data — a regular cadence of same-size sales every month is almost certainly a scheduled plan even if the Form 4 footnote is ambiguous.

Execution mechanics

Once a plan is in place, the trades execute automatically without requiring any instruction or involvement from the insider. The broker executes per the plan parameters regardless of news events, earnings releases, or changes in the insider's personal views. The insider typically cannot modify or cancel the plan while in possession of MNPI — doing so would constitute improper conduct. After the 2023 amendments, there are stricter limits on modifications even outside blackout windows.

2023 SEC amendments — what changed

In December 2022, the SEC adopted significant amendments to Rule 10b5-1 that took effect in February 2023. These were the most substantial changes to the rule since its adoption in 2000, motivated by widespread academic and press reporting on insiders using 10b5-1 plans opportunistically.

Mandatory cooling-off period

The most impactful amendment: insiders must now wait a mandatory cooling-off period between adopting a new plan and the first trade under that plan:

• Executive officers and directors: the later of 90 days after plan adoption or the trading day after the issuer files its next quarterly (10-Q) or annual (10-K) report after plan adoption. Effectively, most executives must wait 90 days to several months.
• Other insiders (non-officers/non-directors): 30 days after plan adoption.

The cooling-off period closes a well-documented loophole where executives adopted plans immediately after receiving positive MNPI, waited just a few weeks, and then traded at highly profitable prices. The 90-day window makes this abuse significantly harder.

One active plan at a time

The 2023 amendments restrict each insider to a single active 10b5-1 plan at a time (with a narrow exception allowing a second plan structured as a "sell-to-cover" for tax obligations). Previously, insiders could hold multiple overlapping plans and execute from whichever was most advantageous — a practice that effectively converted the plans from pre-commitment devices into optionality positions.

Single-trade plan limits

Insiders are now limited to one "single-trade plan" per year. A single-trade plan — a plan that results in just one transaction — is a common structure used for large block sales. The one-per-year limit prevents serial single-trade plans that mimic discretionary trading under the cover of the safe harbour.

Mandatory disclosure in issuer filings

Post-2023, issuers must disclose the adoption, modification, and termination of 10b5-1 plans by executive officers and directors in their quarterly (10-Q) and annual (10-K) filings, including plan adoption dates. This creates a new data source for tracking plan behaviour beyond what appears in individual Form 4 footnotes.

Why 10b5-1 plan trades are less predictive

The core argument is simple: a trade that executes on autopilot according to a schedule set months ago cannot carry information about the insider's current view of the company. The trade is a mechanical output of a pre-set formula, not a discretionary decision.

Academic evidence

Multiple academic studies have measured the return predictability of plan trades vs non-plan trades directly. Jagolinzer (2009) and subsequent work consistently finds that transactions disclosed as made under 10b5-1 plans have significantly lower forward-return predictive power than non-plan transactions, controlling for insider role, company size, and time period. The alpha of insider trading — which is modest but measurable in aggregate — comes almost entirely from the non-plan subset.

The volume effect

At large-cap companies, 10b5-1 plan transactions account for the majority of all Form 4 sales volume. Senior executives at companies like Apple, Microsoft, or Amazon hold equity worth hundreds of millions of dollars and systematically liquidate through scheduled plans. If you do not exclude plan trades, the Form 4 signal for large-cap companies is dominated by mechanical diversification, not informative insider intent.

The purchases question

10b5-1 plans are rarely used for purchases — they are almost exclusively a vehicle for selling. Insiders who want to buy shares on a schedule (e.g., as part of a dollar-cost-averaging programme) could technically use a 10b5-1 plan for purchases, but this is uncommon because purchases do not carry the same legal risk as sales. In practice, if you see a Form 4 purchase marked is10b5Plan: true, treat it with the same scepticism as a plan sale — the purchase was also pre-scheduled, not a fresh discretionary decision.

How to identify 10b5-1 plan trades in Form 4

The Form 4 filing form includes a dedicated field for 10b5-1 plan disclosure in Table I and Table II. The specific location is Column 9 of the non-derivative transactions table (Table I) — a checkbox labelled "Indicate if transaction was made pursuant to a contract, instruction, or written plan." If checked, the corresponding footnote typically reads something like: "This sale was made pursuant to a Rule 10b5-1 trading plan adopted on [date]."

In the raw EDGAR XML, this appears as the <rule10b51> element in the transaction record. A value of "true" or "1" indicates the plan designation. Pre-2023 filings used an inconsistent mix of checkboxes, footnote text, and XML flags — parsing them reliably requires handling all three variants.

Form4API parses and normalises the 10b5-1 designation across all three disclosure formats and exposes it as the boolean field is10b5Plan on every transaction record. Transactions where the designation was ambiguous or missing (common in older filings) are marked false — a conservative default that preserves potential signal rather than aggressively excluding uncertain records.

When to include vs exclude 10b5-1 trades

The general recommendation — and Form4API's default — is to exclude 10b5-1 plan trades from signal-quality analysis. But there are specific analytical contexts where including or specifically targeting plan trade data is valuable:

Exclude by default: signal analysis

For any analysis aimed at predicting forward stock returns — cluster buy signals, insider sentiment scoring, or discretionary buy/sell ratios — exclude plan trades. They are mechanically executed and carry no current-views signal. The /v1/signals endpoint excludes them by default for exactly this reason.

Include for: volume and liquidity analysis

If you are modelling insider-related trading volume, computing total shares outstanding changes from insider activity, or analysing the total number of shares sold by a specific executive over time, you need to include plan trades. Excluding them would understate the actual volume of insider-related transactions.

Include for: plan behaviour analysis

Analysing plan behaviour itself — adoption dates, modification patterns, cancellation frequency, execution vs non-execution rates — requires including plan-designated transactions. Post-2023, the mandatory issuer disclosure in quarterly filings creates additional metadata for this analysis beyond what appears in Form 4 alone.

Edge case: plan cancellations and accelerations

An insider who cancels an active 10b5-1 plan without executing it — particularly when the stock subsequently rises — may be implicitly expressing a bullish view (or was legally prevented from cancelling during a MNPI window). Similarly, an insider who adopts a new plan immediately after the mandatory cooling-off expires and sets a relatively aggressive sell schedule may be sending a directional signal through plan design. These meta-signals are subtle and require contextual judgment. To query plan transactions, add include_10b5_1=true to any /v1/signals request, or filter /v1/transactions client-side on is10b5Plan: true.

Programmatic access — filtering 10b5-1 trades

Form4API exposes the is10b5Plan boolean on every transaction returned from /v1/transactions. Here are the common patterns:

Query transactions and filter client-side

# Fetch all open-market purchases for TSLA
curl "https://api.form4api.com/v1/transactions?ticker=TSLA&code=P&per_page=50" \
  -H "X-Api-Key: $FORM4API_KEY"

# Each record in the response includes:
# {
#   "transactionCode": "P",
#   "is10b5Plan": false,  // <- filter on this field
#   "shares": 5000,
#   "pricePerShare": "214.50",
#   ...
# }

Filter the response to is10b5Plan === falseto retain only discretionary purchases with no pre-arrangement flag.

Use pre-filtered signals endpoint

# Cluster buy signals — 10b5-1 trades excluded by default
curl "https://api.form4api.com/v1/signals?type=cluster_buy" \
  -H "X-Api-Key: $FORM4API_KEY"

# Override to include 10b5-1 trades (e.g., for plan analysis)
curl "https://api.form4api.com/v1/signals?type=cluster_buy&include_10b5_1=true" \
  -H "X-Api-Key: $FORM4API_KEY"

The Free tier covers 15,000 calls per month with no credit card for /v1/transactions. The /v1/signals endpoint is available on Pro at $49/month (includes 1.5M calls and webhooks). See /docs for the full parameter reference.

Real-time alerts excluding plan trades

If you want real-time notifications of discretionary insider buys with plan trades already excluded, set up a webhook subscription and filter on is10b5Plan: false in your webhook handler. Webhooks are HMAC-SHA256 signed, retry automatically on failure, and deliver within 30 seconds of API availability. Configure subscriptions on the dashboard webhooks page.

Frequently asked questions