How to write a scope before “I thought that was included” comes up

Leon Silcott

A clear freelance scope names the work, quantity, handover format and exclusions. Give the client a concrete list to review before either of you starts.

“Everything for launch” sounds useful until one person pictures a website and the other pictures a website, newsletter and social posts. The problem is not necessarily anyone's intention. The phrase leaves several decisions open.

A scope gives you a place to make those decisions together. It cannot prevent every disagreement, but it can make the first conversation more specific than “I thought that was included”.

Describe an output someone can check

Start each deliverable with an action and a named output. Add the quantity and handover format. “Write six service pages, up to 400 words each, delivered in one shared document” gives the client more to review than “website copy”.

If uploading the pages is included, say so. If you are delivering drafts for their team to upload, say that instead. For design work, name the final file formats. For development, identify the feature and agreed acceptance checks rather than using “fully working” as the entire description.

You are not trying to anticipate every future question. You are identifying the boundaries that matter to this job's price and schedule.

Put likely assumptions in the exclusions

Choose exclusions from the actual project. A copywriter might exclude new interviews, translation and CMS upload. A designer might need to distinguish final exports from editable source files. Do not copy another freelancer's list without checking what you have promised.

Use ordinary language and invite questions. “New photography is not included” is easier to discuss than a paragraph of vague exceptions. If a likely extra can be priced now, show it separately as an option rather than burying it in the exclusions.

Define feedback before counting it

“Two revision rounds” needs an explanation. Will each round cover the whole deliverable set? Who gathers the client's feedback? Are new pages a new scope item rather than a revision?

For example:

“Two consolidated revision rounds are included. Please gather comments from your team into one list per round. New pages and new formats are quoted separately before work starts.”

These are written working terms. AsAgreed does not count or enforce rounds automatically. Keep your own review process and discuss unclear feedback rather than treating every message as a separately chargeable round.

A hypothetical web-copy scope

Maya proposes six pages for a garden centre at £960 fixed. The record lists the page names, length limits, shared-document handover and two consolidated feedback rounds. It excludes photography, translation and uploading.

The owner notices that delivery information needs a separate page. Before acceptance, they can discuss whether to replace one listed page, add the new page at an agreed price or leave it for later. That is a useful scope conversation because the choice is visible before the work grows.

Later, a Christmas landing page is requested. Maya first checks whether it was included. If it is new work, she sends a proposal describing the page, price and effect on dates. She does not simply add £140 to the final invoice because the client mentioned Christmas on a call.

Keep accepted and proposed work distinct

Before any new payment report or receipt, AsAgreed supports a complete revised scope and price. The currently accepted terms remain until the client explicitly accepts the revision. A pending proposal should not be described as part of the job already agreed.

After a new payment report or receipt exists, scope and price revisions are unavailable on that agreement. Later extras need a fresh agreement. Plan for that boundary if you take an early payment.

The price basis matters too. A fixed price relates to the defined scope. An estimate range needs separate acceptance of the final price in AsAgreed before a payable balance appears.

Send it as a question, then wait for the answer

A useful covering message is:

“This is the proposed list for the £960 web-copy job. Please check the pages, exclusions and feedback arrangements. If something you expected is missing, tell me before accepting so we can discuss the scope and price.”

Creating the link does not send it. Send it through your usual messages and ask the client to review it; opening the link alone is not acceptance.

The freelancers page shows scope and deliverables alongside the payment record. For your next job, write the actual outputs, exclusions and feedback terms before asking the client to accept.

Write the scope for your next freelance job