Version history: using it for more than undoing mistakes

Most people meet version history once, in a panic, after overwriting something — and then never open it again. That is a narrow use of it. Recovering a previous draft is the emergency case; the everyday value is answering who changed this paragraph, when the figure in the summary stopped matching the table, and what the document looked like when somebody approved it.

What version history is good for

• Seeing who made a change, which settles most "I thought we agreed" conversations in seconds.
• Finding when something changed — usually more useful than who, because it locates the conversation that caused it.
• Recovering a section rather than the whole document: copy from an earlier version instead of rolling the file back.
• Showing what a document looked like at approval, which matters when somebody acted on that version.
• Noticing unexpected edits, which is a weak but real control on documents several people can reach.

What it is not

It is not a backup, and treating it as one is a common and expensive confusion. Version history lives inside the document — delete the document and the history goes with it, which is exactly why a separate copy still matters. It is also not an audit trail in the evidential sense: it records changes to content, not who read the file, and in most systems somebody with sufficient rights can remove the document entirely. Recovering from loss is a different problem with a different answer; this is about understanding a document that still exists.

Name the versions that matter. Most systems let you mark a version — "sent to client", "approved" — and a named point is worth more than fifty timestamps, because the timestamps all look alike a month later.

How long it is kept

1. Find out the actual retention for versions in the system you use, in days, rather than assuming it is unlimited.
2. Check whether the limit is by age or by number of versions — a heavily edited document can exhaust a count-based limit in a week.
3. Mark the versions that must survive, where naming them protects them from pruning.
4. Export anything that has to exist in a fixed form — a signed agreement is a file, not a version.
5. Write the retention figure where people ask about it, because the question always arrives urgently.

Reading a history quickly

Work backwards from the thing that is wrong rather than forwards from the beginning. Find the last version where the figure was right, take the next one, and you have both the change and the person. That takes under a minute and is the one technique that makes the feature genuinely useful on a normal day, as opposed to during an emergency.

Ettex Docs keeps version history per document with the author and timestamp, and restoring an earlier state is covered separately in the guide on recovering a document. Where the question is about a figure rather than a paragraph, the same approach applies to a sheet — find the last version that agreed with reality.