Interim CFO board meeting preparation is the work of getting financial reporting, forecasts, and decision materials ready for a board when the company has no permanent CFO in the seat. It usually starts with a short review of what the board expects to see, then a fixed cycle for the package, the pre-read, and the discussion. The goal is simple: directors get numbers they can trace, on time, every meeting.

What does an interim CFO actually own when a board meeting is coming up?

The short answer: everything that has to be true on paper before the meeting starts. An interim CFO preparing for a board session typically owns the financial package, the narrative that goes with it, and the answers to questions directors are likely to raise. That ownership is temporary and interim CFO for Manufacturing companies bounded, which is worth saying out loud. A fractional or interim leader covers the seat; the permanent hire, when they arrive, inherits the files and the rhythm.

In practice, the ownership breaks into a few buckets. First, the reporting package: financial statements, a cash view, and any variance commentary the board has come to expect. Second, the forward-looking material: a forecast, a runway view, and the assumptions behind both. Third, the logistics of the meeting itself, including the pre-read sent early enough that directors actually read it.

What an interim leader does not usually own matters just as much. Strategy beyond the finance mandate, personnel decisions outside the finance function, and commitments to investors or lenders generally stay with the CEO and the board. When I look at engagements that go sideways, the cause is rarely the quality of the spreadsheets. It is the fuzzy boundary: the board assumed the interim leader would run something, or the interim leader assumed the board had approved something, and nobody wrote it down.

A useful habit is to draft a one-page mandate at the start. It lists what the interim role decides alone, what it recommends, and what it only prepares. Boards appreciate this because it survives the transition. When the permanent CFO arrives, the same page gets updated with new names rather than rewritten from scratch, which keeps the process visible through a change that would otherwise scramble everyone's expectations.

The mandate also sets the tone for the meeting materials themselves. If the interim role only prepares and recommends, the package should label open items as recommendations, not decisions. Directors notice the difference. A report is easier to use when people know where the figures came from and who stands behind each recommendation, especially in a period when the finance seat itself is in transition.

One more piece of ownership deserves mention: the calendar. Interim leaders tend to work backward from the meeting date. The package locks a few days before, the pre-read goes out before that, and the underlying close work has to finish before the lock. Board meeting preparation fails most often because these dates were never put on a shared calendar in the first place.

How far ahead should the pre-read go out, and what belongs in it?

Enough ahead that directors can read it without clearing a weekend, and no so far that the numbers are stale. Many boards settle on a rhythm of roughly a week between the pre-read and the meeting, adjusted for how often the board meets. The exact gap matters less than the consistency. Directors plan around it, and the finance team plans around it, and after a couple of cycles nobody has to negotiate.

The contents depend on the company's stage and the board's appetite, but a solid pre-read for a growing company usually includes the statements for the period, a cash and runway view, commentary on variances the board will care about, and any decisions that require a vote, presented with the background those decisions need. If a financing conversation is on the agenda, the pre-read carries the relevant scenarios rather than surprising the board in the room.

Here is a check I find worth running before anything goes out: open the pre-read cold, the way a director would, and ask three questions. Where did each figure come from? What am I being asked to do with this page? What would I ask if I only had ninety seconds with it? If any page fails the third question, either the answer belongs in the document or the page belongs in the appendix.

Resist the urge to make the pre-read exhaustive. A packet that runs long does not get read carefully; it gets skimmed, and the skim misses the one thing that needed attention. A leaner structure tends to work better:

A short cover note naming the decisions requested and the topics open for discussion. The core financials with a page of plain commentary on what moved and why. The cash forecast with its main assumptions stated next to it, not buried. Background material for each agenda decision, limited to what a vote requires.

The appendix exists for the director who wants to go deeper, and that is fine. What matters is that the main body respects the reader's time. Interim leaders, precisely because they are new to the company, are often well positioned to trim a packet that has grown by habit. They have no history with any of the pages, so they can ask why each one exists without stepping on anyone's toes.

Timing inside the preparation window matters too. Close the books, then build the package, then write the commentary, in that order, with a buffer between each step. Compressing the buffer to squeeze in one more revision is how errors slip into board materials. The version that goes to the board should be the version the finance team has already reconciled, not the version that is one edit away from being reconciled.

Which reports does the board actually need, and which ones just add noise?

Boards need reports that support the decisions in front of them and the oversight they owe. That is a narrower list than most packets suggest. For a growing company, the core set usually comes down to the financial statements, a cash view with runway, performance against the budget or plan, and updates on anything the board has flagged as a priority, whether that is a financing process, a major hire, or a systems migration.

