Interim CFO long range financial planning works best when ownership is split deliberately: the interim CFO owns the models, the forecasts, and the pacing of the work, while the board and the permanent leadership team own the decisions that commit the company. The condition is a written mandate. Without one, planning stalls every time a signature is needed.

Splitting the work between the interim CFO and your team

The cleanest split I know is this: the interim CFO builds and maintains the plan, and your team decides what goes into it. Someone working in an interim capacity can model scenarios, pressure-test assumptions, and tell you that your cash runway looks thinner than you think. What that person should not do, alone, is choose which scenario the company commits to. That choice belongs to the people who stay.

In practice, the interim CFO owns the analytical layer. That means the forecast model, the assumptions log, the variance explanations, and the calendar that keeps the plan refreshed. Your team owns the inputs and the commitments: sales targets they believe in, hiring plans they will actually execute, and pricing changes they can defend. When those two halves stay separate, the plan stays honest.

The blur usually shows up in week three or four. The interim CFO, trying to be useful, starts answering questions the CEO should answer, or the CEO starts deferring operating decisions because "finance is looking at it." Both habits are expensive. A quick fix is a standing agenda item in the weekly finance meeting: what did we decide this week, and who decided it?

A report is easier to use when people know where the figures came from. Make the process visible. If the interim CFO produces a rolling cash forecast, ask for one page that shows which numbers came from the accounting system, which came from managers' estimates, and which are pure assumptions. That single page does more for trust than any polished deck.

One more boundary worth setting early: the interim CFO is not the fallback for routine work that already has an owner. If your controller closes the books, the interim CFO reviews and uses them. Letting strategic planning absorb the close is the most common way both suffer.

What the first 90 days should actually produce

The first three months should end with a working forecast, a short list of agreed priorities, and a decision log. Not a finished five-year plan. Long range planning in an interim engagement is iterative, and the early deliverables are the ones that make later iterations cheap.

A reasonable sequence looks like this:

A diagnostic of what exists: the current model, the last budget, the quality of the cash forecast, and where the numbers disagree. A thirteen-week cash forecast, refreshed weekly, as the anchor for everything else. An assumptions log that names who owns each assumption. A short list of two or three planning priorities, agreed with the CEO and the board. A decision log that records what was decided, by whom, and when.

The diagnostic matters more than people expect. I have seen engagements lose a month because everyone assumed the existing model was fine, and it turned out the revenue tab referenced a product line the company had retired. Opening the model and reading it aloud, line by line, is unglamorous and saves weeks.

Thirteen weeks is a common cash forecast horizon because it is long enough to see a problem coming and short enough that the estimates stay grounded. From there, the longer range model can extend quarter by quarter, with each quarter's assumptions tied to something observable: a contract renewal, a hiring plan, a payment schedule.

By day ninety, you should be able to answer three questions without opening a spreadsheet: how much cash do we expect to hold at the end of the quarter, what are the two biggest assumptions that could move that number, and who owns each of those assumptions. If those answers exist in people's heads and not just in a file, the first ninety days did their job.

Writing a mandate that answers who decides

A mandate is a short document, ideally one page, that says what the interim CFO can decide alone, what requires the CEO, and what goes to the board. Without it, every ambiguous question becomes a negotiation, and negotiations consume exactly the senior attention the engagement was supposed to free up.

Three tiers cover most situations. The interim CFO decides analytical matters: model structure, forecast method, what counts as a variance worth explaining. The CEO decides operating commitments inside the plan: hiring timing, spending trade-offs, which scenario becomes the working budget. The board decides the questions that change the company's direction: taking on debt, raising capital, or committing to a sale process.

The mandate should also name what is out of scope. If the engagement is about planning and investor reporting, say so, and say who covers payroll, the monthly close, and audits in the meantime. Scope creep into routine accounting is the quiet failure mode: the strategic work slips because the interim CFO is untangling a vendor reconciliation.

Put review points in the mandate too. A monthly conversation between the CEO and the interim CFO, against the deliverables list, keeps the engagement from drifting. Ask how routine work is covered when responsibilities shift, and the answer will tell you whether the mandate was written for the real organization or the org chart.

One caution: a mandate is not a control system, and companies differ in what they already have. If your organization has signed approval thresholds, keep them and slot the interim CFO in. If it does not, the mandate is not the place to build a full controls framework; it is the place to make decision rights visible while the planning work happens.

Three ways to assign planning ownership, compared

Companies assign long range planning ownership in three common ways, and the right choice depends on internal capacity and how urgent the financing or transition pressure is. None is universally better; each buys something and costs something.

ApproachWho holds the modelBest suited forMain risk

Interim CFO owns the plan end to endThe interim CFO, with weekly review by the CEOA leadership vacancy with financing or transaction pressureKnowledge leaves when the engagement ends Interim CFO leads, internal manager co-buildsShared, with the internal manager running the model by month fourA growing company with a capable controller or finance managerSlower start while the co-builder comes up to speed Interim Chief Financial Officer CFO advises, internal team buildsThe internal team, with the interim CFO reviewing assumptionsAn established team that needs challenge, not capacityThe plan reflects old habits unless the challenge is real

The middle row is the one I would weigh most carefully, interim chief financial officer because it solves the handoff problem while the engagement is running instead of after it. The cost is a slower first month: the internal manager spends real hours in the model, and the interim CFO spends real hours explaining why each tab is built the way it is.

The first row makes sense when the pressure is immediate. If a lender is asking for projections next month, you want the fastest path to a defensible forecast, and you accept that knowledge transfer becomes a deliberate project later rather than a byproduct.

The third row fails quietly when the review is polite. An advisor who reads the assumptions and says "looks reasonable" every month has not changed anything. If you choose this approach, ask the advisor to write down, each month, the one assumption they would change and why. That habit keeps the challenge honest.

