Write one sentence before opening the datasheet: identify the project decision, lock the exact fixture configuration, and note who owns each unresolved question. For example: “Screen electrical and mounting fit for this exact SKU at this site,” followed by the manufacturer, model or SKU, revision, selected options, site conditions, and responsible reviewer. This turns LED lighting specifications into a decision record instead of a glossary. If the identity, configuration, or decision scope is unclear, stop before approval. Do not use this guide for high-voltage wiring, live testing, breaker selection, wire sizing, or protection bypasses; route circuit design, installation, code, and authority questions to qualified professionals and the local authority.
Write the project decision and lock the exact fixture configuration
Start with the decision that could change the purchase, bid, submittal, or approval. Record whether you are screening for electrical fit, physical fit, layout and task fit, controls, environmental conditions, or project documentation. Then capture the exact manufacturer, model or SKU, revision, voltage, wattage, CCT, mounting method, control options, accessories, project location, and relevant site conditions. Series-level information may not apply to the selected option set.
Keep three types of evidence separate as you annotate: manufacturer product facts, professional design or installation review, and authority or program decisions. The datasheet can describe stated characteristics, but it does not independently prove circuit design, structural adequacy, code compliance, rebate eligibility, or authority approval; assign each unresolved item to the responsible professional, manufacturer support team, program, or authority before continuing.
Check electrical load and physical fit before comparing light output
Use the electrical and mounting fields as a screening reference first. They can show which questions require comparison or review, but none independently authorizes a connection or establishes structural adequacy.
| Datasheet field | Project decision it can change | What it cannot prove alone |
|---|---|---|
| Input voltage and frequency | Whether the stated supply appears to match the proposed fixture | Complete circuit design, installation approval, or code compliance |
| Selected watts, quantity, and total connected load | The load information a qualified electrical reviewer must evaluate | A universal circuit, breaker, or wiring decision |
| Inrush, power factor, and THD | Whether additional electrical review is needed | A universal pass threshold or acceptable circuit arrangement |
| Dimensions, weight, and clearances | Whether the fixture appears to fit the space and access conditions | Structural capacity, hardware adequacy, or installation approval |
| Mounting method and accessories | Whether the proposed mounting approach matches the project conditions | A safe installation method for every structure or site |
| Whole-luminaire output and input power | A fair fixture-to-fixture performance comparison | Task fit, distribution, or project approval |
Compare finished-luminaire performance fields, not component-only LED figures. The finished-luminaire performance fields should have a matching scope for output, measured input power, CCT, CRI, and efficacy. If comparable measured values are available, use the formula efficacy = luminous flux ÷ luminaire input watts. The luminaire efficacy formula supports comparison, not a universal pass mark.
Write the project supply, fixture quantity, selected wattage, mounting method, accessories, and unresolved electrical or structural questions beside the matching fields. Do not turn inrush or power-quality information into wiring instructions.
Match control fields to the project control system
Treat control compatibility as an exact-configuration match, not as a conclusion based on a label. Record the driver or fixture interface, selected dimming option, sensors, photocontrols, accessories, controller, zones, wiring documentation, and required sequence of operation. Compare those details with the project control system and its documentation.
If the interface, accessory identity, protocol detail, wiring information, or operating sequence is missing or mismatched, mark the fixture Verify first. Request confirmation for the exact configuration from the manufacturer’s technical team or the qualified system reviewer. No universal control-interface rule should replace that comparison, and a control label does not prove interoperability with every controller, sensor, driver, or sequence.
Use LED lighting specifications, photometry, and a ceiling-height scenario to test layout fit
Use lumens as total output and beam angle as an angular-intensity distribution descriptor, not as proof that a layout works. Beam angle under the stated convention is commonly based on the angle where intensity reaches 50% of maximum, while field angle uses the 10% point. The LM-79 layout boundary explains why distribution, geometry, and task requirements must be considered together.
Use the following qualitative matrix to decide what to inspect first. These are review contexts, not performance promises.
| Ceiling or installation context | Task | Fixture category | Fields to prioritize | Assumptions and verification |
|---|---|---|---|---|
| Higher-ceiling open work area | General work or circulation | High-bay category | Mounting height, distribution, candela data, exact photometry, task requirements | Confirm geometry, spacing, surfaces, and project criteria through qualified lighting analysis |
| Lower-ceiling close task | Close work or occupied task area | Linear or surface-mounted category | Physical fit, mounting, glare criteria, CCT, CRI, distribution, and control behavior | Confirm task conditions, reflectance, visual requirements, and control sequence |
| Outdoor wall or canopy task | Exterior access, wall, or covered area | Wall-mounted or vapor-tight category | Exposure, location marking, IP scope, temperature, corrosion, mounting, and installation conditions | Match the exact site exposure and installation requirements; review applicable code or authority criteria |
An exact-configuration photometric file can support layout analysis when matched with mounting height, spacing, surfaces, and task requirements. It does not by itself prove illuminance, uniformity, glare, light trespass, or coverage. When those criteria matter, use the datasheet as an input to qualified lighting analysis, such as the available project lighting design support, rather than approving from lumens or beam angle alone.
Check environmental fit without treating a rating as project approval
Record environmental evidence as separate fields: the exact damp- or wet-location marking, IP or enclosure information, operating temperature, corrosion and exposure notes, mounting conditions, and hazardous-location status when relevant. Match each field to the actual site conditions and installation requirements.
A generic outdoor, waterproof, durable, or moisture-resistant description is not a complete environmental determination. Damp- and wet-location markings answer a location-marking question, while IP rating scope describes dust and moisture resistance under defined test conditions. An IP rating does not by itself establish hazardous-location suitability, corrosion performance, installation suitability, code compliance, or local acceptance.
Hold the environmental decision when site exposure exceeds the documented conditions or the exact marking is unclear. Request technical or authority verification instead of inferring suitability from marketing language or transferring a rating from another configuration.
Request exact-SKU documents for certification, claims, and project approval
Build a document packet whose identifiers match the proposed manufacturer, model or SKU, revision, voltage, wattage, CCT, controls, mounting, accessories, and configuration. Request the specification, installation and mounting information, dimensional drawing, controls documentation, exact-configuration IES file, safety-listing evidence, applicable efficiency-program record, warranty terms, and project-specific declarations.
An IES file is photometric data for analysis, not certification or code evidence. Request the exact-configuration photometric file, including the tested product version and context, and understand that an IES-format photometric data file is a transfer and storage format. It cannot substitute for listing, code, rebate, or authority documentation.
Keep these questions separate:
- Product specification: What characteristics and options does the exact fixture document state?
- UL or ETL safety listing: What listing evidence applies to this exact product and configuration?
- DLC or QPL status: Is the exact product or version present in the applicable efficiency-program database when the project requires it? The DLC Qualified Products List distinction is separate from safety listing and building-code review.
- Dark Sky claim: What specific claim and scope are documented, if the project requires one?
- Code compliance, rebate eligibility, and project approval: Which applicable professional, program, specification, or authority review answers each question?
For a practical document-location follow-up, use this exact-SKU document verification guide. If identifiers, revisions, markings, or required documents cannot be reconciled, pause approval and request confirmation. A mismatch blocks confident approval; it does not by itself prove noncompliance.
Annotate the datasheet and assign a readiness status
Turn the marked-up datasheet into a project status by assigning each unresolved field to an owner and separating complete evidence from open questions. Use Buy only when required evidence matches the project and qualified review is complete; otherwise choose Verify first or Do not approve yet according to whether the issue is unresolved or conflicting and material.
Mark every decision-changing field and assign an owner
Use this single before-approval annotation checklist. Write the value, source or document, unresolved question, and owner beside each applicable item.
- Identity: exact model or SKU, revision, selected options, quantity, project location, and site conditions.
- Electrical: supply voltage and frequency, selected watts, total-load question, inrush, power factor, THD, and qualified electrical reviewer.
- Mounting: dimensions, weight, mounting method, accessories, clearances, structural question, and responsible reviewer.
- Optical and layout: lumens, efficacy, CCT, CRI, distribution or beam information, exact IES-file status, mounting height, task, spacing assumptions, and lighting-calculation owner.
- Controls: interface, driver, sensors, photocontrols, accessories, controller, wiring documentation, zones, and sequence of operation.
- Environmental fit: exposure, temperature, corrosion conditions, IP or enclosure information, exact location marking, and hazardous-location question when relevant.
- Approval packet: specification, installation information, listing evidence, program record, Dark Sky or other claims, warranty, project specification, and authority requirements.
- Open questions: unresolved field, requested evidence, assigned owner, response date, and resulting status.
Choose the readiness status and take the closing action
Readiness status is a project workflow classification, not a formal certification or compliance finding.
| Status | Use it when | Next action |
|---|---|---|
| Buy | Required technical fields and exact-SKU documents match the project requirements, and qualified project review is complete | Release the purchase only through the project’s approved process |
| Verify first | The fixture may fit, but configuration, photometry, controls, environmental evidence, or document identity remains unresolved | Request matching evidence and assign the open question to the responsible reviewer, manufacturer, program, or authority |
| Do not approve yet | A material electrical, environmental, safety-listing, code, or project requirement conflicts or cannot be established | Hold purchase or submittal release until the qualified professional or authority resolves the requirement |
Send the annotated exact-SKU packet, open-question owners, and status to the responsible reviewer before purchasing or releasing a submittal. That packet is the clearest next action when LED lighting specifications contain both usable facts and unresolved approval questions.
FAQ: practical LED specification questions
These questions focus on the decisions that most often remain open after a first pass through the sheet.
How do you read an LED light specification sheet?
Start with the project decision, not the glossary. Record the exact SKU, revision, selected options, and site conditions; then map electrical, mounting, optical, control, environmental, and approval fields to that decision. Mark any item that requires separate professional, manufacturer, program, or authority evidence. If the identity or configuration is unclear, use Verify first rather than assuming the sheet applies.
What does beam angle mean on a lighting datasheet?
Beam angle describes the spread of angular light intensity under the stated measurement convention. It is not a promise of floor coverage, illuminance, uniformity, or comfort. Pair it with the exact photometric file, mounting height, spacing, surfaces, and task requirements before accepting a layout.
What documents should a contractor request for LED fixtures?
Request exact-SKU technical specifications, mounting and dimensional information, controls documentation, an applicable photometric file, safety-listing evidence, any required DLC or other program record, warranty terms, and project-specific declarations. Match the model, revision, options, and configuration across every document, and keep listing, program, code, and project approval questions separate.
What should I do if an LED fixture datasheet is missing a required field?
Mark the field unresolved and request matching evidence for the exact configuration. Assign the question to the appropriate manufacturer support team, qualified professional, program, or authority. Keep the fixture at Verify first or Do not approve yet until the missing information is resolved and the project reviewer accepts it.
