Interim CFO Forecast Governance Practices: Make Reporting Visible

From GoldenWiki - Community Building
Jump to navigation Jump to search


The mistake that shows up most often in interim CFO forecast governance practices is treating the forecast as one person's private file. The interim lead builds a model, sends out a summary, and nobody else can explain where the numbers came from. When that person moves on, the organization is left reconstructing assumptions from memory, and the next report to the board looks nothing like the last one. Make the process visible instead: written assumptions, named owners, and a routine anyone can follow.


Start with a written mandate before any modeling begins


Before the first forecast draft, the board and the interim CFO should agree in writing on what the role decides and what it advises on. A one-page mandate prevents the two failures I see most: an interim lead who approves spending nobody asked them to approve, and one who waits for permission on decisions the organization expected them to make. The mandate does not need legal language. It needs names, dollar thresholds where they exist, and a date for review.



A workable mandate answers four questions. Who approves the forecast before it goes to investors or the board? Who signs off on changes to budget assumptions? What spending can the interim CFO authorize alone, and what requires a second signature? Who do they report to, and how often? If any of those answers is "we'll figure it out," that gap will surface later as a delayed report or a disputed decision, which is far more expensive to fix mid-engagement.



The mandate should also say what is out of scope. An interim CFO brought in to steady cash reporting during a leadership vacancy should not be quietly rebuilding the entire chart of accounts in week two, however tempting that may be. Scope creep in an interim role is rarely malicious. It happens because the need is obvious and the person is capable. Writing the boundary down makes it a conversation instead of a surprise.



Keep the mandate short enough that a finance committee member can read it in one sitting. In a small organization, that might be half a page. In a company preparing for financing, it may run longer because lender reporting duties need explicit assignment. The length matters less than the fact that several people have the same copy and can point to the same line when a question comes up.



Review the mandate whenever circumstances change, not on a fixed calendar. A new board chair, a term sheet arriving, or a permanent hire starting the search process are all natural triggers. A mandate written for steady-state reporting can be quietly wrong three months later if nobody revisits it. Put the review question on the agenda of the first finance meeting after any major change.


Put the forecast assumptions in a place everyone can see


The forecast itself is only as useful as the assumptions behind it, and those assumptions are usually the first thing to disappear during a handoff. Write them down in a tab or appendix that travels with the model: collection days by customer type, hiring dates, the revenue recognition approach, and any one-time items. A reader should be able to trace any headline number back to a stated assumption without calling the person who built it.



Assume a hypothetical company with a handful of large customers. The forecast shows a jump in cash receipts next month. If the assumption note says "Customer A historically pays in 45 days and the invoice went out on the 3rd," a board member can judge whether to trust the jump. If the note is missing, the same board member either accepts the number blindly or discounts it heavily, and neither response helps anyone make a decision. Visibility replaces both with judgment.



Version discipline matters as much as the assumptions themselves. Keep a simple log: date, author, and one line on what changed. Avoid editing over old files or emailing copies with names like "final v3 revised." A shared location with dated versions, whether that is a shared drive or a dedicated folder, lets anyone reconstruct how the outlook shifted over the quarter. That history is often more informative to a lender than the current snapshot.



Color coding and formatting help, but they are no substitute for written notes. A cell shaded yellow means nothing to a new controller. The words in the comment are what survive the transition. If your model relies on conventions the builder keeps in their head, the model has a single point of failure, and in an interim arrangement that point of failure is scheduled to leave.



One habit worth adopting: end each forecast cycle with five minutes of assumption housekeeping. Mark assumptions that proved wrong, and note why. Over a quarter or two this builds a record of the organization's actual forecasting patterns, which is exactly the context a permanent CFO needs on day one. It also keeps the interim lead honest about where their track record is strong and where it is weak.


Set a reporting calendar that survives personnel changes


A reporting rhythm is more durable than any individual, which is the whole point of establishing one during an interim period. Pick the cadence first: weekly cash, monthly close summary, quarterly board package. Then attach dates, owners, and a named backup for each deliverable. The calendar should be written where the whole finance function can see it, not kept in one inbox.



The weekly cash view deserves the most care, because it is the one report that people will actually act on between board meetings. Keep it short: starting cash, expected inflows with dates, committed outflows, and the expected ending position. Add one line of commentary on anything unusual, such as a payment slipping or a vendor agreeing to different terms. If the weekly report takes more than an afternoon to produce, the underlying process is too heavy, and that is a finding worth reporting in itself.



