You have hired a senior executive for two days a week. The maths of onboarding is now unforgiving: the first month is not twenty working days, it is eight. Every one of those days spent asking what the job is, chasing logins, or waiting for introductions is billed at the same rate as a day spent doing the job, and it comes out of a much smaller pile.
That is why fractional onboarding cannot be improvised. A full-time hire can absorb a sloppy first month and recover by month three. A fractional executive who loses the first month has lost a quarter of the contact time you will get all year. The fix is cheap: one page written before day one, access prepared in advance, and a 90 day plan both sides agree on.
Before Day One: The One-Page Mandate
The single highest-value document in a fractional engagement is one page long, and the CEO or owner writes it. Not HR, not the executive. The person who is paying for the outcome.
It has six parts:
The role in one sentence. "Own our finances so the board pack is right, cash is planned 13 weeks out, and I stop being the person who answers money questions." One sentence forces clarity about why this seat exists.
Why now. The trigger for the hire: the fundraise, the growth, the departure, the mess. The executive needs to know which fire they were hired to stand near.
Two or three dated outcomes. Not responsibilities, outcomes, with dates. "A monthly close that finishes by day ten, by the end of month two." "A hiring plan for the sales team, agreed by day 60." If everything is a priority, nothing is, and three is the most a part-time executive can genuinely own in a quarter.
Decision rights, in three lists. What the executive decides alone. What they decide with the CEO. What they leave alone entirely. This is the list that prevents the two classic failures: an executive who oversteps in week two, and one who asks permission for everything because nobody told them they could act. Our fractional executive contract guide covers how to carry these rights into the agreement itself.
What has already been tried. The failed system rollout, the consultant's report nobody implemented, the previous hire who left. An executive who does not know this history will propose it all again, and the team will stop listening by the second suggestion.
The numbers to see first. Three or four figures that describe the health of the function: cash and runway for a CFO, pipeline and win rate for a CRO, close time and error rate for a COO. The executive reads these before they meet anyone, so their first questions are informed ones.
Before Day One: The Access Checklist
Alongside the mandate, prepare the practical welcome. This is unglamorous work, and it is where most engagements quietly lose their first two weeks.
- Accounts and access. Email, calendar, the systems and dashboards for their function, the document store, and the communication tools, all working before the start date, all under a company-owned identity. Never let an executive set up company tools under a personal account: when the engagement ends, the access argument starts.
- The document pack. The last board pack or owner report, the current budget or plan, the org chart with names, and the strategy document if one exists. Ten documents chosen on purpose beat a shared drive with four thousand files.
- The meeting map. Which recurring meetings they join, which they lead, and which they skip. A fractional executive's calendar fills by invitation unless someone designs it.
- The introductions. Booked, not promised: their own team first, then the other executives, then the two or three people outside the function who know where the problems actually live.
- The announcement. One short message from the CEO to the company: who this person is, what they own, and that they speak with the CEO's backing. A part-time executive whose authority is rumoured instead of announced spends the first month re-litigating it.
Week One: Listen First
The executive's first week has one job: understand the business before touching it. In practice that means three things.
The kickoff, ninety minutes with the CEO. Walk the mandate line by line. Where the CEO and the executive read a sentence differently, fix the sentence now, in the room, not in month two. Agree what the day-30 summary will contain and when it is due.
The listening round. One-to-one meetings with every direct report and two or three leaders in neighbouring functions. The same questions each time: what is working, what is broken, what should never change, and what would you fix first? The patterns across the answers are the real audit. Where everyone tells the same story, believe it. Where the stories conflict, that conflict is the finding.
The numbers, read against the stories. The executive compares what the data says with what the people said. A function whose team reports health while the figures decline, or the reverse, tells the executive exactly where to dig in month two.
One rule governs the week: no big announcements. The team is watching to see whether this person listens. An executive who restructures in week two spends trust they have not earned yet, on changes they cannot yet judge. The exception is a problem actively costing money or breaking rules; fix that immediately and say why.
Days 1 to 30: Audit and the Written Summary
The first month ends with a deliverable, and it is not a slide deck of impressions. It is a short written summary, usually three to five pages, covering: what the executive found, the top risks and opportunities in order, what they propose to do in the next 60 days, and what they need from the CEO to do it.
This document does three jobs. It proves the executive understood the business rather than importing a standard playbook. It gives the CEO a fair basis for the first real conversation about direction. And it becomes the baseline for the day-90 review: the engagement is later judged against what was found and promised here, not against moving expectations.
By day 30 the executive should also have fixed the small, obvious things that cost nothing to fix: the report nobody reads, the approval step that exists because it always has. Early visible competence buys patience for the larger work.
Days 31 to 60: Decisions and Early Wins
Month two is where the mandate turns into a plan the whole function can see. The executive agrees priorities with the CEO, assigns owners and dates, and sets the measures that will show whether the work is working. Those measures should mix the final outcome with the early signs that predict it: revenue matters, but in month two the pipeline that produces revenue is the fairer test.
Pick one or two early wins deliberately: visible, low-risk, and valued by the team rather than only by the CEO. A close that finishes on time. A hiring process that stops losing candidates. A pricing decision that had been postponed for a year. Early wins are not vanity; they are how a part-time executive earns the standing to make the harder calls in month three and beyond.
This is also the month where the weekly check-in proves its worth. Same slot, every week, thirty to sixty minutes: what was found, what was decided, where the two of you disagree, and what changes in the mandate. Most failing engagements do not fail in a dramatic meeting. They drift, one cancelled check-in at a time.
Days 61 to 90: Delivery and the Review
By the third month the rhythm should run without effort: the reporting lands on time, the team brings problems to the executive directly, and the first results agreed in the day-30 summary are visible, or honestly explained where they are not.
Then the review, booked for 90 minutes back at the start of the engagement. Compare the mandate with reality, line by line. What was delivered. What the numbers did against their starting point. What the team says. Then decide the next phase in plain terms: continue, expand the days or the scope, convert the executive to a full-time hire, or end the engagement cleanly with a proper handover, which our contract guide covers.
Skipping this review is the most expensive small mistake in fractional hiring. Engagements that drift past day 90 unchecked are where scope creep, mismatched expectations, and quiet dissatisfaction take root, and by the time they surface, you have paid for another quarter.
The Warning Signs
Watch for these in the first 45 days, while they are still cheap to fix:
- No written summary by day 30, or one that could have been written without visiting the company.
- Meetings attended and opinions offered, but no decisions recorded anywhere.
- Access or information problems still being raised in week three. That one is on the company, not the executive.
- A proposal for major spend or a restructure before the diagnosis exists.
- The weekly check-in cancelled twice in a row, by either side.
Any single sign is a conversation. Two or more mean reset the engagement now: rewrite the mandate together, or accept that the fit is wrong and end it inside the trial period, which is exactly what the trial period is for. Our guide on how to hire a fractional CXO covers the selection mistakes that produce these signs.
Conclusion: The First 90 Days Are the Engagement in Miniature
A fractional executive who is well onboarded shows you, within one quarter, exactly what the next year will look like: clear priorities, decisions that stick, reporting you can trust. One who is badly onboarded shows you the same thing, at the same price.
Write the page. Prepare the access. Book the review before the start date, not after the drift. When you are ready to hire, browse executives by role in the directory.
More guides like this, weekly.
One hiring insight, one exec resource, one data point. No spam.