Lighting & Photometrics
Photometric Studies: What AHJs Actually Look For
Average footcandles are only the start. Here's what a reviewer checks on a photometric plan — and how to pass the first time.

A photometric plan looks simple: a grid of numbers over a floor or a parking lot. Reviewers read more into it than the average, and knowing what they check helps you pass on the first pass.
Uniformity, not just average
An average footcandle number can hide dark corners. Reviewers look at the max-to-min and average-to-min ratios. A lot that averages 3 fc but drops to 0.2 fc in a corner is a safety problem, and it shows up in the uniformity ratio.
The ratios are the reviewer's lie detector. A typical municipal ordinance caps the average-to-minimum ratio around 4:1 for parking areas — some go tighter, some looser, but every reviewer we have worked with runs the same mental check: take the maximum value on the grid, take the minimum, and ask whether a person walking the lot would feel safe in the dark spots. Interior spaces get the same treatment under IESNA recommendations, where task areas want tighter uniformity than circulation. When we lay out fixtures, we design to the ratio first and the average second, because a compliant average with a blown ratio is the single most common reason a photometric plan comes back with redlines. Spacing the fixtures to the manufacturer's spacing-to-mounting-height guidance — and then verifying with the actual calc grid, not the catalog claim — is what keeps both numbers in bounds.
The right IES files
The study is only as good as its photometry. Using the actual manufacturer IES files for the specified fixtures — not a generic stand-in — is what makes the numbers defensible.
An IES file is the laboratory-measured light distribution of a specific fixture at a specific lumen package and distribution type. Swap in a generic file and three things go wrong: the candela distribution does not match the specified optic, the lumen output does not match the specified package, and the reviewer — who will ask for the IES file by name — finds a fixture schedule that points at one product and a calc built on another. We name every IES file in the fixture schedule and keep the files in the submittal folder, so when the reviewer asks, the answer is a file, not an explanation. One more trap: IES files are versioned. A file pulled from a manufacturer's site two years ago may not match the current-generation LED module in the same housing. We re-pull IES files at submittal time and note the revision on the schedule.
Footcandle targets that actually get enforced
Before running a single calc, know the numbers the AHJ will hold you to. They vary by jurisdiction, but the enforced ranges cluster tightly:
| Application | Typical enforced range |
|---|---|
| Parking lot, average | 0.5–2.0 fc maintained |
| Parking lot, minimum | 0.2–0.5 fc |
| Building entries and canopies | 2.0–5.0 fc |
| Walkways and pathways | 0.5–1.0 fc |
| Property line trespass cap | 0.1–0.5 fc (often 0.1) |
| Gas station / drive-through canopy | Per state or brand standard, often 10–20 fc |
Two words in that table do heavy lifting: maintained and initial. Most ordinances enforce maintained footcandles — the light level after the light-loss factor is applied — which means the calc has to include a defensible LLF accounting for lamp lumen depreciation, dirt, and ballast/driver factor. An LLF of 1.0 on an LED study will get questioned; we use the manufacturer's published LLD curve or the IESNA-recommended factors and state the value in the summary table. Running the calc at initial values and calling it maintained is the fastest way to lose a reviewer's trust.
Light trespass at the property line
For site lighting, spill onto neighboring property and the sky matters. Many jurisdictions cap footcandles at the property line and require full-cutoff optics. We check trespass at the line against the ordinance.
The property-line check is a separate calculation from the lot grid, and it needs its own presentation: a calc line or a dedicated set of points at the property boundary, usually at grade, showing the footcandle value at each point against the ordinance cap. The common failure is aiming: a floodlight tilted even a few degrees past horizontal throws a hot spot across the line, and the calc has to model the actual tilt, not the idealized zero-degree aim. Shielding accessories — house-side shields, visors — go in the fixture schedule with part numbers, because a reviewer who sees a trespass problem will ask what hardware fixes it. Where the site abuts residential, some jurisdictions drop the cap to 0.1 fc and require the calc points to extend past the line onto the neighboring parcel; we confirm the measurement protocol with the ordinance text before running the study.
BUG ratings: read the cut sheet like a reviewer
Reviewers increasingly check the fixture's BUG rating — backlight, uplight, glare — from IES TM-15, printed on the cut sheet. The rating is three numbers, each on a 0-to-5 scale, and the uplight number is the one that kills site plans: many ordinances effectively require U0, meaning zero uplight, which rules out any fixture that throws light above horizontal. A "full cutoff" claim in a catalog does not always survive the BUG table — we read the actual U value off the cut sheet and schedule only fixtures whose published ratings meet the ordinance. Backlight matters at the property line too: a high B rating on a perimeter pole is a trespass problem the calc grid will confirm. When the schedule lists the BUG rating next to each fixture type, the reviewer checks a box and moves on; when it doesn't, the reviewer goes looking for the cut sheet themselves, and the review takes a week longer.

