What is controlled document management?

A controlled document is one you can prove things about

Most documents only have to be findable. A controlled document has to answer questions about itself: which version is in force right now, who approved it and when, what they were looking at when they approved it, and who has been told it changed.

That is the whole distinction. Storage systems answer "where is it". A document control system answers "is this the one I should be following, and can you show me why".

The four properties that make control real

Identity — the document has a number and a title that do not change when its content does, so a reference from a procedure or a training record still resolves years later.

Version integrity — a revision produces a new version rather than editing the existing one. If an approved version can be altered in place, no approval means anything afterwards, because you can no longer say what was approved.

Attributable approval — approval is recorded as an act by a named person against a specific version, not as a status field somebody set.

A history you did not write afterwards — the record of what happened is produced as it happens. A history assembled for an audit is a reconstruction, and reconstructions are exactly what auditors are trained to probe.

Why a shared drive keeps failing at this

A shared drive can be organized well. What it cannot do is refuse. Nothing stops a file being edited after approval, nothing marks a superseded copy as superseded once it has been downloaded, and nothing records that a change happened except a modified-date that any save will overwrite.

The usual response is procedure: naming conventions, a controlled-copies register, a rule that only one person edits. These work exactly as long as everybody follows them, and the failure is silent when somebody does not.

What to look for

Ask what the system physically prevents rather than what it displays. Can an approved version be edited? Can the history be edited? Can a superseded version be mistaken for the current one? Can you show, without exporting to a spreadsheet, which version a signature applies to?

A system that answers those with "it is configured not to" is describing a policy. A system that answers with "it cannot" is describing a control.