// Learn

Client approval workflows that don't live in email

·7 min read·approval · workflow

Why "approved via reply-all email" loses tracks of which version got the green light, and how to move approval into a single URL with a clear paper trail.

In this guide

  1. Why email approval breaks (real examples)
  2. The four states every approval workflow needs
  3. Approving files vs approving projects
  4. Notifications without spam
  5. The paper trail problem (and how to solve it)
This article is part of the SaveITT design-workflow guides. The full article is being written — the outline below shows what it will cover. When the body lands, it will sit here in normal prose paragraphs, with H2 section headings derived from the outline. For now this paragraph plus the outline gives crawlers enough structure to begin indexing the URL.
Related to this guide
See every SaveITT feature that supports this workflow →

Keep reading

Auto-versioning explained: stop renaming files _v3_FINAL_v2
Why filename-based versioning collapses on any active project, and how automatic versioning by filename fixes it without forcing designers to change how they save files.
Sending large design files to clients without WeTransfer
Permanent share links, version history, and a single project URL the client can return to — the alternative to firing off a fresh WeTransfer every revision round.
Try SaveITT free

3 projects, 5 GB, no credit card.

Start free →