Upload a fix to delivered work,
without changing what your client sees.

Delivered and approved

On the project’s Deliverables tab, both deliverables are delivered, approved at v1: “Delivered · Approved v1”.

Upload the fix as a new version

Fix the file, and add it to the same asset as a new version. Open the asset, and in Files & versions click Add file. New version is already selected, and the destination reads Original, V2.

Choose the corrected file and click Add as V2. V2 is now the current version in your library. For more on versions, see Keep file revisions together with version history.

Delivered work stays as it was

Back in the project, the front label is still Delivered, approved at v1. The row shows that v2 was uploaded, “Approved v1 · v2 uploaded”, and marks it Needs re-review.

Open it. The banner reads “A newer version was never reviewed — return to work to review it”. The file your client received is still the one shown here, with “2 versions in the library”.

Return it to work

To send the fix, return the label to work. This needs the project review permission. Click Return to work. The confirmation says the file stays visible in the client portal, marked as being revised. Click Return to work again.

Your client isn’t emailed about it. The front label is back in production, and the banner reads “Approved v1 · new version needs re-review”.

What your client sees meanwhile

In your client’s portal, nothing has changed. The delivered front label is still v1, with the typo. It’s only marked Being revised by the studio.

Send the fix in the next review

Back in the studio, click Prepare client review. The key visual stays out: “Already accepted — return it to work to review a new version.” The front label goes in with v2.

Add a short note for your client, here “Fixed the typo in the headline.”, and click Start review & email clients. Review 2 is open, and your client gets an email with the link. The same steps are in Send a revised version back for approval.

Your client sees the fix

Only now does your client see the fix. In Review 2, the front label is marked v2 · revised, and the portal says “Previous version was approved”.

Until they approve it, the label waits in the review, and their delivered files hold only the key visual. Their side of the decision is in Approve work, or send it back with changes.

Good to know

• New version. Uploading a new version never changes delivered work or what your client sees in the portal.
• Return to work. It needs the project review permission and sends no email. See Mark a deliverable as done, and know who can undo it.
• Next review. Your client sees the fix only when you start the next review.

For the whole revision cycle from both sides, see How revisions work, for your team and your client.

In short: upload the fix as a new version, return the deliverable to work, and send it in the next review. Until then, your client keeps the version they approved.