Resources / procurement evidence

Procurement Answers & Evidence Definitions

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.

Pending confirmation

Capability or requirement is discussed at project level before any model, finish or document claim is published.

Illustrative technical lighting evidence desk with photometric diagrams, optics and measurement tools
Illustrative concept — not project evidence

Four practical checklists

Prepare the inputs before comparing supply options.

These are live page references, not links to nonexistent documents.

Indoor selection checklist

  • Ceiling and mounting
  • Power, dimensions and cut-out
  • Beam, output and glare
  • CCT, CRI and controls
  • Required files and delivery window

Outdoor GCC checklist

  • Application and site plan
  • Ambient temperature
  • Dust or coastal exposure
  • Ingress, surge and voltage
  • Optics, mounting and approvals

LED module RFQ checklist

  • Dimensions
  • Wattage
  • CCT
  • CRI
  • Driver
  • Thermal condition
  • Quantity

Model evidence checklist

  • Named model and version
  • Responsible partner
  • Document owner or issuer
  • Covered scope and date
  • Review status and missing fields

Evidence-state glossary

Labels describe different proof levels.

None of the three labels is an automatic certification, approval or whole-project claim.

Catalogue source

Product family and image are traceable to a supplier catalogue; project configuration still requires review.

Pending confirmation

Capability or requirement is discussed at project level before any model, finish or document claim is published.

Scope reviewed

A named application or file scope has been reviewed; model-level documents and project fit are confirmed per RFQ.

Document purpose map

Know what a file can and cannot support.

Always match the document to its owner, exact model or version, scope, date and current review status.

DocumentPrimary useOwner to identify
DatasheetPublished model and configuration fieldsPartner or named product owner
DrawingDimensions, mounting and version definitionPartner or engineering owner
Photometric fileOptical calculation for the exact versionNamed model data owner
Test reportTest method, sample and measured scopeActual laboratory or issuing body
CertificateStandard and product scope declared by the issuerActual issuer and certificate holder
Sample recordReviewed model, configuration and finish versionBuyer, Topeng and partner by agreed scope
Packing recordPacking marks, quantities and release conditionNamed order and logistics parties

Document 1

Datasheet

Primary use
Published model and configuration fields
Owner to identify
Partner or named product owner

Document 2

Drawing

Primary use
Dimensions, mounting and version definition
Owner to identify
Partner or engineering owner

Document 3

Photometric file

Primary use
Optical calculation for the exact version
Owner to identify
Named model data owner

Document 4

Test report

Primary use
Test method, sample and measured scope
Owner to identify
Actual laboratory or issuing body

Document 5

Certificate

Primary use
Standard and product scope declared by the issuer
Owner to identify
Actual issuer and certificate holder

Document 6

Sample record

Primary use
Reviewed model, configuration and finish version
Owner to identify
Buyer, Topeng and partner by agreed scope

Document 7

Packing record

Primary use
Packing marks, quantities and release condition
Owner to identify
Named order and logistics parties

FAQ / evidence boundary

Evidence interpretation FAQ

These answers separate public evidence from the configuration and file checks completed for a live project.

What is the difference between Catalogue source and Scope reviewed?

Catalogue source traces a product family and published data. Scope reviewed refers to a named application or file scope, not automatic model approval.

How can a certificate be matched to a product?

Check the issuer, holder, standard, covered model and version, date and stated scope.

What happens when a field is missing?

It remains marked for project confirmation instead of being estimated or promoted as evidence.

Next step / evidence question

Use the checklist, then send the gap you need closed.

Name the model, application, file type and approval question wherever possible. That keeps the answer tied to a verifiable scope.