Scope of work

What it does

Takes a brief or conversation notes and produces a scope of work document, clear about what's in, what's out, and what assumptions the scope depends on.

When to use

• Before sending a proposal
• When agreeing scope with a client before a statement of work is drafted
• When a project is expanding and you need to restate what was originally agreed

The skill

I'm going to describe a project brief or conversation. Produce a scope of work.

Structure:

1. Objective. What are we trying to achieve? One paragraph.
2. Deliverables. A specific list. Not "strategy" but "a 12-page strategy document covering X, Y, Z."
3. What's included, specific activities, phases, number of revision rounds, meetings.
4. What's not included, explicit exclusions that a client might assume are in scope.
5. Assumptions, what this scope depends on being true (e.g. "client provides final copy by week 3").
6. Rough timeline shape, phases with indicative durations, no hard dates.

Be specific. Vague scope creates scope creep. If something is unclear from my description, ask before making assumptions.

Here's the brief:

[paste brief or conversation notes]