How to Read an LM-79 Report (What Specifiers Should Verify)
LM-79 reports are the closest thing lighting has to a bank statement. This guide shows what specifiers should verify, what vendors “forget,” and how to cross-check photometrics fast.
Specs can lie. After sitting through too many VE meetings where “same performance” magically appears next to a lower price, I started treating every LM-79 report as evidence—who tested it, what exact SKU was tested, and whether the photometrics, electricals, and color metrics agree with each other across pages, attachments, and the IES file. If the report can’t survive a five-minute cross-check, why should your project carry the risk?
Here’s the hard truth I wish more specifiers said out loud: an LM-79 report is not “proof” of a product line. It’s proof of one tested sample (sometimes a “golden” sample), under one configuration, on one date. Your job is to make sure that sample is actually the thing you’re buying.
If you need a reference point for how often “certified” products still fail in the real world, EPA’s own post-market program is blunt: in the 2023 ENERGY STAR Verification Testing Summary it reports 1,218 models completing verification testing and an overall 94% compliance rate—meaning failures are not theoretical.
Step 1: Confirm the report is actually LM-79 (and current enough to matter)
LM-79 is a method (ANSI/IES LM-79-19 is the common reference in North America). So I look for three things right away:
Standard and revision: “LM-79-19” (or earlier) should be spelled out, not implied.
Test lab identity: name, address, report number, signatures.
Scope match: the lab should be testing luminaires, not just LED modules.
If the cover page is vague, missing signatures, or reads like marketing copy, I stop. Literally stop.
If you want your internal workflow to run faster (and avoid the endless “please resend the IES + report + cut sheet” email chain), bundle your submittal artifacts up front: LED lighting IES files and LM-79 submittal packs for US/EU approvals are exactly the kind of “one-request, one-delivery” structure that keeps projects moving.
Step 2: Match the tested sample to the exact ordering code you’re buying
This is where vendors get cute—especially with families (downlights, linear, track) where one housing supports five drivers and eight optics.
I want to see:
Manufacturer + model code (full string, not “Series X”)
CCT (e.g., 3000 K / 3500 K / 4000 K)
CRI variant (80 vs 90 changes output and efficacy)
Optic/beam (15°, 24°, 36°, batwing, diffused)
Input voltage (120 V vs 277 V vs MVOLT)
Dimming type (0–10 V, DALI, phase-cut—driver matters)
Mounting + trim (recessed vs surface changes thermal and glare behavior)
If the report says 4,200 lm at 28 W, that’s 150 lm/W. Fine. If the cut sheet claims 180 lm/W for the same SKU… I’ve seen that movie.
And yes, small “rounding” games add up. A 7–10% lumen shortfall can force a layout change (more fixtures, tighter spacing, different optics). That’s not a theory—those are change orders.
Step 4: Don’t let “color” be hand-wavy—verify CCT, CRI, and Duv
Most people check CCT and CRI and call it a day. I check Duv because that’s where the ugly shows up.
CCT tells you “warm/cool” (e.g., 3000 K vs 4000 K).
CRI (Ra) tells you average color rendering.
Duv tells you whether the light sits above or below the blackbody locus (that greenish cast specifiers hate).
In retail and hospitality, I’ve rejected products that “met” CRI 90 but had a Duv that made whites look sick. Nobody thanks you for catching it, but everyone notices when you don’t.
What is an LM-79 report? An LM-79 report is a third-party laboratory test report, written to the ANSI/IES LM-79 method, that documents a complete LED luminaire’s measured photometric output (lumens and candela distribution), electrical draw (watts, current, power factor), and color metrics (CCT, CRI, chromaticity) under defined test conditions. If it’s missing the full tested configuration, it’s not usable for specs—period.
What should specifiers verify in an LM-79 report? Specifiers should verify that the tested sample exactly matches the ordered SKU (CCT/CRI/optic/driver/voltage), that lumens, watts, and lm/W are internally consistent, and that the report includes accountable lab identification, standard version, and photometric/color details sufficient to cross-check the IES file and the cut sheet. I also verify Duv, because “CRI 90” can still look green and nobody wants that fight on site.
How do I cross-check an IES file (LM-63) with an LM-79 report? An IES file (LM-63) cross-check means confirming the photometric data file used for calculations corresponds to the same tested luminaire configuration and produces the same lumen total and distribution shape as the LM-79 report, allowing only minor rounding differences and ensuring optics/beam claims align with the candela plot. If totals are far apart, assume the IES belongs to a different variant until proven otherwise.
Does LM-79 prove product lifetime or lumen maintenance? LM-79 does not prove lifetime performance because it measures initial photometric, electrical, and color output of a luminaire at the time of testing, while long-term lumen maintenance requires separate component aging data (LM-80) and projection methods (TM-21) tied to LED packages or modules, not just the finished fixture. So yes, you can have a perfect LM-79 and still get a disappointing field story five years later.
How old is “too old” for an LM-79 report? An LM-79 report is “too old” when the tested configuration is no longer identical to production—driver revisions, LED bin changes, optics swaps, or thermal design tweaks can invalidate results even if the housing looks the same—so the acceptable age depends less on the date and more on documented design change control. If the supplier can’t state “no material changes since test date,” I treat it as stale.
