Futures First Notice Day And Contract Expiration Rollover Automation

Stop letting expiring contracts disrupt your trading. Master futures rollover automation and manage first notice day for ES, NQ, GC, and CL with this guide.

First notice day (FND) is the first date a futures contract holder may be required to take physical delivery of the underlying commodity. For automated futures traders, failing to account for FND and contract expiration can result in unwanted delivery obligations, forced liquidation by your broker, or trades executed on illiquid contracts. This guide covers how to build rollover automation into your futures trading system so you never get caught holding an expiring contract.

Key Takeaways

First notice day varies by instrument: ES/NQ futures expire quarterly, CL crude oil expires monthly, and GC gold has specific delivery months that require different rollover calendars.
Most brokers will liquidate positions 1-3 business days before first notice day if you hold a physically delivered contract, which can trigger fills at unfavorable prices.
Automating your rollover process means updating your TradingView alerts, webhook payloads, and symbol references to the new front-month contract before volume shifts.
Volume typically migrates to the next contract 3-8 trading days before expiration, and trading the old contract after this shift means wider spreads and worse fills.
Cash-settled contracts like ES and NQ don't carry physical delivery risk, but liquidity still drops sharply near expiration, making timely rollovers just as important for execution quality.

What Is First Notice Day in Futures Trading?

First notice day is the first business day on which a buyer of a futures contract can be notified by the exchange that they must accept physical delivery of the underlying commodity. For anyone running a futures first notice day automation setup, this date is the hard deadline by which long positions in physically delivered contracts must be closed or rolled to the next contract month.

First Notice Day (FND): The first date on which a clearing house may notify a long futures position holder of intent to deliver the physical commodity. For automated traders, this is the date by which your system must have already exited or rolled any affected positions.

Here's the thing most newer traders miss: FND only affects the buyer (long side) of physically delivered contracts. If you're short a physically delivered contract, you can actually be assigned delivery notice at any point during the delivery period. For cash-settled instruments like ES and NQ futures, there's no physical delivery at all. The contract settles to a final cash value. But that doesn't mean you can ignore expiration dates. Liquidity dries up near expiration regardless of settlement type, and your automated fills will suffer.

The CME Group publishes first notice day and last trading day calendars for every contract [1]. If you're running any kind of contract expiration automation, these dates need to be hardcoded into your system's calendar.

First Notice Day vs. Contract Expiration: What's the Difference?

First notice day and last trading day are two separate dates, and confusing them is one of the fastest ways to get into trouble with automated futures trading. FND is when delivery notices can begin; last trading day is when the contract stops trading entirely.

Last Trading Day (LTD): The final day a futures contract can be traded on the exchange. After this date, open positions are either settled in cash or proceed to physical delivery. For automation systems, this is the absolute latest a position can exist.DateWhat HappensWho It AffectsAutomation Action RequiredFirst Notice DayDelivery notices can be issued to long holdersLong positions in physically delivered contractsClose or roll long positions before this dateLast Trading DayFinal day to trade the contractAll open positionsAll positions must be closed or rolledVolume Rollover DateMajority of trading volume shifts to next contractAll traders seeking liquiditySwitch automation symbols to new front-month

For CL crude oil futures, first notice day falls roughly one month before the last trading day of the expiring contract. That's a wide window. For GC gold futures, FND is the last business day of the month prior to the delivery month. The timing varies enough between instruments that a one-size-fits-all rollover rule won't work. Your futures instrument automation setup needs instrument-specific rollover logic.

Most retail brokers don't want to deal with physical delivery at all. Brokers like AMP, Tradovate, and TradeStation will typically auto-liquidate positions in physically delivered contracts 1-3 days before FND. If your automation is still sending entry signals on an expiring CL or GC contract at that point, your broker may close the position at a bad price, or your new entries may get rejected entirely.

Rollover Dates by Instrument: ES, NQ, GC, and CL

Each futures instrument has its own expiration cycle and rollover timing. ES futures automation and NQ futures automation both follow quarterly cycles (March, June, September, December), while CL crude oil automation deals with monthly expirations. Knowing these patterns is the foundation of any contract expiration guide.

Front-Month Contract: The futures contract with the nearest expiration date and typically the highest trading volume. When traders say "roll," they mean moving from the current front-month to the next one.

