Scope of Work Template for Hiring a Freelancer | TEC

A scope of work is a one or two page document that lists exactly what a freelancer will deliver, what is not included, the deadlines, the revision rounds, and what happens when the scope changes. Agree it in writing before work starts, and it turns a brief into a project you can both check.

Key takeaways

- A scope of work lists deliverables, exclusions, deadlines, revisions, and the change process. It is not the contract. It is the part of the paperwork that describes the work itself.

- In PMI's 2018 Pulse of the Profession survey, 52% of projects completed in the prior 12 months experienced scope creep or uncontrolled changes, up from 43% five years earlier. A written scope is the cheapest defence against that.

- One page is enough for most freelance jobs under $5,000. Match the paperwork to the project size, not the other way round.

- Name a single approver, a review window, and what silence means, or approvals stall and the project drifts.

- On TEC, client funds are held in escrow and released per milestone only after the client approves, and a project manager oversees scope, deadlines, and quality.

What is a scope of work, and how is it different from a contract?

A scope of work is the document that describes the job itself: what gets delivered, what does not, in what order, and what "finished" means. The contract covers the relationship: price, payment terms, ownership, confidentiality, and what happens if either side walks away. The scope covers the work. On a small project both fit on one page each, and they often sit in the same document, with the scope as an attachment or an appendix.

The two documents answer different arguments. When the freelancer says "that was not in the price" and you say "I thought it was included", the contract cannot settle it, because the contract never listed the work. The scope can, because it did. That is why the scope is the document you read first when a disagreement starts, and the contract is the document you read second.

You will also see the term "statement of work", usually shortened to SOW as well. For freelance projects the two terms mean the same thing in practice. Some larger companies use "statement of work" for the formal document and "scope of work" for the section inside it that lists the deliverables. Do not worry about the label. Worry about whether the document lists countable deliverables.

Why does a scope of work matter before you hire?

Most freelance arguments are not about money. They are about the client thinking something was included and the freelancer thinking it was not. A one-page scope, agreed before any deposit is paid, settles that in advance.

The scale of the problem is not small. In its 2018 Pulse of the Profession survey, the Project Management Institute (PMI) found that 52% of projects completed in the prior 12 months experienced scope creep or uncontrolled changes to scope, up from 43% five years earlier. The full report surveyed 4,455 project practitioners, 447 senior executives, and 800 project management office directors. Even the organisations PMI classed as champions saw scope creep on about a third of their projects.

Small projects are where scope creeps furthest, because nobody thought a $2,000 job was worth the paperwork. A five-page website becomes seven pages plus a blog, a logo becomes a logo plus business cards plus a social media kit, and a two-week build becomes a six-week build. Each extra is small. Together they double the job. A scope of work is the only cheap way to stop that, because it makes the boundary visible before the work starts, when changing it costs nothing.

What should a scope of work include?

Seven sections cover every freelance project. Some take one line. None should be skipped.

Project summary. Two or three sentences describing what the project is and what it is for, in the client's language. If a later request does not serve this summary, it is out of scope.
Deliverables. The section people think is the whole document. List countable things with formats and quantities: 5 pages, 3 logo concepts, 2 rounds of edits, source files in Figma. If you cannot count it, split it until you can. Vague words like "polished", "comprehensive", and "flexible" do not define a deliverable. Replace them with numbers, formats, and acceptance tests.
Not included. The most valuable section and the one almost nobody writes. List the things a reasonable person might assume were included, and say plainly that they are not: copywriting, stock tography licences, hosting, ongoing maintenance, a second language version. The exclusions section prevents more disputes per word than any other section.
Timeline and milestones. Dates for each deliverable, and what triggers each payment. Use durations from a trigger, not fixed calendar dates, where you can: "two weeks after you approve the designs" survives a slow approval; "November 30" does not.
Revisions and approval. How many rounds are included, what one round is, who the single approver is, how long they have to review, and what silence means. Without this, "just one more tweak" never ends.
What you will provide. Copy, logos, product photos, logins, access to accounts, and a decision maker who is available. Every input needs an owner and a date. A project stalls most often on the client's side, not the freelancer's.
Changes. One sentence that does the heavy lifting: work outside this scope is quoted separately and starts only after written approval. Every later request gets checked against this line.

Copy the template below, fill in the brackets, and send it with the quote and the contract. It takes about 20 minutes for a typical project.

SCOPE OF WORK

Project: [project name]

Client: [your name and business]

Freelancer: [freelancer name and business name]

Date: [date]

Attached to: [contract reference, if separate]

1. PROJECT SUMMARY

[One or two sentences: what the project is and what it is for.]

2. DELIVERABLES

[Numbered list. Countable items, with formats and quantities. Example: 1. Homepage design, desktop and mobile, Figma source files. 2. Four inner pages. 3. Contact form wired to email.]

3. NOT INCLUDED

