Most freelance project arguments are not about the work. They are about what was agreed at the start.
A scope document that prevents these arguments is not a complex legal instrument. It is a clear, specific description of what is in and what is out, written in plain language that both sides can reference when memory diverges.
The five sections of an effective scope document
Project overview. One paragraph describing the project in plain language. What problem it solves, for whom, and what the high-level approach is. This paragraph should be readable by the client's non-technical stakeholders.
Deliverables. A numbered list of everything you are delivering. Not categories. Specific items.
Not: "User authentication system."
Yes: "1. Email and password registration. 2. Email verification flow. 3. Login with session management (30-day session expiry). 4. Password reset flow with email link. 5. Account lockout after five failed login attempts."
Every deliverable specific enough that both sides can agree when it is done.
What is not included. The most important section most freelancers skip.
List the things a client might reasonably assume are included but are not. "Social login (Google, Apple, Facebook) is not included in this scope." "Mobile application versions are not included." "Content migration from the existing system is not included."
This section prevents more disputes than any other single element.
Assumptions. Everything you assumed when building the estimate. "This estimate assumes: client provides all copy and images before development begins. Existing API documentation is accurate. Hosting environment is [platform]. One round of revision per deliverable."
When an assumption proves wrong, the scope conversation is simple: "This assumption turned out to be incorrect, which affects [timeline/cost]. Here is how I propose we handle it."
Change order policy. One paragraph: any work outside this document requires a written change order agreed by both parties before work begins.
Sending and confirming the scope
Send the scope document before work begins and ask for explicit confirmation.
"Please review the attached scope document. This defines what is included in this project. If anything looks different from your understanding, let me know before we start."
Explicit confirmation before starting. Not assumed.
The Freelance Command Center includes scope document templates and a project tracking system. EUR 17.
Top comments (0)