Freelance scope records
Revision rounds need a boundary before they become unpaid work
Freelance projects often include a limited number of revisions. The hard part is remembering which round you are in and whether a request is a revision, a new feature, or a changed direction.
Where Work Scope Tracker fits
Work Scope Tracker gives freelancers a way to write the included revision policy, record new revision requests, and separate included work from extra work before the next round starts.
Revision details to define early
- How many revision rounds are included.
- What counts as a revision instead of a new request.
- Whether new pages, new features, or direction changes are excluded.
- How extra revision rounds are priced.
- Who can approve an extra round.
Common revision risks
- The client gives feedback in pieces across several days.
- A revision changes the approved concept rather than refining it.
- Multiple stakeholders reopen the same decision.
- A request is accepted verbally but never written down.
A practical workflow
- 1Write the included revision rule inside the project scope.
- 2Log each revision request separately.
- 3Mark the current round and whether it is still included.
- 4Send approval before extra rounds or changed direction work.
- 5Export the revision history at delivery.
Revision boundary wording
Included revisions: [number] rounds for refining the agreed deliverable. Not included: new concepts, new pages, changed direction, or requests after final approval. Extra revision round: [amount] or [hourly rate], approved before work starts.
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.