Mounting height and tilt
Illuminance falls off with the square of distance. The study has to reflect the real mounting height and any tilt — an optimistic height inflates the grid and invites a correction.
This is where studies most often part ways with reality. The pole height on the site plan, the mounting height in the calc, and the height on the fixture schedule must all agree — a 25-foot pole with the fixture head at 27 feet is a 27-foot mounting height, not 25. Tilt is the quieter killer: adjustable floodlights get modeled at their specified aiming angles, and we note the angles on the plan so the installing contractor can reproduce the study in the field. A study that assumes zero tilt on fixtures the contractor will aim by eye is fiction. For wall packs, the mounting height is the actual elevation above grade at the installed location, accounting for grade changes across the site — a pack mounted 15 feet above a loading dock that sits 4 feet below the parking grade is not at the same effective height as the lot poles.
The calculation grid: drawing-sheet specifics
The sheet itself is a deliverable with a standard anatomy, and reviewers expect every part of it. The calc grid covers the area of interest at a regular spacing — 10-by-10 feet is the workhorse for parking lots, tighter for entries and canopies — with a point value at each node. The summary table states average, minimum, maximum, the avg/min and max/min ratios, the light-loss factor used, and whether values are initial or maintained. The fixture schedule lists each type with the manufacturer, model, lumen package, mounting height, tilt, IES file name, and BUG rating. The compliance note cites the ordinance section and states the result: average and uniformity within limits, property-line trespass within the cap. One sheet, everything a reviewer needs, no hunting through appendices.
Corrections we see on the first submittal
The redlines repeat across jurisdictions. Generic IES files instead of the specified fixture's file. An average that passes with a uniformity ratio that doesn't. Light-loss factor of 1.0 with no justification. Mounting heights in the calc that don't match the site plan. Property-line points missing entirely. Cut sheets without BUG ratings where the ordinance requires cutoff optics. And the classic: the fixture schedule names a product the calc was never run with. Every one of these is a coordination failure, not a lighting failure — and every one is preventable by running the study against the issued schedule, not the preliminary one.
A clean, readable deliverable
Finally, the plan itself has to be legible: the calc grid, the summary table (avg/min/max, ratios), the fixture schedule with IES types, and the compliance note. A tidy sheet gets read quickly and approved quickly.
Get these right and a photometric study clears review without a second look.
Our photometric design service delivers the point-by-point studies reviewers accept — real IES files, uniformity ratios, and property-line trespass checks — and pairs naturally with our lighting design layouts. Request a quote with your site or floor plan and the fixture IES files.
Need similar drawings?
Get permit-ready lighting and photometric drawings for your project
Send us your plans and scope — we'll come back with a fixed price and a turnaround date. No obligation.
Keep reading
Related articles
Lighting & PhotometricsTitle 24 and IECC Lighting Controls: What to Show on Drawings
Lighting control drawings are where energy code compliance lives or dies. What Title 24 and the IECC require on the plans — zoning, sensors, and the…
Lighting & PhotometricsEgress Lighting Drawings: What Reviewers Look For
Egress lighting is life safety drawn on a plan. The foot-candle minimums, battery and generator sources, and coordination details reviewers check…
Lighting & PhotometricsDark-Sky Compliance: Drawing Site Lighting for Local Ordinances
Local dark-sky ordinances are stricter than the energy code and vary city by city. How we draw site lighting plans — cutoffs, curfews, and photometrics…
Get a fixed drafting quote in under 24 hours
Send us your architectural plans and scope. We'll come back with a fixed price and a turnaround date — no obligation.
