Salag
SALAG
Scope and Boundaries

The Scope Agreement Checklist Every Freelancer Needs

Most scope disputes begin before the project starts. This checklist walks through every agreement point to cover before you send a proposal, with Salag's CLEAR framework and a pre-send audit you can use today.

Published scope-creep12 min read

Pre-send checklist

Must haveExample
Deliverables"Daily inbox triage, max 50 emails"
Format"Google Doc report every Friday"
Hour cap or fixed fee"20h/month" or "$800 flat"
Exclusions"Not included: ads, bookkeeping"
Revision limit"Two feedback rounds"
Acceptance"Reply within 3 business days or deemed approved"
TimelineStart, milestones, end
PaymentCurrency, deposit, due date, method
Change process"Extras need written OK"
Primary contactOne approver

CLEAR framework

Salag CLEAR for scope:

  • Confirm deliverables (bullets, not fluff)
  • Limit revisions (two rounds)
  • Exclude non-scope (explicit list)
  • Agree acceptance (how sign-off works)
  • Require change orders for extras

Exclusions examples for VAs

  • Paid ads management
  • Bookkeeping / tax filing
  • Graphic design beyond simple edits
  • 24/7 coverage
  • Phone sales calls
  • Training their new hire for free

See client says just a quick fix.


One-screen scope email

Script

Scope for [project] Deliverables: [...] Not included: [...] Revisions: 2 rounds Fee: [amount] / [hours] Payment: [deposit] due [date], balance [date] Changes: written OK before work Please reply "confirmed" or edits.


After signing: scope creep

  1. Open scope doc.
  2. Is ask inside? Do it.
  3. Outside? Change order email.
  4. Log in change sheet.

Use scope creep detector and agreement builder.


Common mistakes

MistakeFix
Vague deliverablesName counts and formats
No exclusionsAdd "not included" block
Unlimited revisionsCap at two
Verbal kickoff onlyEmail confirm

How Salag helps

Move safer. Not faster.

In short

Most scope fights start before day one because nobody wrote exclusions, revision limits, or how to handle extras.

Use this checklist before you send any proposal. Takes 15 minutes. Saves weeks of free work.

Common questions

Most scope fights start before day one because nobody wrote exclusions, revision limits, or how to handle extras. Use this checklist before you send any proposal. Takes 15 minutes. Saves weeks of free work.

Deliverables, formats, revision limits, exclusions, acceptance rules, timeline, payment, and how to handle extra work. Exclusions and change orders stop most fights.

SOW (scope of work) is what you deliver and when. Contract adds payment, IP, privacy, and exit rules. Many VAs use one doc with both.

Two rounds of consolidated feedback is normal. Say what counts as revision vs new work. Charge for round three.

A short written OK for new work: task, price, date. Before you start the extra, not after.

Exclusions list what is NOT included. Stops "I thought you also did ads."

After discovery, before billable hour one. Never on vague "just start."

How client says "approved" and how many days they have to reply. Silence rule optional but helpful.

Compare ask to written scope. Friendly redirect or change order. Log every add.

Yes. Time zones and memory gaps make writing essential. Plain English is fine.

Confirmed email beats nothing. Bigger jobs need fuller terms too.

Currency, total, deposit, due dates, method, late rule. Tie pay to milestones when you can.

Specific enough that someone else could check. "5-page Figma homepage" not "website stuff."

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

On fixed projects, yes often. Protects you if they cancel mid-build.

"Flexible through change orders" so budget and time stay honest.