Interim CFO permanent successor onboarding is the handoff period in which a temporary finance leader transfers the numbers, the decisions, and the relationships to the person who will stay. The first 30 days decide whether that transfer actually holds. In practice, the companies that get it right treat the handoff as a project with a written scope, named deliverables, and a date when the interim leader steps back, not as a friendly overlap where two people kind of watch the same cash position.

Why the first 30 days decide whether the handoff holds

An interim CFO usually arrives during a squeeze: a resignation, a financing conversation, a run rate that stopped making sense. That leader makes calls fast, often with incomplete documentation, and a lot of the reasoning lives in their head. The permanent successor walks into the opposite situation. There is time, but there is also a finished story that nobody wrote down. The first month is when that story gets captured or lost.

The cost of a sloppy handoff shows up in cash, not in org charts. If the successor does not know why the company moved to weekly cash forecasting, or which customer payment terms were stretched during the gap, they may quietly reverse decisions that were holding the business together. A payroll run that clears twice a month hides a lot until a tax deposit or a vendor prepayment lands in the same week.

There is also a people problem. Your bookkeeper, your controller if you have one, and your department heads built habits around the interim leader. When the successor changes a report format or asks for a different approval path, some of those people will treat it as a step backward unless the transition plan says otherwise. The first 30 days are as much about transferring authority as transferring knowledge.

What "holding" looks like is concrete. By the end of the first month, the successor should be able to produce the cash forecast without asking the interim leader a single question, know which decisions are still reserved for the interim or for you, and have met every external party who matters. Anything short of that means the interim is still the CFO and the successor is still an observer.

One caution before the rest of this guide: not every handoff needs the same depth. A successor promoted from inside the company, say a controller who already runs the close, needs relationship transfer and strategic context more than basics. An outside hire needs almost everything transferred explicitly. The plan should reflect which situation you are in.

In practice, the companies that treat the handoff as a 30-day project with an owner and a deliverable list end the month with a real CFO. The ones that improvise end it with two part-time versions of one job.

Start the handoff with a written mandate and decision rights

The first document to produce is not a report. It is a one or two page mandate that says what the permanent CFO owns, what the interim still owns until a set date, and what only the owner decides. Without it, you get the worst outcome of a transition: nobody is sure who can approve a spend, so everything escalates to you.

The mandate should cover a short list of areas, each with a named owner and an end date for the overlap. A practical version looks like this:

Cash management: bank signatories, payment approvals, and the minimum cash threshold that triggers a conversation with you. Forecasting: who produces the weekly or monthly cash forecast and who can change its assumptions. External parties: who talks to lenders, investors, and the audit or tax firm, and who just receives the summary. Hiring and team decisions: whether the successor can restructure finance roles during the transition or must wait. Commitments: whether the interim can sign new contracts in the final weeks, or only the successor from a given date.

Decision rights matter more than title here. An interim leader wrapping up should generally stop making new commitments well before the last day, because a commitment made in week four of the overlap becomes the successor's problem with zero context. In practice, a clean rule works: the interim can amend or close existing workstreams, but anything new goes to the successor from day one of the handoff.

Write down the reserved decisions too. As the owner, you probably want to keep approval authority over things like credit terms for large customers, any change in lender relationships, and compensation changes in the finance function. The mandate is where you say so, rather than negotiating each case when it comes up.

A short table helps make the overlap explicit, and it doubles as the agenda for your weekly transition check-in:

AreaDuring overlapAfter day 30

Weekly cash forecastSuccessor produces, interim reviewsSuccessor owns Lender and investor callsInterim leads, successor attendsSuccessor leads Payment approvals above thresholdBoth signSuccessor signs, you set threshold New contractsSuccessor onlySuccessor only

If you never wrote a mandate for the interim leader either, this is the moment to fix both gaps. The successor's mandate and the interim's exit scope should be two views of the same document, so there is never a week where an area belongs to nobody.

Expect some friction from the interim here. Good interim leaders know a defined exit is part of the job, but a leader who keeps finding "one more thing to fix" is stretching the engagement. The mandate gives you something to point at that is not personal.

What the interim leader must hand over, in writing

