Indoor selection checklist
- Ceiling and mounting
- Power, dimensions and cut-out
- Beam, output and glare
- CCT, CRI and controls
- Required files and delivery window
Resources / procurement evidence
Use these on-page checklists to prepare a better RFQ and read evidence labels correctly. No download or certificate library is implied where a real file has not been published.
Capability or requirement is discussed at project level before any model, finish or document claim is published.

Four practical checklists
These are live page references, not links to nonexistent documents.
Evidence-state glossary
None of the three labels is an automatic certification, approval or whole-project claim.
Product family and image are traceable to a supplier catalogue; project configuration still requires review.
Capability or requirement is discussed at project level before any model, finish or document claim is published.
A named application or file scope has been reviewed; model-level documents and project fit are confirmed per RFQ.
Document purpose map
Always match the document to its owner, exact model or version, scope, date and current review status.
| Document | Primary use | Owner to identify |
|---|---|---|
| Datasheet | Published model and configuration fields | Partner or named product owner |
| Drawing | Dimensions, mounting and version definition | Partner or engineering owner |
| Photometric file | Optical calculation for the exact version | Named model data owner |
| Test report | Test method, sample and measured scope | Actual laboratory or issuing body |
| Certificate | Standard and product scope declared by the issuer | Actual issuer and certificate holder |
| Sample record | Reviewed model, configuration and finish version | Buyer, Topeng and partner by agreed scope |
| Packing record | Packing marks, quantities and release condition | Named order and logistics parties |
Document 1
Document 2
Document 3
Document 4
Document 5
Document 6
Document 7
FAQ / evidence boundary
These answers separate public evidence from the configuration and file checks completed for a live project.
Catalogue source traces a product family and published data. Scope reviewed refers to a named application or file scope, not automatic model approval.
Check the issuer, holder, standard, covered model and version, date and stated scope.
It remains marked for project confirmation instead of being estimated or promoted as evidence.