Working-alone guide
Writing a scope of work that prevents disputes
Most disputes between self-employed people and their clients are not about bad faith. They come from two people remembering different versions of the same conversation. A scope of work is the written version both sides agree to. This guide is a practical template for thinking it through. It is not legal advice, and contracts with significant money or risk deserve a lawyer's review.
Scope, contract and quote
People use these words loosely. A useful way to separate them:
- Quote. The price, how it was calculated and how long it stands. The quote floor on this site helps you set a minimum.
- Scope of work. What will be delivered, by whom, when, and how it will be accepted.
- Contract or terms. The legal frame: payment terms, ownership, confidentiality, cancellation, liability.
Small projects often combine all three in one document. That is fine, as long as each element is there.
Section 1: the outcome
Start with one or two sentences in plain language about what the client is trying to achieve. It gives context for every later decision.
Example: Redesign the five-page website so visitors can book a consultation from any page.
Section 2: deliverables
List what the client will receive. Each item should be something they can see, open or use.
- Good: "Five page designs in the agreed tool, desktop and mobile."
- Weak: "Website design support."
Add format, quantity and where it will be delivered.
Section 3: exclusions
This is the section most often skipped, and the one that prevents most scope creep. Name things that are not included, especially those a client could reasonably assume are:
- writing the copy;
- stock photos or licensed fonts;
- ongoing hosting or maintenance;
- additional pages;
- training staff.
An exclusion is not a refusal. It is a list of things that would be quoted separately.
Section 4: timeline and dependencies
Give dates for milestones, and state what they depend on. Your timeline almost always depends on the client: content, access, feedback, approvals.
Example: Draft designs within ten working days of receiving final copy and logo files.
That sentence protects both parties. It also makes delays visible as they happen.
Section 5: client responsibilities
List what the client provides and by when: materials, logins, a single decision-maker, feedback within a set number of days. If feedback is slow, the schedule moves.
Section 6: revisions
State how many revision rounds are included and what a round means, for example one consolidated set of comments. Say what happens after: an hourly rate, a fixed fee per round, or a new quote.
Section 7: acceptance
Define when a deliverable is done. Common approaches:
- written approval;
- approval assumed if no comments arrive within a stated number of days;
- launch or use of the deliverable.
Clear acceptance prevents projects that never quite finish, and makes it clear when the final invoice is due.
Section 8: changes
Describe a simple change process:
- Either party describes the change in writing.
- You reply with the effect on price and timeline.
- Work on the change starts once the client confirms.
With this written down, an extra request becomes routine: "Happy to add that. Here is what it changes. Shall I go ahead?"
Section 9: payment terms
Link payments to milestones. Many self-employed people take a deposit before starting, with the balance on acceptance, and spell out the due date and accepted payment methods. See chasing late payments for what to do if one is missed.
Getting it agreed
Send the scope as a document or in the body of an email and ask for written confirmation. An email reply saying "Agreed" is far better than nothing. Save the confirmed version with the client's records.
If you already started without one
Write a short summary now: "To confirm what we agreed: deliverables, dates, price, revisions." Ask the client to reply to confirm. It is never too late to put the agreement in writing.
Revisit after each project
After each project, note where the scope was unclear and update your template. Over time it becomes your own standard terms, shaped by real projects rather than guesses.
Do this week
- Write each deliverable as something the client can see or receive.
- List at least three things that are not included.
- State how many revision rounds are included and what happens after.
- Name what the client must provide and by when.
- Get written confirmation before work begins.
About this guide
This is a practical editorial guide, not legal advice. It cites no statistics or rules, so it lists no sources. For a contract with significant money or risk, ask a lawyer licensed where you work.