Beth Pullman
Interim CFO mandate objectives and timeline to set upfront
Setting the interim CFO mandate objectives and timeline before the engagement starts changes how the whole finance function behaves. Instead of a senior hire improvising priorities week to week, you get a written scope: what the interim CFO decides alone, what comes to you, which deliverables matter first, and when the handoff to permanent leadership happens. Questions about records, forecasts, and decision rights get answered in days rather than resurfacing every month.
Most owners bring in an interim chief financial officer CFO when something has broken or is about to: the finance leader left mid-year, a lender is asking for new reporting, a deal is in play, or growth has outpaced the accounting function. Any of those situations works, but only if the engagement has a defined shape. This article walks through the steps I would follow to set that shape before the first invoice arrives, with the attention a transaction planner gives to underlying detail. The order matters, because each step builds on the one before it.
Write down why the company needs an interim CFO before anything else
The first step is a one-page statement of the actual problem. Not "we need finance leadership" but the specific situation: the controller cannot produce a lender-quality forecast, an acquisition conversation has started and nobody owns the data room, or the board wants monthly reporting the current team cannot build. A different problem leads to a different mandate, and the difference shows up in what you ask the interim CFO to do in the first month.
Be skeptical of vague framing. If the reason is "we can't afford a full-time CFO," that is a budget observation, not a mandate. If it is "the last CFO left and things are fine," you may need a closer look at whether things actually are fine. Check the underlying detail: when was the last clean close, does the forecast reconcile to the ledger, who signs the bank requests. The answers tell you whether this is a gap-filling role or a repair job.
Write the reason in a sentence you would be comfortable saying to a lender. That sentence becomes the anchor for everything else: the objectives, the timeline, and the decision rights. If you cannot write it yet, that is itself a finding worth slowing down for. An interim engagement built on an undefined problem tends to extend indefinitely and deliver reports nobody asked for.
Here is a checklist of questions worth answering in writing before moving on:
- What event triggered this: a departure, a financing, a transaction, or growth strain?
- Who currently owns the monthly close, and how far behind is it?
- Is there a forecast today, and does anyone trust it?
- What will outside parties (lender, investor, buyer) need from the finance function in the next two quarters?
None of these questions requires an expert to answer, and that is the point. The mandate-setting step belongs to the owner, not the incoming executive. Come with the answers and the interim CFO spends the first days on work instead of discovery.
Distinguish the objectives that are urgent from the ones that merely feel urgent
Once the reason is written, sort the work into two groups. Urgent objectives are ones with a date or a dependency attached: the bank reviews the covenant package in a specific month, the buyer's diligence starts when a letter of intent is signed, the annual audit fieldwork has a window. Important-but-not-urgent objectives, like cleaning up the chart of accounts or documenting controls, have no external deadline and can wait or run in the background.
The sorting matters because an interim CFO with limited months will do urgent work first whether or not you agree. If you wanted the close process rebuilt but the covenant package is due, the covenant wins. That is the right call, but you should have made it consciously. I prefer to see the two lists next to each other, with the trade-off written down in one sentence: "the close redesign waits until after the lender package because both draw on the same controller."
A common mistake is treating everything the previous CFO did as urgent by inheritance. Monthly board decks, annual budgets, and quarterly investor updates all feel mandatory. Some are; some are habits. Ask who actually reads each one and what decision it supports. If the answer is "nobody remembers," that deliverable is a candidate to pause for the length of the engagement, which frees real capacity for the objectives you actually care about.
This sorting also protects you from scope creep in the other direction. Interim executives are often capable of an enormous range of work, from pricing analysis to systems selection, and a capable person will happily do all of it if asked. The urgent-versus-optional split gives you a polite, written way to say no. When a new request arrives mid-engagement, it goes on the optional list and competes there, rather than displacing the work you set upfront.
One caution applies here. Sorting assumes you know enough about the finance function to classify its work. If you do not, add a diagnostic objective to the urgent list: "assess the close, forecast, and controls in the first few weeks and report back." Then expect the two lists to be revised once. That revision is not a failure of planning. It is the engagement working as intended.
Define decision rights so the interim CFO knows what to settle without you
Decision authority is the part of an interim CFO mandate objectives and timeline conversation that owners most often skip, and it is the one that causes the most friction later. Write down which decisions the interim chief Financial Officer CFO makes alone, which require your approval, and which belong to the board or lender. Without this, every choice either escalates to you (and the engagement stalls) or gets decided quietly (and you find out late).
A practical split looks like this in many mid-sized companies, though the right answer depends on your situation:
- Alone: enforcing the close calendar, adjusting journal review procedures, requiring documentation from the accounting team, pausing discretionary spending above a stated threshold.
- With your approval: changing the forecast the lender sees, modifying headcount plans, renegotiating terms with the bank, engaging outside advisors.
- Not theirs: selling assets, changing ownership matters, commitments that bind the company beyond the engagement.
Notice the pattern. Routine financial hygiene moves fast; anything with external consequences comes to you. The exact lines matter less than having them written. An interim CFO who has to ask about everything becomes expensive email. One who decides everything becomes a risk you did not price.
Decision rights also interact with the transaction angle. If a sale process is plausible during the engagement, decide now who talks to advisors, who sees drafts of diligence materials, and who can commit the company to an exclusivity period. A careful transaction planner treats this as a governance question, not a courtesy one. The worst time to establish who signs the confidentiality agreement is the afternoon a buyer sends it.
There is a staff dimension too. The accounting team needs to hear, from you, that the interim CFO has the authority the document describes. Otherwise the controller routes everything around the newcomer and the engagement underperforms for reasons that look mysterious but are not. Ten minutes of clear communication at the start prevents a quarter of quiet resistance.
Finally, put a sunset on the special authority. Interim decision rights should end when the engagement ends, or convert explicitly into the permanent CFO's job description. An arrangement that persists past its purpose creates ambiguity about who is actually accountable for the finance function, which is precisely the question this whole exercise exists to answer.
Set the timeline around dates and dependencies, not around a generic duration
Interim engagements often get described in quarters, and that shorthand is fine for budgeting, but a real timeline is a set of dated dependencies. Start from the external dates you cannot move: covenant reporting deadlines, audit windows, forecast deliveries a lender or investor expects, any transaction milestones. Then work backward and place the objectives where they can actually be finished.
An example shows the method, and this one is explicitly hypothetical. Suppose a company's lender needs a reforecast in a specific month, and the company wants a sale process to start after that. The dependency chain is straightforward: the close must be current before the forecast can be trusted, the forecast must be built and pressure-tested before it goes to the bank, and the diligence-readiness work should draw on the same cleaned data. Put dates on each link and you have a timeline that means something, rather than "a three-month engagement."
Two timeline habits are worth adopting. First, mark the objective that would delay everything else if it slipped. Usually that is getting the books current, because nearly every other deliverable consumes its output. Second, leave slack between the finance deliverable and the external date. A forecast finished the day before the lender meeting has no room for the questions the lender will inevitably ask.
Timelines should also distinguish work that finishes from work that continues. The covenant package gets delivered and stops. The improved close process, by contrast, has to keep running after the interim CFO leaves, which means it is not done when the first clean close lands; it is done when the team can run it without help. Plan for that continuation explicitly, because it drives the knowledge-transfer step later in this sequence.
Be honest about what an interim timeline cannot do. A short engagement can stabilize reporting, produce a credible forecast, and prepare records for scrutiny. It generally cannot rebuild the accounting function's culture, complete a system migration and a transaction at once, or compensate for headcount that simply is not there. When someone suggests a timeline that requires two of those at once, treat it as a negotiation opening, not a plan. Compressing scope does not compress the work; it just moves the shortfall somewhere less visible.
Review the timeline at fixed points rather than continuously. A check-in every few weeks, tied to the dependency dates, is enough. Daily status conversation is a sign the mandate was never really defined, and weekly can work for the first stretch in a distressed situation, but the goal is a schedule you could describe to a board member in two sentences.
Specify the deliverables in enough detail that quality can be checked
"Better reporting" is not a deliverable. "A three-statement forecast reconciled to the ledger, delivered before each lender review, with assumptions listed on a separate tab" is. The difference is not pedantry. Vague deliverables get met in letter and missed in spirit, and you will have no basis for the mid-engagement conversation about whether things are on track.
For each objective, write down the artifact, the recipient, and the standard. The artifact is what exists at the end: a forecast, a covenant package, a controls memo, a data room index. The recipient is who consumes it: you, the board, the lender, a buyer's advisors. The standard is how you will judge it. A forecast standard worth writing down: every line ties to the ledger or to a documented assumption, and the bridge from last actuals to the first forecast month is explainable in one page.
Deliverable detail also exposes hidden work. If the objective is diligence readiness, the artifact list includes more than financial statements: contracts organized and summarized, related-party arrangements documented, revenue recognized on a defensible basis (for many software companies that means ASC 606), and tax filings current. Each item on that list consumes days of someone's time, and seeing them together is how a realistic timeline emerges instead of an optimistic one.
| Deliverable | Typical recipient | What "done" looks like |
|---|---|---|
| Current- period close package | Owner, board | Issued on a fixed calendar date, with a short variance explanation |
| Lender forecast | Bank | Ties to ledger, assumptions documented, delivered with slack before review |
| Diligence index | Buyer's advisors | Every requested document locatable within minutes, gaps flagged honestly |
| Controls memo | Owner, incoming CFO | Key processes documented, weaknesses listed with proposed fixes |
Resist the temptation to specify deliverables so rigidly that judgment is squeezed out. The purpose of the detail is to make quality checkable, not to script the executive. If the interim CFO proposes a better artifact for the same purpose, that proposal is a sign of a good engagement, and the written deliverable is easy to amend by agreement. What the document protects against is silence, not improvement.
One deliverable deserves its own line even when it feels obvious: a monthly one-page status note against the objectives and timeline. It costs almost nothing to produce and gives you, the board, and eventually the permanent CFO a record of what changed and why. In any later diligence or financing conversation, that record is the difference between narrating your own progress and reconstructing it from memory.
Connect the strategic finance work to the operating routines that already exist
A forecast that lives in the CFO's laptop helps nobody. The strategic work of an interim engagement creates value when it plugs into routines the company already runs: the monthly operations meeting, the sales pipeline review, the purchasing decisions, the payroll calendar. Define those connection points during mandate-setting, or the finance function will produce excellent documents in parallel to the business instead of inside it.
Start with the meetings that already happen. Which ones should include a finance segment, and in what form? A short cash and performance section in the existing operations meeting usually beats a separate finance meeting that managers resent attending. Ask the interim CFO to attend the pipeline review before building the revenue forecast, not after, because the assumptions that matter (sales cycle, renewal behavior, hiring plans) live in those conversations, not in the ledger.
Then look at the decisions that recur. Pricing changes, large purchases, customer credit terms, and bonus accruals all have financial consequences that show up either in advance (in a forecast) or in arrears (as a variance). Decide which of these require a finance input beforehand and write that into the operating rhythm. A company where finance sees large commitments only after they are made will produce forecasts that are always surprised, and no amount of executive talent fixes that.
There is also a data plumbing question. If the interim CFO's forecast depends on numbers the accounting team assembles by hand each month, say so in the mandate and decide whether that is acceptable for the engagement's duration. Often it is, provided the process is documented. Sometimes it is not, and a modest systems fix belongs on the urgent list. Either conclusion is fine; an unstated one is not. Check the underlying detail here, because "the system will handle it" is a phrase that deserves the same skepticism as any other unverified claim in a transaction.
Investor and lender reporting connects through the same principle. Whoever receives external reports should receive them on a calendar, in a format that repeats, with variance explanations that reference the operating reality rather than accounting jargon. When the interim CFO inherits existing reports, have them review rather than rebuild by default. Rebuilding a format consumes weeks that might belong to the forecast, and a reader who was fine with the old format rarely notices the improvement.
For a company approaching a transaction, this connection has an extra payoff. Buyers and their advisors form early impressions from how internally consistent the business appears: whether the story told in the data room matches what the monthly numbers show. An engagement that has woven finance into operations produces that consistency as a byproduct. An engagement that produced reports in isolation produces two versions of the company, and diligence will find both.
Plan the knowledge transfer as an objective, not a closing courtesy
Knowledge transfer fails when it is treated as the thing that happens in the last two weeks. By then, the interim CFO's habits, assumptions, and unresolved questions have already drifted out of documentation and into memory, and memory leaves with the person. The mandate should name the handoff artifact early and let it accumulate throughout the engagement.
What belongs in that artifact is concrete. A close calendar with named owners for each step. A forecast model whose assumptions are labeled well enough that a new reader can update them. A list of judgment calls made during the engagement, with the reasoning: why a reserve was estimated a certain way, why a report was paused, why a control was added. A summary of open items and known weaknesses, written plainly. None of this is glamorous, and all of it is what a permanent CFO would otherwise spend a month reconstructing.
Decide also who the successor is expected to be, because that shapes the transfer. A permanent CFO hire needs depth and decision context. A controller being elevated needs authority as much as knowledge, and the transfer should include explicit introduction to the lender, the auditors, and the board. A strong interim executive can be a useful advisor in choosing and onboarding the successor, but that role should be part of the mandate, priced and scheduled, not assumed as unpaid goodwill.
Structure the transfer over the engagement's final stretch with a simple overlap:
- The successor reviews the handoff artifact and lists questions.
- The interim CFO answers in writing, updating the artifact where the answer was missing.
- They jointly run one close or one forecast cycle, with the successor leading and the interim observing.
- The interim CFO writes a short closing memo: what was done, what remains, what to watch.
That sequence costs a few weeks of overlap and buys continuity that no exit interview replicates. Budget for it in the timeline from the start. Engagements that end abruptly on a Friday tend to lose, in the following quarter, more value than the overlap would have cost, usually in re-created work and re-learned context.
A transfer plan also disciplines the engagement itself. An interim CFO who knows the assumptions memo will be read by a successor writes it well from month one. The prospect of a documented handoff raises the quality of everything upstream of it, which is a quiet argument for making the artifact explicit even in engagements where the successor is not yet identified.
Agree on how you will judge progress without assuming outcomes
Measuring an interim engagement is easier if you resist the two broken approaches. The first is output counting: pages produced, meetings attended, systems touched. The second is outcome borrowing: crediting the engagement with a valuation, a financing, or a sale that depended on many other things. Both mismeasure. The useful middle ground is progress against the objectives and timeline you wrote in the earlier steps, judged by checkable facts.
Concretely, at each review point ask questions like these:
- Is the close current, and did the last package issue on the calendar date?
- Can the forecast be traced to the ledger and to written assumptions?
- Do the people who consume the reports say they are using them?
- Are the decision rights operating as written, with escalations happening where the document says they should?
- Is the handoff artifact growing, or is everything scheduled for the final month?
None of those questions requires you to be a finance expert, and each one points at evidence rather than impression. When an answer is no, the review conversation is about the obstacle, not about assigning blame. Sometimes the obstacle is real (a systems gap, a staffing shortage) and the timeline moves by agreement. Sometimes the obstacle is scope drift, and the earlier objective lists are what pull the engagement back.
Beware of milestones that can only be verified at the end. If the only evidence of success is "the transaction closes" or "the financing lands," you will fly blind for the whole engagement. Break every end-state into intermediate, checkable conditions: the data room index exists and is populated, the revenue recognition memo is drafted, the lender has the package. This is the same discipline a transaction planner applies to a closing checklist, where no single sign-off matters unless the items beneath it are actually done.
There is an honest limit to state here, to yourself and to any advisor you work with. Good preparation improves the odds of a smooth process; it does not guarantee a deal, a buyer, a particular valuation, or any financing outcome. An interim CFO engagement that goes perfectly can still end without a transaction, because markets and counterparties are outside anyone's mandate. Judging the work by readiness rather than by results is not lowering the bar. It is measuring what the mandate actually controlled.
Finally, let the measurement evolve once, deliberately, rather than continuously. The first review might reveal that an objective was mis-specified or that an external party needs something unplanned. Amend the objectives document then, in writing, and hold it steady afterward. A mandate that is renegotiated every month is not a mandate; it is a conversation with paperwork.
Questions to settle with any advisor before you commit to an engagement
Before signing anything, sit down with the prospective interim CFO or the firm providing one, and walk through the mandate document together. The conversation itself is diagnostic: a careful practitioner will welcome specific questions and give specific answers, and hesitation in the right places tells you something too. Bring this list and expect to leave with written responses, not vibes.
- Given our written reason for hiring, what would you put on the urgent list, and what would you deliberately defer?
- Which decisions do you expect to make alone, and where will you insist on our approval?
- What external dates drive the timeline, and what happens to the plan if the first dependency slips?
- What artifacts will exist at the end, and who receives each one?
- How will you connect the forecast and reporting work to our existing operating meetings?
- What does the handoff to permanent leadership include, and how much overlap does it require?
- What would cause you to tell us the timeline we proposed is not achievable?
The last question is the one I would listen to most closely. An advisor who can name the conditions under which the plan fails is someone who has read the underlying detail rather than the brochure. Confidence without stated limits, in finance work as in transactions, is usually a sign that the difficult questions have not been asked yet.
Settle the commercial terms separately and quietly: duration, rate, expenses, and what happens if either side ends the engagement early. The mandate document and the commercial agreement are different papers with different jobs. Mixing them (tying objectives to payment contingencies, for instance) tends to distort the work toward whatever is measurable and away from what is useful, and it invites exactly the outcome-guarantee framing that no honest practitioner should accept.
One closing habit worth adopting regardless of whom you hire: keep the mandate document, the revised objectives, and the monthly status notes in one folder you could hand to a lender, a board member, or a future buyer without embarrassment. Companies rarely get in trouble because they lacked talent. They get in trouble because nobody can trace what was decided, when, and on what basis. This whole sequence, from the one-page problem statement to the closing memo, exists so that trace is there when you need it.
Share Profile