Work Scope Tracker

Freelance scope records

Unpaid revisions are harder to discuss when the record is scattered

By the time a billing conversation becomes tense, the real problem is often older: the extra work was not recorded, priced, or approved clearly before it started.

Where Work Scope Tracker fits

Work Scope Tracker is not a debt collection tool and does not perform administrative action for you. It is useful earlier in the workflow, when you still have a chance to create a clean approval trail.

What usually goes wrong

  • The freelancer starts extra work before confirming the added amount.
  • Client approval is buried in a chat message or call memory.
  • The original scope and revision rule are not easy to show.
  • The final invoice includes work the client does not remember approving.

A better record before the invoice

  • Original scope and included revisions.
  • Each request that changed scope, cost, or delivery.
  • The reason each request was treated as extra work.
  • The approval link, decision, amount, and date.
  • A clean export for your own billing review.

A practical workflow

  1. 1Use the project scope as the baseline.
  2. 2Record each potentially unpaid revision before doing it.
  3. 3Ask for approval when it affects the agreed boundary.
  4. 4Keep the approval record attached to the request.
  5. 5Use the export to review billing, not to replace professional advice.

Before doing unpaid-feeling work, ask this

I can handle this revision. Before I begin, I want to confirm whether we should treat it as an included revision or extra work.

Original scope/revision rule: [summary]
New request: [summary]
Reason this may be extra: [reason]
Proposed amount or time impact: [amount/hours]

Please confirm how you want to proceed.

Related problem guides

Try it on a real project

Create a project, write the agreed scope, and record the next request before it becomes another memory test.

Open Work Scope Tracker