The CME FedWatch Tool is a market-pricing monitor. It uses prices of 30-Day Federal Funds futures to estimate the market-implied probabilities of possible interest-rate outcomes at upcoming Federal Open Market Committee meetings. It does not publish the Federal Reserve’s own forecast, nor does it guarantee what the FOMC will decide. That distinction matters because FedWatch translates a traded futures market into an easily read set of probabilities. The numbers reflect the pricing embedded in those contracts at a given time, using CME’s stated methodology and assumptions. They can change as futures prices change. What the CME FedWatch Tool measures CME Group’s FedWatch Tool presents market-implied probabilities for upcoming FOMC rate outcomes. The underlying instrument is the 30-Day Federal Funds futures contract, rather than a survey of economists or a direct statement from Fed officials. The FOMC is the Federal Reserve committee that sets the target range for the federal funds rate. FedWatch starts somewhere different: with the price at which market participants trade contracts tied to the average effective federal funds rate during a particular calendar month. CME then converts the information in a sequence of contract months into possible outcomes around scheduled policy meetings. This makes the tool useful for observing how the market is positioned around a meeting. A displayed probability is best understood as an estimate inferred from futures pricing, not a declaration that the central bank is likely or required to take a particular action. EFFR and the FOMC target range Two related rates sit at the center of the calculation, and they should not be treated as identical. The FOMC sets a target range for the federal funds market. The effective federal funds rate, or EFFR, is a reference rate calculated by the Federal Reserve Bank of New York as the volume-weighted median of overnight federal funds transactions. In other words, the target range is the policy setting, while EFFR is an observed market rate. The New York Fed’s EFFR methodology explains that the rate is derived from overnight federal funds transactions; the FOMC’s target range guides the market in which those transactions occur. FedWatch relies on futures linked to EFFR because the futures contract settles against that observed rate. Its output is then expressed in terms readers recognize from FOMC decisions: target-range outcomes, including a possible unchanged setting, hike or cut. FedWatch presents a structured estimate of market pricing, not a direct measurement of policymakers’ intentions. CME’s methodology can make that conversion because policy and EFFR are closely connected, though the conversion remains an analytical step. How a Fed Funds futures price becomes an expected monthly rate A 30-Day Fed Funds futures price follows a simple quotation convention: it is priced as 100 minus the expected average EFFR for the contract month. CME states that the contract’s final settlement is based on the arithmetic average of daily effective federal funds rates in that month. For a simple hypothetical illustration, a futures price of 96.00 corresponds to an implied average monthly EFFR of 4.00%: 100 minus 96.00. A price of 95.75 would correspond to 4.25%. These examples show the quotation arithmetic only; they are not forecasts or current market prices. The monthly-average feature is crucial around an FOMC meeting. A contract month may include days before and after the policy decision. Its price therefore reflects the expected average EFFR across the whole month, not solely the rate expected immediately after the meeting. That is why a FedWatch-style calculation needs more than one subtraction from a futures price. It must account for the calendar placement of the meeting and infer the rate outcome consistent with the monthly averages priced in the relevant contracts. CME’s description of Fed Funds futures sets out both the 100-minus-price convention and the final-settlement basis. How FedWatch turns monthly pricing into meeting probabilities CME’s methodology converts changes implied by futures pricing into probabilities by using simplifying assumptions. It assumes policy moves occur in 25-basis-point increments and that EFFR responds proportionally to changes in the target rate. Those assumptions allow the tool to map an implied EFFR change into discrete policy possibilities. Rather than presenting a single fractional outcome, FedWatch can assign estimated probabilities across possible target-range results at an individual meeting. The traditional calculation uses a probability tree. It first derives probabilities for individual meetings from the relevant monthly futures contracts, then combines successive meeting outcomes to calculate cumulative probabilities for rate levels further into the future. A simplified sequence helps illustrate the distinction. For the next meeting, the market may price a range of possible outcomes. For a later meeting, the result depends not only on what happens then, but also on the path taken at the earlier meeting. The probability-tree approach combines those branches to show the possible cumulative rate levels by the later date. This is also why a probability shown for a distant meeting should not be read as a stand-alone judgment on that meeting alone. It incorporates the path of possible intervening decisions under the model. CME describes the 25-basis-point and proportional-response assumptions, as well as the probability-tree framework, in its FedWatch methodology overview . Aggregated versus conditional probabilities FedWatch offers views that answer related but different questions. Confusing them can lead readers to mistake a cumulative expected path for the implied move at one particular meeting. The aggregated view measures the total number of hikes or cuts priced relative to the current target range. It is designed to show how far above or below the current setting the market has priced a future policy level. The conditional view is meeting-specific. It estimates the move at a meeting relative to the rate implied by the preceding contract month. Put simply, it focuses on the increment associated with that decision rather than the total change from today’s target range. Suppose a future date displays an outcome that is lower than the current range. In an aggregated reading, that reflects the total easing priced between the current point and that date. In a conditional reading, the displayed move for a particular meeting is assessed against the rate implied immediately before it. CME explains this distinction in its note on the aggregated FedWatch view . Neither display is inherently more authoritative. They are different ways of organizing the same broad task: translating futures-market pricing into an expected sequence of potential FOMC outcomes. CME educational visual introducing the FedWatch Tool and its use of Fed Funds futures to assess market expectations for FOMC rate moves. — Source: CME Group How to use FedWatch without treating it as a Fed forecast FedWatch can be a useful shorthand for what is priced in the Fed Funds futures market at a particular moment. It is especially helpful when readers want to see whether pricing has shifted toward a hold, a hike or a cut, and how that shift extends across several meetings. The percentages are estimates of futures-market pricing, not literal or objective odds that the FOMC will make a specific decision. That pricing may reflect risk premia, hedging demand, liquidity effects and expectation errors. In addition, the conversion rests on methodological assumptions, including CME’s use of discrete 25-basis-point policy increments. The Bank for International Settlements has noted the broader limitation in extracting expectations from market prices: prices can include compensation for risk and other market effects, rather than pure expectations alone. That does not make FedWatch uninformative; it means the estimates describe pricing, not certainty. A practical reading starts with the date and the view being displayed. Next, distinguish the probability of a move at one meeting from the cumulative policy level priced for a later meeting. Finally, compare changes over time as changes in market pricing, while keeping the underlying futures contract and the tool’s assumptions in view. FedWatch is therefore a translation tool. It turns prices tied to the monthly average EFFR into a standardized, meeting-by-meeting presentation of possible FOMC outcomes. The input is a futures market; the output is an estimate of what that market implies. Frequently Asked Questions Does the FedWatch Tool predict what the Federal Reserve will do? No. It estimates probabilities implied by 30-Day Federal Funds futures prices. Those prices can reflect market expectations as well as risk premia, hedging, liquidity conditions and other influences. What futures contract does FedWatch use? FedWatch uses 30-Day Federal Funds futures. These contracts are quoted as 100 minus the expected average effective federal funds rate for the contract month and settle using the arithmetic average of daily EFFR observations. Why do FedWatch probabilities change? The figures change when the prices of the underlying futures contracts change. Since the tool derives its estimates from market pricing, new trading conditions can alter the implied distribution of rate outcomes. What is the difference between aggregated and conditional FedWatch views? Aggregated probabilities show total hikes or cuts relative to the current target range. Conditional probabilities focus on the move at a specified meeting relative to the rate implied by the preceding contract month. What does a FedWatch probability of a rate move mean? It represents CME’s model-based estimate of the outcome implied by Fed Funds futures pricing under its assumptions, including 25-basis-point policy increments and a proportional EFFR response to target-rate changes. Disclaimer: This article is provided for informational purposes only. It is not offered or intended to be used as legal, tax, investment, financial, or other advice.
