Simplification · Traceability
Two hundred documents can become twenty without a single requirement ceasing to be covered. On one condition, and it is a complete one: being able to show, for each of the one hundred and eighty withdrawn, what it contained, where that content now lives, who decided and on what grounds.
Withdrawn ≠ erased
Document control requires superseded versions to be removed from points of use and retained in archive. A document taken off the workstation remains consultable. These are two distinct obligations, and they do not conflict.
That distinction dissolves most of the anxiety. Nobody is asking you to keep in force what no longer serves; you are asked to know what existed, and until when. A lighter, properly archived document set satisfies the requirement better than a sprawling one in which nobody can guarantee that no obsolete version is still circulating at the workstation.
The belief that costs you
"If someone wrote it one day, there must have been a reason."
Probably — and that is exactly the question to settle. In a document set that has aged, a notable share of documents answers a requirement that has gone, equipment that has been dismantled, or an audit observation closed ten years ago. The reason existed; it no longer does. Not daring to check means keeping in force texts nobody can any longer attach to anything — and in front of an inspector, that inability is a weakness, not a protection.
The method
A photograph of the document set before you start: full inventory, versions in force, last review dates, consultation rates. It is the reference everything afterwards is compared with. Without it no demonstration is possible — and it cannot be reconstructed later.
For each applicable requirement, the document or documents covering it, before and after. This is the centrepiece: it proves no requirement has been orphaned. It also reveals, nearly always, two or three requirements the original set did not cover — the exercise improves compliance, it does not merely lighten it.
Merged into which document, withdrawn on what grounds, replaced by what. One line is enough, but it must exist for every one. That register is what turns a clean-up into an act of quality management — and it reads in ten minutes in the room.
Impact assessment, approval at the right level, update of the associated qualifications, archiving of withdrawn versions. Nothing exotic: the loop you already have, applied to a documentation operation. That is where the line runs between simplifying and deviating.
Our conviction
A well-kept simplification file is one of the best interview topics a site can offer: it shows an organisation that knows its document set, knows what it covers and why, and decides rather than accumulates. Explaining is part of the file — and it is that, far more than volume, which builds confidence.
What you gain
Review
Periodic review workload is proportional to the number of documents in force. Halving the set halves an annual burden that falls on the same people every year.
Coherence
Fewer texts means fewer chances that they contradict each other. A contradiction between two documents in force is one of the hardest findings to explain away in the room.
Deviations
On the sites we support, the share of deviations of documentary origin falls markedly — the most tangible effect, and one you read in your own indicators.
So the programme does not start with rewriting, but with measurement: the dated baseline is both the first item in the file and the best argument for launching the rest.
Frequently asked
Two days on an export of your document system is enough to produce the dated baseline — the first item in the file, and often the most convincing.
