Document control is not filing

Document control is widely treated as an administrative function — somewhere between filing and reception. This is a category error, and an expensive one.

The purpose of the discipline is not to store documents. It is to make it possible, at any future point, to establish what was issued, to whom, when, and what was in force at the time. That is evidence management, and it is closer to what a court reporter does than to what an office administrator does.

The four habits that matter

Across projects that handle this well, the same practices recur, and none of them require expensive software to begin:

• Number consistently, from day one. A convention that survives three years and four changes of personnel is worth more than a clever one that only its author understands.
• Record distribution, not just issue. Who received a document, and when, is the fact most often in dispute and the one least often captured.
• Never overwrite a revision. Superseded documents are not clutter. They are the answer to what was in force on the date the work was built.
• Capture email against the project. The most consequential correspondence on most projects is informal, and it lives in personal inboxes until somebody leaves.

What good looks like in practice

A useful test: how long does it take a new starter to find the current revision of a specific drawing, the transmittal that issued it, and the comments raised against it?

On a well-run project that is under a minute, because the register answers the question. On a badly run one it takes an afternoon and a phone call, because the answer lives in somebody’s memory of where things were put.

Why it is worth the argument

The cost of poor document control never appears as a line item. It shows up as rework against a superseded drawing, as a claim that cannot be substantiated, as the fortnight a commercial team spends reconstructing a paper trail before an adjudication.

Those costs are real and large, but because they are distributed across other budget lines, the function that would have prevented them is perpetually under-resourced. That is the argument worth having at the start of a project rather than the end.