Separate a document version from a different idea

A revision changes a document along an agreed path. An alternative explores a different path. Giving both the same version sequence can hide an important decision.

Before saving a copy, ask whether it replaces the current draft or offers another option. A corrected figure belongs to the revision history. A proposal with a different audience or structure may deserve a separate branch with its own name. Keep the original available until the team has chosen how to proceed.

Mark the relationship

Record a short note describing what changed and which file it relates to. Use the application's version history where it is suitable, but check what remains available after export or account changes. An automatically saved timestamp is not a complete explanation of an editorial decision.

Keep one clearly identified working version in the shared location. Archive superseded copies so they remain recoverable without appearing to be current. If several people edit simultaneously, agree on the collaboration method before circulating attachments.

When an alternative is accepted, record that choice and carry forward the relevant comments. Do not silently discard the other path if it contains unresolved questions. A useful version system lets someone understand both the current document and how it became current, without needing to reconstruct the team conversation from filenames.