Copy-and-fill scope of work
Use this as the working project boundary. Keep it specific enough that both sides can tell what is included, what is excluded and what completion means.
PROJECT NAME: [Project name] PROJECT OBJECTIVE: [What this project is intended to accomplish] FREELANCER: [Name / business] BUYER: [Name / business] INCLUDED DELIVERABLES: 1. [Deliverable] 2. [Deliverable] 3. [Deliverable] INCLUDED WORK: - [Task or responsibility] - [Task or responsibility] - [Task or responsibility] EXCLUDED WORK: - [Explicit exclusion] - [Explicit exclusion] - [Explicit exclusion] BUYER RESPONSIBILITIES: - [Assets, access, approvals or information buyer must provide] FREELANCER RESPONSIBILITIES: - [Work freelancer is responsible for completing] MILESTONES: 1. [Milestone] 2. [Milestone] 3. [Milestone] TIMELINE: Start date: [Date] Target completion: [Date] REVISION POLICY: [Included revision rounds and boundaries] ACCEPTANCE CRITERIA: - [Condition for acceptance] - [Condition for acceptance] PAYMENT STRUCTURE: [Hourly / fixed / milestone-based] [Amounts and payment triggers] FINAL HANDOFF: - [Final files] - [Editable/source files] - [Repository or account access] - [Documentation] CHANGE CONTROL: Any material change to deliverables, scope, price or timeline should be agreed in writing before the additional work begins.
The scope of work should describe the version of the project both sides are actually agreeing to, not an earlier version that has already changed.
Core scope sections
Define exclusions
Writing down what is not included can prevent as much confusion as writing down what is included.
Connect scope to payment
For milestone projects, each payment stage should map to a meaningful deliverable or accepted result.
Update scope when reality changes
If the project materially changes, revise the written scope rather than pretending the original agreement still describes the work.
A scope of work can also feed into structured freelance agreement rules for deadlines, reviews and settlement.