Engagement Charter
When To Use
You were hired to lead and every decision still goes back to the founder. The contract says two days a week and an outcome; it does not say whether you can approve a hire, change a supplier or stop a project, or how fast you answer on the days you are elsewhere. This page answers: how do we work week to week, and who decides what?
When Not To Use
If you need the signed commercial baseline (deliverables, acceptance, fee, exclusions, exit triggers), run Fractional Statement of Work; no fee or legal term belongs on this page. If the friction is with the team and not the CEO, run Team Interface Agreement.
Inputs
- The signed statement of work, or what was agreed on outcome and days
- Three to five real decisions from the last weeks in your function, and who made each
- When your days fall for this client, and the channels you will watch on the other days
If you have none of this, I start from the outcome and the days in your words, mark both "not yet signed" and mark the page as a first draft.
Approach
A one-page scope with decision rights in three lists, as a fractional marketplace's guidance and a public playbook for fractional executives describe it: what the leader decides alone, what they recommend for approval, what stays with the CEO. The judgment is to fill the lists from real decisions, not from principle. The failure this prevents is the company paying for leadership and getting advice: every choice waits for the founder's calendar, and three months in nobody can say what you were allowed to do.
Workflow
- Ask at most three questions: which recent decisions in your function got stuck or went back to the founder; which days are this client's, and how do they reach you in between; has the CEO told the team what your role is?
- Quote the primary outcome and the days from the statement of work by version and date. Do not restate or change them here; if the working reality differs, name the gap for a scope change request.
- Sort the real decisions into the three lists: you decide, you recommend and the CEO approves, stays with the CEO. Test each line with "who decided this last time, and how long did it take?". Add limits the CEO sets (spend, hiring, contracts) as [limit the CEO sets].
- Write the working rules: the days and when they fall, the channels, a response window in hours for other days, and one urgent route with what counts as urgent. A reply within minutes on an off day trains everyone to expect it.
- Write what you are not doing, in plain words that point to the statement of work's exclusions, and how you say you use AI on this work.
- Set the rhythm and the reviews: the weekly sync, the day-30, 60 and 90 reviews and what each looks at, and the likely exit (a finish at a milestone, a continuing seat, a path to a full-time hire). The CEO agrees the page and announces the role; the page is revised at each review without a contract change.
Output Format
# Engagement Charter
Client: [name] · Agreed with: [CEO] · Version: [n], [date] · Baseline: statement of work [version, date, or "not yet signed"]
## Outcome and days
Primary outcome (quoted from the statement of work): [one sentence] · Days: [which days, how they fall]
## Decision rights
| I decide | I recommend, the CEO approves | Stays with the CEO |
|---|---|---|
| [decision, with any limit the CEO sets] | [decision] | [decision] |
## How we work
- Channels: [channels] · Response on other days: within [hours you set] · Urgent route: [route] for [what counts as urgent]
- Weekly sync: [day, length] · Written update: [day]
- Not doing: [plain words, see statement of work exclusions] · AI use: [one line]
## Reviews and exit
| Review | Date | Looks at |
|---|---|---|
| Day 30 / 60 / 90 | [dates] | [access and assessment / plan / results and the decision to continue] |
Likely exit: [milestone finish / continuing seat / path to a full-time hire]
## Decision
[CEO] agrees the three lists and announces the role to the team by [date]; [you] bring the page to each review.
Done When
- Every line in the three lists comes from a real or expected decision, with no line in two lists
- Outcome and days are quoted from the statement of work, not rewritten
- There is a response window, an urgent route and a definition of urgent
- The page fits on one side and carries no fee and no legal term
Quality Bar
- Lists name decisions, never people's worth or reliability
- Response times are set by you from the days you really have; I suggest no standard
- Where the charter and the statement of work disagree, the statement of work wins and the gap is named
- Limits on spend, hiring and contracts are the CEO's to set and stay bracketed until they do
- Claude drafts from what you give it, uses nothing from another client's charter, and the CEO and you agree it in person
Next
Run frac-onboarding-checklist (Fractional Onboarding Checklist) to ask for the access, introductions and announcement the charter needs.
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-engagement-charter3description: Drafts the one working page a fractional leader agrees with the CEO, with the single primary outcome, the days and when they fall, decision rights in three lists (you decide, you recommend, stays with the CEO), response times and the urgent route, what you are not doing, review dates and the likely exit. Use for "run frac-engagement-charter", "write an engagement charter", "decision rights for a fractional role", "every decision still goes back to the founder", "rules of engagement with the CEO", "who decides what in my fractional seat", "set response times with my client", part of the Claude for Fractional Leaders Pack by 90n.4metadata:5 source: https://skillmd.com/skills/polar-bear-org/frac-engagement-charter6---78# Engagement Charter910## When To Use11You were hired to lead and every decision still goes back to the founder. The contract says two days a week and an outcome; it does not say whether you can approve a hire, change a supplier or stop a project, or how fast you answer on the days you are elsewhere. This page answers: how do we work week to week, and who decides what?1213## When Not To Use14If you need the signed commercial baseline (deliverables, acceptance, fee, exclusions, exit triggers), run Fractional Statement of Work; no fee or legal term belongs on this page. If the friction is with the team and not the CEO, run Team Interface Agreement.1516## Inputs17- The signed statement of work, or what was agreed on outcome and days18- Three to five real decisions from the last weeks in your function, and who made each19- When your days fall for this client, and the channels you will watch on the other days20If you have none of this, I start from the outcome and the days in your words, mark both "not yet signed" and mark the page as a first draft.2122## Approach23A one-page scope with decision rights in three lists, as a fractional marketplace's guidance and a public playbook for fractional executives describe it: what the leader decides alone, what they recommend for approval, what stays with the CEO. The judgment is to fill the lists from real decisions, not from principle. The failure this prevents is the company paying for leadership and getting advice: every choice waits for the founder's calendar, and three months in nobody can say what you were allowed to do.2425## Workflow261. Ask at most three questions: which recent decisions in your function got stuck or went back to the founder; which days are this client's, and how do they reach you in between; has the CEO told the team what your role is?272. Quote the primary outcome and the days from the statement of work by version and date. Do not restate or change them here; if the working reality differs, name the gap for a scope change request.283. Sort the real decisions into the three lists: you decide, you recommend and the CEO approves, stays with the CEO. Test each line with "who decided this last time, and how long did it take?". Add limits the CEO sets (spend, hiring, contracts) as [limit the CEO sets].294. Write the working rules: the days and when they fall, the channels, a response window in hours for other days, and one urgent route with what counts as urgent. A reply within minutes on an off day trains everyone to expect it.305. Write what you are not doing, in plain words that point to the statement of work's exclusions, and how you say you use AI on this work.316. Set the rhythm and the reviews: the weekly sync, the day-30, 60 and 90 reviews and what each looks at, and the likely exit (a finish at a milestone, a continuing seat, a path to a full-time hire). The CEO agrees the page and announces the role; the page is revised at each review without a contract change.3233## Output Format34```markdown35# Engagement Charter36Client: [name] · Agreed with: [CEO] · Version: [n], [date] · Baseline: statement of work [version, date, or "not yet signed"]37## Outcome and days38Primary outcome (quoted from the statement of work): [one sentence] · Days: [which days, how they fall]39## Decision rights40| I decide | I recommend, the CEO approves | Stays with the CEO |41|---|---|---|42| [decision, with any limit the CEO sets] | [decision] | [decision] |43## How we work44- Channels: [channels] · Response on other days: within [hours you set] · Urgent route: [route] for [what counts as urgent]45- Weekly sync: [day, length] · Written update: [day]46- Not doing: [plain words, see statement of work exclusions] · AI use: [one line]47## Reviews and exit48| Review | Date | Looks at |49|---|---|---|50| Day 30 / 60 / 90 | [dates] | [access and assessment / plan / results and the decision to continue] |51Likely exit: [milestone finish / continuing seat / path to a full-time hire]52## Decision53[CEO] agrees the three lists and announces the role to the team by [date]; [you] bring the page to each review.54```5556## Done When57- Every line in the three lists comes from a real or expected decision, with no line in two lists58- Outcome and days are quoted from the statement of work, not rewritten59- There is a response window, an urgent route and a definition of urgent60- The page fits on one side and carries no fee and no legal term6162## Quality Bar63- Lists name decisions, never people's worth or reliability64- Response times are set by you from the days you really have; I suggest no standard65- Where the charter and the statement of work disagree, the statement of work wins and the gap is named66- Limits on spend, hiring and contracts are the CEO's to set and stay bracketed until they do67- Claude drafts from what you give it, uses nothing from another client's charter, and the CEO and you agree it in person6869## Next70Run frac-onboarding-checklist (Fractional Onboarding Checklist) to ask for the access, introductions and announcement the charter needs.7172## About the makers7374This 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).