Skip to content
Guide7 min read

Immutable Email Versions: Why Snapshots Beat “Latest Draft” Review

Review breaks when nobody knows which draft was approved. Immutable versions fix that with a frozen artifact and auditable history.

By The Memo Team

Last updated

Quick answer

An immutable email version is a frozen snapshot of compiled output at a point in time - review, approval, and export reference that snapshot so “approved” means a specific artifact, not whatever the editor shows today.

“Approved” without a version number is a story, not a record. Immutable versions turn approval into an object you can export, test, and defend later.

Snapshot vs live edit

Editors keep working on the latest canvas. Reviewers sign off on a numbered version. Export pulls from approved snapshots - see Create immutable versions.

Request changes without losing history

Requested changes create a new version upstream. You can always answer what changed between v2 and v3 because history is append-only.

Pair with preflight and export gates

Gates attach to the snapshot: preflight on compiled output, approval recorded, then export.

Frequently asked questions

Can I edit an approved version?
No - approved versions stay frozen. New edits become a new version requiring review.
How is this different from undo history?
Undo is for drafting. Versions are for collaboration and handoff with named decisions.
Do versions store HTML?
Versions capture the compiled artifact used for review and export - not a vague “saved draft” label.
What if only one person is on the team?
Still useful - future you is also a collaborator who forgot what “final v2” meant.