Version history

Save a numbered version before large AI rewrites, structural reorganisations, or pasting in content from another pack. Those moments have the highest regret rate. A cheap checkpoint beats reconstructing memory.

Also checkpoint after closing a major comment cycle or before starting an approval workflow. That creates a clean “submitted” state. If reviewers request changes, you can compare against the submitted version without ambiguity.

For recurring deliverables — monthly reports, renewal MSAs — keep milestone versions that reflect “customer-approved” or “board-sent.” Restoring then becomes a deliberate rollback to a known external commitment, not just undoing a typo.

Do not rely only on automatic saves if your process needs named meaning. Numbered history is most useful when humans understand what a version represented. Add a short mental or written label in your team’s ritual (“v12 = post-legal”).

Approvers should review diffs, not vibes. Version compare shows what moved since the last gate. Pair that with unresolved comment checks so process and content stay aligned.

Audit-minded organisations benefit when version history sits next to the platform audit trail for AI calls. Versions explain human edits; the usage ledger explains which AI tools ran and how many tokens they consumed. Together they reconstruct a month of work.

If a dispute arises about when a clause changed, version history is the document’s memory. Keep membership and roles intentional so only trusted editors can alter the chain of drafts that matter.

After restore, communicate in a comment thread: “Restored to v11 because the AI expand introduced unsupported claims.” That prevents teammates from re-applying the bad change.

Live collaboration without versions is brave to a fault. Presence reduces collisions; versions heal the ones that still happen. Comments explain why; versions capture what.

Signature requests and watermarked share links should generally point at a known version state. Do not sign a moving target. Freeze via process: resolve comments, save a version, then request signatures or share externally.

Design assets may change while the document version stays pinned. If a letterhead updates in Design Studio, note whether the document export needs a refresh. Version the document again after brand swaps that affect the pack.

Export remains free. Exporting does not replace versioning — it produces an artifact. Keep the living document’s history in Document Studio as the system of record.