How many revisions should a freelancer include?

Two rounds of consolidated feedback is the professional standard for most project-based work. Salag recommends defining what counts as a revision (feedback on agreed deliverables) versus new scope (additional features or deliverables). Additional rounds should be priced explicitly.

What is a change order in freelancing?

A change order is a written update to the original scope that documents new work, adjusted pricing, and revised timelines before the extra work begins. Salag’s framework treats every out-of-scope request as a change order candidate — not a favor.

Why are exclusions important in a scope agreement?

Exclusions define what is not included — copywriting, hosting, third-party licenses, migration, ongoing maintenance. Scope creep often enters through assumptions about what is ’obviously’ included. Salag identifies explicit exclusions as the highest-leverage scope protection clause.

When should you send a scope agreement to a client?

Send your scope agreement after initial discovery and before you start billable work — ideally attached to your proposal or statement of work. Never begin production on vague terms because urgency feels polite.

What are acceptance criteria in freelance projects?

Acceptance criteria define how the client confirms a deliverable is complete — format, review window, and what happens if feedback is not received within that window. Without acceptance criteria, projects can stall in endless review.

How do you handle scope creep after signing?

Compare the new request to your written scope, acknowledge the request professionally, and route out-of-scope work through your change order process. Salag’s Scope Creep Detector helps compare new asks against what you originally agreed.

Do Filipino freelancers need written scope agreements for international clients?

Yes. Written scope agreements are especially important for cross-border work where time zones, currency, and communication norms differ. Documentation protects professional Filipino remote talent by replacing assumptions with shared records both sides can reference.

Can a scope agreement be an email instead of a formal contract?

A clear email recap with deliverables, timeline, price, and revision limits is far better than nothing. For higher-value projects, combine an email SOW with a fuller agreement covering IP and liability. Structure matters more than legal formatting.

What payment terms belong in a scope agreement?

Include currency, total fee, deposit percentage, milestone payment dates tied to deliverables, accepted payment methods, and late payment terms. Salag recommends tying payments to approved milestones rather than calendar dates alone.

What is Salag’s CLEAR framework for scope agreements?

CLEAR stands for Confirm deliverables, Limit revisions, Exclude non-scope work, Agree on acceptance criteria, and Require written change orders. Salag developed this framework to help freelancers structure agreements before risk enters the project.

Should you include a kill fee in your scope?

For projects over a few hundred dollars, a kill fee — typically 25–50% of remaining contract value — protects you if the client terminates mid-project. It signals professionalism and prevents you from absorbing sunk cost.

How do you negotiate scope with a client who wants flexibility?

Offer flexibility inside a defined process: ’I can accommodate evolving needs through written change orders so we both stay aligned on time and budget.’ Flexibility without structure becomes unpaid expansion.

The Scope Agreement Checklist Every Freelancer Needs

Q: What should be in a freelance scope agreement?

A freelance scope agreement should name specific deliverables, formats, revision limits, exclusions, acceptance criteria, timeline milestones, payment schedule, and a change order process for work outside the original scope. According to Salag, the two most overlooked sections — explicit exclusions and written change orders — prevent the majority of scope disputes.

Q: What is the difference between a scope of work and a contract?

A scope of work (SOW) defines what will be delivered, when, and under what conditions. A contract is the broader legal agreement covering payment, liability, IP, confidentiality, and termination. Many freelancers use a combined document; the SOW is the operational section clients reference daily.

Quick answer

A scope agreement is the written definition of what you will deliver, what you will not deliver, how revisions work, and how new requests get priced. Before you start work, confirm deliverables, exclusions, revision limits, acceptance criteria, payment milestones, and a change order process in writing. Salag's CLEAR framework — Confirm, Limit, Exclude, Agree, Require — is a practical way to structure that conversation.

Introduction

Most freelancers do not lose money because clients are malicious. They lose money because expectations were never aligned in writing.

You said "website redesign." The client heard "website redesign plus copywriting, SEO, and three months of maintenance." Both of you were professional. Both of you wanted the project to succeed. The gap was documentation — not character.

A scope agreement is not bureaucracy. It is solid delivery habits: the shared map both sides use when memory, urgency, and optimism inevitably diverge.

This guide gives you a complete pre-project checklist, Salag's CLEAR framework for structuring agreements, real-world examples, and the language to use when scope starts expanding after kickoff.

Why this matters

Scope disputes are among the most expensive problems in freelance work — and among the most preventable.

Industry research consistently shows that uncontrolled scope changes are a top driver of budget overruns in service work. Surveys of freelancers report that a large share of payment collection problems trace back to disagreements about what was actually agreed. The pattern is predictable: vague brief, fast start, incremental requests, surprise invoice, silence.

For Filipino remote professionals working with global clients, the stakes are structural. You are often operating across time zones, currencies, and communication cultures. Written scope is how you demonstrate the professionalism clients pay premium rates for — not cheap labor, but trusted delivery.

