When a client says “I thought that change was already approved,” the problem is often not the design work it is the absence of a shared record. A freelance revision round tracker connects each feedback request to the draft version, reviewer, due date, and final decision. It keeps changes visible without forcing a solo freelancer to buy a project-management platform.
Below is a copyable spreadsheet structure, a worked example, a workflow for consolidated feedback, and scripts for handling extra requests. The tracker is useful for designers, editors, web developers, copywriters, and any freelancer who submits work for review. It complements a statement of work; it is not a substitute for an agreement.
Key takeaways
- Give each draft a version ID and each requested change its own row.
- Define an included revision round in writing before the project begins.
- Ask for consolidated feedback from one named decision-maker.
- Separate corrections needed to meet the original specification from new work outside scope.
- Record explicit approval, not just silence or a vague “looks fine.”
Free editable spreadsheet: Download the revision round tracker (.xlsx) with a request log, approval states, scope dropdowns and a summary dashboard. Replace the fictional examples with your own project details.
What should a freelance revision tracker accomplish?
At minimum it should answer: which file was reviewed; which comments were submitted; who requested them; whether the change is included in scope; who is doing the work; and when the decision was made. “Round two” means little if feedback is scattered across five email chains and two chat channels.
The tracker also reduces misunderstandings between a correction and a change request. If your delivered page has the wrong approved product name, fixing it is ordinarily part of completing the original requirement. If a client introduces a new target audience and asks for a redesigned site architecture, that may be additional work requiring a separate estimate.
The number of included rounds is a commercial term, not a universal industry law. Define it explicitly in your quote or statement of work. A common approach for creative projects is to count one consolidated set of feedback on one delivered version as one round, but project complexity may justify a different arrangement.
Copy this revision tracking spreadsheet template
Create a sheet called Revision Log with the following headings. You can paste the header names into Excel or Google Sheets, then create one row for each distinct request.
| Column | Header | Purpose |
|---|---|---|
| A | Project | Client or job name |
| B | Version | Document or design version ID |
| C | Round | Feedback round number |
| D | Request ID | Unique comment reference |
| E | Location | Page, section, slide, or timecode |
| F | Requested Change | Observable, specific edit |
| G | Requestor | Who provided the comment |
| H | Scope | Included, Correction, or Change Request |
| I | Owner | Who makes or approves the edit |
| J | Status | Open, In Progress, Ready for Review, Resolved |
| K | Decision Date | Date of client decision |
| L | Proof Link | Comment, file, or approval record |
Keep a second Round Summary tab with the project, agreed included rounds, rounds consumed, approver, and overall approval state. This separates administrative limits from the individual edits. If the project has security requirements, store the sheet and linked assets only in an approved shared workspace.
Suggested data validation rules
Restrict the Scope field to Included / Correction / Change Request and Status to Open / In Progress / Ready for Review / Resolved / Rejected. Standardized labels make filtering useful. A request marked Resolved should link to the updated file or contain a note explaining the decision; otherwise nobody can verify what changed.
Formula for open issues
=COUNTIF(J2:J500,"Open")+COUNTIF(J2:J500,"In Progress")That counts unresolved issues in the tracker. It does not tell you how much work remains; a single open redesign request can take longer than ten small corrections. Add a separate effort estimate where needed.
Worked example: a landing page design with two rounds
Imagine a freelancer delivering a homepage mockup to one client with two included review rounds. The fictional records below show how to distinguish planned revisions from a new request.
| Round | Request | Scope | Status |
|---|---|---|---|
| 1 | Replace hero image with supplied final photo | Included | Resolved |
| 1 | Correct brand name spelling in footer | Correction | Resolved |
| 2 | Reduce navigation labels from six to five | Included | Ready for Review |
| 2 | Add a new product comparison landing page | Change Request | Open / Awaiting Quote |
The first three requests relate to the existing design. The additional landing page is a new deliverable. It should be estimated and approved separately rather than quietly counted as a minor edit. Keep the original agreed two-round limit intact unless both parties agree to change it.
The tracker also needs a version map. For example, Homepage-v1 is the original submission; Homepage-v2 contains round-one responses; Homepage-v3 is the revised file awaiting final approval. Choose a naming pattern that makes sense for your tools; do not label two different files with the same version.
A six-step review and approval workflow
Step 1: write the feedback rules before delivery
State how many rounds are included, what counts as a round, how the client should send feedback, who has final approval, and what is excluded. Give the client the same definition in the quote and handoff email. A brief written agreement prevents disagreement about rules that only emerged after the work began.
Step 2: send a clearly labeled version
Use one shareable file or a precise version link. In your message, include the review deadline and expected response format. For example: “Please review Homepage-v1 and return one consolidated comment list by Thursday. Round one will be based on that list.”
Step 3: consolidate comments into one log
Ask the client to resolve conflicting stakeholder feedback before formally submitting it. If marketing wants one message and sales wants another, they should decide which direction is approved. A freelancer can help identify the conflict, but should not silently become the final decision-maker for the client.
Step 4: classify and clarify each request
Mark obvious corrections, included refinements, and scope changes. Ask clarifying questions on vague phrases such as “make it pop” or “feels too corporate.” Turn them into observable changes: larger headline, different supplied image, reduced copy length, or alternative color treatment.
Step 5: implement and point to evidence
Update status as work progresses and link to the new version. For each resolved row, note where the change appears. If you decide not to implement a comment because it conflicts with another requirement, record the explanation and ask the client to decide.
Step 6: request explicit approval
Present the final version with a short summary of changes and a clear action: “Please confirm approval of Homepage-v3 for handoff, or identify any remaining items under the agreed scope.” Save the approval message. A reaction emoji or lack of reply is weaker evidence than written sign-off.
Asana’s documentation on proofing and approvals illustrates how structured review states and precise comments improve handoffs. You can apply the same principles with free tools; the paid features themselves are not required.
How to handle extra rounds without damaging the relationship
Start with the agreed definition. If two rounds were included and a client requests a third set of new refinements, describe the remaining work, estimated hours or fixed fee, and timeline impact before doing it. If the third round is needed because you failed to deliver the original brief, that may be your responsibility rather than a legitimate extra charge.
Polite message for an additional round
Thanks for the detailed notes. We’ve completed the two review rounds included in the current project scope. I can make these additional refinements as a separate revision round. The estimated fee is [amount], and delivery would be [date] after approval. Would you like me to send a short change order?
Message when multiple reviewers conflict
I noticed the comments request both a shorter and a more detailed product section. Could your team confirm the preferred direction and return a consolidated decision? Once confirmed, I’ll update the next version and log it in the revision tracker.
Message requesting final approval
Version [ID] now contains the approved edits from round [number]. The change log lists each item and its status. Please confirm whether this version is approved for handoff, or send any remaining corrections tied to the original specification by [date].
For the broader commercial process of agreeing on new deliverables and fees, use how to prevent freelance scope creep. That article discusses project boundaries; this article focuses on tracking review iterations and approvals.
Free tools to maintain your revision history
A Google Sheet can store the log and links. Google Drive’s file version guidance explains how to inspect and preserve versions; note that Google Docs history works differently from uploaded PDF or image files. A shared PDF with pinned comments can make visual feedback more precise than email alone.
For designers already using Adobe Illustrator, Adobe’s Share for Review process supports comment links and contextual feedback. Do not add a paid subscription just for a tracker if your existing workflow already provides traceable comments and clear version names.
Set reasonable permissions. A client reviewer may need commenting access but should not always have permission to overwrite original files. Keep final approved deliverables in a separate folder and preserve your contractual records according to applicable requirements.
What makes a revision tracking system succeed?
The best sign is not a pretty dashboard. It is that both sides know which version is current, which comments are outstanding, and which decision is final. At the end of each project, examine how many requests needed clarification, how often reviews missed deadlines, and where feedback became contradictory. Use those lessons to improve your next handoff brief.
Related resources include the freelancer offboarding checklist for handing over approved files and the freelance proposal template for describing revision boundaries before the project begins.
Frequently asked questions
What counts as one revision round?
A common contract definition is one consolidated set of feedback on a specific delivered version. The exact definition should be agreed in writing before the project starts.
How do I track revision rounds for free?
Use a spreadsheet with columns for version, round, request, reviewer, scope, status, owner, and proof link. Keep the approved file versions in a shared folder with appropriate permissions.
Are corrections the same as paid extra revisions?
Not necessarily. Correcting an error against the original specification is different from adding a new deliverable or changing the agreed direction. Your agreement determines how changes are handled.
What do I do when stakeholders disagree?
Identify the conflicting comments and ask the named decision-maker to provide one consolidated direction before implementing mutually exclusive changes.
How do I prove that a final version was approved?
Request explicit written approval naming the version and save the dated message or approval record alongside the final deliverables.