BUG Rating and Dark-Sky Basics for Municipal Bids

Direct answer. BUG rating lighting classifies a luminaire's zonal lumens as Backlight, Uplight and Glare components. Municipal buyers can use maximum B, U and G values to screen products for a defined environmental zone and application, but the rating does not prove property-line compliance, low glare or dark-sky performance after installation. Pole location, tilt, orientation, output, quantity, curfew and complete photometric calculations must also be reviewed.

Key Takeaways

• B, U and G are three separate ratings; a strong result in one does not cancel a weak result in another.
• Ratings are based on luminaire photometry and defined angular zones, not measurements at a property boundary.
• Installed tilt and rotation can change where light goes even if the catalogue rating is unchanged.
• Municipal bids should state the applicable lighting zone, exceptions and calculation evidence.
• Full cutoff, zero uplight, BUG limits and curfews answer different questions.

Read the Three Letters Separately

Backlight concerns light behind the luminaire relative to its intended forward direction and can relate to light trespass. Uplight concerns light at and above horizontal and relates to sky glow. Glare concerns high-angle forward light that may affect observers. IES assigns each letter a rating from zonal-lumen thresholds.

For BUG rating lighting, direction matters. The photometric file needs a defined forward orientation. If a product is rotated on the pole, its backlight zone rotates with it. A B rating cannot be interpreted without knowing how the luminaire is installed relative to roads, homes or boundaries.

BUG Is a Luminaire Rating, Not a Site Result

The rating is derived from a photometric test of a luminaire. A site contains many luminaires, mounting heights, tilts, surfaces and observer positions. Boundary impact is the sum of installed sources and reflected light. A compliant product can still be poorly placed.

Municipal specifications should therefore request exact IES/LDT files and a site calculation. The calculation should show property lines, façades, roads and sensitive receptors. It should state whether values are initial or maintained and identify the coordinate system.

The ULR, BUG and full-cutoff guide explains why these terms should not be merged. BUG rating lighting is one layer in a broader impact assessment.

Connect Limits to the Environmental Zone

Many ordinances or model codes vary allowable ratings by lighting zone, mounting height or lumen package. A city should identify which adopted rule applies and how mixed-use boundaries are handled. Do not copy a table from another jurisdiction without legal and technical review.

The bid should define the zone for each project area and note permitted exceptions, such as roadway safety or specific operational needs. If a roadway standard requires light that conflicts with a general outdoor ordinance, qualified designers and authorities must resolve it rather than silently reducing visibility.

FHWA notes that master-plan requirements should not dictate roadway quantity or quality in a way that compromises user safety. This makes coordination essential.

Uplight Is Not the Whole Dark-Sky Story

U0 can be a valuable screen for luminaires intended to emit no direct uplight in the tested orientation. Yet sky glow also includes light reflected from pavement, façades and other surfaces. Higher total site output can increase reflected contribution even when every luminaire is U0.

Tilt is critical. A fixture with zero direct uplight in its tested horizontal position may send light above horizontal when tilted. Require installation drawings and field verification. Decorative elements, signs and façade lighting should be included in the site inventory.

For BUG rating lighting, pair uplight requirements with task-based output, dimming schedules and curfew. The goal is sufficient useful light with controlled waste, not merely a low letter-number code.

Backlight Does Not Equal Property-Line Illuminance

Backlight rating describes lumens in defined zones behind the luminaire. Property-line illuminance depends on distance, height, aiming, multiple luminaires and terrain. A low B rating can help, but setbacks and shielding may be more important at a specific boundary.

Show the property line in the calculation and report agreed vertical and horizontal points. Include windows or residential façades where required. If vegetation is used as mitigation, do not assume permanent shielding unless the authority accepts it and maintenance is defined.

Glare Rating Is Not an Observer Calculation

The G component evaluates high-angle zonal lumens. It can help screen luminaire brightness, but actual discomfort or disability glare depends on source luminance, size, observer view, background and geometry. Road curves, hills and elevated fixtures can change exposure.

Use BUG rating lighting with route-based review where drivers, pedestrians or neighbours are sensitive. The driver glare checklist provides a method for transport locations.

Write the Municipal Bid in Layers

1. Identify adopted ordinance, standard and lighting zone.
2. Define tasks and safety criteria.
3. Set maximum B/U/G screens where applicable.
4. Require exact photometry and order code.
5. Calculate road, task, boundary and façade points.
6. State mounting, tilt and orientation limits.
7. Add controls, curfew and override.
8. Define site measurement and correction.

Require bidders to disclose deviations. A product may have different BUG ratings at different lumen packages or optics; request the exact offered configuration.

Verify Installation and Controls

At handover, inspect model, optic, mounting height, arm, tilt and rotation. Compare them with the approved schedule. Test scenes and curfew. Night observations should include critical boundaries and routes under documented weather and operating conditions.

If a complaint occurs, use the as-built record to reproduce the scene. Do not respond by turning off safety-critical lighting without review. Options can include re-aiming within approved limits, shields, output adjustment or layout change, followed by recalculation.

