Clients Commenting on Old Versions Creates Rework
When a client reviews the wrong file, the problem is rarely the client. It is usually the handoff: too many links, unclear versions, and no obvious place to leave feedback.
When clients comment on old versions, the issue is usually not careless feedback. It is a design approval workflow problem. The client needs one obvious current version to review, one place to leave feedback, and a clear way to approve or request changes.
A client leaves notes on a logo concept or mockup that is no longer current.
The designer acts on feedback that belongs to an outdated version.
The team has to clarify, undo, revise, and send the work back again.
For design studios, version confusion is not a small admin issue. It quietly creates rework.
Why old-version feedback keeps happening
The latest file is not obvious
A Drive folder can hold every version, but it does not always make the current review version obvious to the client. If the client sees v2, v3, final, final-new, and revised, they may choose the wrong one without realising it — a common source of client feedback on the wrong version.
Feedback arrives away from the work
A note in an email, a screenshot in WhatsApp, a comment in a shared file, and a call summary can all refer to different versions. The team then has to guess which comment belongs to which design instead of using one design review workflow.
Approval is remembered, not recorded
Someone may say a design was approved, but the approval is buried in a thread or implied after a call. Later, when revisions continue, the studio has no clean approval history of what was reviewed, changed, or signed off.
Old-version feedback is a workflow problem,not a client problem.
The folder is not the approval workflow
Myth
If the files are organised in Google Drive or Dropbox, the review process is organised.
Reality
Shared drives store files. They do not create a clear client approval workflow around the current version, feedback, request changes, and sign-off history. Creative approval software, online proofing software for design agencies, and client design approval software all exist because teams need more than folders.
This is why design studios can have tidy folders and still lose time. The file may be stored correctly, but the client-facing review moment is still scattered across links and messages.
A stronger design approval workflow makes one thing very clear: this is the current version to review, this is where feedback goes, and this is what has already been approved. Design studios need version history, comments, and approval records connected — not spread across channels.
What a cleaner design approval workflow should make obvious
Current version for review
Previous versions kept as history
Feedback attached to the right deliverable
Approve or request changes action
Clear status for the studio team
Simple review experience for the client
The real goal is not more control. It is less guessing.
Design work already has enough subjective discussion. The workflow around it should not add more uncertainty. Clients should not need to ask which file is final. Designers should not need to decode whether a comment belongs to an old version. Account managers should not need to search email threads to confirm what was approved.
A client approval portal for agencies does not need to replace the studio's design tools or project management tools. It should sit around the handoff moment as a client-facing approval layer — a deliverable review workspace where the client reviews the current version, leaves feedback, requests changes, or approves.
For a design studio, that clarity can protect creative time. Less rework from old comments. Less chasing for confirmation. Less confusion about what changed. More confidence that everyone is reviewing the same thing. That is what version control for design feedback should feel like in practice.
SignOffly is being built as a client approval portal for agencies that need a clearer way to manage deliverables, versions, feedback, and approval history. Shared drives store files; SignOffly manages the approval workflow around those files. SignOffly is not a project management replacement. Browse our practical guides on client approvals or join early access if old-version feedback is a familiar problem in your studio.
Common questions about clients commenting on old versions
What does it mean when clients comment on old versions?
It means a client leaves feedback on a file, design, or mockup that is no longer the current version. This often happens when review links, folders, screenshots, and email threads make it unclear which version needs attention.
How can design studios prevent clients reviewing the wrong version?
Design studios can reduce wrong-version feedback by making the current version obvious, keeping older versions as history, and collecting feedback in one review workflow instead of across email, Drive, chat, and screenshots.
Is Google Drive enough for design approval?
Google Drive is useful for storing design files, but it does not manage the approval workflow around those files. A design approval workflow needs current version clarity, feedback in context, approve or request changes actions, and approval history.
What is a design approval workflow?
A design approval workflow is the process a studio uses to send a design version to a client, collect feedback, handle requested changes, and record approval. A good workflow keeps every comment connected to the right version.
Does SignOffly replace design tools or project management tools?
No. SignOffly is designed as a client-facing approval layer. Studios can keep using their design and internal project tools while giving clients a simpler place to review the current version, comment, request changes, or approve.