Ask what the document actually covers
A test report, declaration or certificate should identify the applicant or manufacturer, sample or model, standard or method, date and conclusion. A component report cannot automatically establish compliance of a finished device, and a family certificate should not be assumed to cover an unlisted configuration.
Build the file in three layers
Organizing evidence by layer makes gaps easier to see and prevents marketing language from replacing engineering review.
- Company layer: legal registration and supplier identity
- Component layer: datasheets, drawings, material or substance test reports
- Finished-device layer: risk, electrical, optical, thermal, EMC, software and market-specific evidence as applicable
Match the evidence to the target market
Product classification, intended use, claims, power source, wireless functions and sales territory affect the documentation route. Define these before quotations are compared so that suppliers are pricing the same scope.
Use a model-level document index
Create one index for the exact quoted configuration. Record document number, revision, model coverage, issuer, date and open items. This is more useful than a page of certification logos because procurement and engineering can verify each item.