Connecting the long range plan to monthly routines

A long range plan that lives in its own file, updated once a year, is a decoration. The whole point of interim finance leadership is to wire the plan into the routines the company already runs: the close, the monthly package, the weekly cash meeting. That wiring is design work, and someone has to own it.

Start from the close. The monthly close produces actuals, and the plan consumes them. The connection point is the variance review: each month, the plan's assumptions get compared to what happened, and the people who own each assumption explain the gap. This is where a plan earns credibility or loses it.

The weekly cash meeting is the second connection. It should be short and concrete:

What did cash actually do last week, versus the thirteen-week forecast? Which receipts or payments moved, and interim chief financial officer by how much? Does anything in the next four weeks need a decision now? What assumption, if any, needs to change in the long range model?

Notice the last item. Most weekly cash meetings stop at item three, which keeps the short-term forecast honest but lets the long range model drift. Ten minutes of item four is what keeps the two views of the company telling the same story.

The handoffs deserve as much design as the meetings. Who updates the model when the sales director revises a pipeline estimate? Who tells the interim CFO that a contract payment slipped? In a small team these handoffs happen informally, and informality works until someone is out for two weeks. Ask how routine work is covered when responsibilities shift, then write the answer into the calendar.

None of this requires a specific system. Companies run this pattern in ordinary spreadsheet software, in dedicated planning tools, or both. What matters is that the path from an operating event to the plan is visible: an event happens, someone records it, the forecast moves, and the change is explained. Make the process visible and people stop arguing about whose numbers are right.

Keeping investor and board reporting aligned with the plan

Investor reporting fails in a predictable way: the board package shows one set of expectations and the planning model holds another. When the two disagree, the board meeting becomes an archaeology dig, and the finance team spends the week before it reconciling spreadsreads instead of thinking. The fix is structural, not heroic.

One set of numbers should feed both. The planning model holds the forecast of record; the board package quotes it directly, with a short bridge from last period's forecast to this one. A bridge can be three lines: here is what we expected, here is what changed, and here is who owns the change. Investors and directors can work with revisions. What they cannot work with is silence about why the numbers moved.

The interim CFO's role here is ownership of consistency, not ownership of the message. The narrative about performance belongs to the CEO. The finance leader's job is to guarantee that every figure in that narrative traces back to a source someone can name: the accounting system, a signed contract, or a documented assumption in the model.

Timing matters as much as content. If the board meets monthly, the plan should be refreshed before the package goes out, not after, so directors are never reacting to a model that is already two weeks stale. In a financing process, the same discipline applies to lender or investor requests: agree once on the base case, then give everyone the same base case with clearly labeled scenarios on top.

For revenue recognition, name the standard you follow, such as ASC 606 in the United States, and make sure the plan's revenue assumptions use the same recognition logic as the reported figures. A forecast that books revenue on cash receipt while the books recognize it over time will produce a variance nobody can explain, and explaining variances is the whole job.

A last practical check: keep an assumptions page inside the board package itself. Directors who can see the assumptions ask better questions and grant more patience when reality moves. Reporting that hides its foundations invites suspicion precisely when the company most needs credibility.

Making the handoff to permanent leadership real

The handoff starts on day one, or it does not start at all. Interim finance leadership that ends with a farewell email and a folder of files has transferred artifacts, not capability. The permanent leader, whether a newly hired CFO or a controller stepping up, should be inside the work while it happens.

The concrete mechanics are simple and easy to skip. The interim CFO maintains documentation as the plan is built, not at the end: a map of the model, the assumptions log with named owners, the decision log, and the meeting rhythm with its standing agenda. Each of these should read like something a successor could pick up on a Monday morning.

A useful test is the vacation test. If the interim CFO were unreachable for two weeks, could your team refresh the forecast, explain the variances, and answer a director's question about the model? Every gap the test reveals is a handoff task, and it belongs on the same priority list as the planning work itself.

Involve the successor in the routines early, in this order:

Observes the weekly cash meeting and the monthly variance review. Runs the meetings with the interim CFO present as backup. Owns the model refresh for one full cycle, including the board package figures. Takes the board or investor questions directly, with a debrief afterward.

Companies sometimes worry that this slows the engagement down. It does, modestly, and that is the correct trade. An engagement that ends with a brilliant model nobody can run has solved this quarter's problem and created next year's.

The mandate should say when the interim engagement ends, or at least what "done" looks like. A clean ending is a permanent leader running the cycle unassisted, documentation current, and the board briefed on what changed during the engagement. Anything short of that leaves the company renting a capability it meant to build.

The costly mistake: leaving decision rights unwritten

The most expensive mistake in this arrangement is not a bad forecast. Forecasts get revised; that is what they are for. The mistake is leaving decision rights unwritten, so that during the exact weeks when a lender or a buyer is pressing for answers, the company is negotiating internally over who can commit to what.

It shows up in small ways first. The interim CFO softens a projection because nobody confirmed whether the hiring freeze is real. The CEO tells a director that a plan is "in review" because the mandate never said who signs the working budget. Each ambiguity costs a few days, and days compound when financing deadlines are involved.

Avoiding it takes one page and one meeting. Write the three decision tiers, name the out-of-scope work and who covers it, list the deliverables for the first ninety days, and put the page in front of the CEO and the board chair for explicit agreement. Revise it monthly if the situation changes.

Then make the process visible. Keep the decision log current, keep the assumptions log owned by name, and let the weekly cash meeting end with the question that guards the whole arrangement: is there any decision pending that nobody clearly owns? Asked every week, it stays a small question. Asked for the first time in a crisis, it becomes an expensive one.