Weekly CEO Update
When To Use
Your update is a list of meetings and the CEO still asks what you did. On two days a week, the CEO sees little of the work, so the update is most of what they know about the seat. This answers: what moved against the plan, what is off, and what do I need from you by when?
When Not To Use
If something has just turned and cannot wait for the weekly rhythm, run Early Warning Note today. If you need the month against what was agreed, with the scoreboard, run Monthly Value Report.
Inputs
- This client's log for the week: decisions, commitments, days used, scope asks
- The 90-day plan: objectives, measures, targets and the current figures with their source
- With the Gmail connector I can place the draft in your drafts folder; I never send it
If you have none of this, I start from what you tell me moved this week, mark every figure "to confirm" and mark the update as a first draft.
Approach
Bottom line first, then status against the plan, a plain-writing convention described generically: the reader gets the conclusion in the first line and the support underneath. The judgment is to report results, and to report red the week it is true. The failure this prevents is the activity list ("met with sales, reviewed the pipeline, joined the offsite"), which reads as busy and tells the CEO nothing about whether the outcome is nearer.
Workflow
- Ask at most three questions: what is the one thing the CEO should know this week; what do you need them to decide; did any ask this week go beyond the agreed days?
- Write the bottom line in one or two sentences: the main result, or the main problem. If the week went badly, the first line says so.
- For each objective in the plan, give the status as it is this week, the figure with its source, and what moved it. Where nothing moved, write that. Meetings appear only when a decision came out of them.
- List the decisions you need from the CEO, each with the options in a line and the date after which the work waits.
- Name the scope asks that arrived this week and go beyond the agreed days, with the baseline line each touches. They are stated here, not absorbed and not argued.
- Close with next week: the one or two results you are working toward and what you need. Keep it to a screen. You edit it and send it yourself.
Output Format
# Weekly CEO Update
Client: [name] · Week of: [date] · From: [you] · Days used this month: [n] of [n]
## Bottom line
[One or two sentences: the main result or the main problem]
## Against the plan
| Objective | Status this week | Figure (source) | What moved it |
|---|---|---|---|
| [objective] | [on track / at risk / off track] | [figure, system] | [effect, or "nothing moved"] |
## Decisions I need from you
| Decision | Options in a line | By when |
|---|---|---|
| [decision] | [options] | [date] |
## Asks beyond the agreed days
- [ask, from whom, date] · touches: [statement of work or charter line] · proposed: [scope change request / swap / defer]
## Coming week
- [result you are working toward] · I need: [what, from whom]
## Decision
[CEO] answers the listed decisions by [date]; [you] send this update and raise anything urgent in person.
Done When
- The first line is a result or a problem, never a list of activity
- Every figure has a source in your log or the client's systems
- Each decision asked has a date
- The update fits on one screen
Quality Bar
- Status is reported as it is this week; nothing stays "on track" to avoid a conversation
- No adjective does the work of a figure
- Team members are named for decisions and ownership, never assessed
- Scope asks are stated neutrally, with no comment on the asker's motive
- Facts come only from this client's log, nothing is invented or borrowed from another client, and you send the update, not Claude
Next
Run frac-monthly-value-report (Monthly Value Report) to roll the weeks into the page that shows what the seat changed.
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-weekly-ceo-update3description: Drafts the weekly update a fractional leader sends to the CEO, with the bottom line first, results against the 90-day plan in place of activity, status reported as it is this week, the decisions needed from the CEO with a date, the scope asks that go beyond the agreed days and next week, using facts only from your log. Use for "run frac-weekly-ceo-update", "write my weekly update to the CEO", "weekly status report for my client", "the CEO asks what I did this week", "turn my log into an update", "update for my fractional client", "bottom line first update", part of the Claude for Fractional Leaders Pack by 90n.4metadata:5 source: https://skillmd.com/skills/polar-bear-org/frac-weekly-ceo-update6---78# Weekly CEO Update910## When To Use11Your update is a list of meetings and the CEO still asks what you did. On two days a week, the CEO sees little of the work, so the update is most of what they know about the seat. This answers: what moved against the plan, what is off, and what do I need from you by when?1213## When Not To Use14If something has just turned and cannot wait for the weekly rhythm, run Early Warning Note today. If you need the month against what was agreed, with the scoreboard, run Monthly Value Report.1516## Inputs17- This client's log for the week: decisions, commitments, days used, scope asks18- The 90-day plan: objectives, measures, targets and the current figures with their source19- With the Gmail connector I can place the draft in your drafts folder; I never send it20If you have none of this, I start from what you tell me moved this week, mark every figure "to confirm" and mark the update as a first draft.2122## Approach23Bottom line first, then status against the plan, a plain-writing convention described generically: the reader gets the conclusion in the first line and the support underneath. The judgment is to report results, and to report red the week it is true. The failure this prevents is the activity list ("met with sales, reviewed the pipeline, joined the offsite"), which reads as busy and tells the CEO nothing about whether the outcome is nearer.2425## Workflow261. Ask at most three questions: what is the one thing the CEO should know this week; what do you need them to decide; did any ask this week go beyond the agreed days?272. Write the bottom line in one or two sentences: the main result, or the main problem. If the week went badly, the first line says so.283. For each objective in the plan, give the status as it is this week, the figure with its source, and what moved it. Where nothing moved, write that. Meetings appear only when a decision came out of them.294. List the decisions you need from the CEO, each with the options in a line and the date after which the work waits.305. Name the scope asks that arrived this week and go beyond the agreed days, with the baseline line each touches. They are stated here, not absorbed and not argued.316. Close with next week: the one or two results you are working toward and what you need. Keep it to a screen. You edit it and send it yourself.3233## Output Format34```markdown35# Weekly CEO Update36Client: [name] · Week of: [date] · From: [you] · Days used this month: [n] of [n]37## Bottom line38[One or two sentences: the main result or the main problem]39## Against the plan40| Objective | Status this week | Figure (source) | What moved it |41|---|---|---|---|42| [objective] | [on track / at risk / off track] | [figure, system] | [effect, or "nothing moved"] |43## Decisions I need from you44| Decision | Options in a line | By when |45|---|---|---|46| [decision] | [options] | [date] |47## Asks beyond the agreed days48- [ask, from whom, date] · touches: [statement of work or charter line] · proposed: [scope change request / swap / defer]49## Coming week50- [result you are working toward] · I need: [what, from whom]51## Decision52[CEO] answers the listed decisions by [date]; [you] send this update and raise anything urgent in person.53```5455## Done When56- The first line is a result or a problem, never a list of activity57- Every figure has a source in your log or the client's systems58- Each decision asked has a date59- The update fits on one screen6061## Quality Bar62- Status is reported as it is this week; nothing stays "on track" to avoid a conversation63- No adjective does the work of a figure64- Team members are named for decisions and ownership, never assessed65- Scope asks are stated neutrally, with no comment on the asker's motive66- Facts come only from this client's log, nothing is invented or borrowed from another client, and you send the update, not Claude6768## Next69Run frac-monthly-value-report (Monthly Value Report) to roll the weeks into the page that shows what the seat changed.7071## About the makers7273This 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).