A clear yes, tied to the exact file
No more reading between the lines of a long email to figure out whether the client approved the work. They tap approve or request a change right on the deliverable. Comments attach to the file they are about, and you get the decision the moment it is made.
homepage-v3.png
v3 · 4.2 MB
Love it, approving the final pack
Feedback that stays on the work
Approve or request changes
Two clear actions on every file. The client picks one, so you never have to guess whether 'looks good' meant ship it or keep going.
Comments on the file
Notes attach to the deliverable they are about, in a thread you can both follow. The feedback is not scattered across three messages anymore.
Approved on a version
An approval is pinned to the exact version it was given on. If you change something after, it is obvious which round was actually signed off.
You hear about it right away
When a client approves, comments, or asks for a revision, it surfaces for you immediately, so nothing waits in a portal you forgot to check.
End the 'is this approved?' guessing game
Vague feedback is where projects slip. When the client has to write a paragraph and you have to interpret it, rounds drag and scope blurs. A clear approve or request-changes on each file turns a fuzzy conversation into a decision you can act on, and a record you can point back to.
- One decision per file, not a paragraph to decode
- Revisions come with the note attached to the file
- A record of who approved what, and when
Recent decisions
homepage-v3.png
Approvedlogo-suite.ai
Changesbrand-guidelines.pdf
ApprovedA timeline of what actually happened
Every project keeps an activity record: when the client opened a file, when they commented, when they approved, and when an invoice was viewed. If a question comes up later about what was agreed, the answer is in the timeline rather than in someone's memory.
- See when a file was opened, not just whether it was
- Approvals, comments, and revisions all on one timeline
- A neutral record both you and the client can rely on
Opened brand-guidelines.pdf
May 30Commented on logo-suite.ai
May 30Approved homepage-v3.png
May 31ApprovedQuestions about approvals
They open the deliverable in the portal and tap approve or request changes. It is two clear actions, so the decision is unambiguous and you see it straight away.
Yes. They can comment on a file in a thread tied to that deliverable, so the note stays attached to the work it is about instead of getting lost in chat or email.
An approval is recorded against the exact version it was given on. When you upload a new round, it is clear which version the client actually signed off, so a later change does not quietly carry the old approval.
Yes. Approvals, comments, and revision requests surface for you as they happen, so you are not refreshing the portal to find out whether the client looked at the work.
Yes. Each project keeps an activity timeline showing when files were opened, commented on, approved, and when invoices were viewed. It is a neutral record both sides can refer back to.
No. They act on the work from the portal link. There is no separate account to create and nothing to install.