REVISION TRACKING
Revision tracking for client designs
Designers track client revisions by giving every upload its own version, leaving comments on that version, and recording approval only for the file the client accepted. ApproveLoop does that for still images. The next upload does not erase the previous one, and an approval does not move.
ApproveLoop does not compare two files automatically, and an approval is a project record, not a legal signature. Uploads are PNG, JPEG, or WebP.
Free plan: $0. One active project, no credit card.
Slim this pergola, and add more lavender along the edge.
EXAMPLE
Two versions of the same courtyard
Fictional project, shown to illustrate versions. Not a customer’s work.
Client Soften the planting along this wall, and warm the pergola.

How should designers track client revisions and know which version is approved?
Give every upload its own version, leave comments on the version the client was looking at, and record approval only for the file they accepted. In ApproveLoop each PNG, JPEG, or WebP upload is a new version. Earlier comments stay where they were. An approval stores the person’s name, the version number, and the time, and it does not move to a later upload.
A revision, without losing the previous file
The history shows which file the client saw, what they asked for, and what they accepted.
-
01
Upload the first version
Upload a PNG, JPEG, or WebP image. That file is version 1. You can note the fee and how many revision rounds are included.
-
02
Collect comments on that version
The client pins comments on that image and submits them. Those comments stay on version 1. The submission counts as one revision round.
-
03
Upload the next version, or record the approval
Upload the changed image as the next version. When the client approves, ApproveLoop stores their name, the version number, and the time on that file.
Comments stay on the version they belong to
A comment is a numbered pin on the version that was open. It does not migrate when you upload the next image. You can reply in that thread, then upload the revision as a new version.
Approval stays on the accepted file
Each upload is a new version. Comments belong to the version the client was looking at. An approval does not move to a later upload. The record shows who approved which version and when. It does not replace your contract.
What gets a version
Track versions of PNG, JPEG, and WebP still images. ApproveLoop does not compare files automatically, and it does not version PDFs, video, native design files, or a live website.
Included
- A numbered version for each upload
- Comments that stay on that version
- Approval stored as name, version, and time
Not included
- Automatic comparison of two files
- PDF, video, and native design-file versions
- A legal signature or a payment
Use it when email loses track of which file was approved. It fits architectural drawings, interior concepts, and other still images you already export for review.
Questions about revision tracking
How do I know which version is approved?
Open the version history. An approval names the person, the version number, and the time. It stays on that version.
Does an approval carry forward?
No. If the image changes, upload a new version and ask the client to review it. The earlier approval does not move.
What if I need to replace a file?
Upload another version. The previous file, its comments, and any approval stay in the history.
Can I see comments from an earlier round?
Yes. Open the earlier version. The pins from that round are still on that image.
Related
Keep the next revision attached to its file
One active project, with each upload kept as its own version and the approval stored on the file your client accepted.
Start my free projectFree plan: $0. One active project, no credit card.
