Contract Identity and Expiry: Know What a Futures Price Describes

Begin with the full identity

An instrument label should identify the exchange, product, contract month, currency, quote unit and contract size. The observation also needs a field such as settlement or last trade, plus its timestamp. Two rows both described as crude oil can represent different delivery months, different products or different measurement times. Treating them as interchangeable can create a fictitious price change.

For a concrete specification, NYMEX Light Sweet Crude Oil futures use a 1,000-U.S.-barrel trading unit and dollar-per-barrel quotations. The exchange's Chapter 200 rulebook defines the contract rather than leaving those details to a chart label. These facts concern that particular futures product, not every instrument whose name refers to oil.

Distinguish a month from a trading deadline

A delivery-month label is not necessarily the month in which trading ends. Under the cited NYMEX Light Sweet Crude Oil rules, termination is tied to business days before the 25th calendar day of the preceding month, with a non-business-day adjustment. Exact dates therefore require the applicable exchange calendar and contract terms, not a universal assumption about month-end expiration.

Keep last trading time, any relevant delivery-notice events and the delivery period as separate fields. They serve different operational purposes. This guide does not provide a liquidation deadline or advice for a particular account. Exchange rules and intermediary restrictions must be checked for the actual contract and account before any real exposure is maintained near an operational deadline.

Understand the alternatives at expiration

CME's expiration and contract-roll lesson distinguishes offsetting, rolling and proceeding to settlement. Settlement can involve cash or delivery according to the product. These are different outcomes, not synonyms for a chart automatically advancing to its next month. A continuous chart can change its displayed contract without changing any position held in a separate account.

Rolling a hypothetical long position from one month to another means reducing the old contract exposure and establishing the new one. The new contract is not merely a renamed copy of the old contract. Its price, liquidity and remaining life can differ. A research explanation should record both identities even when the intended directional exposure remains unchanged.

Check a two-contract example

Suppose two hypothetical NYMEX Light Sweet Crude Oil delivery months are quoted simultaneously at $70 and $72 per barrel. One contract of each corresponds to 1,000 barrels, but their quote-based notionals are $70,000 and $72,000. The $2,000 difference compares two contract values at the same instant. It is not a gain or loss from a price move through time.

If yesterday's reference row used the $70 contract and today's row uses the $72 contract, the displayed increase might reflect a contract switch rather than a within-contract change. Without yesterday's and today's values for the same identified contract, the attribution remains unresolved. A ticker root alone cannot supply the missing evidence or justify treating the difference as an executable movement.

Preserve specifications alongside prices

Contract metadata should be versioned with the period it describes. A present-day specification page is not proof that every historical observation used the same tick, multiplier or settlement convention. For an educational historical example, state which specification supports the arithmetic and limit the claim accordingly. Material uncertainty about a specification should remain visible instead of being resolved by a convenient assumption.

A useful record separates native contract code from any vendor alias. It also retains exchange, delivery month, quote unit, multiplier, price field and source date. Aliases can change while the underlying economic identity does not, or remain familiar while a vendor's front-contract mapping changes. Maintaining both fields makes these differences explainable without requiring readers to decode a proprietary symbol convention.

Recognize what a reference series omits

A front-contract reference can support questions about its own sequence of published values. It cannot by itself establish the prices at which a specified contract was bought, sold or rolled. The gap is evidential: a reference observation and a broker fill are different records. More precise arithmetic on the reference series does not transform it into the missing execution record.

Where constituent mapping is unavailable, describe that limitation plainly. It may still be possible to compare deterministic directional rules on the reference series, provided the comparison is labelled accordingly. Do not silently assign the current contract month to the entire history or infer historical contract ownership from the series' present label. Both substitutions would manufacture identity information.

Ask the identity question first

Before interpreting an unusual observation, ask which contract, which field and which timestamp it represents. A surprising difference between adjacent rows may become ordinary once the two contract months are identified. Alternatively, identical-looking labels may conceal a stale field or unit conversion problem. Identity checks provide a disciplined starting point without asserting that every unusual observation is an error.

The practical reading habit is simple: do not let a recognizable commodity name substitute for a specification. Verify the stated identity and explain any series construction separately. This preserves the distinction between an economic topic, an exchange-listed obligation and a statistical reference. It also prevents later discussions of rolls, sizing and negative prices from resting on an undefined instrument.

Source record

1. NYMEX Rulebook Chapter 200: Light Sweet Crude Oil Futures
2. CME Group: Understanding Futures Expiration and Contract Roll