Knowledge transfer fails when it stays conversational. A call where the interim explains the numbers is pleasant and evaporates. The handoff package should be a small set of written documents the successor can reread, and the interim should draft them in the first half of the overlap, not the last week.

The core package is short. Each item answers a question the successor would otherwise have to reconstruct under pressure:

A cash forecast model with its assumptions documented: which customers pay late, which vendors must be paid on the day, and which weeks are historically tight. A list of open commitments: contracts signed, deposits paid, hiring offers extended, and anything with a date in the next two quarters. A decision log: the significant calls the interim made, why, and which ones were reactions to the gap rather than long-term choices. Contact context: lenders, investors, board members, the external accounting firm, key vendors, each with the state of the last conversation. Close and reporting calendar: who does what and when, including any lender or investor reporting deadlines.

The decision log deserves emphasis, because it is the piece everyone skips. An interim leader under time pressure often makes reversable choices: stretching a payment run, delaying a hire, moving a marketing spend. The successor who inherits these without the reasoning will either blindly keep them or blindly reverse them, and both can hurt. One page per major decision, dated, is enough.

Watch for the documentation that exists only in someone's head. In a smaller company, that often includes the actual mechanics of payroll timing, how the sales team's commissions get calculated, and which customer invoices quietly roll every month. If the interim cannot point to a written procedure, the handoff of that item is not done.

Format matters less than completeness, but a shared drive folder with clear names beats a stack of attachments. The test: could the successor find the current forecast without asking anyone? If not, the transfer has not happened, regardless of how many meetings took place.

A hypothetical shows the cost of skipping this. Suppose an interim leader negotiated extended terms with a packaging supplier to protect cash, verbally, with no paper. The successor, seeing a stressed vendor relationship, pushes to consolidate volume with a cheaper supplier for a better unit price. The cheaper supplier demands prepayment the company cannot cover in that week. Nobody did anything wrong; the context just never moved.

Set a checkpoint around day 15: the successor lists every item they still cannot execute alone, and the interim fills those specific gaps. That is more useful than a general "any questions?" in week four.

Set priorities based on why you needed an interim at all

The first 30 days of a permanent CFO should serve the reason the seat went interim in the first place. A company covering a resignation has different needs than one heading into a financing round or cleaning up after fast growth, and the onboarding plan should say so explicitly.

Three situations cover most cases. If the gap came from growth, the successor's priority is usually forward-looking: a forecast the owner can actually use for hiring and spending decisions, and visibility into whether the current burn rate matches the plan. If the gap came from a financing conversation, the priority is lender and investor readiness: statements that hold up to questions, and a single person who speaks for the numbers. If the gap came from a transaction, the priority is data room hygiene and clean internal controls, because diligence punishes surprises.

Resist the temptation to hand the successor all three. In practice, a new permanent CFO who tries to rebuild the chart of accounts, retool the forecast, and refresh investor materials in the same month does none of them well. Pick the one that matches the company's next decision, and let the others queue.

It helps to separate what must be stable from what can be improved later. The close, payroll, and cash visibility are stability items: the successor verifies they work before changing anything. The forecast model, the reporting format, and the budgeting process are improvement items, and they can wait a cycle. New leaders who reorganize the close in their first month create the exact fire drill they were hired to prevent.

The interim's role here is context, not advocacy. A leader who spent months holding things together will have opinions about what matters most, and some of those opinions are worth hearing. But the priority call belongs to you and the successor, because the successor lives with the consequences after the interim leaves.

Write the top three priorities for the first 30 days on one page, in order. Anything that does not fit on that page waits. This sounds rigid, and it is; the constraint is what makes it work.

Connect the finance work to how the business actually runs

A recurring failure in finance transitions is a clean handoff to an empty room: the new CFO inherits perfect models and no connection to operations. The first 30 days should wire the finance function into the routines of the business, or the successor ends up reporting on a company they never touch.

That means scheduled contact with the people who generate the numbers. In a growing company, the practical minimum usually looks like a weekly conversation with sales leadership about the pipeline and collections, a regular check with whoever runs delivery or operations about capacity and cost, and a monthly session with you on the plan versus reality. Everything else can flex.

