Compare live requests against original agreements before you say yes.
Why track scope
Scope creep is rarely one big ask. It is ten small ones: "Can you also...", "While you are at it...", "Just a quick update." Without tracking, you work extra hours at the same rate.
VAs who track scope protect their margin and their energy.
Tools that work (low to high tech)
| Tool | Best for |
|---|---|
| Shared Google Doc SOW | Simple projects, one client |
| Notion or ClickUp board | Retainers with ongoing tasks |
| Spreadsheet change log | Date, request, in scope Y/N, decision |
| Salag Scope Creep Detector | Quick check against original terms |
| Email recap thread | Proof when tools fail |
Pick one primary system. Do not split scope across five apps.
Your scope tracking workflow
- Save the original agreement where you can open it in 10 seconds.
- Log every new request with date and source (email, Slack, call).
- Tag each item: in scope, revision, or change order.
- Confirm out-of-scope items before you start.
- Update the log weekly on retainers, at each milestone on projects.
Sample change log row
| Date | Request | In scope? | Action |
|---|---|---|---|
| Aug 1 | Add 5 new leads to CRM | Yes | Done |
| Aug 3 | Build new landing page | No | Sent change order |
Common mistakes
- Verbal yes to new work with no log entry.
- No original SOW to compare against. Fix that first.
- Tracking tasks but not decisions. The decision email matters most.
- Using project tools the client never sees. Share read-only access when possible.
Final thoughts
Scope tracking is not about saying no to clients. It is about knowing what you said yes to. Tools make that visible so nobody has to rely on memory.
How Salag helps
- Client Red Flag Checklist. Spot clients who treat every ask as included.
- Payment Method Risk Check. Protect payment terms when scope expands.
- Request Clarifier. Turn vague requests into trackable tasks before you log them.
Move safer. Not faster.
In short
Scope tracking means comparing every new client request to what you originally agreed to deliver. You do not need fancy software. You need one source of truth: your agreement, plus a simple log of changes. Say yes only after you check the ask against that log.
Common questions
Scope tracking means comparing every new client request to what you originally agreed to deliver. You do not need fancy software. You need one source of truth: your agreement, plus a simple log of changes. Say yes only after you check the ask against that log.
Write down what you agreed on and what changed. Do not start new work on vague terms.
Use plain English, confirm in writing, and set clear hours. Clients hire you for reliability, not cheap labor.
Put the basics in your agreement or a recap email before billable work starts. Bigger projects need fuller terms.
Stay warm but firm. Offer options inside a clear process, like a change order or a short written recap.
VERIFY means: capture facts, compare to your agreement, name tradeoffs, confirm in writing, and save the decision for next time.
Escalate when the same problem repeats: unpaid extras, late approvals plus new asks, or refusal to confirm in writing.
Yes. A clear email with tasks, dates, price, and limits beats a verbal yes every time.
Salag gives you tools and templates so you can set boundaries before small problems grow.
Use written recaps, scope trackers, and Salag tools like agreement builders and scope detectors.
Most recaps take five minutes after a call. That small step saves hours of arguing later.
Yes. Retainers need weekly change logs. Projects need milestone gates. Always compare new asks to written terms.
Pause billable work on unclear items. Send a narrow summary of what you will do. Save their reply either way.