Technical note for lighting designers, facade engineers and planning consultants. Exterior architectural lighting is increasingly assessed not only on how a building looks after dark, but on what it sends into the sky and into neighbouring windows. A hotel facade that photographs beautifully at 9 p.m. can still fail a planning condition, disturb guest rooms, or trigger a late-night complaint from an adjacent residential block. The specification problem is that "dark-sky friendly" is not a product property; it is a set of measurable outcomes produced by luminaire distribution, aiming, mounting geometry, control scheduling and commissioning discipline. This note sets out how to write those outcomes into a submittal so they can actually be checked.
Most obtrusive-light frameworks (for example the IES/IDA model lighting ordinance guidance and CIE 150 zoning work) define environmental zones — from intrinsically dark rural areas to high-activity urban centres — and set allowable limits by zone and by time of night. Before selecting any luminaire, establish the project's zone and the curfew hour written into the consent. The same wall-grazer is acceptable in a dense commercial district at 20:00 and unacceptable in a coastal resort zone after 23:00. Record the zone, the curfew, and the applicable limit table in the basis-of-design document; a submittal that omits them cannot be evaluated for compliance. Also identify sensitive receptors explicitly: nearby bedrooms, a sea-turtle nesting beach, an observatory, an airport approach, or a protected habitat each impose a different constraint.
The IES BUG (Backlight – Uplight – Glare) rating derived from TM-15 and its addenda summarises the luminaire's zonal lumen distribution. For facade work the U value is the obvious one, but the other two matter just as much:
U0 (no uplight at all) for facade-mounted equipment, with any deliberate architectural uplight treated as a separate, tightly controlled and curfew-switched circuit.Require the full BUG rating plus the zonal lumen table in the submittal, not merely a marketing "dark sky approved" badge. A product can carry a third-party dark-sky listing by virtue of its U value while still producing significant G flux at the aiming angle actually used on site — the rating is distributional, and aiming changes the effective distribution.
Zero-uplight performance depends on how the fixture is mounted. A luminaire rated U0 in its native orientation becomes an uplight source if it is tilted beyond its designed range, mounted on a soffit with the wrong bracket, or installed upside down to reach a setback. Specify: the exact tilt range allowed by the photometric file, a positive mechanical aiming stop or protractor marking, a mounting detail showing the relationship to the facade plane, and a shield or baffle where the beam would otherwise spill above the parapet. For grazing applications, note that a narrow beam aimed close to a textured wall produces substantial inter-reflection: even with U0 direct flux, reflected light can leave the facade upward. A simple calculation or a mock-up with a calibrated camera is worth more than an assumption that the beam "stays on the wall".
Almost every obtrusive-light regime becomes stricter after a curfew. The robust approach is a scheduled scene change rather than a manual instruction to "turn it down". Specify an astronomical clock or BMS-driven schedule with at least three states: full pre-curfew scene, reduced post-curfew scene (typically a defined percentage of initial output, with decorative and uplight circuits off), and an event override that requires manual release and auto-reverts. State the target illuminance or dimming level for each scene and require the commissioning engineer to demonstrate the transition on site with a timestamped log. Where a DALI-2 or DMX512 control system is used, verify that the dimming curve remains flicker-free at the low end (see IEEE 1789 and PstLM/SVM considerations), because a curfew scene that dims to 10% using a low-frequency PWM driver can create a visible flicker problem while technically meeting the light-limit condition. Also check the failure state: after a power cycle or controller fault, the system should default to the post-curfew scene, not restore full output at 2 a.m.
Compliance is measured at the boundary or the receptor, not at the luminaire. Require a calculation grid showing vertical illuminance at the nearest sensitive facade or property line, both pre- and post-curfew, with the limit value quoted alongside. For a hotel, add an internal check: guest-room windows directly above or beside an illuminated facade element can receive reflected or direct light even when the external boundary passes. Window recesses, balcony soffits and internal blinds are mitigations, but they should be modelled rather than assumed. Where the project is near a coastline or protected habitat, add spectral considerations — short-wavelength-rich sources scatter more and are commonly restricted to warmer correlated colour temperatures (often 2700 K or lower, and in some jurisdictions 2200 K or amber) with explicit limits on content below 500 nm. A "warm white" label is not a spectral specification; ask for the SPD or at least a declared CCT with a documented bin and tolerance.
| Item | Evidence to request | Typical failure |
|---|---|---|
| Zone & curfew | Planning condition extract + basis-of-design note | No curfew defined, so no reduced scene exists |
| BUG rating | Full B/U/G values + zonal lumen table + IES/LDT file | Only a logo or a single U value quoted |
| Aiming | Mounting detail, tilt limits, shield/baffle schedule | Field-adjusted tilt silently exceeds U0 envelope |
| Post-curfew scene | Scene table with dim levels + automatic revert + fault default | Manual dimming only; full brightness after power loss |
| Trespass | Vertical illuminance grid at boundary and guest windows | Calculation stops at the building line |
| Spectrum | CCT with bin/tolerance, or SPD where habitat rules apply | 4000 K facade in a 2700 K restricted zone |
| Commissioning | Night-time aiming record, timestamped scene log, as-built photos | Design intent verified only in rendered images |
Obtrusive light is one of the few facade-lighting failures that surfaces only after handover, when the building is occupied and the planning authority receives a complaint. Retrofitting shields, re-aiming hundreds of fixtures on a rope-access crew, and re-programming a control system costs far more than specifying the constraints at submittal stage. The practical discipline is to make each requirement measurable and to attach it to a document that already exists in the workflow: the photometric file, the control scene schedule, the calculation grid and the commissioning record. Teams at Topeng Lighting treat the curfew scene and the aiming schedule as part of the luminaire submittal rather than as an afterthought, and that is the sequence worth asking any facade-lighting bidder to demonstrate.
A dark-sky compliant facade is the result of a U0 distribution, a physically constrained aiming geometry, a scheduled and fail-safe curfew scene, and a boundary-level calculation that someone actually checked at night. Each of those can be written into a submittal as a verifiable line item. For project-specific photometric files, aiming schedules and control-scene documentation for architectural facade luminaires, see the technical resources at www.topenglighting.com.