Freelance Scope of Work (SOW) & Milestone Addendum

Freelance Scope of Work (SOW) & Milestone Addendum: a practical guide

A Freelance Scope of Work (SOW) & Milestone Addendum describes a specific freelance project, its stages, and the payment or delivery points tied to those stages. It helps the client and freelancer record what each side expects before work begins.

What it's for

Use this document when a freelancer and client have agreed to work together and need to spell out a particular project. It can describe the work, the deliverables, when each stage is due, how progress will be reviewed, and what fees apply. Both sides can use it to check their shared understanding as the work moves forward.

The addendum can be used alongside a broader services agreement that covers the ongoing working relationship. If the project is part of a longer engagement, keep the SOW focused on the specific work and milestones, and check that its terms fit with the other agreement. For a one-time project, the parties can still use it to write down the project details they have agreed on.

Who uses it

• A freelance designer and a business commissioning a brand package.
• A writer and a client planning a set of articles in stages.
• A consultant and a customer dividing research or planning work into milestones.
• A web developer and a client agreeing on features, review points, and delivery stages.
• A photographer or other creative professional and a client planning a defined project.

Terms to decide on

Scope and deliverables

Describe the work and the items the freelancer will provide. Use concrete descriptions, such as file types, quantities, functions, or included services, and state what is outside the scope.

Milestones and review

List each stage, what must be delivered at that stage, and how the client will review it. State what information or action the freelancer needs from the client to proceed.

Dates and dependencies

Set a target date for each milestone and a final delivery date. Note dependencies such as access, content, decisions, or approvals that may affect the schedule.

Fees and payment points

Say whether payment is a total project fee, an hourly rate, or a combination, and connect each payment to a clear event, such as a milestone delivery. Explain how the parties will handle approved expenses if they apply.

Changes and extra work

Describe how either side can request a change, how the parties will agree on any effect on price or timing, and how work outside the listed scope will be handled. Use Additional Terms & Provisions for specific change steps.

Revisions and acceptance

State how many review or revision rounds are included, what counts as a revision, and how the parties will confirm a milestone is accepted. Explain how to raise a concern about a deliverable.

Intellectual property and materials

Clarify what rights the client receives in the completed work and when any transfer or permission takes effect. Identify any pre-existing materials, third-party items, or tools that are not being transferred.

Common mistakes

• Using broad phrases such as “complete the website” without listing the pages, features, content, or files included. Vague scope can lead each side to expect different work.
• Listing milestones without describing the deliverable for each one. A stage name alone may not show what the client should receive or review.
• Setting dates without considering when the client must provide information, access, or decisions. Record those dependencies so both sides can plan around them.
• Tying payment to unclear events, such as “when satisfied,” without saying what review or milestone triggers payment. Describe the event in observable terms.
• Treating every new request as included work. Explain how the parties will agree on changes to scope, fee, and schedule before the extra work proceeds.
• Leaving rights to images, fonts, software, drafts, or other pre-existing materials unclear. Identify what the freelancer can transfer and what the client may use.

Before you sign

• Check that the work and each deliverable are described in terms both sides understand.
• Confirm that milestone dates account for client inputs, review time, and dependencies.
• Make sure each payment point is linked to a clear milestone or time period.
• Read the change, revision, and acceptance terms and confirm they match the planned workflow.
• Clarify rights in completed work and any third-party or pre-existing materials.
• Compare this addendum with any related services agreement and resolve inconsistent terms.
• Check whether local rules call for witnesses, notarization, registration, particular wording, or notice steps; ask a qualified lawyer when the stakes are high.