Freelancers guide
Project Scope Template for Freelancers
Define what is included, excluded, reviewed, and accepted before an engagement begins.
Practical guide · 6 min read
Scope is the shared boundary around an engagement. A good scope does not predict every conversation; it makes the important decisions visible before work begins. Use this template inside a proposal or as a referenced scope document, and obtain appropriate professional review where needed.
1. Write a controllable project objective
The project will [create or change] [specific thing] for [audience] so they can [observable outcome].
An objective is not a guarantee. “Create a clearer checkout flow” is controllable; “increase sales by 40%” is not unless the evidence, engagement, and responsibility genuinely support that commitment.
2. Define included deliverables
For each deliverable, answer four questions.
| Field | Prompt |
|---|---|
| Output | What tangible item or working behavior is delivered? |
| Limit | How many pages, screens, records, rounds, or hours? |
| Review | What will the client inspect? |
| Acceptance | What observable condition means complete? |
Example: a responsive homepage design can specify one approved direction for desktop and mobile, named sections, two consolidated review rounds, and acceptance once approved content and feedback are represented.
3. List plausible exclusions
Exclusions prevent assumptions from becoming surprise work. Depending on the engagement, name boundaries around:
- Copywriting, translation, photography, illustration, or video.
- Paid fonts, stock assets, plugins, hosting, or domain fees.
- Data cleanup or migration beyond a stated quantity.
- Authentication, payments, CRM, automation, or analytics.
- Legal, privacy, certification, tax, or security audits.
- Ongoing support after the handoff or defect window.
Only include exclusions that are plausible for this project. A giant generic list is difficult to review.
4. Assign inputs and responsibilities
| Input or decision | Owner | Due | Condition |
|---|---|---|---|
| Final copy | Client | [date] | Approved document |
| Brand assets | Client | [date] | Licensed source files |
| Design/build | Freelancer | [date] | Review link |
| Legal approval | Client adviser | [date] | Written approval |
Name one client decision-maker and one person responsible for consolidated feedback. For each milestone, include the start condition, output, review window, decision point, and any linked payment.
5. Control reviews and changes
Define a review round as one consolidated set of feedback delivered within a stated window. An included revision refines the approved direction; a different direction or an additional deliverable is usually a change.
Change requested:
Reason:
Affected deliverables:
Fee impact:
Schedule impact:
Decision by:
Approved by/date:Do not begin material out-of-scope work based only on an informal message when fee or timing changes.
6. Acceptance and handoff
- Complete the acceptance checklist.
- Record known non-blocking issues and owners.
- Hand over files, access, documentation, and licenses.
- Identify production and renewal responsibility.
- State the final invoice or handoff condition.
A third party should be able to see what will exist, what will not be delivered, what the client must provide, how outputs are accepted, and what happens when a request changes fee or schedule.