An exterior luminaire can meet its target illuminance and still create a problem for the project: light beyond a property line, a bright source in a driver’s field of view, or light sent above the horizontal plane. The familiar answer is to ask for a “full-cutoff” fixture. That label is no longer a complete way to evaluate an outdoor optic.
BUG ratings give a more useful first screen. They describe where a luminaire sends potentially troublesome light as Backlight, Uplight, and Glare. The current ANSI/IES TM-15-20 Luminaire Classification System uses lumen distribution in defined solid angles and includes BUG ratings; IES says it is intended to replace the older cutoff system. That makes the rating relevant to an area light, wall pack, or outdoor flood light, but it does not make a fixture suitable everywhere by itself.
Use BUG to narrow the submittal, then use the matching photometric file and site conditions to make the design decision.
What the three letters describe
Each letter is a separate rating, normally shown as a compact code such as B2-U0-G1. Lower values generally mean less light in the corresponding concern area; they do not mean a fixture produces less useful light on the intended surface.
Backlight: consider the boundary behind the fixture
Backlight is light emitted behind a luminaire. It is relevant wherever the rear side of a pole-mounted fixture, wall-mounted luminaire, or floodlight faces a property line, a residence, a neighboring façade, or a sensitive part of the site. The joint IES/DarkSky Model Lighting Ordinance uses backlight limits that become more restrictive as a luminaire gets closer to a property line.
That relationship is the important idea for a submittal. A “low-backlight” optic may still be the wrong choice if the fixture is placed near a boundary and aimed poorly. Conversely, a fixture with more backlight may be acceptable where the rear of the luminaire faces a large, controlled part of the same site. Record the mounting height, pole location, orientation, and the nearest relevant boundary before comparing codes.
Uplight: check what leaves above horizontal
Uplight concerns light emitted above the horizontal plane of the luminaire. It is often used when reviewing sky glow, but it is also a direct check on whether a fixture is spending output where the project needs it. A zero-uplight rating can be a sound project requirement for many downward-facing parking, pathway, and building-perimeter applications, provided the selected configuration and installation preserve that condition.
Do not assume the family name establishes the rating. An adjustable floodlight, a different optic, a tilt, or field aiming can change where light goes. The Model Lighting Ordinance specifically notes that its BUG table applies to the luminaire rating and restricts adjustable mounting devices in that option. Review the submitted configuration rather than copying a generic “dark-sky friendly” statement into the schedule.
Glare: evaluate the people who must see through the scene
The G rating addresses high-angle light that can create visual discomfort. It is not a complete glare calculation, because glare depends on the observer’s location, the source brightness, and the surrounding adaptation level. The U.S. Department of Energy’s outdoor LED glare guidance distinguishes disability glare, which can reduce visibility, from discomfort glare, and notes that a bright source in a dark setting is more likely to be problematic.
For a parking entrance, driveway, pedestrian route, or loading area, review the fixture from the likely driver and pedestrian viewpoints. A low-G luminaire is helpful evidence, but it does not replace checking the pole spacing, mounting height, tilt, shielding, façade reflections, and the modeled scene.
BUG ratings are not a substitute for a lighting calculation
A BUG code describes the luminaire’s distribution in concern zones. It does not tell a reviewer the horizontal or vertical illuminance at a particular location, whether the site is uniform, or whether a specific neighbor will see a source. Those are application questions.
Ask for the IES photometric file corresponding to the proposed catalog configuration, then use it in the exterior calculation. The Department of Energy’s outdoor area-lighting fact sheet defines light trespass as light that strays from its intended purpose and becomes an annoyance, nuisance, or detriment to visual performance. A site calculation is how the team tests that risk at the actual property line, roadway, pedestrian path, façade, or window.
The calculation should state the assumptions that affect the result:
- Exact fixture, output setting, CCT, optic, mounting height, orientation, and tilt.
- Pole and building locations, property lines, adjacent uses, and relevant viewing directions.
- Calculation planes for the task, plus vertical planes or boundary grids where the project needs them.
- Controls state, including whether late-night dimming changes the intended operating condition.
- Any shields, house-side optics, or field-aiming limits that are part of the installed design.
This is especially important for an alternate. A proposed fixture can carry a seemingly favorable BUG code while delivering a different distribution on the pavement or building face than the scheduled fixture. Compare the same calculation criteria, not just the three-letter label.
Use lighting zones as project context, not as a universal code
The IES/DarkSky Model Lighting Ordinance organizes land uses into five lighting zones, from LZ0 through LZ4. The USGBC summary of the model ordinance describes LZ0 as a setting for pristine natural environments with limited outdoor lighting and LZ4 as a limited-use setting in extensively developed large cities. The model also ties fixture shielding and BUG concepts to those zones.
That is useful context for an owner, architect, or lighting designer. It is not proof that a local jurisdiction has adopted the model, its zone map, or its thresholds. Start with the adopted local code, zoning conditions, campus standards, owner criteria, and any sustainability program requirements. Then use the model’s zone logic to ask a better question: how sensitive is this particular site to spill light, high-angle brightness, and sky glow?
A submittal workflow that keeps BUG useful
For every exterior luminaire, document the proposed configuration before accepting a BUG rating:
- Identify the exact catalog number, output setting, optic, CCT, mounting hardware, and aiming condition.
- Obtain the manufacturer cut sheet and the matching IES file; make sure the BUG code belongs to that configuration rather than only to the product family.
- Map boundaries, adjacent residences, public rights-of-way, windows, and driving or walking approaches that could be affected.
- Check applicable code and owner criteria, including any required lighting zone or boundary measurement method.
- Run and retain the exterior calculation, adding vertical or boundary planes where the project needs proof of spill-light or visibility conditions.
- Coordinate shields, house-side distributions, tilt limits, and controls with the installation drawings so the tested design survives value engineering and field adjustment.
For parking-lot lighting, the same review should include drive aisles, vehicle approaches, pedestrian paths, and the property edge. For façade and floodlighting work, include the nearby viewing locations and the final aiming diagram. The less the decision depends on a generic fixture label, the easier it is to defend after installation.
The takeaway
BUG ratings turn a vague request for “better shielding” into three reviewable questions: What light goes behind the fixture? What goes upward? What high-angle light may be seen by an observer? They are a strong early filter for exterior luminaires, especially near boundaries and dark surroundings. Pair the exact BUG code with the correct IES file, the actual site geometry, applicable local requirements, and a documented calculation. That is how a good optic becomes a good outdoor-lighting installation.