Business analyst writing with laptop and smartphone showing trend graphs on a white desk.
FP&A

FP&A reforecast cadence lags the AI tools now running it

Midsize finance teams adopted AI for planning in about two years, but most still reforecast on a quarterly rhythm built for manual consolidation. The gap is now a governance problem CFOs own.

The FP&A reforecast cadence at most companies was designed around a constraint that no longer exists: the time it took humans to pull, scrub and consolidate the numbers. That constraint is gone, or at least badly weakened. CFO.com, citing research from Vena Solutions, reported that most midsized companies now use AI somewhere in their FP&A process, a sharp reversal from the same outlet's earlier finding that only 23% of FP&A practitioners were using AI at all. The tooling moved in roughly two years. The quarterly ritual did not move at all.

The adoption curve inverted faster than the planning calendar

Two data points from CFO.com frame the shift. The older one, now close to two years old, put AI use among FP&A practitioners at 23%. The newer one, based on Vena Solutions research, describes AI use in FP&A as the majority position among midsized companies. Treat the pair as direction rather than a precise delta, because the surveys sample different populations and ask different questions. The direction is still unambiguous. CFO.com also reported that FP&A software implementation more than doubled in 2024, which is the capital-spending signature of exactly that kind of inversion.

What did not change in the same window is the operating rhythm. Most finance organizations still run an annual plan, a quarterly reforecast and a monthly variance review, with the reforecast scheduled to land after close because close was historically the gating item. Vendor roundups for 2026 from Prophix and Jedox are uniformly pushing continuous planning, and PwC's leadership center is running a live 2026 CFO agenda that points the same way. The marketing has converged on continuous. The calendars have not.

Once a model can refresh a forecast in hours, the binding constraint stops being speed and becomes decision rights.

Why the bottleneck moved from model speed to decision rights

When consolidation took three weeks, cadence was a capacity question. You reforecast quarterly because you could not afford to do it monthly. Once a model can refresh a driver-based forecast in hours, the limiting factor becomes something else entirely: nobody has defined what a refreshed number means or who is allowed to act on it.

That is a governance gap, not a technology gap, and it produces three specific failures. First, no trigger rule. The model can detect a material shift in bookings or input costs, but there is no documented threshold that converts detection into an official reforecast. Second, no approval path. If the system moves a revenue line, it is often unclear whether that number is a draft, a scenario or the number of record, and who signs it. Third, no reporting convention. A board that was trained on a plan versus actual story starts receiving something closer to a live feed, with no agreement on which version is the baseline.

None of these are solved by better software. They are solved by writing down the rules, which is work the CFO owns and cannot delegate to the planning system administrator.

Designing a cadence that is continuous where it matters

The useful reframing is that cadence is not one setting. It is at least three, and they can run at different speeds. The sensing layer, where the model watches drivers and flags variance, can run continuously with no governance overhead because nothing it produces is binding. The decision layer, where a number gets approved and resources actually move, should be event-driven and tied to explicit thresholds. The reporting layer, which is what the board and lenders consume, usually benefits from staying periodic and stable, because comparability is the whole point.

In practice that means defining what counts as a trigger before the quarter starts. A pipeline coverage ratio falling below a stated level. A key input cost moving more than a set percentage. A top-ten customer churning. Each trigger names an owner, a response window and the approval level required to make the revised figure official. Companies that skip this step tend to end up in one of two bad states: a team that reforecasts constantly and commits to nothing, or a team with expensive continuous tooling that still only produces four numbers a year.

What it does to headcount shape and the close-to-forecast handoff

A cadence redesign changes the job description before it changes the headcount. If the model does the mechanical refresh, the marginal FP&A hire is less valuable for building the forecast and more valuable for interrogating it: understanding why a driver moved, pressure-testing the assumption set, and translating the result into an operating decision with a business partner in the room. That is a different hiring profile and a different compensation band.

It also forces a cleaner handoff between close and forecast. In a quarterly rhythm, the forecast waits for the close because the actuals anchor it. In a trigger-driven rhythm, the forecast may need to move before the books are final, which requires an agreed convention for using estimated actuals and an audit trail showing what was known when. Controllership and FP&A need to settle that boundary explicitly, otherwise the first off-cycle reforecast turns into a dispute about whose number is right.

The questions to answer before the next planning cycle

Five questions separate a genuine cadence design from a tooling upgrade. What events trigger an off-cycle reforecast, stated as thresholds rather than judgment calls? Who approves a figure the model moved, and at what dollar threshold does approval escalate? Which version of the forecast is the number of record, and where does it live? What does the board see, and how often, and is it a plan or a feed? And what is the documented treatment of estimated actuals in a mid-close reforecast?

None of these require a vendor decision. All of them require a CFO decision. The honest caveat is that the underlying adoption statistics here come from surveys with different populations and dates, and the most useful of them is several months old. The structural point survives the imprecision. Planning tooling got faster than planning governance, and only one of those two is something finance can fix without a purchase order.

Key takeaways

  • AI adoption in midsize FP&A flipped from minority to majority in roughly two years, according to CFO.com reporting on Vena Solutions research, while the quarterly reforecast rhythm stayed put.
  • Treat cadence as three separate layers: continuous sensing, event-driven decisions, periodic board reporting. They do not need to run at the same speed.
  • Write trigger thresholds before the quarter starts, each with a named owner, a response window and an approval level.
  • Settle the close-to-forecast handoff explicitly, including how estimated actuals are used and audited in a mid-close reforecast.
  • The marginal FP&A hire shifts from building the forecast to interrogating it, which changes the hiring profile more than the headcount.