Request outdoor-lighting documents with identity and scope attached.
Conformity attestations, test reports and certificates are useful only when you keep their document type, number, date, named model or sample scope, and the destination question they were issued against.
Use this list for every proposed configuration.
| Request field | Why it stays with the file |
|---|---|
| Document type | Distinguish a test report, conformity attestation, certificate or another record rather than relabelling it. |
| Identifier and date | Record the number, issue date, issuer or laboratory and file revision supplied. |
| Named subject | Ask which model, configuration, component or submitted sample the file identifies. |
| Stated scope | Retain limitations, sample language, requested-test scope and any exclusions. |
| Project relevance | State destination, intended use and the open question the project needs the file to answer. |
Each document and the model it names.
The public document register identifies each EMC, electrical-safety and restricted-substances record by its own type and named scope. A management-system certificate image is not presented as independently registry-verified.
- Keep source wordingPreserve the issuer, holder and stated model or sample relationship.
- Keep limitationsA tested sample or selected component does not silently become every configuration.
- Match destinationAsk the project team to check the relevant market and purchase description.
- Keep unknowns openDo not infer that a requested file exists or applies until it is supplied and reviewed.
File, configuration and destination, read together.
Check current management-system validity, any required market approval and the document match for your requested model. Product and company records have different scopes; review the exact file against your project before relying on it.
- Document registerReview the public scope notes and supplied record types.
- Requirements reviewKeep each requirement, evidence reference and open question in an editable review.
- Sample approvalCarry the named configuration into a sample record.
- General RFQAttach document questions to the project brief.
Send the model, destination and purpose of the request.
State the proposed configuration if known, the destination, the document type requested and the exact decision the project needs to make.