Monthly work should follow a close checklist with owners and deadlines for each step: bank reconciliations, accrual entries, variance notes against budget, and the updated forecast. The interim CFO's job is to make sure the checklist exists and reflects reality, then to review the output, not to be the only person who can execute any step. When one person is the sole performer of a task, ask directly how routine work gets covered when they are out or gone.



For board and investor reporting, agree on a fixed package early: the reports, the order, and the one page of narrative at the front. Lenders and investors notice consistency, and a package that changes shape every month invites questions about what else is unstable. Where accounting standards bear on the numbers, such as revenue recognition under ASC 606, the package should state the treatment used so a reader does not have to guess.



Publish the calendar with the reports themselves. A simple line at the top of the board package saying "next cash report on the 15th, close summary by the 10th" tells readers when to expect the next update and reduces the chasing emails that otherwise consume the finance team's week. Visibility applies to the schedule as much as to the figures.


Separate what the interim CFO decides from what they recommend


Boards get confused when recommendation and decision look identical in the reporting. Make the distinction visible on the page: label items as "decision required," "decided, for information," or "recommendation, no action needed." A reader should never have to infer from tone whether a line item is asking them for something. This is a small formatting choice with a large effect on meeting quality.



A typical trap: the interim CFO recommends holding off on a hire to protect cash, and the minutes record no objection, so everyone assumes a decision happened. Two months later, the department head is still waiting and the position is unfilled in the forecast but funded in the budget. Labeled items prevent this. The recommendation line either converts to a recorded decision with a date and a decider, or it expires visibly.



Decision rights usually split along these lines, and writing them into the mandate makes the split explicit:



Day-to-day disbursements within an agreed threshold: interim CFO decides, reported in the weekly cash view.
Changes to forecast assumptions: interim CFO proposes, finance committee or owner approves anything material.
Spending above the threshold, new debt, or pricing changes: board or owner decides, interim CFO provides analysis.
Hiring and firing outside the finance team: line leadership decides, interim CFO shows the cash impact.



The value of this split is speed with accountability. Decisions get made at the right level, and the record shows who made them. In a transition period, when people are inclined to defer to whoever seems most in control, an explicit map of decision rights keeps authority where the governance structure says it belongs.



Review the decision log quarterly alongside the mandate. Patterns emerge quickly: if every significant item is "decision required" from the board, the interim role is being used as an analyst rather than a finance lead, and the organization is paying for capacity it is not drawing on. If nothing ever reaches the board, the opposite problem exists. Either way, the log tells you which adjustment to make before the arrangement calcifies.


Build the handoff into the routine from the first week


Knowledge transfer is not a final-week scramble; it is a byproduct of the visible process. If assumptions are written, the calendar is published, and decisions are logged, most of the handoff document already exists. The interim CFO should still maintain a running file of open items: reconciliations pending, estimates that need judgment, contacts at the bank and the audit firm, and any known gaps in the records. Update it monthly, not at the end.



Where the organization has a controller or bookkeeper, involve them in the forecast cycle from the start rather than handing them a finished model. A person who has entered the actuals and refreshed the assumptions can run the process; a person who only received the output cannot. This is the difference between an interim engagement that leaves capability behind and one that leaves paperwork behind.



For the permanent hire's arrival, prepare a short orientation set: the current forecast with its assumption log, the last three board packages, the decision log, and the open items file. Walk through it in a live session, not just an email transfer. An hour of conversation about why the assumptions are what they are saves the new CFO weeks of reverse engineering, and it protects the organization from the quiet information loss that otherwise accompanies every departure.



Watch for the handoff gap that appears when there is no permanent hire on the horizon. interim Cfo services arrangements that stretch on tend to drift toward dependence: the organization stops asking how the routine work is covered because the coverage is a person rather than a process. A quarterly question from the finance committee, "if this arrangement ended next month, what would break first?", keeps the answer honest and the documentation current.



The final deliverable of any interim engagement should be a statement of what was changed, what was started, and what remains unfinished. Honest language matters here. An honest "the revenue forecast still relies on management estimates for two product lines" is far more useful to the next leader than a tidy summary that glosses over the rough edges. Continuity is served by accuracy, not by polish.


Review the forecast against actuals on a fixed cycle


