Scope creep is the slow expansion of a project after the price is agreed: one more page, one more revision, one more meeting. Each addition seems small, but together they can double the work for the same fee. A scope of work document stops that. It is a short, plain-language description of exactly what you will deliver, what you will not, and what happens when the client asks for more — agreed before the work starts.

A good scope of work template covers six sections. The project overview states the goal in one or two sentences. The deliverables list names every item you will produce, with quantities and formats. The timeline gives dates for drafts, reviews, and delivery. The revision policy states how many rounds are included and what extra rounds cost. The exclusions list names the things that are not part of the job. And the assumptions note anything you are relying on the client to provide, such as content, images, or access.

Free scope of work templates are available as Word documents, Google Docs, and Notion pages, and most take five minutes to adapt. The best ones are short — one or two pages — because a ten-page scope document never gets read. Fill in the template for each new project, send it with your proposal, and ask the client to confirm it in writing before you start. That confirmation is what turns the scope from a suggestion into an agreement.

The revision policy is the section that saves the most money. State clearly how many revision rounds are included — two is standard — and what an extra round costs. When a client asks for a third revision, you can point to the agreed policy instead of having an awkward negotiation. The same applies to deliverables: if the scope says five pages and the client asks for eight, the answer is a new quote for three pages, not free work.

Scope documents also protect the client, which is why good clients welcome them. A clear scope means the client knows exactly what they are paying for and when they will get it, with no surprises at the end. If a project goes wrong, the scope is the first document both sides look at — and the freelancer who has one is the freelancer who gets paid fairly. Download a free template, adapt it to your services, and use it on every project, no matter how small.

Change requests are normal — clients think of new ideas once they see the work taking shape, and some of those ideas are genuinely good. The question is not whether to accept them, but how to price them. The fair approach is to treat each change as a mini-project: estimate the extra hours, multiply by your rate, and send a short written quote for the change before doing the work. Most clients accept this readily, because it is transparent and it respects their budget.

The mistake is to accept changes verbally and sort out the price later. Later never comes, or it comes as an argument. A simple email — "Happy to add that, it will take about three hours, so the additional cost is X, shall I go ahead?" — protects both sides and keeps the relationship friendly. Keep a running list of approved changes alongside the scope document, so the final invoice matches what was actually delivered.