ES and NQ (E-mini S&P 500 and E-mini Nasdaq)

ES and NQ are cash-settled contracts that expire quarterly. There's no physical delivery risk, but volume migrates to the next quarterly contract about 8 trading days before expiration, typically on the Thursday before the third Friday of the expiration month. The CME Group refers to this as "roll week." After the roll date, the expiring contract's volume drops by 70-90% within a day or two [1].

For ES futures automation, this means updating your TradingView chart symbols from something like ESH2026 (March) to ESM2026 (June) on or before the Thursday of roll week. If your alerts are still firing on the old contract, you'll be trading into thin liquidity with wider bid-ask spreads.

GC (Gold Futures)

GC gold futures automation is trickier because gold has an unusual contract calendar. While contracts exist for every month, the most liquid delivery months are February, April, June, August, October, and December. The first notice day for GC is the last business day of the month before the delivery month. Volume typically rolls 3-5 days before FND.

Because GC is physically delivered, holding a long position past first notice day means your broker may force-close your position. Your automation system needs to stop entering long GC trades at least 2-3 days before FND of each active delivery month.

CL (Crude Oil Futures)

CL crude oil automation requires the most frequent attention because crude oil contracts expire monthly. The last trading day for CL is three business days before the 25th of the month prior to the delivery month. First notice day is one business day after the last trading day. Volume rolls to the next month roughly 5-8 trading days before expiration [2].

Monthly expirations mean you're dealing with rollover automation twelve times a year instead of four. Miss one and you could end up with positions on a contract with almost no liquidity.

Micro Futures (MES, MNQ)

Micro futures automation follows the same expiration calendars as their full-size counterparts. MES rolls when ES rolls. MNQ rolls when NQ rolls. The rollover dates and process are identical. The difference is the tick value ($1.25 per tick for MES vs. $12.50 for ES), not the timing [1].

InstrumentExpiration CycleSettlementVolume Roll TimingFND RiskES / MESQuarterly (H, M, U, Z)Cash-settled~8 days before expiryNone (cash-settled)NQ / MNQQuarterly (H, M, U, Z)Cash-settled~8 days before expiryNone (cash-settled)GCEven months primaryPhysical delivery~3-5 days before FNDHigh for longsCLMonthlyPhysical delivery~5-8 days before expiryHigh for longs

How to Automate Contract Rollovers in Your Trading System

Automating contract rollovers involves three steps: knowing when to roll, updating your trading symbols, and verifying that your alerts and webhook payloads reference the correct contract. Here's how to handle each piece.

Step 1: Build a Rollover Calendar

Download the CME Group's expiration calendar at the start of each quarter [1]. For each instrument you trade, note three dates: the volume rollover date (when most traders switch), first notice day (for physically delivered contracts), and last trading day. Add these to whatever calendar or scheduling system you use. Some traders put alerts in their phone. Others build a spreadsheet that flags the next rollover date.

For CL crude oil automation, this means marking twelve rollover dates per year. For ES and NQ, it's four. For GC gold futures automation, it depends on which delivery months you trade, but typically six per year.

Step 2: Update Your TradingView Symbols and Alerts

If you're using TradingView for futures automation, your alerts are tied to specific chart symbols. When you roll from ESH2026 to ESM2026, you need to:

Change the symbol on your TradingView chart to the new front-month contract
Delete or disable alerts on the old contract symbol
Create new alerts on the new contract symbol
Verify your webhook payload references the correct contract in the symbol field

One approach some traders use is TradingView's continuous contract feature (e.g., ES1! for the front-month ES contract). This automatically references the most actively traded contract. The catch is that continuous contracts can create artificial price gaps at rollover points, which may trigger false signals on your indicators. Test this with your specific strategy before relying on it.

Step 3: Verify Your Automation Platform's Symbol Mapping

Your automation platform needs to send the correct contract symbol to your broker. If you're using a platform like ClearEdge Trading, check that the symbol in your webhook JSON matches what your broker expects for the new contract month. A mismatch here means your alert fires, your webhook sends, but your broker rejects the order because the symbol doesn't exist or has already expired.

Rollover Automation: The process of programmatically switching your trading system from an expiring futures contract to the next active contract month. This includes updating chart symbols, alerts, webhook payloads, and broker symbol mappings.