The operating meeting matters most. If the company already has a weekly or monthly leadership meeting, the successor should attend from week one and gradually take the finance portion, with the interim fading out of the room rather than both standing there presenting. Two finance voices in one meeting reads as uncertainty to your team.

Forecasting is where the connection either forms or fails. A cash forecast built only from the accounting system tells you what has already happened. A useful one also carries what operations knows is coming: the hire starting next month, the equipment quote under review, the customer who always pays ten days late. The successor should learn to pull those inputs from named people, not guess them.

Watch for handoffs that overload one direction. If every finance question during the transition still routes to the interim, the operating team never builds the habit of going to the successor. Announce early, clearly, and once: from a stated date, the successor answers finance questions. Routing through the interim after that date delays the answer and slows the transfer.

Internal controls deserve a mention here too, because they are an operating habit, not a document. Who approves what, who touches the bank account, who can change vendor records. The successor should map these in the first month, partly to inherit them and partly because a leadership change is exactly when control gaps get noticed from outside, including by auditors and lenders.

By day 30, a reasonable test is: does each department head know the successor by name, know what to bring to them, and know the successor is the one who decides? If the answer is vague, the connection work is not done.

Transfer investor and lender relationships without losing credibility

External parties judge a transition faster than your own team does. Lenders and investors met the interim, may have built trust with them, and will read a bumpy handoff as a signal about the company, not just the finance function. The relationship transfer deserves its own plan inside the first 30 days.

The mechanics are simple and often skipped. The successor should review the last several communications with each external party: update letters, covenant compliance certificates, board reporting packages, and any open questions from lenders. Then the interim introduces the successor in writing, with a sentence on why the hire strengthens the company. A joint call or meeting follows for the relationships that carry weight.

Consistency of message matters more than polish. If the interim told investors the company would hit a certain milestone, the successor needs to know that commitment exists, whether it still holds, and who communicates if it slipped. Investors forgive changed plans that get explained early. They do not forgive a new CFO who does not know what was promised.

Reporting cadence should carry over before it changes. The successor keeps the existing format and deadlines for at least one full cycle, then proposes adjustments with reasons. Rewriting the investor update in week two reads, fairly or not, as inexperience. In practice, the sequence "run it as-is once, then improve it" costs almost nothing and buys credibility.

If a financing conversation is active during the transition, be explicit about roles. Typically the successor leads the numbers and the process, the interim supports as long as needed, and you remain the decision maker on terms. Lenders will ask who to call; there should be one answer.

Two warnings from the direction of over-promising. First, neither the interim nor the successor should make new commitments to external parties during the overlap without your sign-off, since both have incomplete pictures of each other's work. Second, do not let the transition itself become the headline of your investor update. A sentence on the appointment, then straight to the business: performance, cash, and what is next.

Track the transfer as a checklist with dates, because relationship handoffs drift otherwise. Every lender, every active investor, the external accounting firm, and any advisor with a live workstream: introduced, communicated to, and confirmed as the successor's contact.

A first-month checklist for cash visibility and controls

Cash and controls are where a half-finished handoff bites first, so verify them item by item rather than trusting the general sense that everything is fine. This checklist is deliberately unglamorous; each item is something the successor can confirm directly, usually within a day.

Bank access: the successor has view access to every account immediately and signer status on the accounts that need it, and the interim's own access has a defined end date. Cash forecast: the successor has produced the current forecast at least once, unassisted, and can explain every major assumption in it. Payment runs: the successor has run or supervised at least one full payment cycle, including payroll, and knows the timing constraints around tax deposits. Receivables: the successor knows the top customers, who pays late, and who owes what, and has seen the aging report with the interim's annotations. Payables: the successor knows which vendors have terms, which require prepayment, and any verbal arrangements made during the interim period. Reconciliations: bank and account reconciliations are current as of the handoff, with no inherited mystery items. Access controls: who can log into the accounting system, who can change vendor bank details, and whether anyone who left the company still has access. Compliance calendar: payroll tax filings, sales tax, estimated income tax, and any loan covenant reporting, each with its next due date and its owner.

Two of these deserve extra attention. Vendor bank detail changes are the classic fraud vector during transitions, precisely because everyone assumes someone else verified the new account. The successor should confirm any vendor bank change made in the last few months through a known contact, not through the email that requested it.

