Use Cases

This page maps Track Changes to common workflows, and shows how it plays well with other features.

Use case 1: Review → finalize (solo or team)

Best for documents that require an audit-ready review process (contracts, policies, specs).

Suggested flow:

1. Enable tracking (revision.defaultEnabled: true or toggle it in the panel)
2. Review in final-markup (final view with marks visible)
3. Accept/reject changes (per-change or all) to finalize
4. Export/share the finalized version

Use case 2: Collaborative review (with comments)

Track Changes records what changed; Comments capture why it changed.

Recommended approach:

• Use Track Changes for edits and accountability (filter by author when reviewing)
• Use Comments threads to discuss and resolve decisions
• Use the Review panel as a unified “review stream” (changes + comments) to finish review in one place

Use case 3: Milestones + fine-grained review (with version history)

For collaboration projects with approvals and checkpoints:

• Versions are your named milestones (snapshots you can revert to)
• Revisions are the day-to-day review layer between milestones

Suggested flow:

1. Create a version at the start of a milestone
2. Track changes during the milestone, review and finalize
3. Create a “milestone accepted” version after finalization

Use case 4: Templates + protection (with content locking)

For “template author → form filler” workflows:

• Locking protects the template structure
• Track Changes records maintenance edits and helps you finalize before publishing

Use case 5: AI draft → human edit (with AI features)

When AI generates a first draft and a human team must refine it:

• generate a draft with AI
• enable Track Changes for human edits to keep review transparent
• accept/reject to finalize before exporting

Use case 6: Legal and compliance review

For review workflows that require audit trails and accountability:

• enable Track Changes to capture all edits
• use comment threads to record decisions and risks
• accept/reject to produce a compliant final copy

Use case 7: Cross-team delivery (pre-sales proposals / project reports)

• sales, product, and delivery teams edit their own sections
• review by filtering changes by author/role
• create milestone versions and export for external delivery

Use case 8: Long-term template maintenance (policies / contract clause iterations)

• enable Track Changes during maintenance so every change is traceable
• lock key clauses; unlock only when a change needs to go through review and finalization
• use versions to record each template release milestone

Use case 9: Teaching and coaching review

• students submit documents; instructors edit with Track Changes
• use comments to explain the reasoning and standards
• export PDF/images as feedback materials after finalization

Use case 10: Pre-release freeze and external publishing

• enable Track Changes to converge last-minute edits
• lock key paragraphs after finalization to prevent accidental edits
• create a “release version” and export the external copy

Working with other features

Collaboration

• In collaboration mode, revision marks sync to all connected users.
• Set options.user on each client to keep authorship accurate.

Comments

Use Comments for discussion and decisions, then apply the actual edits under Track Changes and finalize via accept/reject.

Version History

Use versions for milestones; use Track Changes for review between milestones.

Export

If you need a clean final export (no revision marks), finalize first (accept/reject) and then export.

Content Locking

• Lock key clauses after finalization to prevent accidental edits during collaboration: Content Locking

Import

• Import legacy documents, then enable Track Changes and finalize via your review workflow: Import