Clover

The approval problem

Where did the client sign off on this?

Somewhere between the shared folder, the thread and the call, a decision was made. Six weeks later nobody can point at it. Clover is the fix for that, and only that.

See how it works
01 — Today: six tools, no recordWhere sign-off actually happens
Email chain, 14 replies
Slack DM, no context
Drive folder, v2_final
PDF markup, unversioned
A call nobody minuted
And the actual decision?

The fix

One path, start to signed

Every proof enters the same flow. The client sees one decision at a time; your team sees the whole chain.

Upload
→
Review
Approve
→
Logged
Logo lockup — v3SHARED 2 DAYS AGO
Proof artwork
ApproveRequest change

Three things the screen guarantees

Version history

v1 through v3 stay reachable, with what changed between them.

Comments pinned in place

Feedback sits on the artwork, at the spot it refers to.

A sign-off stamp

Name, role, version and timestamp — exportable as a PDF record.

Every decision timestamped

The audit log is the project's memory. Filter by person, phase or file and read back exactly what was agreed.

Change requested — Packaging v2J. Park · 11:20
Shared — Brand guide draftStudio · 09:41
Client view

2 items need your decision

Studio view

2 client decisions pending · 5 internal drafts · 3 unbilled hours

Clients never see your backstage

The same project renders differently by role. Drafts, margins and internal chatter stay on your side of the wall.

Jonah Park — Partner, Park Studio

“We used to reconstruct decisions from memory. Now the project tells us who approved what, and we move on.”

Stop chasing sign-off

Walk through Clover with your own project. Twenty minutes, no slides.

Book a walkthrough