Your January Forecast Didn't Survive H1. Here's the Rolling Reset H2 Demands.

If your annual plan assumed a weaker dollar through 2026, you weren't being careless. You were in good company. Goldman Sachs built its 2026 FX outlook around continued dollar weakness, stating plainly that it expected the dollar to keep softening as demand for US assets diminished. 

JPMorgan's research team, in its 2026 market outlook, described the risks to the dollar as skewed to the downside, with any dollar strength likely to be bounded while weakness stayed open ended. Two of the most resourced research desks in the world built their house views on the dollar continuing to slide. It didn't.

So, if Goldman and JPMorgan's own economists can build a consensus around a scenario that fails to show up, a single annual forecast built by any finance team, however good, carries the same exposure. It’s a simple example of how a plan which is built on one view of the world, refreshed once a year, has nowhere to go when that view breaks. A rolling forecast doesn't have that problem, because it was never betting on one view holding for twelve months in the first place.

What Happened in H1?

Three separate assumptions gave way inside the same six months, each in a different part of the business. None of them were reckless bets, but just reasonable calls that stopped being true.

Dollar Goes Against Consensus Outlook

The Federal Reserve held rates through the first half of the year and signaled it was open to hikes rather than the cuts that both Goldman Sachs and JPMorgan's outlooks were leaning on. That outlook was driven largely by an energy led inflation spike following the conflict in the Middle East, which pushed oil and gas prices sharply higher and closed off the room for the rate cuts the bearish dollar calls depended on. Any FX hedge, overseas revenue assumption, or cost of capital estimate built on this forecast consensus needed revisiting well before H1 closed, and needed revisiting again as the year goes on.

Tariffs Impact Working Capital

Across several sectors, tariff costs are settling into inventory rather than flowing straight through as an expected cost increase, quietly stretching working capital long before the impact ever shows up in quarterly gross margin. That's a different problem to plan for than a simple cost line. It's cash tied up in stock and a working capital cycle that no longer matches the assumptions baked into January's model.

Oil Volatility and Geopolitical Risks

Treasury yields have recently fallen and oil prices have climbed on renewed Middle East supply threats, with the 30 year bond yield hovering near 5%, a level it hadn't closed above since early June. At the same time, many companies are issuing new debt to fund AI infrastructure, and heavy Treasury supply is adding to an already jumpy rates market. Whether or not your business touches oil directly, that combination of energy price shocks and changing rate expectations moves your discount rates, your FX hedges, and your cost of capital in the same quarter.

Deloitte's Q1 2026 CFO survey captured the mood well. Concern over geopolitical risk hit an all time high of 79% following the conflict in the Middle East, with CFOs specifically flagging disrupted energy supplies and higher energy prices as a direct risk to their businesses. All of this shows just how many moving parts a forecast needs to account for, and why a flexible, rolling forecast can be a more appropriate way for 2026 and beyond.

Why The Static Forecast Couldn't Keep Up

None of this is a forecasting failure in the sense of bad modelling. An annual plan encodes a single set of assumptions about FX, energy costs, and rates, then gets revisited on a fixed schedule regardless of what's actually changing in the world. 

By the time March's actuals get reconciled against January's assumptions, the assumptions themselves are already out of date, and the fix isn't waiting for a better forecast. What’s needed is to build a process that doesn't depend on getting the call right in the first place, which is exactly what a rolling forecast is designed to do.

The Rolling Reset Playbook

As we’ve mentioned, the fix is replacing the annual cycle with a rolling forecast built on two horizons that talk to each other.

Dual Rolling Forecast

The first step is to run a 13 week direct forecast alongside a 12 month rolling view. Both should be rebuilt from live bank data rather than static exports. The 13 week forecast handles near term liquidity with precision, drawing on actual receipts and payments rather than projected averages. Each week the oldest period drops off, a new one gets added, and the forecast is checked against what actually happened. That variance loop is what keeps the model honest as conditions shift, rather than waiting for a quarterly reforecast to catch up.

Build Scenario Branches

Not a generic best case and worst case built around a single consensus call. FX, energy and commodity costs, and interest rates each deserve their own branch with explicit triggers, not a single blended ‘downside scenario’ that blurs which variable is actually driving the outcome. 

If oil moves 10%, what happens to your cost base and your customers' demand? If the dollar breaks back above or below a given level, what happens to your hedges and your overseas revenue when it converts home? If the Fed's tone shifts from cuts to hikes, what happens to your cost of debt and your capital allocation plans. To make this level of detail feasible, automated scenario planning is a must, so that each variable can update automatically rather than requiring a fresh spreadsheet every time a bank revises its house view.

Rebuild Continuously

Not a monthly export. The lag of your static forecasts is a feature, not a bug. If your starting point each month is a manually reconciled spreadsheet pulled from three bank portals, you are structurally incapable of reacting inside the quarter, whatever the consensus view happens to be at the time. Real time, API connected bank data removes that lag, so the 13 week and 12 month views are always built from what's actually in the accounts rather than what someone exported two weeks ago.

Analyze surprises daily, not quarterly

A rolling forecast is only as useful as the signals feeding it. Three things are worth instrumenting now, before the next consensus call breaks.

First, track FX exposure against the specific pairs and levels that affect your business, not a single bank's house view or the headline dollar index. Teams that built their H1 planning entirely around one forecaster's call, however credible the desk, had no fallback when the Fed's hold caught that call out.

Second, tag tariff related costs separately in your cash data as they hit, rather than waiting for them to surface in quarterly gross margin. 

Third, set an explicit rate and energy trigger that automatically flags when your scenario branches need reassessment, rather than relying on someone noticing a headline or a bank's revised outlook. Treasury teams that built this kind of automatic trigger into their process moved faster than teams still working from a single annual view when oil and rates moved together in early July.

Trovata rebuilds your 13 week and 12 month forecasts directly from live, multi bank data, with scenario branches that update as FX, rates, and costs move rather than waiting for the next reforecast. If you want to see what a rolling forecast looks like on your own numbers, book a demo with our team.