A forecast earns trust through comparison, not through presentation. Set a standing monthly review: actuals versus forecast for cash, revenue, and the few lines that drive decisions, with a short written explanation for anything that missed by enough to matter. Defining "enough to matter" is itself a governance decision worth recording, because it varies by organization size and by how tight the cash position is.



The explanations do more work than the variances. "Collections came in below forecast" is a headline; "two large customers paid late, one has agreed to a revised schedule" is information a board can act on. Encourage whoever writes the notes to name causes rather than restate the numbers. Over a few cycles, the pattern of causes tells you whether the forecast's weakness is in timing, in volume assumptions, or in data quality, and each of those has a different fix.



Guard against the opposite failure too: forecasts that are adjusted so often, or so gently, that they never miss. A forecast that always lands exactly on target usually means the target moved. Keep the original version of each cycle alongside the revised one so the comparison is honest. The discipline of comparing against what was actually predicted, not what was later decided, is what makes the review meaningful.



Frequency should follow the stakes. Weekly cash comparisons make sense in a tight liquidity period or during financing negotiations; monthly is generally enough otherwise. Resist the urge to add reports during uncertainty; more frequent reporting of the same weak numbers does not improve anything. Better to improve the two or three inputs that drive the forecast, such as accounts receivable aging and the payroll calendar, and let accuracy rise from there.



Use the review to retire assumptions that no longer earn their place. Every extra driver in a model is a claim on someone's time each cycle. A lean forecast with documented, tested assumptions beats an elaborate one that nobody can maintain after the interim period ends. The question to ask of each input is plain: does changing this number change a decision? If not, simplify.


Match the depth of the process to the organization's stage


Governance that fits a company preparing for a sale is heavier than what a stable owner-led business needs, and pretending otherwise wastes effort. A business in financing discussions needs forecast documentation that can withstand a lender's questions: sourced assumptions, consistent accounting treatments, and a clear audit trail from actuals to projections. A family-owned company bridging a vacancy needs the weekly cash view, a close checklist, and not much more. Same principles, different weight.



The table below gives a rough mapping, not a rulebook. Organizations differ in systems, staffing, and appetite for process, so treat it as a starting point for a conversation about fit.




SituationCore routineExtra when it fits


Leadership vacancy, steady operationsWeekly cash view, monthly close checklistDecision log for unusual items
Rapid growth, hiring pressureRolling 13-week cash, hiring forecast in the modelScenario versions for funding gaps
Financing or transaction preparationDocumented assumptions, fixed board packageQuality-of-earnings readiness review
Turnaround or tight liquidityTwice-weekly cash, vendor schedule reviewDaily cash during peak weeks




Be honest about internal capacity when choosing the weight of the process. A small team with part-time bookkeeping support cannot sustain a reporting stack designed for a finance department, and an interim arrangement that installs one will see the routine decay within weeks of the departure. It is better to leave behind three reports that run reliably than seven that ran for a quarter and stopped. Ask what will actually happen on the Friday after the engagement ends.



Systems matter less than people assume. A well-documented workbook in a shared location outperforms an expensive planning tool that only one person can operate. If the organization already has software in place, use it; if not, the interim period is rarely the right time for a selection project unless the mandate says so. Process first, tools when the process outgrows them.


What to check each quarter to keep the process honest


A short quarterly check keeps forecast governance from drifting into paperwork for its own sake. The finance committee or owner can run it in one meeting, and it works best when the interim CFO is in the room to answer rather than to present. The point is to test whether the routine is still serving decisions, not to grade the numbers.



Work through these items, and note the answers somewhere durable:



Can someone other than the interim CFO produce the weekly cash view and the monthly package?
Does every headline number in the last board package trace to a written assumption?
Are decisions from the period recorded with a date and a decider, including the ones made by email?
Did the forecast comparison notes name causes, or only restate the variances?
Is the open items file current enough that a departure next month would not surprise anyone?
Does the mandate still match reality, or has scope quietly shifted?



Where an item fails, the response is usually a small fix: add a backup owner, interim cfo services write the missing assumption note, close out the stale decision. Where the same item fails twice in a row, that is a structural signal, and it deserves a real conversation about staffing, systems, or the shape of the interim mandate itself. Repeated small failures in reporting routines tend to precede larger ones in the numbers.



Treat the check as the permanent leadership's inheritance. A quarter of documented answers gives an incoming CFO a running start and gives the board a record of what was actually governed during the gap, not just what was reported. Visibility, in the end, is the whole deliverable: a finance process that any capable person can step into, question, and continue.