Check-in / check-out

The problem it solves#

Two people edit a document at the same time from separate copies. Both save. The organisation now holds two documents that both look authoritative, and reconciling them is manual, error-prone and usually incomplete.

Check-out prevents this by making the lock visible before work starts, which is the important part — a lock nobody can see is a lock that gets worked around.

Why it excludes co-authoring#

Check-out and real-time co-authoring are incompatible models rather than competing features. One assumes a single editor and produces a clean version series; the other assumes many editors and produces a continuously merged document with no discrete versions.

Controlled records need the first. Collaborative drafting needs the second. Most organisations need both, for different documents, which is why authoring often stays in a collaboration platform while the approved output moves into a document system.

Practical details worth getting right#

Show the lock in the listing rather than in a properties dialog. Allow an administrator to force a check-in when someone locks a document and goes on holiday — and log it when they do, because a forced check-in can discard work.

When to skip it#

For genuinely collaborative drafting where several people work simultaneously and no discrete version matters until the document is finished. Applying check-out there creates a queue and people work around it by emailing copies, which is the outcome it was meant to prevent.