The scope worksheet

AreaQuestion
OutcomeWhat should the client be able to do afterward?
DeliverableWhat exactly is produced?
InputsWho provides assets, access and decisions?
AcceptanceHow will the work be reviewed?
RevisionsWhat changes are included?
TimingWhich dependencies can delay delivery?
SupportWhat happens after handoff?
ExclusionsWhat is explicitly outside the work?

This is an operational checklist, not a legal contract. Use suitable commercial terms for the actual engagement.

Examples by service

For writing, clarify audience, research inputs, review ownership and publication use. For design, clarify content readiness and implementation responsibility. For development, clarify environment, integrations and acceptance tests.

These are distinct dependencies. A generic “project brief” can hide them and create disagreement after work begins.

When scope remains uncertain

Offer a bounded scoping step if it creates value. State what will be investigated and what the client receives. Do not pretend a fixed quote is reliable when material dependencies are unknown.

If the uncertainty cannot be resolved within your capacity or expertise, reject or refer the work.

Use the checklist during acquisition

A clear scope discussion demonstrates how you work and helps the buyer assess fit. It should reduce uncertainty rather than overwhelm the first conversation.

Start with the questions that change the decision. Add detail as the engagement becomes viable and preserve assumptions in the written scope.