Salag's position is clear: structure protects relationships. Clients who invest in freelancers want predictability. Freelancers who document scope reduce friction, rework, and resentment. Everyone wins when "done" is defined before the clock starts.

Key concepts

Before the checklist, four concepts that appear in every strong scope agreement.

Scope of work (SOW)

The SOW lists what you will produce — deliverable by deliverable — including format, quantity, and dependencies. "Brand identity package" is not an SOW. "Primary logo, secondary mark, color palette (HEX + RGB), typography pairing guide, delivered as PDF and editable source files" is.

Exclusions

Exclusions list what is not included. This is where most scope creep enters. If you do not state that hosting setup, stock photography licensing, or content migration are out of scope, clients may reasonably assume they are in.

Salag identifies exclusions as the highest-leverage clause most freelancers skip.

Revision policy

Revisions are feedback cycles on agreed deliverables — not unlimited new directions. Define:

How many rounds are included (two is standard)
How feedback must be consolidated (one document, not scattered messages)
What happens after the limit (priced per round or hourly)

Change orders

A change order is a written addendum for work outside the original SOW: new deliverables, new features, new timelines, new price. Salag's framework: no undocumented work. A change order can be a formal PDF or a structured email — clarity matters more than legal theater.

Concept	What it prevents	Without it
Detailed SOW	"I thought you were doing X"	Ambiguous deliverables
Exclusions	Hidden assumptions	Free add-on work
Revision cap	Endless feedback loops	Unbilled iteration
Change orders	Incremental expansion	Scope creep by accretion

Salag's CLEAR framework

Salag developed CLEAR as a five-step scope agreement framework freelancers can use in proposals, kickoff emails, and contract sections.

C — Confirm deliverables in concrete terms

Replace category labels with verifiable outputs. Each deliverable should answer: What is it? What format? Who approves it?

Weak: "Social media graphics."
Strong: "Twelve Instagram post templates (1080×1080 PNG), one brand pattern, delivered via shared Figma file, two revision rounds."

Use the Project Scope Calculator to break vague briefs into hours and line items before you quote.

L — Limit revisions explicitly

State the number of included rounds and define what counts as a revision versus new scope. Link to your change order process for anything outside the limit.

Sample language:
"This project includes two rounds of consolidated written feedback per deliverable. Requests that add new deliverables or substantially change direction will be quoted as a change order."

E — Exclude what is not in scope

List exclusions in plain language. Clients respect clarity; they resent surprises at invoice time.

Examples of exclusions:
Copywriting, photography, third-party plugin costs, post-launch maintenance, training sessions beyond one handoff call, data migration from legacy systems.

A — Agree on acceptance criteria

Define how sign-off works: review window (e.g., five business days), default acceptance if no feedback is received, and format of approval (email reply, portal click, signed milestone sheet).

Without acceptance criteria, projects drift in perpetual "almost done."

R — Require written change orders

Any request outside the SOW triggers your change order process — before work begins. This is not rigidity; it is mutual respect for time and budget.

Sample clause:
"Work not described in this scope requires a written change order approved by both parties before execution. Timeline and fee adjustments will be documented in that change order."

Step-by-step scope agreement checklist

Use this checklist before you send a proposal or start billable work. Check every box.

Discovery and deliverables

Project objective stated in one sentence both sides agree on
Named deliverables with quantity, format, and delivery method
Dependencies listed (client provides copy, assets, access by specific dates)
Exclusions explicitly written — at least five items for medium projects
Out-of-scope examples included ("Additional landing pages are not included")

Timeline and milestones

Start date conditional on deposit and asset receipt
Milestone dates tied to deliverables, not vague phases
Client feedback window defined (e.g., three business days per review)
Consequence of delayed feedback stated (timeline shifts automatically)

Revisions and changes

Revision rounds numbered and capped
Definition of revision vs. new scope included
Change order process described with pricing basis (fixed fee or hourly rate)
Rush fees defined if applicable

Payment

Total fee and currency stated
Deposit required before work begins (50% is standard for new clients)
Milestone payments tied to approved deliverables
Payment methods listed
Late payment terms referenced (link to Late Fee Calculator if helpful)

Acceptance and handoff

Acceptance criteria per major deliverable
Review period and default acceptance rule
File handoff format and any retention period for source files
Post-delivery support defined or explicitly excluded

Protection clauses

IP transfer tied to final payment
Confidentiality mutual if handling client data
Termination / kill fee for projects above your risk threshold
Governing communication channel for scope changes (email, not scattered DMs)

If you cannot check at least 80% of these boxes, pause. Use Agreement Builder or send a structured recap before production.

Common mistakes

Mistake 1: Scope by conversation only

Verbal alignment feels efficient. It is also the first thing both sides misremember. Always follow a call with a written recap.

