Scope Change Request
When To Use
"Could you also sit in on hiring?" arrives for the third time this month. Each ask is reasonable, and each one makes the agreed days mean a little less. Use this at the first instance, not the third, to size one ask against what was signed and get a named person to choose before you start.
When Not To Use
If the change log shows the whole shape of the seat is wrong, run Retainer Redesign. If nothing was ever signed, there is no baseline to measure against: run Fractional Statement of Work first.
Inputs
- The ask as it was put (message or note), who asked and when
- The signed statement of work and the charter, and your day rate or fee basis
- Your estimate of the effort, and what else it would displace this month
If you have none of this, I start from the ask in one line, mark every impact "unknown, to find out by [date]" and mark the request as a first draft.
Approach
Change control against a signed baseline, a practitioner convention, with a swap rule from MoSCoW prioritisation as the Agile Business Consortium publishes it (Must, Should, Could, Won't have this time): a new item comes in only if an item of similar size goes out, so what must be delivered still fits the days. A fractional marketplace's guidance adds the tone: an out-of-scope ask is a conversation, opened the first time it happens. The failure this prevents is the part-time seat that becomes a full-time job at part-time pay, one favour at a time.
Workflow
- Ask at most three questions: what exactly is asked, and by whom; which line of the statement of work or charter does it touch; what would it push out this month?
- Write the ask in one line with who asked and the date. Drop "small" and "quick": the size comes from the check, not the label.
- Quote the baseline line and mark the ask in scope, out of scope or unclear. Unclear is common; say so and note the wording to fix at the next review.
- Size the impact in days and, at your own rate, in fee, plus what it displaces. Where you have no estimate, write "unknown" with a date. Faster work with AI is not a reason to price at zero: the judgment and the accountability still take your days.
- Lay out four options. Accept and price. Defer to a later month. Swap: name the Could or Won't item of similar size that leaves so the Must items still fit. Decline, with one plain reason and, where it helps, who is better placed.
- Name the decider on the client side and the date, and write the change log entry. Any effect on the contract: check with a qualified adviser.
Output Format
# Scope Change Request
Client: [name] · Number: [n] · Asked by: [role] · Date: [date]
The ask: [one line] · Baseline line: "[quoted line]" · [in scope / out of scope / unclear]
## Impact
| Dimension | Effect | Source |
|---|---|---|
| Days | [n, or unknown by date] | [your estimate] |
| Fee | [at your rate] | [statement of work] |
| What it displaces | [named work, new date] | [90-day plan] |
## Options
| Option | What happens | Fee | What leaves or moves |
|---|---|---|---|
| Accept and price | [..] | [your figure] | [..] |
| Defer | [to which month] | [none now] | [..] |
| Swap | [..] | [no change] | [named item that leaves] |
| Decline | [reason, who is better placed] | [none] | [nothing] |
## Change log entry
| Number | Date | Ask | Option chosen | Fee | Approved by |
|---|---|---|---|---|---|
| [n] | [date] | [ask] | [option] | [fee] | [name] |
## Decision
[Client decider] chooses accept, defer, swap or decline by [date]; [you] start no work on it before then.
Done When
- The baseline line is quoted, or its absence is noted
- Every impact has your figure or "unknown" with a date
- The swap names the exact item that leaves, the log entry is filled, and the decider has a name and a date
Quality Bar
- Neutral words about the ask and nothing about the asker's motives; accept always carries a fee or a swap, so there is no free option
- Fees come from your own rates, never a market figure
- Raised at the first instance, in conversation first and in writing after
- Claude sizes the ask from what you give it about this client only, invents no estimate, and you raise it with the CEO yourself
Next
Run frac-retainer-redesign (Retainer Redesign) when the change log shows the role no longer matches the days you sold.
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-scope-change-request3description: Turns a "could you also" into a scope change request for a fractional engagement, with the ask in one line, the charter or statement of work line it touches, the impact in days and fee at your rates, four options (accept and price, defer, swap, decline), the decider and date, and a change log entry. Use for "run frac-scope-change-request", "could you also", "scope creep on my retainer", "is this in scope", "write a change request", "price this extra ask", "how do I say this is outside my days", part of the Claude for Fractional Leaders Pack by 90n.4metadata:5 source: https://skillmd.com/skills/polar-bear-org/frac-scope-change-request6---78# Scope Change Request910## When To Use11"Could you also sit in on hiring?" arrives for the third time this month. Each ask is reasonable, and each one makes the agreed days mean a little less. Use this at the first instance, not the third, to size one ask against what was signed and get a named person to choose before you start.1213## When Not To Use14If the change log shows the whole shape of the seat is wrong, run Retainer Redesign. If nothing was ever signed, there is no baseline to measure against: run Fractional Statement of Work first.1516## Inputs17- The ask as it was put (message or note), who asked and when18- The signed statement of work and the charter, and your day rate or fee basis19- Your estimate of the effort, and what else it would displace this month20If you have none of this, I start from the ask in one line, mark every impact "unknown, to find out by [date]" and mark the request as a first draft.2122## Approach23Change control against a signed baseline, a practitioner convention, with a swap rule from MoSCoW prioritisation as the Agile Business Consortium publishes it (Must, Should, Could, Won't have this time): a new item comes in only if an item of similar size goes out, so what must be delivered still fits the days. A fractional marketplace's guidance adds the tone: an out-of-scope ask is a conversation, opened the first time it happens. The failure this prevents is the part-time seat that becomes a full-time job at part-time pay, one favour at a time.2425## Workflow261. Ask at most three questions: what exactly is asked, and by whom; which line of the statement of work or charter does it touch; what would it push out this month?272. Write the ask in one line with who asked and the date. Drop "small" and "quick": the size comes from the check, not the label.283. Quote the baseline line and mark the ask in scope, out of scope or unclear. Unclear is common; say so and note the wording to fix at the next review.294. Size the impact in days and, at your own rate, in fee, plus what it displaces. Where you have no estimate, write "unknown" with a date. Faster work with AI is not a reason to price at zero: the judgment and the accountability still take your days.305. Lay out four options. Accept and price. Defer to a later month. Swap: name the Could or Won't item of similar size that leaves so the Must items still fit. Decline, with one plain reason and, where it helps, who is better placed.316. Name the decider on the client side and the date, and write the change log entry. Any effect on the contract: check with a qualified adviser.3233## Output Format34```markdown35# Scope Change Request36Client: [name] · Number: [n] · Asked by: [role] · Date: [date]37The ask: [one line] · Baseline line: "[quoted line]" · [in scope / out of scope / unclear]38## Impact39| Dimension | Effect | Source |40|---|---|---|41| Days | [n, or unknown by date] | [your estimate] |42| Fee | [at your rate] | [statement of work] |43| What it displaces | [named work, new date] | [90-day plan] |44## Options45| Option | What happens | Fee | What leaves or moves |46|---|---|---|---|47| Accept and price | [..] | [your figure] | [..] |48| Defer | [to which month] | [none now] | [..] |49| Swap | [..] | [no change] | [named item that leaves] |50| Decline | [reason, who is better placed] | [none] | [nothing] |51## Change log entry52| Number | Date | Ask | Option chosen | Fee | Approved by |53|---|---|---|---|---|---|54| [n] | [date] | [ask] | [option] | [fee] | [name] |55## Decision56[Client decider] chooses accept, defer, swap or decline by [date]; [you] start no work on it before then.57```5859## Done When60- The baseline line is quoted, or its absence is noted61- Every impact has your figure or "unknown" with a date62- The swap names the exact item that leaves, the log entry is filled, and the decider has a name and a date6364## Quality Bar65- Neutral words about the ask and nothing about the asker's motives; accept always carries a fee or a swap, so there is no free option66- Fees come from your own rates, never a market figure67- Raised at the first instance, in conversation first and in writing after68- Claude sizes the ask from what you give it about this client only, invents no estimate, and you raise it with the CEO yourself6970## Next71Run frac-retainer-redesign (Retainer Redesign) when the change log shows the role no longer matches the days you sold.7273## About the makers7475This 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).