Covenant compliance is the second. If the company has debt, the successor should read the credit agreement in the first week, not when a certificate is due. Ratios, definitions, reporting deadlines, and any restriction on distributions or additional debt. Discovering a covenant issue after the interim leaves is a preventable emergency.

If any checklist item cannot be closed in the first month, that is useful information, not a failure. It becomes a named gap with an owner and a date, rather than a vague worry. What you want to avoid is the item nobody thought to check.

In practice, walking this list together once, in a single meeting with both finance leaders present, surfaces more than weeks of separate conversations. The questions the successor asks while pointing at each item are the real transfer.

Keep the completed checklist. It doubles as evidence, for you and eventually for a board or lender, that the transition was managed rather than improvised.

How to judge progress at day 30 without fooling yourself

Assessing the handoff is different from assessing the new cfo interim's performance, and mixing the two leads to bad conclusions. The first month's question is narrow: did the transfer complete? The successor's broader results come later and depend on the company's situation, not on onboarding mechanics.

Judge the handoff on observable facts. The mandate exists in writing and both leaders point to the same version. The written transfer package is complete, and the successor can execute the core routines, forecast, payment runs, close oversight, and reporting, without calling the interim. External parties communicate with the successor as the default contact. The checklist from the previous section is closed or has named open items with dates. Each of these is verifiable, not a feeling.

It also helps to listen for specific signals in how the successor talks. By day 30, they should be explaining the company's cash position in their own words, including the quirks, rather than repeating the interim's phrasing. They should have raised at least one thing they would do differently, with a reason. A successor who agrees with everything the interim built has either not looked closely or is not comfortable disagreeing, and both are problems you want to surface early.

For the CFO's own early performance, use leading indicators rather than outcomes. Quality of questions in meetings, accuracy of the first few forecasts against what actually happened, responsiveness of the operating team to finance requests. Results like financing closes or cost reductions take quarters and depend on circumstances; onboarding metrics that promise them set everyone up to fail.

Set the review as a conversation with the successor, not a verdict delivered to them. Ask what is still harder than it should be, what they cannot see yet, and what they need from you. The answers tell you whether the gaps are in the handoff, in the role's definition, or in the fit, and those three call for different responses.

Give the arrangement more than one checkpoint. A brief review at day 30 on the transfer itself, then a fuller one around day 90 on whether the role and the person are working out. Two dates beat a vague "let's see how it goes," which in practice means nobody evaluates anything.

Questions to confirm with a professional before you commit to a plan

Before finalizing any onboarding arrangement, whether you are working with an interim staffing firm, an advisory practice, or assembling the plan yourself, put these questions to the people involved and get answers you can write down. The questions are as useful for what they reveal as for what they produce.

What exactly does the interim leader hand over, and which of those items exist in writing today rather than in conversation? Which decisions does the interim keep until which date, and which move to the successor on day one of the handoff? Who introduces the successor to lenders, investors, and the external accounting firm, and by when? What happens to open workstreams, an active financing, a system migration, an audit, if the interim's end date moves? How will we measure whether the handoff is complete, and who calls it complete? What does the permanent CFO's first-quarter mandate cover, and what is explicitly out of scope for now?

The last question matters more than it looks. A successor hired to lead strategic finance through growth needs different authority than one hired to stabilize a close, and the onboarding plan should say which one you hired. If a professional cannot describe the scope they would propose for the role in plain sentences, treat that as information.

Ask about the exit as directly as the arrival. Interim engagements that lacked a defined end date are the usual reason handoffs drag, and a firm or advisor who resists naming one is telling you how the next few months will go. The best interim leaders take pride in making themselves unnecessary; that instinct is exactly what a clean transfer needs.

Confirm the cost of the overlap too, not just the fee for each engagement. Two senior finance salaries for a month is real money for a growing company, and it is worth paying when it buys a real transfer. It is not worth paying for a vague coexistence with no deliverables. The plan you write should make that distinction visible before the invoices do.

And keep one decision for yourself: the date when the interim's access, signing authority, and advisory role end. Everything else in the transition can flex a week in either direction without damage. That date, held firmly, is what turns an interim arrangement into a permanent finance function.