[The following are not included and can be added by written change order: copywriting, stock photography licences, hosting, ongoing maintenance.]

4. TIMELINE AND MILESTONES

[Milestone 1: Designs approved, due 2 weeks after kickoff, 30% payment. Milestone 2: Build complete, due 2 weeks after design approval, 40% payment. Milestone 3: Launch and handover, due 1 week after build approval, 30% payment.]

5. REVISIONS AND APPROVAL

[2 revision rounds included. One round means one consolidated list of changes from the named approver. Approver: [name]. Review window: 5 business days. Silence after 5 business days counts as approval.]

6. WHAT YOU WILL PROVIDE

[Final copy by [date]. Logo files by [date]. Access to hosting and domain by [date].]

7. CHANGES

[Any work not listed in section 2 requires a written change order, priced and approved before the work begins.]

What does a filled-in scope of work look like?

Here is the same template filled in for an illustrative example: a $3,200 website redesign for a dental clinic. It is an example, not a quote, and the price is there so the milestone split makes sense.

Project: Website redesign, Bright Smile Dental Clinic. Client: Priya Shah, Bright Smile Dental Clinic. Freelancer: a freelance web developer hired for the build. Date: November 13, 2026.

Project summary: Redesign the clinic website so new patients can find the clinic, see the treatments, and book an appointment without calling. Five pages, live in six weeks.

Deliverables: 1. Homepage, desktop and mobile layouts, Figma source files. 2. Four inner pages: Treatments, About, Pricing, Contact. 3. Online booking form wired to the clinic email. 4. Basic on-page SEO: titles, meta descriptions, and image alt text on all five pages.

Not included: copywriting (the clinic supplies final copy), stock photography licences, hosting, and ongoing maintenance after launch.

Timeline and milestones: Milestone 1, designs approved, 2 weeks after kickoff, $960. Milestone 2, build complete, 2 weeks after design approval, $1,280. Milestone 3, launch and handover, 1 week after build approval, $960.

Revisions and approval: 2 revision rounds. Approver: Priya Shah. Review window: 5 business days. Silence after 5 business days counts as approval.

What the clinic provides: final copy by November 20, 2026, logo files by November 18, 2026, and hosting access by kickoff.

Changes: any work not listed above requires a written change order, priced and approved before the work begins.

Notice what the example does not contain: no adjectives, no promises about quality, no "and anything else needed". Every line is checkable. A stranger could read it and tell you, item by item, whether the project is done.

Project size	Scope format	Sections to keep
Under $1,000	Bulleted scope inside the proposal or a recap email	Deliverables, exclusions, price, deadline
$1,000 to $5,000	One-page scope, attached to the contract	All 7 sections, short form
Over $5,000	Full scope plus a milestone schedule	All 7 sections, with acceptance criteria per deliverable

What are the most common scope mistakes?

Five mistakes cause most scope arguments. Check for each one before you send the document.

Naming deliverables you cannot count. "A polished website" means one thing to you and another to the freelancer. "Five pages, desktop and mobile, with a booking form" means the same thing to both of you.
Skipping the exclusions section. It feels rude to write down what is not included. It is the section that saves the relationship, because scope creep starts where assumptions differ.
No revision limit, or no definition of a round. Two rounds means nothing if one round is "all the changes anyone on your team thinks of this week". Define a round as one consolidated list from one approver.
No named approver and no review window. If three people can approve and none of them has a deadline, the project waits on the slowest inbox. Name one person and give them five business days.
Fixed dates instead of durations from a trigger. A deadline of November 30 means nothing if the designs are approved on November 28. Write "two weeks after design approval" and the schedule moves with the project instead of breaking.

Post your project free on TEC and get a vetted shortlist in about 48 hours, with milestone escrow and a project manager keeping the scope on track.

How does TEC handle scope on your project?

The Expert Community (TEC) is a managed marketplace where businesses hire vetted experts, including web developers, designers, and marketers. When you post a project brief, which takes about 60 seconds, TEC typically shares a shortlist of 2 to 3 vetted experts within about 48 hours. Every expert goes through a 5-step screening that includes ID verification, portfolio review, and a skills or technical assessment. Matching considers skills, domain fit, past outcomes, and the expert's rate, and there is no bidding.

Scope is protected by how payment works. Client funds are held in escrow and released per milestone only after the client approves. If the client does not respond within 7 days of a milestone delivery, funds release automatically. A TEC project manager oversees milestones, scope, deadlines, and quality, so a request that falls outside the agreed scope gets flagged before it becomes unpaid work. There are no bidding fees for clients, and a full fee and tax breakdown is shown before the client accepts. If you want to hire with the scope written down and the payment protected, post your project free on TEC.

Post your project free on TEC. Get a vetted shortlist in about 48 hours, with milestone escrow and a project manager keeping the scope on track. Free, takes 2 minutes.