How to Read a Photometric Report: IES Files, Footcandles & Lighting Calculations

Photometric Reports vs. IES Files: Know What You Are Reading

A lighting proposal may include an IES photometric file, a luminaire test report and a site or room calculation. Those documents are related, but they answer different questions. The product data describe how a particular fixture distributes light; the layout report predicts what happens when selected fixtures are placed in a defined space.

Before comparing footcandle averages or color plots, confirm that the fixture configuration, mounting geometry, calculation surfaces and assumptions match the project. That is how a photometric report becomes useful evidence for selecting commercial lighting—not just a polished graphic.

How IES Files Support Lighting Calculations

The Illuminating Engineering Society's public explanation of IES files describes an IES file as standardized photometric data representing a light source's distribution. The data include luminous intensity by angle and identifying information. Lighting software uses those characteristics in calculations for an environment.

An IES file is therefore an input to a project model, not a project-specific approval. The reader still needs the equipment arrangement and model conditions. A filename containing a familiar family name is not sufficient evidence that the file represents the ordered optic and output configuration.

Verify Fixture Models, Optics and Output Settings First

Find the exact catalog designation, quantity, optical option and selected output setting. Match them to the proposal and the supporting photometric data. Where a report uses a representative file, a multiplier or another adjustment, request the basis and approval for that treatment.

The FEMP Energy Efficiency and Indoor Environmental Quality Assessment Guide, February 2024, emphasizes the exact source file and geometry inputs in lighting simulation. Its lighting section also notes that simulations approximate actual conditions. These points support checking the model rather than accepting the appearance of a rendered image.

Make a short discrepancy list. If the purchasing schedule names one optic and the report names another, resolve it before comparing results. If the report omits the selected setting, ask which condition was modeled. Retain the corrected document rather than relying on a verbal assurance that the difference is unimportant.

Verify Fixture Position, Orientation and Aiming

A luminaire's position and orientation need to be identifiable on the project plan. For asymmetric products, the drawing should make the intended direction clear. Mounting elevation, aiming and suspension should agree with the project information.

This does not mean the purchasing team should edit the photometric file or adjust aiming to obtain a preferred result. Request a revised calculation from the responsible designer when the arrangement changes. Preserve the version trail so that procurement and installation use the same basis.

Check Calculation Planes, Heights and Boundaries

A summary labelled “area average” is incomplete without its receiving surface and boundaries. Identify whether each calculation zone is horizontal, vertical or otherwise defined, and locate its elevation or orientation. A floor grid cannot silently stand in for a raised task or a vertical rack label.

Then inspect the included and excluded areas. A model might evaluate an open circulation zone while omitting a workbench. The omission could be intentional, but the report needs to show it. Compare the zones with the project brief rather than assuming the entire building has been evaluated.

When comparing reports, convert footcandles and lux consistently, but confirm that the calculation planes, locations and operating conditions also match. A unit conversion cannot correct a mismatch in the surfaces being evaluated.

Interpret Footcandle Grids, Minimums and Uniformity

Locate the calculation point pattern, grid spacing, boundary offsets and summary definition. Ask whether the point locations represent the critical task positions and transitions. A coarser or differently bounded grid can answer a different question even when the report uses the same metric names.

As a hypothetical illustration, Report A summarizes a whole storage floor, while Report B summarizes only an inspection zone within it. Both report an average of 30 fc. That numerical match does not establish equivalent coverage or prove that either report evaluates the other area. The scope must match before the averages become comparable.

Keep maximum, minimum and ratio definitions visible. If a report lists an average/minimum ratio, do not compare it with another report's maximum/minimum ratio as though they were identical measures. A zero or very low denominator also needs investigation; avoid silently removing a troublesome point from the summary.

Read Color Scales Alongside Actual Values

A plot can help locate patterns quickly, but read its legend and underlying values. If two revisions use different colour ranges, their apparent similarity or contrast can mislead. Request the point data or clearly labelled contours needed to understand the change.

A presentation rendering can communicate appearance, while a calculation grid reports a defined quantity. Keep their roles separate in the review package. Neither an attractive image nor a dense table eliminates the need to check the inputs.

Understand Initial vs. Maintained Lighting Results

Identify whether the results are described as initial or maintained and what factors were applied. Record the basis for any light-loss treatment and keep it tied to the equipment and maintenance assumptions. Do not insert a generic factor merely because it is familiar.

The FEMP guide discusses reflectance and light-loss assumptions within its assessment method. Its example values are not a determination of the appropriate factors for every project. A defensible review asks the designer to identify and justify the chosen values rather than treating a published example as a universal setting.

Likewise, record which light sources are included in each scene. If daylight, task lighting or another system contributes to a result, make that contribution explicit. A normal daytime model does not automatically describe operation after dark or under emergency conditions.

Resolve Missing Inputs Before Approving a Lighting Layout

“Please improve the photometrics” leaves the recipient guessing. Tie each comment to a specific discrepancy, missing input or criterion. The following is a proposed review format, not a design standard.

Assign each question to the responsible party. The reviewer should not fill a missing code criterion or mechanical assumption with a guess just to close the comment.

Use Photometric Reports to Compare Real Lighting Proposals

For high bay applications, confirm the rack layout, fixture mounting height and task surfaces before relying on a warehouse-wide average.

For outdoor applications, examine property boundaries, mounting and aiming, and the distinct tasks served by each zone. Indoor assumptions do not automatically apply to an exterior site.

At purchase, freeze the evaluated configuration or require review of substitutions. At closeout, retain the report revision, equipment schedule and relevant field evidence. A future change in layout or equipment can then be evaluated against a known baseline.

A reliable lighting decision starts with the right fixture data and ends with the light delivered to the areas that matter. Check the model, examine the weakest locations, and compare results against the actual project requirements before ordering equipment. The numbers are most valuable when you know exactly what they represent.