What is a project scope document?

A project scope document defines exactly what you'll deliver, when you'll deliver it, and what's not included. It's the single most effective tool for preventing scope creep - that slow, painful expansion of work that eats into your time and profit.

Think of it as a map for the project. Without one, you and your client might have completely different ideas about what "done" looks like.

When should you use one?

Every project with multiple deliverables, stages, or any room for interpretation. It's especially important for design and development projects where clients often assume revisions and additions are included by default.

What's included

Project overview - a plain-language summary of what the project is and what you're trying to achieve.

Deliverables - the specific items you'll hand over. Be as detailed as possible.

Timeline and milestones - key dates and checkpoints including start date, milestone reviews, and final delivery.

What's not included - list common assumptions clients might make that aren't part of the deal.

Revision process - how many rounds of feedback are included and what counts as a revision versus a new request.

Change request process - how scope changes are handled, estimated, and approved in writing before extra work begins.