Fractional Onboarding Checklist
When To Use
Week two and you are still waiting for logins and nobody told the team who you are. On two days a week, a lost fortnight is most of the first month. Use this as soon as the engagement is agreed, to ask once, in one list, for everything the first 30 days depend on.
When Not To Use
If you need to work out who matters and what each person needs from you, run Stakeholder Map after this. If the rules themselves (decision rights, response times) are not agreed, run Engagement Charter first; the announcement is built from it.
Inputs
- The charter or the statement of work: the outcome, your days, your decision rights
- The two or three questions your diagnostic must answer, if you have them
- What you have already been sent, and who on the client side handles access
If you have none of this, I start from your function and the outcome in your words, and mark the list as a first draft.
Approach
An onboarding sequence for a fractional executive, following a public playbook and a fractional marketplace's guidance: documents before the start, access on day one, a clear signal of authority from the CEO, introductions with a reason attached, a rhythm, and a first deliverable in week one. The judgment is restraint: ask for what the outcome needs, not for everything. The failure this prevents is the team treating you as a passing contractor because nobody said whether you own the function.
Workflow
- Ask at most three questions: what is your start date; who handles access and introductions on their side; what has the CEO already told the team?
- List the documents to receive before day one, each tied to the outcome or a diagnostic question: plans, the last board papers, the numbers for your function, the org chart, the contracts you will inherit.
- List system access by role, with the level you need (read, edit, admin) and the reason. Ask for the minimum; admin rights you do not need are a risk you carry.
- Draft the CEO's announcement for the CEO to send: what you are there to achieve, your days, what you decide, how to reach you. It comes from the charter word for word where it can.
- Propose the first-week introductions, each with one line on why that person matters to the outcome, and a standard agenda: their goals, what gets in the way, what they need from your function.
- Set the rhythm (weekly sync, team meeting you join, the update day) and the first deliverable with its date. Give every line an owner on the client side, a needed-by date and a status, so you can chase one list.
Output Format
# Fractional Onboarding Checklist
Client: [name] · Start date: [date] · Sent to: [role] on [date]
## Before day one
| Item | Why it is needed | Owner (client side) | Needed by | Status |
|---|---|---|---|---|
| [document] | [outcome or diagnostic question] | [role] | [date] | [open / received] |
| [system, access level] | [reason] | [role] | [date] | [open / done] |
## The announcement (for the CEO to send)
[Draft: why you are there, your days, what you decide, how to reach you]
## First-week introductions
| Person | Role | Why this person matters to the outcome | When |
|---|---|---|---|
| [name] | [role] | [one line] | [date] |
## Rhythm and first deliverable
Weekly sync: [day] · Meetings joined: [list] · First deliverable: [what] by [date]
## Decision
[CEO] sends the announcement and confirms the owners of each line by [date]; [you] send the list.
Done When
- Every item has a reason, an owner on the client side and a needed-by date
- The announcement states your decision rights in the charter's words
- Each introduction has one line on why it matters
- A first deliverable and its date are named
Quality Bar
- Ask for the minimum access the work needs, and say when it should be removed
- Introductions are described by role and reason, never by reputation
- Nothing is requested "just in case"; an item with no reason is cut
- Access and security rules are the client's; anything in their policy you are unsure about: check with a qualified adviser
- The CEO sends the announcement, not you and not Claude, and material received for this client stays in this client's workspace only
Next
Run frac-stakeholder-map (Stakeholder Map) to record who the work depends on and what each has said they need.
About the makers
This pack is made by 90n (90n.ai): AI-native ways of working and tools for Product, Marketing and HR teams, built by ex-McKinsey founders. We map where time and money leak, redesign the work around AI and stay until your people run it themselves, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).
1---2name: frac-onboarding-checklist3description: Builds the request list a fractional leader sends before day one, with the documents, the system access, the first-week introductions with one line on why each matters, how the CEO announces your role and authority, the meeting rhythm and the first deliverable with its date. Use for "run frac-onboarding-checklist", "onboarding checklist for a fractional executive", "what to ask for before day one", "still waiting for logins", "nobody told the team who I am", "first week as a fractional leader", "draft the announcement of my role", part of the Claude for Fractional Leaders Pack by 90n.4metadata:5 source: https://skillmd.com/skills/polar-bear-org/frac-onboarding-checklist6---78# Fractional Onboarding Checklist910## When To Use11Week two and you are still waiting for logins and nobody told the team who you are. On two days a week, a lost fortnight is most of the first month. Use this as soon as the engagement is agreed, to ask once, in one list, for everything the first 30 days depend on.1213## When Not To Use14If you need to work out who matters and what each person needs from you, run Stakeholder Map after this. If the rules themselves (decision rights, response times) are not agreed, run Engagement Charter first; the announcement is built from it.1516## Inputs17- The charter or the statement of work: the outcome, your days, your decision rights18- The two or three questions your diagnostic must answer, if you have them19- What you have already been sent, and who on the client side handles access20If you have none of this, I start from your function and the outcome in your words, and mark the list as a first draft.2122## Approach23An onboarding sequence for a fractional executive, following a public playbook and a fractional marketplace's guidance: documents before the start, access on day one, a clear signal of authority from the CEO, introductions with a reason attached, a rhythm, and a first deliverable in week one. The judgment is restraint: ask for what the outcome needs, not for everything. The failure this prevents is the team treating you as a passing contractor because nobody said whether you own the function.2425## Workflow261. Ask at most three questions: what is your start date; who handles access and introductions on their side; what has the CEO already told the team?272. List the documents to receive before day one, each tied to the outcome or a diagnostic question: plans, the last board papers, the numbers for your function, the org chart, the contracts you will inherit.283. List system access by role, with the level you need (read, edit, admin) and the reason. Ask for the minimum; admin rights you do not need are a risk you carry.294. Draft the CEO's announcement for the CEO to send: what you are there to achieve, your days, what you decide, how to reach you. It comes from the charter word for word where it can.305. Propose the first-week introductions, each with one line on why that person matters to the outcome, and a standard agenda: their goals, what gets in the way, what they need from your function.316. Set the rhythm (weekly sync, team meeting you join, the update day) and the first deliverable with its date. Give every line an owner on the client side, a needed-by date and a status, so you can chase one list.3233## Output Format34```markdown35# Fractional Onboarding Checklist36Client: [name] · Start date: [date] · Sent to: [role] on [date]37## Before day one38| Item | Why it is needed | Owner (client side) | Needed by | Status |39|---|---|---|---|---|40| [document] | [outcome or diagnostic question] | [role] | [date] | [open / received] |41| [system, access level] | [reason] | [role] | [date] | [open / done] |42## The announcement (for the CEO to send)43[Draft: why you are there, your days, what you decide, how to reach you]44## First-week introductions45| Person | Role | Why this person matters to the outcome | When |46|---|---|---|---|47| [name] | [role] | [one line] | [date] |48## Rhythm and first deliverable49Weekly sync: [day] · Meetings joined: [list] · First deliverable: [what] by [date]50## Decision51[CEO] sends the announcement and confirms the owners of each line by [date]; [you] send the list.52```5354## Done When55- Every item has a reason, an owner on the client side and a needed-by date56- The announcement states your decision rights in the charter's words57- Each introduction has one line on why it matters58- A first deliverable and its date are named5960## Quality Bar61- Ask for the minimum access the work needs, and say when it should be removed62- Introductions are described by role and reason, never by reputation63- Nothing is requested "just in case"; an item with no reason is cut64- Access and security rules are the client's; anything in their policy you are unsure about: check with a qualified adviser65- The CEO sends the announcement, not you and not Claude, and material received for this client stays in this client's workspace only6667## Next68Run frac-stakeholder-map (Stakeholder Map) to record who the work depends on and what each has said they need.6970## About the makers7172This pack is made by 90n ([90n.ai](https://90n.ai)): AI-native ways of working and tools for Product, Marketing and HR teams, built by ex-McKinsey founders. We map where time and money leak, redesign the work around AI and stay until your people run it themselves, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).