When comparing lighting manufacturers, treat each product claim as an assertion—not proof. Match it to the exact product model, selected configuration, document scope and currency, and the project requirement that determines acceptance. A product page, specification sheet, test report, listing, environmental rating, or program record may answer one question while leaving another unanswered.
Use a Claim-to-Evidence Matrix Before Comparing Lighting Manufacturers
Start with the claim you need to check, then use the document type that can address it. The matrix below is a first-pass screen for comparing lighting manufacturers and suppliers. It does not replace review by a qualified electrician, lighting professional, engineer, inspector, or local authority when project approval or safety decisions are involved.
| Claim or decision | Document that may support it | What the document does not prove | Buyer action |
|---|---|---|---|
| Supplier claim or product-page statement | A matching manufacturer record, independent report, listing, certification, rating record, or program entry | The statement itself is not independent proof, and a similar model is not the exact product | Write down the claim and request the record that addresses it |
| Declared product characteristics | Current specification sheet or submittal for the identified fixture and configuration | It does not automatically prove independent measurements, safety listing, environmental suitability, rebate status, or project acceptance | Compare the model, options, revision, and stated limitations with the requirement |
| Measured lighting performance | Test report identifying the sample or model, method, conditions, date or revision, and scope | It is not automatically a safety listing, certification, or proof for another configuration | Confirm that the tested identity and conditions match the proposed fixture |
| Safety listing or certification | Record from the recognized certification body, including the mark, product identity, applicable standard, and scope | It does not prove every marketing statement or blanket approval by an owner, inspector, insurer, rebate administrator, or authority. For the U.S. NRTL boundary, OSHA's NRTL FAQ provides scope context for certification | Match the official record to the exact model and project requirement |
| Environmental rating or use statement | Defined rating record and the evidence required for the intended location or use | An IP classification describes enclosure protection; it does not by itself establish complete location suitability or project approval. The IEC 60529 classification is the relevant scope reference | Identify the rating, conditions, limitations, and separate approval requirement |
| Project requirement | Project specification, owner requirement, insurance condition, rebate rule, inspection criterion, or code-related requirement | It defines what must be demonstrated; it is not supplier proof that the fixture meets the requirement | Name the controlling requirement and approving party before accepting the evidence |
For program qualification, the current DLC Qualified Products List can help establish a matching program entry and its listed attributes. DLC qualification does not substitute for a safety listing or automatically establish utility or rebate approval, so the applicable utility or rebate rule still needs separate review. Document volume is not the threshold. The threshold is whether the evidence answers the exact claim for the exact product and project.
Know What Each Lighting Document Actually Supports
Use each document for the decision it is designed to address: supplier materials describe, reports measure, records classify or list, and project requirements set acceptance.
A supplier claim is the starting assertion. It identifies the attribute the seller says the fixture has, such as a performance value, listing, rating, or program status. A specification sheet adds manufacturer-declared characteristics, options, identifiers, dimensions, and stated limitations. Use these documents to set the comparison baseline; measured performance, formal certification, environmental suitability, and project acceptance require their own records.
A test report answers a measured question under the method, conditions, sample or model, date or revision, and scope stated in the report. If it covers one configuration, do not transfer its result to a different wattage, optic, control package, mounting arrangement, or other variant without supporting scope. A test report is not a certification or listing.
A certification or listing is a separate evaluating-body determination for an identified product and defined standard scope. The OSHA NRTL program ties an NRTL mark to applicable product-safety standards within the laboratory's recognized scope. Review that scope rather than treating a generic certification term as sufficient. The record still does not establish every marketing claim or formal project approval.
A DLC entry is program-status evidence for the matching product and current program scope. Compare the model and listed attributes with the current DLC requirements and QPL. The entry does not replace safety-certification evidence, prove warranty or field performance, or guarantee a rebate.
An IP code is an enclosure-protection classification under IEC 60529. It can describe the degree of protection provided by an enclosure under the stated standard and conditions, but it does not answer every question about location, exposure, intended use, installation conditions, hazardous or special-use settings, or project acceptance. Treat generic words such as outdoor, sealed, or rugged as prompts to request the defined rating and applicable approval evidence.
Finally, the project requirement is the acceptance question. An owner, insurer, rebate administrator, inspector, engineer, or local authority may require evidence beyond the seller's documents. Identify who controls that decision and what record they will accept. For a sign-permit packet, LED sign permit documents shows how a submission can require more than supplier literature.
Match the Record to the Exact Fixture and Project Scope
Use this six-step applicability check before relying on a document in a purchase order, submittal, inspection, insurance review, or rebate submission.
- Define the claim and threshold. Write the precise claim, such as a listing, measured output, environmental classification, or program qualification. Record the project requirement, intended use or location, approval stage, and party responsible for acceptance.
- Record the exact product identity. Capture the manufacturer, model or SKU, product family, document revision, and complete selected configuration. Potentially material fields include voltage, wattage, CCT, optics, controls, mounting, accessories, and other selected options. Do not assume every field controls every record, but do not omit them from the comparison.
- Cross-check identifiers. Compare the identity across the product page, quotation, specification sheet, submittal, test report, certification record, and program entry. A family name alone is not enough when the official record uses a model number, file number, construction number, or variant identifier.
- Inspect scope and currency. Identify the issuing organization or test method, applicable standard, sample or product scope, conditions, limitations, date or revision, and current status. For a claimed UL certification, search the official UL Product iQ record using an available file number, CCN, assembly, design, system, or construction number, then compare its scope with the proposed fixture.
- Compare the record with the project threshold. Ask whether the record addresses the actual requirement, not merely a related attribute. If qualification matters, compare the exact model and attributes with the current program entry. If the record covers a component, accessory, family member, or different revision, mark that limitation instead of treating it as support for the complete fixture.
- Document every mismatch for clarification. Record the missing identifier, option, rating definition, test condition, date, limitation, or approval rule. State who must resolve it and what record is requested. A missing or conflicting link between the claim, product, record, and requirement means the matter is unresolved.
Choose Buy, Verify First, or Escalate
The right outcome depends on scope, not on how large or polished the document packet looks.
| Documentation condition | Buyer outcome | Required next move |
|---|---|---|
| The exact product and configuration are identified; the appropriate current record supports the claim; scope and project fit are clear; and no responsible approving party has an unresolved objection | Buy | Retain the matched record with the procurement or submittal file and follow the project approval process |
| The documentation is plausible, but an identifier, option, method, date, rating definition, limitation, current status, or threshold is incomplete or ambiguous | Verify first | Send a specific question to the supplier's technical contact and request the missing record or written scope clarification |
| Records conflict, the listing or certification cannot be matched, environmental or special-use conditions affect acceptance, or the decision belongs to an engineer, inspector, insurer, rebate administrator, owner, or authority | Escalate | Send the full evidence packet to the responsible technical or approving party and wait for that party's determination |
For a claimed ETL status, search Intertek's ETL directory by manufacturer, exact model or number, or standard. If the result is absent or unclear, request certification verification rather than inferring approval from a similar entry.
Before procurement or submittal approval, send one focused request containing the exact model or SKU, full selected configuration, claimed attribute, intended use or location, project requirement or threshold, approval stage, and specific record requested. Ask the supplier or reviewer to state what the record proves, which product and configuration it covers, what conditions or limitations apply, and what it excludes. Then route the response to the person responsible for project acceptance when that decision is outside your authority.
Frequently Asked Questions
Use these questions when a document packet leaves one decision point unclear.
What Is the Difference Between a Lighting Certification and a Test Report?
A test report records results for an identified sample or model under stated methods and conditions. A certification or listing is a separate evaluating-body determination for an identified product and defined standard scope. Keep those document types separate when the requirement names one, and request the record type specified for the decision.
What Should Be on an LED Lighting Specification Sheet?
Use the sheet to establish the fixture's declared model, options, characteristics, and limitations. If a purchasing decision depends on a measured value or formal approval, attach the separate test, listing, certification, rating, or acceptance record named by the requirement.
How Do I Verify a Lighting Listing or Environmental Rating?
Start with the issuing body's record, such as UL Product iQ, Intertek's ETL directory, or the current DLC QPL, depending on the claim. If the exact identifier is absent or the record's conditions do not fit the intended use, hold the purchase and send the issue to the responsible technical or approving party.
