The evidence types
Test reports record what happened in a furnace or a rig, on a specific specimen, on a specific date. Classification reports turn those results into a classification and, critically, state the field of application — the range of products the result may be applied to. Assessment and extended application reports extend that range by reasoning rather than by further testing.
Certificates record that a certification body has assessed a product, and usually a factory production control system, against a scheme. Declarations are the manufacturer's own formal statements. Installation and maintenance instructions define the conditions under which the tested performance can be expected in a real building. Every one of these is evidence, and every one has its own scope and its own dates.
The relationships matter more than the documents
A single document rarely tells you anything on its own. A test report without the classification report does not give you a classification. A classification report without the configuration it applies to does not tell you which of your products it covers. A certificate without its scope schedule does not tell you which products are listed under it.
The unit of control is therefore not the document but the link: this claim, supported by this evidence, for this configuration, in this version, between these dates. Once those links exist, the questions that used to take a week — which products are affected if this report is withdrawn? — become lookups.
The gaps that cause trouble
Evidence that has expired or been superseded while claims still rely on it. Claims with no traceable supporting evidence at all, usually inherited and usually old. Configurations that have drifted from the tested assembly through a substituted hinge or a changed closer. Instructions that describe a previous revision of the product.
None of these is exotic. All of them are ordinary consequences of managing evidence in folders and spreadsheets over a decade, with staff turnover in the middle. They are found by structure, not by diligence.
What to fix first
Start with the claims you actually make in the market, not with the document library. For each claim, find the evidence that supports it and write the link down. The claims you cannot trace are the ones that need technical review, and they are usually a small and identifiable set.
Then attach dates. Expiry and review dates on evidence are what turn a static record into something that tells you when it needs attention, rather than waiting for a customer to ask.