Step 4: Test Before the Roll Date

A few days before the scheduled rollover, set up your new alerts on the next contract month in paper trading mode. Confirm that alerts fire correctly, webhooks deliver, and your broker accepts the orders. Then on roll day, disable the old alerts and enable the new ones. This overlap period lets you catch problems before they cost real money.

Common Mistakes Traders Make Around Contract Expiration

Most automation failures around expiration come from forgetting to update something, not from the rollover concept itself being complicated. Here are the mistakes that come up most often.

1. Trading the old contract after volume has rolled. Your automation is still running on ESH2026 while 90% of volume has moved to ESM2026. Your fills are terrible because there's no one on the other side of your order. Slippage on low-liquidity contracts can be 2-4 ticks instead of the normal 0-1 ticks, which on ES means an extra $25-50 per contract in execution costs [3].

2. Forgetting to update the webhook payload symbol. You change your TradingView chart but forget to update the symbol field in your JSON webhook payload. The alert fires on the new contract, but the execution request goes to your broker with the old contract symbol. The order either fails or executes on the wrong contract.

3. Holding physically delivered contracts past FND. This mostly affects GC gold futures automation and CL crude oil automation. Your broker force-liquidates your position, often at a price you wouldn't have accepted. Some brokers charge additional fees for handling delivery-related closures.

4. Not accounting for the price gap between contracts. The new front-month contract trades at a slightly different price than the old one due to cost of carry, storage costs (for commodities), and interest rates. If your automation uses fixed price levels for stops or targets, those levels may not be valid on the new contract. Recalculate them based on the new contract's price.

Frequently Asked Questions

1. What happens if I hold a futures contract past first notice day?

For physically delivered contracts like CL and GC, your broker will typically force-liquidate your position 1-3 days before FND to avoid delivery obligations. Cash-settled contracts like ES and NQ don't have FND delivery risk, but liquidity drops sharply near expiration.

2. How often do I need to roll futures contracts?

ES and NQ roll quarterly (four times per year). CL crude oil rolls monthly (twelve times per year). GC gold primary delivery months roll six times per year. Your rollover frequency depends on which instruments your automation trades.

3. Can I use TradingView continuous contracts to avoid manual rollovers?

TradingView's continuous contract symbols (like ES1!) automatically reference the front-month contract. However, the price gap at rollover can trigger false signals on indicators that use historical price data, so test your strategy thoroughly with continuous contracts before relying on them.

4. Does first notice day affect micro futures like MES and MNQ?

MES and MNQ are cash-settled, so there's no physical delivery risk at FND. They follow the same quarterly expiration schedule as ES and NQ, and volume rolls on the same dates. You still need to update your symbols and alerts on schedule.

5. How do I know when volume shifts to the next contract?

Watch the volume column on both the expiring and next contract. When the next contract's daily volume exceeds the expiring contract's volume, the roll has happened. For ES and NQ, this typically occurs on the second Thursday before expiration [1].

Conclusion

A solid futures first notice day automation and contract expiration guide comes down to three things: know your dates, update your symbols, and test before you switch. Build a rollover calendar for every instrument you trade, update your TradingView alerts and webhook payloads before volume migrates, and verify everything works in paper trading before going live.

For instrument-specific automation settings including rollover handling for ES, NQ, GC, and CL, see the complete futures instrument automation guide. If you want to understand how rollover fits into broader automation setup, the automated futures trading guide covers the full workflow from strategy to execution.

Want to dig deeper? Read our complete guide to futures instrument automation for detailed instrument-specific settings, session times, and rollover procedures for ES, NQ, GC, and CL.

References

Disclaimer: This article is for educational purposes only. It is not trading advice. ClearEdge Trading executes trades based on your rules; it does not provide signals or recommendations.

Risk Warning: Futures trading involves substantial risk. You could lose more than your initial investment. Past performance does not guarantee future results. Only trade with capital you can afford to lose.

CFTC RULE 4.41: Hypothetical results have limitations and do not represent actual trading.

By: ClearEdge Trading Team | 29+ Years CME Floor Trading Experience | About Us

Heading 1

Heading 2

Heading 3

Heading 4

Heading 5

Heading 6

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.