How to Write a Project Scope for Freelance Work

A good project scope answers a practical question: what exactly is being delivered, under what conditions, and what happens when the requested work changes?

Start with the outcome

Describe the result the client is paying for in plain language. Avoid starting with a long list of internal tasks if the client mainly cares about the finished outcome.

List the deliverables

Make each major deliverable identifiable. For a website project, that might mean a defined number of pages, responsive layouts, a launch handoff, and a specific number of content uploads. For design work, it could specify file formats, concepts, and final assets.

State what is not included

Exclusions are as useful as inclusions. Examples include extra pages, additional concepts, copywriting, stock assets, ongoing maintenance, or third-party subscription fees. Only include exclusions that actually matter to the project.

Define assumptions and client responsibilities

If your timeline depends on the client supplying copy, approving designs, or providing access, say so. A scope can identify those dependencies without making unsupported promises about what will happen if they are delayed.

Set milestones and review points

Break larger work into meaningful checkpoints. A milestone might include a draft, client review, revision round, and approval. This makes progress easier to track and gives both sides a clear point for decisions.

Define revisions

Specify what counts as a revision and how many rounds are included. Also explain how additional work is handled. Keep the wording concrete enough that both sides can tell when a request falls outside the agreed scope.

Example scope structure

1. Project objective
2. Deliverables
3. Included pages, assets, or outputs
4. Exclusions
5. Client-provided materials
6. Timeline and milestones
7. Included revision rounds
8. Price and payment schedule
9. Approval and change process

Scope changes

A scope should not try to predict every possible request. Instead, establish a simple change process: identify the requested change, estimate its effect on time and price, and get agreement before treating it as included work.

Frequently asked questions

How long should a project scope be?

It should be long enough to remove important ambiguity, not long for its own sake. A small project may need only a page or two; a complex project may require a more detailed statement of work.

Should the scope include the price?

It is often useful to show the agreed price and payment schedule, while keeping the detailed scope and commercial terms consistent with the contract or proposal.

Related guides: Client Onboarding · Revision Policy · Client Change Requests