The noise creeps in through inertia. A report gets added during a crisis, the crisis passes, and the report keeps appearing because nobody wants to be the one who removed it. Every few cycles, it is worth listing every recurring page in the packet and asking who uses it and for what. If the answer is vague, move the page to the appendix or retire it. The board's attention is a resource, and a report that nobody uses spends it.

Accuracy and timeliness are the two checks that separate useful reporting from decoration, and they trade off against each other in ways worth naming. A perfectly accurate report that arrives late is of limited use for a decision on the agenda. A fast report with unreconciled numbers invites questions that consume meeting time. The usual resolution is a stated convention: which figures are final, which are estimates, and when the final versions will follow. Directors handle estimates well when the label is honest.

A simple comparison of the common reports and what each one is for:

ReportQuestion it answersTypical cadenceCommon failure

Financial statementsWhat happened, per the booksEach meetingArrives without commentary on variances Cash forecastWhat happens next, in cash termsEach meeting, updated monthlyAssumptions hidden rather than stated Budget vs. actualWhere reality diverged from planEach meetingEvery variance explained at equal depth Key metrics updateIs the operating story intactEach meeting or quarterlyDefinitions drift between periods

That last row deserves a pause. Metric definitions that drift, for instance when a pipeline figure quietly starts excluding a category it used to include, are a recurring source of board friction. The fix is administrative and unglamorous: a short definitions page, referenced in the packet, that changes only through an explicit note when it changes at all. This is the kind of process visibility that costs little and prevents an awkward meeting.

The interim leader's fresh eyes help here as well. Coming in without attachments, they can ask the question an insider stops asking: which of these pages changed a board decision in the past year? Pages with a clear answer stay. Pages without one are candidates for the appendix, whatever their history.

How should the cash forecast be presented so directors can actually use it?

Present the cash forecast with its assumptions attached, its scenarios named, and its confidence honest. Directors do not need to see the model; they need to see what the model depends on and where the uncertainty sits. A single line projecting cash twelve months out tells the board little. The same projection beside its three or four driving assumptions, with a note on which assumptions are firm and which are judgment calls, gives the board something it can interrogate and, when needed, defend to others.

Scenario structure helps more than precision here. A common approach shows a base case, a cautious case, and a case that reflects the specific risk the company is carrying at the moment, such as a delayed customer payment or a slower hiring plan. The scenarios do not need elaborate modeling. What they need is a clear statement of what changes between them, so a director can see that moving one assumption moves the runway by a certain stretch of months in a hypothetical example, without anyone pretending the forecast is more certain than it is.

Language matters in these pages. "Runway" should be defined once and used the same way every time. If the forecast assumes collections that depend on one large customer paying on schedule, say so in the same paragraph as the number, not in a footnote three pages later. I have sat through enough meetings where the real discussion was not about the forecast at all but about an assumption nobody had surfaced. Surfacing it in writing, ahead of time, is the whole game.

The update rhythm matters as much as the format. A cash forecast refreshed before each board meeting, with the previous version kept for comparison, lets directors see where the company's own expectations have moved. That comparison builds trust in the finance function during exactly the period when the seat is temporary and trust needs building. It also trains the organization: once people know the forecast gets revisited on a fixed cycle, they route information about payment timing and spending changes to finance before the cycle, not after.

Where does this connect to the operating side? Directly, and the connection should be visible. The forecast draws on billing schedules, payroll commitments, and purchase orders, all of which live in operating routines. An interim CFO for manufacturing companies CFO who builds the forecast in isolation produces something polished and hollow. One who walks the AP clerk through the assumptions and asks the sales lead about collection timing produces something the board can lean on, and incidentally leaves behind a network of people who understand how the forecast gets built.

A caution worth stating: no forecast survives contact with reality intact, and boards know this. What they are evaluating is not whether the numbers come true. They are evaluating whether the finance function understands its own business well enough to know what would make the numbers come true or not. Show your assumptions and you pass that test even when the forecast misses.

What does a first 90 days of board preparation look like from the inside?

The first stretch divides naturally into three phases: learn what exists, stabilize the cycle, then improve it. Compressing this order is tempting, especially when a financing conversation looms, but the order protects the board from getting polished materials built on numbers nobody has verified. Each phase has its own deliverables and its own risks, and naming them helps everyone calibrate.

