Delivery team online — 09:30–19:00 IST
How to · Sales and pipeline

How to write a scope that prevents later arguments

Learn how to write a scope in countable units with a definition of done so month two disagreements become priced variations instead of free work.

The argument that always starts in month two

Almost no client dispute starts with the price. It starts when the client asks for something the seller believes was never included. Both parties are reading the same document and reaching opposite conclusions. The seller sees a request outside scope. The client sees the job they thought they bought.

Scope documents fail for a dull reason. They describe activity rather than quantity. Activity has no end. A line that promises website maintenance promises everything the client can imagine under that word. A line that promises four hours of maintenance each month promises four hours.

What a tight scope costs and what it does not do

A well written scope is not a legal instrument and nothing here is legal advice. It describes obligations in plain language so humans agree. Whether a particular clause binds either party depends on your contract and on Indian contract law. Have a qualified lawyer confirm the enforceable parts for your situation before you rely on them.

The direct cost is sales friction. Specific documents provoke questions and some buyers walk away when they see limits written down. Treat that as the scope doing its job early rather than delivery doing it late. There is drafting time too. Expect a few hours per service line the first time and very little after that once the template exists.

Where a fixed scope is the wrong tool

Genuinely exploratory work should not be scoped this way. If neither side can describe the deliverable because the first phase exists to find out what it is then a fixed scope forces both parties to invent one. Sell a time boxed investigation with a named output such as a written recommendation. Scope the build only once the investigation has run.

Very small jobs also do not justify this. A one day task does not need a definition of done that takes half a day to write. Use a short written confirmation of the deliverable and the fee. The other business that should avoid a tight scope is one selling trust rather than output. A long standing retainer with a client who sends work informally can be damaged by a sudden document full of limits. Introduce it at renewal rather than mid term.

The six parts that actually prevent disputes

Write every deliverable as a number and a noun. Twelve posts. Three pages. Two revision rounds. Then write a definition of done for each one. Done usually means delivered in a named format and approved in writing within a stated window. Without that sentence nothing is ever finished and a project from March is still open in August.

Next name the inputs the client owes you and the date each is due. Logos. Product photographs. Access to the analytics property. Approval of the first draft. Then state what happens when an input is late. The honest mechanism is that the timeline shifts by the length of the delay and the fee does not change. Write that sentence down because every delayed project eventually needs it.

Finally define the unit of change. A variation is a written request plus a quoted price plus an approval before work starts. Give the whole document a version number and a date. When a dispute arrives you want to point at version two rather than at an email thread.

Whether the scope is holding

The metric that matters is unpaid delivery hours. Count the hours your team spent on work nobody billed. A rising figure means the scope is leaking regardless of how pleasant the client relationship feels.

The metric that flatters is the number of signed agreements. It says nothing about the terms inside them. Client satisfaction measured at kickoff flatters just as badly. Satisfaction is highest exactly when the seller has agreed to everything and the bill for that agreement arrives in month three.

The mistake that costs the most

The common error is listing what you will do without listing what stops it. Revisions are the usual case. A scope that says revisions until the client is happy has priced an unknown quantity at a fixed fee. Some clients approve the first draft. One client will take eleven rounds and consume the entire margin of the account.

It is expensive because the loss is invisible. The invoice went out at the agreed value so the project looks profitable in the sales report. The cost sits in a designer who worked three extra weeks and in the two deals your team could not pursue while they did it. Two revision rounds followed by a priced variation turns that loss into revenue.

One note on changing an existing scope

You cannot rewrite a live agreement on your own. Changes to an existing arrangement need the other party to agree in writing and the terms of the current contract govern how that happens. A qualified professional should confirm the position for your specific agreement before you act on it.

This guide explains how something works. It is not legal, tax or financial advice, and rules change. Confirm anything regulatory with a qualified professional before you act on it.