Write the client-ready confirmed-scope statement
Drafts the formal scope statement for this engagement — translating fit verdicts, clarification decisions, and any boundary resets into a clear, signed-off document that both parties will operate from.
In / outFit verdicts, clarification decisions, boundary resets → formal scope statement draft (what is included, what is excluded, decision rationale)
You might say…
“We agreed on everything verbally but two months in the client thinks we're doing something we never actually committed to — because nothing got written down.”
What it does
Single-judgement skill: takes the resolved verdict and drafts the scope statement for the client — what is confirmed in, what is confirmed out, the conditions and caveats attached, and the expectation reset where the client's original ask was wider than the method delivers. Decides tone and what to foreground so the boundaries read as clarity, not as the firm pulling back. Used as the closure act when the method can run as-is; the operator reviews before it goes out.
Trigger: Use after all scope ambiguities are resolved and it is time to produce the definitive written record of what this engagement does and does not cover.
Recognise the problem?
The primitives are the commodity part. The fastest next step is a conversation about composing them into something that works for you.
Start a conversation