Interim CFO During An Executive Leave: Split The Mandate
Bringing in an interim CFO during an executive leave works when the mandate is split before the first day: decision rights in writing, operating routines listed by deliverable, and strategic projects named with dates and owners. The main condition is the leave itself. A short planned absence and an open-ended departure justify different splits, and what the finance calendar holds over the coming quarter decides which work can wait.
The symptom that shows up in the first month
The pattern appears fast: the interim is busy from the first morning, and the finance function still stalls. Meetings fill the calendar, everyone gets a listening session, and the decisions keep waiting. The board pack slips by a week. Payments sit unapproved because nobody is sure who may sign them. Activity looks healthy while the real work queues up behind it.
The likely cause is a mandate written as one undivided role. A mandate that says "cover everything until I'm back" produces an inbox instead of a priority list. The interim inherits every open question because nothing draws a line between what must move now, what can hold, and what should not start at all. Without that line, the safest move for a newcomer is to ask before acting, and asking is slower than deciding.
There is a second symptom underneath the first. Questions that used to go to finance get routed to the chief executive, the cash view ages quietly in a spreadsheet nobody refreshed, and the team waits for direction the mandate never authorized anyone to give. A leave is exactly when a company finds out which routines lived in one person's head.
The correction is the split: three pages, each with its own limits. One page for decision rights, which says who signs what. One page for operating routines, which lists the recurring deliverables by name and deadline. One page for strategic projects, which names the non-repeating work, its owner, and its target dates. Separated this way, a vague assignment becomes three agreements you can actually check.
I would rather see a narrow mandate executed well than a broad one executed anxiously, and the split is what makes narrow possible without leaving gaps, because the pages together cover the whole function. It also lets a company say out loud that some things will wait until the CFO returns. Named limits cost an afternoon to write and pay for themselves in the first stalled week.
Decision rights: who signs what while the CFO is away
Start with authority, because it is the part that damages trust when guessed wrong. The tool is an authority matrix: a short document saying which financial decisions the interim can make alone, which need the chief executive, and which belong to the board. Written before day one, it takes an afternoon. Left unwritten, it gets improvised one invoice at a time.
The symptom of a missing matrix is easy to miss, because it looks like diligence. Payments wait for a signature nobody is sure the interim can give, or the interim signs something the returning CFO would have escalated. Both directions cost you: one stalls the operation, the other spends goodwill you will want later, especially with a financing conversation anywhere on the calendar.
A workable matrix has few moving parts:
The interim approves routine spending inside stated limits, and the limits are monthly rather than per item, so the test stays simple.
The chief executive approves exceptions, new commitments, and anything that changes headcount or contracts.
The board keeps whatever its governance documents reserve: budgets, banking changes, and any new debt or equity.
Anything the matrix does not cover goes to one named escalation path, the same one every time.
Access should follow the matrix rather than trail it. If the interim may approve payments, the payment platform and the accounting system need provisioning before the first Monday, with the returning CFO's credentials left untouched. Access granted in week two quietly invalidates a mandate that looked clean on paper.
The next question is memory. Keep a decision log: one line per decision, with the date, the choice, and who was consulted. The log is what makes the return work, because the CFO can read it in an hour and disagree selectively, instead of re-auditing everything. It also protects the interim, since written reasons age better than recollections.
The operating routines that cannot pause for a leave
The close, the cash forecast, and the reporting to boards, lenders, and investors continue whether or not anyone enjoys that fact. The correction here is to define routines by deliverable, by owner, and by deadline, and to put that list in the mandate itself. Activity descriptions like "support the monthly close" hide the fact that a specific package leaves the building on a specific date.
The symptom shows up as variance in the board materials: numbers that arrive late, then get re-explained in the meeting because the schedule slipped upstream. The cause is usually that the routine lived in the CFO's head, in folder names, and in a few private reminders. A leave surfaces that within one reporting cycle, which is one cycle too late to fix politely.
Name the recurring deliverables concretely. The monthly close comes first, with revenue recognition consistent with ASC 606 if you report under US GAAP. Beside it sit a weekly cash forecast with a horizon long enough to act on, the board pack, and any lender or investor update already promised. Each one gets an owner on the finance team, not only the interim, because the team is what survives the leave.
Routines and strategic work are connected, and the connection runs through credibility. A forecast is useful in a fundraising conversation when you can explain what sits behind it, so the weekly refresh has to carry its assumptions, and the close has to be tight enough that the historical numbers hold still while someone studies them. The next question is whether the routine produces that material or only a headline total.
One instruction is worth writing down verbatim: run the routines with the existing team, not around it. The interim chairs the close and reviews the output, while the staff accountant who reconciles payroll keeps doing exactly that. It protects the leave period twice over, since the work keeps its owner and the team keeps its muscle memory for the day the mandate ends.
Strategic projects need their own page in the mandate
Non-repeating work is what a leave usually puts at risk, because it is the easiest to postpone and the hardest to catch up. The correction is to name each project in the mandate with a deliverable, a date, and an explicit boundary. A mandate that says "support the fundraising" has not said anything yet; a mandate that says "maintain the model and the assumptions register" has.
The symptom is a stalled quarter dressed up as patience. The forecast rebuild waits for a quieter week, the lender package waits for the forecast, and the quieter week never arrives because the routines consume it. The cause is structural: without protected scope, urgent work will always displace important work in a calendar, and nobody involved has to be careless for that to happen.
Reasonable project candidates include a rebuilt forecast with documented assumptions, a financing package prepared for a specific audience, and a review of internal controls before the company grows past them. Transaction readiness belongs on the page only if a sale is genuinely plausible, since readiness work is real work and should not be decorative.
Debt and equity are separate conversations, and the mandate should say which one is in scope. A lender package leans on cash flow, covenant headroom, and the quality of the close. An investor audience asks about the growth model and the assumptions underneath it. Preparing both at once is possible, but the documents are not interchangeable, and the interim's preparation serves whichever conversation is actually scheduled.
Then set the boundary on outcomes. The interim prepares materials, stress-tests assumptions, and sits in meetings; the mandate should not hand one person the authority to commit the company to a round or a sale. That boundary protects everyone involved. Preparation is controllable and judgeable; closing is not, and a mandate that blends the two ends up grading the interim on weather.
Why a clean split still fails: causes worth checking
Most mandates that fail do not fail on competence. They fail on access, expectations, and the informal routes that old habits keep open. When a split looks right on paper and the function still stalls, work through the causes in order, because each correction is cheap early and expensive late.
Start with access. Banking portals, accounting systems, and the data room arrive in the second week, which means the first week was introductions without work. The correction is provisioning before day one, in the same motion as signing the mandate, with the access list attached to the authority matrix so the two documents agree.
Next comes the two-audience problem. The chief executive wants the routine protected; a board member wants the financing package accelerated; both believe they stated the mandate. The correction is a one-page priority memo that ranks the projects, agreed by the chief executive and the board contact in the same week the interim starts. Priorities that are not shared are not priorities.
A quieter cause is the shadow of the returning CFO. People who trust their absent finance chief route questions around the interim or quietly wait out the leave. The correction is public and cheap: the chief executive states, in writing and in the operations meeting, who decides what until further notice. Silence reads as temporary, and temporary reads as optional.
Drift is the last cause. Every new problem discovers a reason to walk into finance, and the three pages quietly become twelve. Build a change rule into the mandate: anything added pushes something out, extends the engagement, or gets a written exception. A mandate that cannot say no ends the way the undivided one would have, only with better paperwork.
How to judge the first 30 to 90 days without assuming results
Judge the mandate by artifacts and behavior, and leave outcomes out of the scoring. Artifacts exist or they do not; outcomes depend on markets, counterparties, and luck, none of which report to your interim. A grading system that mixes the two will misread a well-run leave as a failure, or a lucky quarter as proof of process.
The checkpoints look like this:
By the end of the first 30 days: a written priority memo, a confirmed authority matrix, provisioned systems, and documented assumptions under the current forecast.
By day 60: the routines running with named owners on the finance team, board materials delivered on the calendar, and a decision log current enough to read.
By day 90: the priority project in reviewable draft, the handoff plan started, and any variance between the memo and reality explained in writing rather than smoothed over.
These checkpoints describe state, not speed. A draft model with honest assumptions at day 90 is a healthy result; a finished model nobody can defend in a board meeting is a warning sign wearing good news. Ask what exists, who can explain it, and what changed since the last look. Those questions work in any order and never require a benchmark you do not have.
Keep the financing out of the scorecard. If a raise or a loan is in view, the interim's work changes the quality of your preparation, and preparation deserves to be judged hard. The closing depends on counterparties, terms, and timing you do not control, and crediting or blaming the interim for it teaches everyone the wrong lesson about what a mandate is.
One more check costs nothing: ask the finance team, interim cfo services privately, what has gotten clearer since the Interim cfo services arrived. Clearer priorities and a more useful forecast are the outcomes a mandate can actually produce. If the honest answer is "more meetings," the split exists on paper and not in the calendar, which is a cause worth revisiting before it compounds.
The return date: knowledge transfer as a deliverable
Treat the handoff as a deliverable with a due date, on the same page as the projects. The symptom of a missing one is familiar: the leave ends, the interim departs, and the function runs on an inbox nobody else can search. The cause is a mandate that described coverage and forgot to describe what gets left behind.
The correction is to require artifacts that outlive the engagement: a short memo per routine, the assumptions register behind the forecast, the decision log, and a living handover document updated while the work happens rather than reconstructed at the end. Reconstruction is where details die, because the person reconstructing is the only one who cannot see what is missing.
Knowledge transfer has mechanics, and they differ by ending. For a returning CFO, plan a reverse overlap: the returner sits in on one close and one board cycle while the interim is still present, and reads the log before the first meeting. For a permanent hire, the transfer is bigger: the interim's memo on the function becomes the new CFO's first map, and a written view of the team belongs among the deliverables.
Define done in terms someone can test. Done means the close runs without the interim in the room, the variances in the board pack can be explained by a team member, and the forecast's assumptions can be defended by whoever owns the document next month. If those statements hold, the leave cost time and money and still left the function stronger, which is the realistic best case.
The dates matter more than the ceremony. Put the handoff tasks in the project page with real deadlines, and let the checkpoints include them, so transfer is inspected at day 60 rather than discovered on the last day. Companies that skip this step tend to meet the same leave twice: once as coverage, once as archaeology.
The split changes with the company's stage
The three pages keep their shape, but their weight moves with the company. A mandate copied from a template, or from what worked somewhere else, misallocates the leave because it assumes the same priorities exist everywhere. Set the weight by situation:
SituationDecision rights pageRoutines pageProjects page
Small team, no financing in viewTight limits, simple matrixClose and cash forecast, minimal reportingLight: controls and cleanup
Growth stage, board and investors activeClear tiers, board calendar respectedFull reporting calendar, forecast disciplineForecast rebuild, reporting upgrades
Financing or transaction in viewExact limits, no solo commitmentsClose quality under scrutinyPackage preparation, readiness review
Read the last row with care, because it is where founders feel the temptation most. When a financing is in view, the project page looks like the whole job, and skipping the close to polish a model feels efficient. The opposite holds: the close is what makes the model credible, and a lender or an investor will find the seam between them. The routines carry the projects, not the reverse.
Sector habits bend the split further. A company with inventory has a cash rhythm tied to buying and selling cycles, so the forecast routine weighs more. A services firm with long contracts cares about revenue timing and recognition, so close discipline grows. The honest move is matching the pages to how your cash actually behaves, then writing that reasoning into the priority memo.
Situations also change mid-leave, which is the strongest argument for keeping each page to one sheet. If a financing conversation appears midway through the leave, interim cfo services revisit the split in writing: what moves from the routines page to the projects page, and what waits. A mandate is an assumption about a period of time, and periods have a habit of not cooperating.
A short list to verify before the mandate is signed
Before signature, or before the leave starts when you have that luxury, run the check below. Each item is a document or a state of the world, so every answer is a yes or a no, and a no comes with a known fix.
Run the check with whoever will own the relationship with the interim, and include the departing CFO when the leave is planned, since the routines page usually lives in that person's head. When a financing or a transaction is in view, add the board contact, because the exclusions on the projects page belong in front of the people most tempted to forget them.
The authority matrix exists, matches the governance documents, and has been shared, so nobody has to guess at a signature.
Systems access is provisioned, from banking to the accounting platform, and tested once before day one.
The priority memo is agreed by the chief executive and the board contact, and ranks the projects explicitly.
Routines are listed by deliverable, owner, and deadline, including every report already promised to outsiders.
Projects are named with dates, and the exclusions are written, especially around commitments the interim may not make alone.
Knowledge transfer and the decision log are required deliverables with deadlines, resting inside the project page.
After signature, the discipline is lighter: revisit the three pages at the checkpoints, and revise them when the situation moves. The split is what makes an interim CFO during an executive leave survivable for the company and fair to the person holding the role, and it costs less than one week of confusion later. Write it down, check it, and let the leave be a leave.