Getting the sign-off
“Fine by me” in a thread, or one click on the delivery itself.
Both leave a written answer from the client. colis attaches it to the file it answers, keeps a single answer per parcel, and makes it readable by a script.
Sign-off by email
In its own terms.
Send the work, then wait for the client to reply “approved” or list the changes by email. Everyone knows how, and the reply is in writing.
Side by side
Where they part ways.
| colis | Sign-off by email | |
|---|---|---|
| Where the file lives | Your bucket: S3, R2, MinIO, Scaleway, Wasabi | Wherever the file was sent |
| Knowing it was opened | Sent, opened, approved or changes, each with its time | None |
| The client’s answer | Approve, or ask for changes with a comment, from the pickup page. Once, for good | Free text, in a thread |
| Starting an automation | A signed webhook at every step, and an n8n node | Reading the email, by hand or with parsing |
| Large files | Straight from the browser to the bucket in parts, resumable; 2 GB by default | Depends on how the file was sent |
| What the client needs | Nothing: a code or a link | An email address |
| When it goes away | When you say: ten minutes to your maximum, or at the first download | None |
The differences
What actually changes.
Tied to one file
The verdict belongs to one parcel, under its code. There is no guessing which attachment, which link or which version a reply was about.
Once, for good
A client answers a parcel once, and the answer is never overwritten. A new version is a new parcel, with its own answer.
Readable by a machine
colis statut prints the state on its first line and --json the whole receipt. A webhook carries it the moment it is given, with the comment for changes.
The decision
Pick the one that fits.
Keep sign-off by email when
- The approval needs a discussion rather than a yes or no
- The client prefers to answer in their own words, in their own mailbox
Pick colis when
- You want a yes or a list of changes, attached to the version it answers
- The approval should start the next step on its own
- You want the time of opening and of answering on record
More comparisons
The other ways.
Send it. They sign off. You know.
Your storage, a delivery page under your name, a webhook at every step. Nothing hosted by someone else.