# Frac Early Warning Note

> Drafts a short early warning for the week something turns in a fractional engagement, with what changed, the evidence, what is known against estimated against unknown, the implication for the plan, two or three options with their cost, and the decision or help asked and by when. Use for "run frac-early-warning-note", "a target will be missed", "how do I tell the CEO bad news", "write an early warning", "flag a risk before the monthly report", "SBAR note for my client", "the plan is slipping and I need a decision", part of the Claude for Fractional Leaders Pack by 90n.

- Skill: `polar-bear-org/frac-early-warning-note` (Agent Skill)
- Install (CLI): `npx get-skill add polar-bear-org/frac-early-warning-note`
- Raw SKILL.md: https://api.skillmd.com/api/skills/polar-bear-org/frac-early-warning-note/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: polar-bear-org (https://skillmd.com/u/polar-bear-org)
- Updated: 2026-11-14
- Page: https://skillmd.com/skills/polar-bear-org/frac-early-warning-note

---


# Early Warning Note

## When To Use
A target will be missed and you are tempted to wait for the monthly report. You are in the building two days a week; by the time the report lands, the cheap fix is gone and the CEO learns it from someone else. Use this the day you know, to say it once, plainly, with a way forward.

## When Not To Use
If nothing has turned and this is the routine week, run Weekly CEO Update. If the problem is a broken commitment between you and a colleague, run Relationship Repair Plan.

## Inputs
- What changed, and how you know: the figure, message or event, with its source and date
- The commitment it touches in the 90-day plan, the statement of work or the board page
- The options you see and what each would cost in time, money or scope
If you have none of this, I start from what you saw and when, mark everything else "unknown, to find out by [date]" and mark the note as a first draft.

## Approach
SBAR (situation, background, assessment, recommendation), the communication tool published by the Institute for Healthcare Improvement and developed for urgent handovers between clinicians. Its order is the method: the problem in one sentence, only the background that matters, what you think, what you want. It suits a warning and is too clinical for a routine update. The failure this prevents is the softened notice, where the turn is buried under context and reassurance and the reader finishes it without knowing a decision is needed.

## Workflow
1. Ask at most three questions: what changed and when did you learn it; which commitment does it touch; what do you need from the CEO, and by when?
2. Situation: one sentence. What changed, on which measure or date. No lead-in and no apology.
3. Background: the commitment it touches and the evidence, with source and date. Only what the reader needs to judge it.
4. Assessment: sort what you have into known, estimated and unknown, and say what it means for the plan. An estimate is labelled; an unknown gets a date by which you will know.
5. Recommendation: two or three options, each with its cost and what it protects, including holding course. State the one you recommend and the decision or help you need, with a date. Promise nothing on behalf of another person or team.
6. Check the tone against one test: could the CEO read only the first two lines and know that something turned and a decision is due? You send it, or say it and follow in writing.

## Output Format
```markdown
# Early Warning Note
Client: [name] · To: [CEO] · Date: [date] · Decision needed by: [date]
## Situation
[One sentence: what changed]
## Background
Commitment it touches: [plan, statement of work or board line] · Evidence: [figure, message, event; source, date]
## Assessment
| Known | Estimated | Unknown, and when I will know |
|---|---|---|
| [fact] | [estimate, labelled] | [gap, date] |
Implication for the plan: [what moves, by how much if known]
## Recommendation
| Option | Cost | What it protects |
|---|---|---|
| [hold course / option / option] | [time, money, scope] | [commitment] |
I recommend: [option] · I need from you: [decision or help]
## Decision
[CEO] chooses an option by [date]; [you] send or say this today and update the plan once it is decided.
```

## Done When
- The first sentence states what changed
- Known, estimated and unknown are in separate columns
- There are two or three options, each with a cost, and one is recommended
- The ask has a date

## Quality Bar
- Sent the week it is true, not held for the next report
- No reassurance that the evidence does not support
- The note describes the event and its effect, never who is to blame
- No commitment is made for another person or team
- Nothing is estimated by Claude or drawn from another client's situation; the evidence is yours, and you deliver the warning yourself

## Next
Run frac-team-interface-agreement (Team Interface Agreement) if the turn came from work that stalled on your off days.

## About the makers

This 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).

