Version control

What version control actually provides#

Three things, and organisations usually implement the first and stop.

A history. Each revision is retained rather than overwritten, so nothing is lost when a document is updated.

An unambiguous current version. More important than the history and more often missing. If a reader cannot tell at a glance which version is in force, the history has not helped them.

Retained supersession. Old versions are labelled as superseded and kept, because the question in any investigation is which version was in force at the time — not what the document says now.

Why deleting old versions is a mistake#

It looks like housekeeping and it is the removal of evidence. A retained version limit — common on file platforms, often set by default and rarely reviewed — silently discards the revision that someone will eventually need. Storage is cheap relative to the cost of explaining an absence.

Check-out and check-in#

Checking a document out locks it for editing and shows who holds it. It is the mechanism that prevents two people producing conflicting versions of the same document, which is how organisations end up with two files that both look authoritative.

Check-out and real-time co-authoring are different models and cannot both apply to one document. Collaborative drafting suits co-authoring; controlled records suit check-out.

The failure this prevents#

Work performed against a superseded document. On a construction site it means building to an old drawing; in manufacturing it means an operator following a retired work instruction; in a legal practice it means an agreement signed with a clause the firm retired. All three trace back to a reader being unable to tell which version was current.