Review street and area lighting applications and ZCLED products for candidate families. Send the adopted criteria and site geometry through the contact page.

The final BUG rating lighting schedule should remain with the asset record because future substitutions can change all three components.

Build a Municipal Compliance Matrix

Create one row for each lighting zone, fixture family and operating scene. Record the adopted rule, permitted B/U/G value, offered rating, lumen package, mounting and tilt, boundary criterion, curfew and evidence reference. Include a column for exceptions and approving authority. This makes mixed-use projects easier to review than a single site-wide statement.

Separate luminaire evidence from site evidence. The photometric report and rating belong to the product configuration. Property-line calculations, observer studies and curfew schedules belong to the project. Field measurements and tilt surveys are installed evidence. A reviewer should be able to move from one layer to the next without assuming that a product report proves the site.

For phased developments, calculate the credible completed condition as well as the first phase. A boundary that is dark today may receive contributions from later poles. Temporary construction lighting may need a different control plan. State which phase each table represents.

Handle Exceptions Without Weakening the Bid

Some safety tasks may need output or distribution that exceeds a general screening limit. Require the designer to identify the task, alternatives considered, calculated impact, controls and approving authority. Limit the exception to the necessary product and operating scene.

Use curfews and adaptive output carefully. A reduced scene may lower impact when activity declines, but transition, override and failure state must be explicit. Emergency response should not depend on a password or cloud connection. Keep a local operating method and record every commissioned level.

A robust BUG rating lighting specification also defines complaint handling. Record location, observer direction, time, weather and active scene. Verify product orientation before changing output. Corrective work should preserve required safety and be followed by calculation or measurement as applicable.

Maintain Ratings Through Procurement

Optic, lumen package, shield and tilt can affect the offered evidence. Require a revised compliance matrix for substitutions. Delivery inspection should compare labels and order codes with the approved schedule. Installation teams need drawings that show forward direction and maximum tilt.

At handover, provide editable calculations, photometric files, scene settings and an asset list. Train maintenance staff to identify the approved configuration. The second use of BUG rating lighting is lifecycle control: it helps prevent a future replacement from silently increasing backlight, uplight or high-angle output.

The ZCLED Knowledge Center contains related articles on intrusive light, full cutoff, glare and controls. Local ordinances and the authority's interpretation remain decisive.

Frequently Asked Questions

Municipal review should also cover maintenance scenarios. Ask what happens when a shield is removed, a failed driver is replaced, a tree is pruned or a pole is hit and rebuilt. These events can change the accepted light distribution without changing the planning permission or road geometry. Link work orders to the asset schedule and require a technical review when the optic, output, arm or tilt changes.

For public communication, describe measurable controls rather than promising “no impact.” State the operating scene, curfew, orientation and complaint process in plain language. Residents can then report a reproducible location and time, while the municipality can compare the observation with the approved calculation. Transparent evidence improves trust without implying that one rating eliminates every form of obtrusive light.

Does U0 mean there will be no sky glow?

No. U0 indicates no direct uplight in the relevant tested zones for that luminaire configuration and orientation. Light reflected from roads, walls and other surfaces can still contribute to sky glow. Installed tilt, total site output and other sources matter. Pair U limits with task-based design, output control and curfew where appropriate.

Does B0 guarantee zero light at a property line?

No. Backlight rating is based on lumens in angular zones behind the luminaire. Property-line illuminance depends on distance, height, orientation, terrain and contributions from multiple fittings. A B0 product may help, but the project still needs a boundary calculation and, where specified, site measurement under the accepted scene. Document installed orientation.

Is a lower G rating always better?

Lower high-angle output can reduce one glare risk, but the luminaire must still provide required visibility and uniformity. An optic with very low high-angle intensity may require different spacing or output. Use the lowest practical rating consistent with the application, then verify critical observer views and the complete lighting calculation.

Can a luminaire's BUG rating change with wattage?

It can change with lumen package, optic, distribution or other configuration because the zonal lumens change. Do not accept a family-level rating without the exact order code and photometric file. If a driver is programmed to another output, confirm how the manufacturer reports the rating and keep the approved configuration in the schedule.

Is “dark-sky compliant” enough for a tender?

No. The phrase needs a named programme, ordinance, version and product scope. Municipal tenders should state measurable B/U/G, uplight, boundary, output and control requirements. Check current programme rules and exact model listings. A logo or marketing phrase does not replace a project calculation or legal review. Keep the cited version in the tender.

What should ZCLED receive for a BUG review?

Provide the site plan, pole coordinates, mounting and tilt, property lines, sensitive receptors, adopted lighting zone, required BUG limits, task criteria and controls. ZCLED can supply model-specific photometry and ratings where available. The responsible designer and municipality approve applicability, calculations and installed compliance. Include the ordinance edition and exception process.

Sources and Evidence Boundary

1. IES, TM-15 BUG Ratings Addendum.
2. FHWA, Roadway Lighting Details.
3. FHWA, Lighting System Selection.

Confirm the adopted ordinance and current standard version. A BUG rating is not by itself proof of installed-site compliance.