Send a revised version
back for approval.
Your client asked for changes, you’ve made the fix, and now it needs to go back to them for a new decision, with what they asked for still in view.
By the end, you’ll have added the fix as a new version of the same asset, started Review 2, and seen your client compare it with what they last reviewed and approve it.
Before you start
- A client review that came back with changes requested on at least one deliverable.
- The fixed file on your computer.
- Permission to manage client reviews (Owner or Project Manager by default).
Watch the walkthrough
Send a revised version back for approval.
Harbor and Pine's first client review is back. On the project's Overview, the Client review card shows how it ended: one asset approved, one change requested.
Under Needs attention, the front label is waiting for a new version. Click View feedback.
Maya wants the darker green from their brand guide. Her decision applies to the version she reviewed, v1.
The deliverable file is one asset in your library. Open it there.
The revision goes onto this same asset as a new version, not as a new file. That keeps its comments and its history together.
Click Add file. New version is already selected, and the destination reads Original, V2.
Choose the revised file, and click Add as V2.
V2 is at the top, marked Current. While the deliverable is in work, it follows the current version.
Once processing is done, the darker green is on screen.
Back on the project, the front label now has two versions in the library. Maya's decision stays with v1, which is marked as an earlier version.
Close it, and click Prepare client review.
The key visual was approved, so it's left out. An accepted deliverable has to go back to work before it can be reviewed again.
The front label is included with v2, and its last review reads Changes requested.
Check the deadline, and add a short note for Maya.
Click Start review and email clients. Review 2 opens, and Maya gets an email with the link.
The Client review card now reads Review 2, awaiting client. Nothing is approved until Maya decides.
Now, your client's side.
In the portal, Maya sees Review 2 with your note. The front label is marked v2, revised.
She opens it. Under Review, she can compare it with the previous version.
Previous means the version from her last review, here v1. Side by side, the darker green stands out.
The slider lays one version over the other. Drag it to see exactly what changed.
She closes the comparison and approves v2.
Back on the review, she clicks Finish review, checks the summary, and clicks Submit review.
Both assets are now in her delivered files.
Back in the studio.
Nothing needs attention anymore, and Review 2 ended with one approval. If Maya had asked for more changes, the same steps would bring her v3.
In short: add the fix as a new version of the same asset, then prepare a new client review. Your client compares it with what they last reviewed, and decides again.
Search across all videos and guides.
Fix it, version it, and ask again.
Harbor & Pine’s first client review is back: Maya Chen approved the key visual and asked for changes on the front label. Alex Morgan adds the fix as a new version of the same asset and sends it back in Review 2. Maya compares it with what she last reviewed and decides again.
Nothing is approved until your client decides. Their earlier decision stays with the version they reviewed. Sign in to YetOnePro and open a project whose last review asked for changes to follow along.
- 01
See what the client asked for
On the project’s Overview, the Client review card shows how the last review ended: Last review: Review 1, “1 approved · 1 change requested”.
Under Needs attention, the front label is waiting for a new version. Click View feedback: Maya wants the darker green from their brand guide, and “Decision applies to this reviewed version.”, v1.
- 02
Add the fix as a new version
The deliverable file is one asset in your library. Use its Open … in the library link. The revision goes onto this same asset as a new version, not as a new file, so its comments and history stay together.
In Files & versions, click Add file. New version is already selected, and the destination reads Original, V2. Choose the revised file and click Add as V2. For more on versions, see Keep file revisions together with version history.
- 03
V2 is current
V2 is at the top, marked Current. While the deliverable is in work, it follows the current version. Once processing is done, the fix is on screen.
To check the fix against v1 yourself before you send it, see Compare two image versions to see what changed. - 04
The decision stays with v1
Back on the project, the front label now has 2 versions in the library. Maya’s decision stays with v1, marked as an earlier version: the attached file has changed since that review.
- 05
Prepare the next review
Close the window and, on the Client review card, click Prepare client review.
The approved key visual is left out: “Already accepted — return it to work to review a new version.” The front label is included with v2, and its last review reads Changes requested. Check the Deadline, and add a short note under Message to client.
- 06
Start Review 2
Click Start review & email clients. Review 2 opens, and Maya gets an email with the link. The Client review card now reads Review 2 · Awaiting client. Nothing is approved until she decides.
- 07
Your client compares and decides
In the portal, Maya sees Review 2 with your note. The front label is marked v2 · revised. She opens it, and under Review clicks Compare with previous version.
Previous means the version from her last review, here v1, not necessarily the previous number. Side by side shows both; Slider lays one over the other, so she can drag to see exactly what changed.
- 08
Approve and submit
Maya closes the comparison and approves v2. On the review, she clicks Finish review, checks the summary and clicks Submit review. Both assets are now in her delivered files. Her side is in Review work your creative team sent you and Approve work, or send it back with changes.
- 09
Back in the studio
Nothing needs attention anymore, and Review 2 ended with one approval. If Maya had asked for more changes, the same steps would bring her v3.
Each change request opens a revision round. To see rounds against what you agreed with your client, see Track revision rounds against your agreed allowance.In short: add the fix as a new version of the same asset, then prepare a new client review. Your client compares it with what they last reviewed, and decides again. For the first review, see Send work to your client for approval.
Check the result
- You read the client’s feedback under Needs attention, with View feedback.
- You added the fix as a new version of the same asset, and it’s marked Current.
- You prepared the next review with the revised deliverable and a note.
- You started the review, and the Client review card reads Review 2, awaiting client.
If it didn’t work
An approved deliverable isn’t in the next review.
Accepted work is left out. It has to go back to work before a new version of it can be reviewed again.
Is the fixed version approved once I upload it?
No. Nothing is approved until your client decides in the new review. Their earlier decision stays with the version they reviewed.
Which version does my client compare against?
Previous is the version from their last review, which isn’t always the previous version number.
My client asks for more changes again.
Repeat the same steps: add the next version, then prepare and start another review.