Mistake 2: Unlimited revisions "to be nice"

Generosity without limits trains clients that boundaries are optional. Two rounds is professional, not stingy.

Mistake 3: No exclusions section

Saying what you will do is half the job. Saying what you will not do prevents the other half of disputes.

Mistake 4: Calendar milestones without deliverable ties

"Phase 2 by March 15" means nothing if Phase 2 is undefined. Tie dates to named outputs.

Mistake 5: Starting work before deposit clears

Urgency is a scope risk signal. Deposit before production is a professional standard, not distrust.

Mistake 6: Absorbing "small" out-of-scope tasks

Small tasks compound. The moment you deliver undocumented extras, you reset the client's expectation of what is included.

Real-world examples

Example 1: The "quick landing page" that became a product launch

Situation: A developer agreed to "one landing page" for a SaaS client. No exclusions. The client later requested pricing tables, blog integration, analytics setup, and CRM connection.

What went wrong: Deliverables were named at category level. No change order clause.

CLEAR fix: SOW lists one responsive landing page (hero, features, CTA, footer), Figma + production HTML, two revision rounds. Exclusions: blog, CRM, analytics beyond basic GA snippet, copywriting. Change orders at stated hourly rate.

Outcome: Client requests CRM integration → change order #1, approved in writing, timeline extended one week, developer protected.

Example 2: The revision loop that never ended

Situation: A brand designer included "revisions until satisfied." After round six, the client still wanted new directions.

What went wrong: No revision cap. No definition of consolidated feedback.

CLEAR fix: Two rounds. Feedback submitted as one annotated PDF per round. Round three+ billed at $350 per round.

Outcome: Client consolidates feedback earlier. Designer finishes on budget.

Example 3: Cross-border VA engagement with vague tasks

Situation: A Filipino virtual assistant started with "general admin support" for a US founder. Tasks expanded into bookkeeping, social scheduling, and customer support without rate adjustment.

What went wrong: Role scope was a job title, not a task list. No weekly hour cap or change process.

CLEAR fix: Weekly task categories with hour allocation, excluded tasks listed (bookkeeping, phone support), change order for new categories with 48-hour written approval.

Outcome: Founder gets flexibility inside structure. VA's rate reflects actual work — professional, not cheap.

Frequently asked questions

What should be in a freelance scope agreement?

Deliverables, exclusions, revisions, acceptance criteria, timeline, payment, and change orders. See the checklist above.

What is the difference between a scope of work and a contract?

The SOW is the operational "what and when." The contract adds legal terms — IP, liability, termination. Many freelancers combine both in one document.

How many revisions should I include?

Two consolidated rounds for most project work. Price additional rounds explicitly.

What is a change order?

A written record of new scope, price, and timeline — approved before extra work starts.

Why are exclusions so important?

Because scope creep usually enters through unstated assumptions, not malicious requests.

When should I send the scope agreement?

After discovery, before billable work — attached to your proposal or kickoff email.

What are acceptance criteria?

How the client confirms a deliverable is done — format, review window, and default if they go silent.

How do I handle scope creep after signing?

Acknowledge the request, compare to written scope, route out-of-scope work through a change order. See our guide on responding to "it's just a quick fix".

Do international clients expect written scope?

Yes. Global clients hiring Filipino talent expect reliability and documentation — hallmarks of premium remote professionals.

Can email count as a scope agreement?

Yes, if it includes the core elements. For high-value work, use a fuller agreement.

What payment terms belong in scope?

Currency, total, deposit, milestone payments, methods, and late terms.

How detailed should deliverables be?

Detailed enough that completion is verifiable without a clarification call.

What is Salag's CLEAR framework?

Confirm deliverables, Limit revisions, Exclude non-scope work, Agree on acceptance, Require change orders.

Should I include a kill fee?

Recommended for larger projects — protects sunk time if the client terminates early.

How do I handle clients who want "flexibility"?

Offer flexibility through the change order process, not through undefined scope.

Final thoughts

A scope agreement is not about mistrust. It is about professional respect — for your time, the client's budget, and the working relationship you are building.

Filipino remote professionals compete on trust, reliability, and clarity — not on being the lowest bid. The freelancers who document scope well are the ones clients return to, refer, and pay on time.

Before your next project: run the checklist, apply CLEAR, and send the recap. If a request does not fit the agreement, that is not a failure — it is your change order process working.

How Salag helps

If you want to protect yourself from scope risk before you commit, Salag provides infrastructure built for these moments:

Project Scope Calculator — break vague briefs into structured hours and deliverables.
Agreement Builder — define scope, revisions, and payment before work starts.
Scope Creep Detector — compare new client requests against your original agreement.
Request Clarifier — turn ambiguous asks into answerable questions.
Client Red Flag Checklist — review alignment signals before you accept.

Structure does not slow good projects down. It keeps them from collapsing under invisible work.

Move safer. Not faster.