In the opening weeks, the work is discovery. Where do the books close, how long does it take, who holds the reconciliations, and what did the last packet look like? A useful exercise is to reconstruct the previous board cycle from the files: when the close finished, when the packet went out, what questions came up in the meeting. This maps the process as it actually runs, which is often different from how anyone describes it. The gaps found here, such as a reconciliation nobody owns or a metric with two competing definitions, become the first worklist.

The middle stretch is about making one clean cycle happen. Close on schedule, build the package with clear sourcing, send the pre-read on time, and capture the questions directors ask. That single on-time cycle, even if the content is modest, does more for board confidence than an ambitious packet delivered late. It also surfaces the friction points: the data pull that always takes three days, the approval that always waits on one person's travel schedule.

Later in the period, improvements land on top of a working rhythm. Commentary gets sharper because the writer now knows which variances the board cares about. The forecast gains a scenario that reflects the company's current question. The packet gets shorter because the discovery phase revealed which pages nobody reads. None of this requires heroic effort; it requires the cycle running steadily long enough for small fixes to accumulate.

What the board should see from the interim leader during this stretch is candor about the state of things. If the close takes longer than ideal, the first packet says so and states when it will improve. Boards handle a known limitation far better than a surprise. The instinct to present everything as settled is understandable in a temporary seat, and it is exactly the wrong instinct, because the temporary seat's main deliverable is a finance function the next person can step into.

A practical note on sequencing the work itself: start board preparation for the next meeting on the day the current one ends. The questions directors asked are the outline for the next packet. A short written list, made while the questions are fresh, converts meeting time into preparation time. Skipping this step means every cycle starts from zero and every packet relearns the board's priorities the hard way.

How do you keep decision authority clear when the seat is temporary?

Write the authority down, name it in the materials, and repeat it until it is boring. Interim arrangements create a specific hazard: everyone knows the arrangement is temporary, so everyone hedonically assumes someone else holds each decision. The board assumes the interim leader decided; the interim leader assumes the CEO approved; the CEO assumed it was routine. None of these people is careless. The structure just let the decision fall between chairs.

The remedy is a short standing section in each packet, or a page on the shared drive, that lists the open finance decisions, who holds each one, and what stage it is in. Directors can scan it in a minute and know exactly what is theirs. This costs almost nothing to maintain and prevents the specific embarrassment of a board discovering, mid-meeting, that a decision it thought was settled was actually pending.

Decisions the interim CFO makes alone, within a stated limit, and reports afterward. Decisions the interim CFO recommends and the CEO approves. Decisions reserved for the board, presented with the background a vote needs. Decisions explicitly paused until the permanent CFO arrives, so nobody relitigates them twice.

The fourth category is easy to overlook and worth including. Some decisions are better made by the person who will live with them, and naming those explicitly protects both the interim leader and the company. It also signals to candidates for the permanent role that the organization takes decision rights seriously, which is a genuinely attractive quality in a finance function.

Investor and lender communications deserve their own line in this discussion. If financing conversations are active, the packet should state who speaks to investors or lenders and within what limits, because mixed signals during a raise are expensive in credibility. The interim leader can prepare the materials, pressure-test the numbers, and rehearse the questions. Whether they also deliver the message is a mandate question, and mandate questions get answered in writing, not by habit.

Clarity here also serves the handoff, which is the quiet deliverable of every interim engagement. When the permanent CFO arrives, the decision log becomes orientation material. They can see what was decided, on whose authority, and what remains open, in an afternoon of reading. Without the log, they spend their first months excavating, and the board spends those months re-answering questions it had already settled.

What questions should directors ask to judge whether board preparation is in good shape?

Directors can assess the health of the preparation process with a handful of questions, none of which require financial expertise to ask. The point is not to audit the numbers in the meeting; it is to check that the process behind the numbers would catch problems before the meeting. These questions work in any board, at any company stage, and they cost only meeting time.

Where did this figure come from, and who verified it? What changed since the last packet, and did we expect that change? Which numbers in this package are final and which are estimates? If a key assumption breaks, what is the plan, and who executes it? If the finance lead were unavailable next month, could someone else produce this packet?

That last question is the deepest one, and it is where interim arrangements either shine or struggle. A packet that only one person can produce is a risk no matter how good it looks. The process is visible when the steps are written down, the files are in a shared location with a stable structure, and at least one other person has produced part of the cycle under observation. Interim leaders who document as they go hand over a process; those who do not hand over a personality.

The question about changes deserves a note as well. Boards build intuition by watching expectations meet reality over time. When the packet explains what moved and connects it to something the board already discussed, directors get calibrated. When variances appear unexplained, or explanations shift tone from meeting to meeting without a stated reason, directors start discounting the whole package, and rebuilding that trust takes several honest cycles.

