Write a statement of work

Define exactly what is in scope and out of scope for a project, to prevent disputes and scope creep later.

You write a formal Statement of Work (SOW) for a freelancer or small agency. This document comes after a client has already agreed to work together. It is not a pitch and not a quick price, its only job is to define precisely what is and is not included, so neither side can later claim they assumed something different.

Here is the project and what we have agreed to deliver:

[paste your rough notes here, in your own words]

Here is what is explicitly out of scope or would count as extra (optional):

[list anything that should not be assumed included]

Here is the timeline or milestones we have agreed, if any (optional):

[key dates or stages]

Write the statement of work as a plain-text document with short section headings, in this order:
- Project overview: one or two sentences confirming what the project is and that both parties have agreed to proceed. If a client or business name is missing, use [client name] and [your name or business] as placeholders.
- Deliverables (in scope): rewrite the rough notes into a precise, unambiguous list of exactly what will be delivered. Turn vague phrasing into concrete, checkable statements. Do not invent deliverables that were not described or implied.
- Out of scope: everything explicitly excluded or that would count as extra, made just as specific as the deliverables. If nothing was given, add a short line stating that anything not listed under deliverables is considered outside this scope.
- Timeline or milestones: only include this section if timeline details were given, laid out plainly and in order. Omit entirely if nothing was given; do not invent dates.
- Changes to scope: one short, general clause stating that work beyond what is listed here will be scoped and priced separately before it begins. Keep it general, for example "Any request outside this scope will be reviewed and quoted separately before work on it begins." Do not invent a specific change-order fee or process.
- Confirmation: a brief closing line noting this document reflects the agreed scope, with a [placeholder] for anything like a start date or sign-off that still needs confirming.

Rules: never invent a deliverable, a date, a price, or a term that was not given, use a [placeholder] for anything still to be confirmed. Give the out-of-scope section equal care and specificity to the deliverables section, since it protects both sides from assumption-based scope creep. Plain, professional language, no legal jargon, no markdown bold or tables.

Paste this into Claude or ChatGPT and replace the bracketed parts with your own text.