Freelance Revision Tracker: Separate Client Feedback, Scope Changes and Approval
October 17, 2026
A freelancer often finishes the requested work and still cannot close a job. One stakeholder requests another small change; someone else says the files look good; and the final approver has not responded. The problem is not always the number of revisions. It is the missing distinction between feedback, scope change, internal readiness and client approval.
The Freelance Revision & Approval Studio gives a small project a structured place for those distinctions. Each project stays in your browser unless you export it; there is no shared approval portal or automatic email.
Start with the original agreement
Write down the scope that the client actually accepted: deliverables, formats, number of included revisions, deadlines and who has authority to approve. These terms come from the agreement or correspondence, not from the studio.
Use the Freelance Scope Studio to separate the initial scope from later requests. A project can have new tasks without those tasks being included in the original price.
Record feedback as a factual action
For each requested change, note what the client asked for, when it was received, who requested it and what answer or evidence is still missing. Avoid translating ambiguous language into approval.
| Message you receive | What to record | What not to assume |
|---|---|---|
| “Can we move the logo?” | Proposed logo placement change | That a new scope is approved |
| “This looks good to me” | Positive feedback from the sender | Final sign-off by an authorized person |
| “Please send files tonight” | Requested delivery time | Agreed rush fee or feasible deadline |
| “Use the earlier version” | Request to revisit an earlier option | That all subsequent changes are canceled |
Keep sensitive login credentials, customer personal data and payment card details outside shared summaries.
Compare an original and a revised entry
The studio’s Compare two records section is helpful when you have recorded two versions or two candidate decisions. Select the original record and its proposed update. The comparison shows which fields match and differ and where a value was never entered.
It does not determine whether the revision is billable or approved. That determination depends on your agreement and the client’s actual communications. Download a text comparison if you need a short private change explanation.
If two records appear to be duplicates, inspect them; sometimes two requests on the same date genuinely refer to the same issue, but two rounds of feedback may also use identical words. Never delete the audit trail just because labels match.
Write a clear decision request
A useful approval request contains four components: the exact item or version; the change being confirmed; the specific decision requested; and a realistic response date if one was actually agreed. Do not present an invented deadline as the client’s commitment.
A short message could read:
The updated homepage design reflects the three changes listed in our last review. Please confirm whether version B is approved for handoff or list the remaining requested changes. Any additional work outside the agreed scope can be reviewed separately.
Before sending, verify that this message matches the real agreement. Save the response in your ordinary client correspondence, then update your local record.
Handoff and invoice closeout
Once approval is explicitly recorded, prepare the deliverable list and use the Photo Delivery Approval Desk if the project involves media delivery. The Client Payment Follow-Up Studio can track known invoice and receipt checkpoints, while the Freelance Invoice Receipt Review separates issued documents from money received.
For an internal or client-facing copy, choose a focused PDF or a short handoff brief, checking notes for private information first. Remember that a PDF of your entered records does not itself create legal acceptance.
Five-minute end-of-week review
Check each open revision for an owner, the exact source message, scope classification, next action and explicit approval status. Where something is unknown, leave it unknown and ask a precise question.
Start here: Create a separate client project in the free revision tracker and record a real request before importing an entire backlog.