All option guides
A DV01 ratio is a sensitivity record before it is ever a portfolio action11 min read

Treasury Futures Hedge Ratio by DV01

Learn how a Treasury futures hedge ratio compares cash-exposure and contract DV01, plus the CTD, basis, curve, roll, and rounding risks left over.

Prepared by Mark · Primary sources below

Direct answer

A dollar-weighted Treasury futures hedge ratio can begin by comparing the DV01 or BPV of an identified cash exposure with the implied DV01 or BPV of one named futures contract. CME expresses the basic relationship as BPV at risk divided by BPV of the contract. That ratio is a normalized sensitivity record, not a recommendation for a position direction or contract count, and it does not guarantee that the exposure will be offset.

Define the exposure and the objective before using a ratio

The numerator must identify what is at risk: one cash Treasury, a portfolio, or another rate-sensitive exposure. The denominator must identify a particular Treasury futures product and month. A broad “Treasury hedge” label does not show whether the two sides use the same currency, unit, valuation time, yield scenario, curve definition, or sensitivity convention.

The purpose also needs a separate record. A partial sensitivity reduction, a duration adjustment, and a full offset are different objectives. This guide does not select an objective, direction, or target percentage; it explains the information a ratio needs before those choices can be described.

DV01 and BPV defines the one-basis-point sensitivity record that must be normalized first.

Normalize the exposure DV01 and futures DV01

Match the valuation date and time, currency, notional or face-value unit, yield-shock size, curve or yield definition, and sign convention before comparing two sensitivities. A cash portfolio's dollar value per basis point cannot safely be divided by a futures number calculated from a different time, different unit, or different shock definition.

For a standard price-quoted, physically deliverable Treasury note or bond future, the contract sensitivity may depend on the current CTD security and conversion factor. Treasury futures DV01 sets out that contract-specific scope. It does not apply a delivery-basket relationship to every Treasury-related futures design.

Read BPV at risk divided by contract BPV as a sensitivity ratio

CME's Treasury education presents a simple dollar-weighted relationship:

Sensitivity ratio = BPV at risk ÷ BPV of the named futures contract

The output describes how two normalized one-basis-point sensitivities compare. It does not by itself set a long or short direction, decide what portion of an exposure should be changed, resolve a fractional-contract choice, or account for execution and account constraints. Those decisions require information outside a bare ratio.

Keep the numerator and denominator beside the result. A formula with two unlabeled DV01 values hides the conditions that decide whether it can be reproduced. Futures hedge ratio and basis risk adds the general distinction between a sensitivity ratio and the risks left after a hedge.

CTD, basis, curve, and roll differences can leave residual risk

The ratio does not make a cash Treasury or portfolio identical to a futures contract. In a standard deliverable contract, CTD and conversion-factor inputs can matter. The cash exposure and futures contract can also differ through basis, non-parallel yield-curve moves, liquidity, the delivery process, rolling to another month, and the time at which each value is observed.

Treasury futures basis explains why the cash reference and futures contract must remain distinct. Treasury futures roll shows why replacing one month with another creates a new contract record rather than preserving every nearby input unchanged.

Reconcile the ratio whenever the underlying record changes

Save the exposure source, futures product and month, price fields, observation times, DV01 or BPV units, CTD and conversion-factor inputs where applicable, the calculation result, any rounding, and the stated objective. Review the record when the contract month, cash holdings, price inputs, or methodology changes.

A disciplined record is more useful than a permanent hedge number. It makes clear what was measured, which assumptions were made, and which residual risks were not removed. It also prevents an old ratio from appearing more current or more complete than it is.

This guide describes a sensitivity-comparison framework. It does not recommend a futures position, hedge direction, contract count, portfolio adjustment, or rate view. Current contract specifications, prices, financing, margin, liquidity, account policies, and a user's objectives all matter in a real decision.

Common questions

What is a Treasury futures hedge ratio by DV01?

It is a way to compare the one-basis-point dollar sensitivity of an identified exposure with the one-basis-point sensitivity of a named futures contract after their measurement conventions have been matched.

Does the ratio tell me whether to buy or sell futures?

No. A ratio compares magnitudes under stated assumptions. Position direction and the objective for an exposure are separate choices that a bare ratio does not make.

Why must the futures contract month be included?

A futures contract is dated. Its price, delivery inputs, and sensitivity can differ from another month, so the denominator must identify the actual month being measured.

Does matching DV01 remove all Treasury risk?

No. Basis, curve shape, CTD inputs, time differences, liquidity, rolling, and other factors can create residual risk even when the stated DV01 values match.

Can I use a historical hedge ratio as a current number?

Not without checking every underlying input. The cash exposure, futures month, price fields, CTD data, conversion factor, valuation time, and methodology can all change.

Sources and further reading

Related guides