Commercial lighting documentation should start with the claim, not a generic product packet. Ask for the record that supports the specific lighting product claim, then match its model, variant, configuration, method, revision, and stated conditions to the project. If a safety, compatibility, environmental, design, program, or authority question remains unresolved, hold approval and route it to the responsible project reviewer.
Match Commercial Lighting Documentation to the Claim First
Name the claim before requesting records. The matrix below turns the main lighting product claims into model-specific requests and keeps marketing language separate from records used in review.
| Claim | Document or record to request | Exact checks | Reviewer who may be needed |
|---|---|---|---|
| Safety listing or certification | Current certification or listing record from the issuing organization | Identify the NRTL, registered mark, applicable recognized standard, exact model or file number, complete-product scope, and any configuration limits. OSHA's criteria for a properly certified product include the NRTL's registered mark, recognized standard, and product coverage, so a logo or product-page phrase alone is not enough. | Supplier first; designated electrical professional, engineer, or authority if the project requires an acceptance decision |
| DLC or utility eligibility | Current DLC Qualified Products List entry and any applicable utility-program record | Match manufacturer, model, status, qualification date, requirements version, voltage, controls, and relevant performance fields. The DLC Qualified Products List supports a program-specific check, not a safety certification or automatic rebate approval. | Supplier and utility or program administrator |
| Photometric performance | Applicable IES file and, when measured performance matters, the underlying LM-79 test report | Match the tested luminaire configuration, electrical settings, operating position, conditions, revision, and limitations. Photometric data can support calculations, but it does not by itself establish listing, environmental suitability, or project approval. | Lighting designer, engineer, or other designated design reviewer |
| Electrical and controls compatibility | Specification sheet, compatibility statement, control or sensor documentation, and project electrical requirements | Match voltage, wattage, controls, sensors, mounting configuration, load-related information supplied for the project, and selected options. Do not treat a generic voltage or controls statement as confirmation for a different configuration or site. | Supplier for product details; electrician or electrical professional for project application |
| Environmental or enclosure suitability | Model-specific environmental rating evidence and technical documentation | Identify the rated enclosure or covered parts, test basis, stated conditions, and proposed exposure. An IP phrase needs to be matched to the conditions; it is not automatically a blanket wet-location or project-suitability conclusion. | Supplier, designer, engineer, electrician, or authority, depending on the project question |
| Project-specific approval | Project specification, submittal requirements, owner criteria, utility conditions, and authority requirements | List the acceptance conditions separately from product evidence. Determine which documents, formats, dates, calculations, and reviewer signoffs the project actually requires. | Owner, designer, engineer, utility, general contractor, or authority named by the project |
The claim-first approach is the core of commercial lighting documentation: tie each request to a decision, and have the supplier identify the record and scope that address it.
Separate What Each Lighting Document Can and Cannot Establish
Each document answers a different question. Use the product page to identify what is being offered, then use technical and issuing-organization records for the particular claim under review.
Product Page Versus Specification Sheet
A product page is a starting point for seller-stated features, options, and identifiers. It can help you identify the model and the claims that need follow-up, but it is not automatically a certification record, test result, or project approval.
A specification sheet organizes electrical, optical, mechanical, and operating information for comparison. Use it to compare the selected variant, but match its revision and identifiers to the item being submitted. Neither document replaces an issuing organization's certification record or a project requirement.
Photometric File Versus Test Report
An IES file is a photometric data file that can support lighting calculations when it corresponds to the tested luminaire configuration. An LM-79 test report records measurements taken under stated methods and conditions. The LM-79 measurement procedures cover reproducible photometric and electrical measurements, but measured data is not automatically a certification or listing decision.
Request both pieces when measured performance matters: the usable file for modeling and the report or test evidence that supplies the testing context. Neither item independently establishes environmental suitability or project acceptance. If the project needs an electrician-facing record package, see these photometric data needs.
Certification, Environmental Evidence, and Project Requirement
A certification or listing record identifies an issuing organization, product scope, and status. For an environmental claim, the ANSI/IEC 60529 IP Code scope concerns defined enclosure protection, including protection related to hazardous-part access, solid-object ingress, and harmful water ingress. The covered parts and conditions still need confirmation.
A project requirement comes from the owner, designer, specification, utility, authority, or another acceptance source. It is a condition the product must meet, not proof that the product meets it. Keep certification, program qualification, environmental evidence, and project acceptance as separate checks.
Verify the Exact Model Against the Project Conditions
A document applies only when its identity and scope match the product you are reviewing. Compare the ordered configuration with every submitted file and official record; a family name or similar-looking model is not enough when options can change the evidence.
Check the Product Identity
Use this short identity check across the specification sheet, photometric file, test report, certification or listing record, environmental evidence, and supplier response:
- Record the exact SKU or model number, including the file or product identifier used by the issuing organization.
- Match the variant and selected options, including wattage, voltage, and CCT setting.
- Match controls, sensors, mounting, and enclosure configuration.
- Compare revision or date information where the document provides it, and note exclusions or configuration limits.
- Treat a family-only record, missing identifier, component-only result, or conflicting value as an unresolved gap.
Use UL Solutions Product iQ as a search starting point, then read whether the result covers the complete product or only a component. The search helps locate a record; it does not by itself confirm that the ordered configuration carries the claimed status.
Check the Project Condition
Ask the responsible project reviewer to confirm the conditions that the product evidence must satisfy:
- What electrical and control requirements apply to the proposed application?
- Where will the equipment be mounted, and what environmental exposure is relevant?
- What photometric or design criteria must the calculation or submittal address?
- Are there utility or program conditions beyond the product's current program record?
- What do the specification, owner, submittal package, and authority require for acceptance?
An official record can establish its own stated scope without establishing that the project accepts the product. For example, a QPL entry may identify model and configuration fields, while the utility or project may apply separate eligibility conditions. Likewise, an IP record must be compared with the actual location and exposure. Missing project conditions, outdated records, unclear scope, or conflicting values mean the claim is not ready for acceptance.
Know When Supplier or Professional Review Is Required
Route each open question to the project-designated reviewer who owns that decision, rather than asking one document to answer every technical or approval issue. Pause approval when a consequential safety, compatibility, design, environmental, program, or authority question has no confirmed owner or answer.
Ask the supplier to resolve product-identity questions such as missing model identifiers, document scope, revisions, exclusions, variant differences, or contradictory values. The supplier should identify the record and limitations for each unresolved product question.
If the unresolved question concerns design performance, ask the project-designated lighting designer, engineer, or other design reviewer to interpret photometric assumptions, calculations, design criteria, or specification language. An IES file can provide modeling input, but the designated project reviewer decides how it fits the design requirement.
For voltage, controls, sensors, mounting, load-related, or site-condition questions, use the electrician or other electrical professional designated for the project. This article does not replace that professional's review and does not authorize installation.
For program eligibility, contact the utility or program administrator named by the project. Route owner, submittal, and acceptance questions to the owner, general contractor, engineer, or authority identified in the project documents. If no role is assigned, ask the project team to name the responsible reviewer before proceeding.
Send the Request, Then Accept, Verify, or Escalate
Copy this model-specific request into an email and replace the brackets with the project details:
- Product identity: Please confirm the exact SKU or model, variant, and selected wattage, CCT, voltage, controls, sensors, mounting, and enclosure configuration: [insert details].
- Claims under review: Please address these specific claims: [safety listing or certification, DLC or utility eligibility, photometric performance, electrical or controls compatibility, environmental suitability, or project approval].
- Applicable documents: Please provide the current specification sheet, applicable photometric file, relevant test report, current certification or listing record, environmental evidence, and compatibility information as applicable to this configuration.
- Record details: For each document, identify the issuing or testing organization, record or report identifier, revision or date, product scope, tested or stated conditions, and exclusions.
- Project conditions: Please map the evidence to the project voltage, controls, mounting location, exposure, lighting criteria, utility rules, and submittal or owner requirements: [insert requirements].
- Claim-to-evidence statement: Please state which document supports each claim, whether it covers the complete product and selected configuration, and what remains unconfirmed.
- Open conflicts: Please explain any missing identifier, family-only record, configuration difference, outdated record, conflicting value, or condition not addressed.
Use one disposition rule after the response. Accept only when the model, configuration, evidence scope, project conditions, and required reviewer checks align. Verify first when the evidence is relevant but an identifier, revision, scope connection, or project condition is incomplete. Escalate when the unresolved issue affects safety, electrical or controls compatibility, design performance, certification interpretation, environmental suitability, program eligibility, or authority acceptance.
For a safety-listing claim, the OSHA NRTL criteria provide a record-level check, but they do not decide whether a particular project approves a product. Hold approval if the supplier cannot connect the claim to an exact-model record and applicable project condition. Assign each open question to its responsible reviewer and wait for written clarification or a professional decision. This documentation disposition is not installation authorization.
FAQ
How do I verify a lighting certification?
Identify the issuing NRTL, registered mark, applicable standard, and exact model or file number. Search that organization's current record and read its scope, because a result may cover a component rather than the complete product. Resolve any mismatch before submittal or approval.
What is the difference between a test report and a certification?
A test report records testing or measurement under stated methods and conditions. Certification or listing is an organization's decision with a defined product scope and status. A test report may support a technical claim without replacing a certification record, and a certification record does not replace project-specific design evidence.
What documents should I request from a lighting supplier?
Start with the exact model and variant, then request the specification sheet, relevant photometric file or test report, current certification or listing record, environmental and compatibility documentation, and project requirements. Ask for a written map connecting each requested claim to its supporting document and identifying exclusions.
Can a product title prove an environmental rating?
No. A title or marketing phrase is not sufficient evidence. Request model-specific enclosure documentation, identify the covered parts and conditions, and compare those details with the proposed location and exposure. If the match is unclear, keep the claim in verify-first status and route the question to the responsible project reviewer or authority.