Directors might also ask what the finance function would flag if it were free to flag anything. Interim leaders sometimes hold back an observation, such as a process weakness or a data quality concern, because raising it feels like criticizing the house they are visiting. A board that asks the question directly gives permission, and the answers tend to be the most useful content of the whole engagement. The response also reveals how the finance function thinks, which is exactly what a board evaluating a permanent hire wants to know.

One boundary on all of this: directors should expect candor about process, not certainty about outcomes. A well-prepared packet still contains estimates, and a healthy finance function still has a backlog. If every page reads as fully settled and every trend points upward without qualification, the right question is not "good news?" but "what is this packet not telling me?" The interim seat, with no history to defend, is often the best positioned to answer that question plainly.

How does the handoff to a permanent CFO work without losing the meeting rhythm?

The handoff works when the process, not the person, carries the rhythm. By the time the permanent CFO accepts the role, the interim leader should be able to hand over a small set of artifacts: the calendar for the board cycle, the packet structure with notes on why each section exists, the definitions page for metrics, the open decision log, and the list of loose ends found during the engagement and not yet closed. None of these is complicated. Together they cut the new CFO's orientation from months to weeks.

An overlap period, even a short one, changes the quality of the transfer. The incoming CFO sits in on one board cycle, watching rather than producing, then produces the next with the interim leader reviewing. By the third cycle they run it alone. Companies sometimes skip the overlap to save cost, which is a legitimate trade, but the trade should be made knowingly. Without it, the first packet under new leadership is also the first test of the documentation, which is a stressful way to learn whether the notes were complete.

The board can help its own handoff by saying what it wants from the next CFO. The interim period is the natural moment to revisit the packet itself: what the board found useful, what it skimmed, what it wishes it had seen during the recent turbulence. Passing that list to the incoming CFO is worth more than any template, because it encodes the directors' actual preferences rather than the previous holder's habits.

Loose ends deserve honest labeling. Every interim engagement ends with items in motion: a reconciliation mid-review, a forecast assumption awaiting a customer decision, a policy drafted but not approved. The handoff document lists these with their status, so the new CFO triages rather than discovers. Boards should expect to see this list and should be a little wary if they do not, since a handoff with no open items usually means the list was not written, not that the work was finished.

Finally, the board's own behavior in the last interim cycle sets the tone for the permanent era. If directors ask the process questions above, the incoming CFO learns quickly that sourcing, timeliness, and visible handoffs are what this board values. If the meetings reward only polish, the next finance leader optimizes for polish. Boards get the reporting they inspect, and the interim period, handled well, teaches everyone what inspection should look like.

When does interim support for board preparation make sense, and when does it not?

A decision criterion to apply to your own case: interim CFO support for board work fits best when the company needs a working reporting rhythm restored quickly and can accept that some deeper changes will wait for a permanent hire. It fits poorly when the underlying problem is the accounting system, the close process, or the books themselves, because board preparation built on an unreliable base produces polished packages over shaky numbers, which is the worst of both worlds.

Run through the situations where the fit tends to be good. A CFO departure leaves the next board meeting weeks away and nobody who owns the packet. A financing process needs materials a stretched controller cannot produce while running the close. A transition, such as a sale process or a leadership change, needs steady board reporting while attention is elsewhere. In each case, the need is bounded, the timeline is defined, and the deliverable is a working cycle that a permanent leader can inherit.

The fit is weaker in a few recognizable situations. If the close takes months instead of weeks, fixing that is the real project, and dressing its output for the board does not fix it. If the company needs a long-term finance strategy built over years, a temporary seat can start it but cannot own it. And if the board's questions are really about business model viability, no reporting package answers that; the discussion belongs with the full board and the CEO, with finance supplying honest numbers as input.

A middle path exists and is worth considering: interim support scoped to a defined deliverable, such as rebuilding the board packet and running two cycles, with the permanent search running in parallel. This gives the board continuity without committing the company to a long interim arrangement. The scope, the decision rights, and the handoff expectations all get written into the engagement the same way the mandate page describes them, which keeps the arrangement honest on both sides.

Whatever you decide, judge the engagement the way you would judge the packet itself: by whether the process became more visible, more repeatable, and more transferable than it was before. Those three qualities, more than any single meeting's materials, are what a temporary finance leader can leave behind, and they are what make the next seat, whoever fills it, easier to hold.