Freelance Scope of Work Template & Example

Freelance scope of work template: freelancer working on a laptop at a desk

A freelance scope of work needs seven parts: the goal, the deliverables, the exclusions, the timeline, the revision limit, the change process, and the payment terms. When one is missing, the project usually grows while the price stays where it was.

Below is a fill-in template, a completed example for a small website project, and the exact wording that handles the two situations behind most scope disputes: extra revisions and late client feedback.

What a scope of work covers

A scope of work is the part of an agreement that says what will be delivered, by when, and what is not included. The contract covers legal terms such as ownership and liability. The scope covers the work itself, which is why it deserves its own page even when the contract is short.

Write it so that a stranger could read it and tell whether a given task is inside or outside the project. If two readers could disagree on that, the scope is too vague.

The template

Copy this and replace the brackets.

PROJECT: [name]
CLIENT: [name]   FREELANCER: [name]   DATE: [date]

1. GOAL
[One sentence on the result the client wants, e.g. "A five-page website that lets visitors book a consultation."]

2. DELIVERABLES
- [Item, format, quantity, e.g. "Five page designs in Figma, desktop and mobile"]
- [Item]
- [Item]

3. NOT INCLUDED
- [e.g. "Copywriting, photography, logo design, hosting setup"]

4. TIMELINE
Start: [date]. Final delivery: [date].
Dates depend on the client supplying [content/access/feedback] within [number] business days.

5. REVISIONS
[Number] rounds of consolidated feedback per deliverable. A round means one set of changes sent together in one message.

6. CHANGES
Work outside this scope is quoted separately and starts only after written approval.

7. PAYMENT
[Total]. [Deposit] due at signing, [amount] at [milestone], [amount] on delivery. Invoices are due in [number] days.

Completed example: five-page business website

Here is how the template reads once filled in for a realistic small project.

PartEntry
GoalA five-page website that lets visitors book a consultation
DeliverablesHome, About, Services, Contact and Booking pages built on the client's existing hosting; mobile and desktop layouts; one contact form connected to the client's email
Not includedCopywriting, photography, logo design, ongoing maintenance
TimelineStart 3 March, final delivery 4 April, assuming all text and images arrive by 10 March
RevisionsTwo rounds of consolidated feedback per page
ChangesExtra pages, new features or a third revision round are quoted separately
Payment1,800 total: 40% at signing, 30% when the design is approved, 30% on delivery

Notice how many items are written as countable things: five pages, one form, two rounds. Countable items settle arguments quickly because nobody has to debate what "a few tweaks" meant.

The exclusions list does the most work

Deliverables describe what you will do. Exclusions describe what a client may reasonably assume you will do anyway. Think about the tasks that sit next to your work and write down the ones you are not taking on.

For a designer, that might be copywriting and stock photo licenses. For a writer, it might be image sourcing, publishing to the client's CMS, and social posts. For a developer, hosting, domain setup and fixing problems caused by third-party plugins.

An exclusion that feels obvious to you is exactly the kind a client has never thought about.

Wording for revisions

The word "unlimited" is the most expensive word a freelancer can put in a scope. Replace it with a number and a definition of a round.

A workable definition: a round is one message containing all requested changes for a deliverable. Feedback that arrives in five separate emails counts as one round only if it is combined before work starts. Ask the client to consolidate, and say so in the scope.

If you want a gentler tone, add a line such as "Additional rounds are billed at [rate] per hour." That keeps the door open without promising free work.

Wording for late feedback

Late feedback pushes delivery dates, and the scope should say who owns that delay. A short clause does it:

"If feedback or materials are more than [number] business days late, the delivery date moves by the same number of days. Delays of more than [number] days may require rescheduling the project start."

This protects your calendar too. A project that stalls for three weeks can collide with the next client's work, and the clause gives you a reason to restart on a new date.

Handling a change request

Changes will happen, and a good scope makes them routine instead of tense. Use a three-step response:

  1. Confirm what the client wants in one sentence.
  2. State the effect: added cost, added days, or both.
  3. Ask for written approval before starting.

A reply can be as short as: "Adding a blog page is outside the current scope. It would add 150 and two working days. Reply 'approved' and I will schedule it." The approval can be an email. It only needs to exist.

Sizing the price from the scope

Once the scope is written, price it from the deliverables, not from the headline. List each item, estimate hours with a margin for feedback cycles, and add them up. A common mistake is pricing the visible work and forgetting meetings, file handovers and revision rounds.

Once hours are known, check what winning that client cost you, using customer acquisition cost. If a project's hours are hard to estimate, split it into a paid discovery phase and a main phase. The scope for the main phase is then written with real information. This pairs well with the steps in the freelance client onboarding checklist, which collects the materials and access you need before the clock starts.

Pairing the scope with payment terms

The payment section should match the work in stages. A deposit at signing protects your time, a mid-project payment follows an approved milestone, and the last payment is due on delivery. Tie each payment to something the client can verify.

Clear payment dates are only useful if they are followed up. An invoice reminder schedule keeps the follow-ups polite and consistent so you do not have to decide each time whether to chase.

FAQ

How long should a freelance scope of work be?

One page is enough for most small projects. Larger projects may take two or three pages, mostly because the deliverables and milestones list grows. Length matters less than whether each item can be counted or checked.

Is a scope of work the same as a contract?

No. The scope describes the work, and the contract covers legal terms such as ownership, confidentiality and liability. Many freelancers attach the scope to the contract so both documents are signed together. For larger or higher-risk projects, a lawyer's review of the contract is worth the cost.

What if the client refuses to sign a scope?

Send it as a summary email and ask for a written "yes". An email reply that says "agreed" gives you a record. If a client will not confirm what the project includes, treat that as a risk signal before starting.

Should the scope include a project price?

It can, and it should if you charge a fixed fee. For hourly work, include the rate, an estimate range, and a point at which you will pause and check in, such as at 80% of the estimate.

Putting it to use this week

Take your last finished project and write its scope in the seven-part format after the fact. The gaps you notice, such as an unspoken exclusion or a revision count nobody agreed on, are the clauses your next template needs. Save the result as your standard file and adjust the brackets for each new client.

Similar Posts

Leave a Reply

Your email address will not be published. Required fields are marked *