HOA Approval Success: Laser Fixture IES File Guide

“Will these lights actually make our street safer—or just turn our bedrooms into night-shift offices?”

That’s the question I heard—*twice*—in the first 90 seconds of the second HOA meeting about streetlights. Not “How much do they cost?” Not “Who maintains them?” But: *What will this light do to my sleep, my view, my kid’s room facing the curb?* The first vote failed. Badly. Because we led with specs—not stories. With wattage instead of windows. With “dark-sky compliant” as a slogan, not a demonstrable condition. So we started over. Not with brochures. With photons.

We built the neighborhood—in software

Using AGi32, we modeled every existing pole location, every tree canopy height (yes, we measured), every house elevation and window sill height. Then we imported two IES files: one for the HOA’s original 4000K, 60W LED shoebox (the kind that throws light *up*, not down), and one for the proposed 2700K, 35W full-cutoff cobrahead—mounted at 18 feet, aimed precisely 15° below horizontal. The magic wasn’t in the “before/after” renderings—it was in the *data layers* we toggled on demand: - A heat map showing horizontal illuminance *at the bedroom window plane* (not the street!): 0.8 lux for the old fixture vs. 0.22 lux for the new one—well under ALA Model Lighting Ordinance §4.2’s 0.20 lux *maximum* at habitable room openings. (We noted the slight overshoot was due to an adjacent driveway light—not the streetlight—and offered to retrofit that too.) - A skyglow overlay comparing upward light emission: 12% ULR (upward light ratio) for the approved fixture vs. 38% for the rejected one. That number landed hard when paired with a photo of the Milky Way taken from the subdivision’s back trail—*before* the old lights went in. - A pedestrian visibility simulation at 5 mph: same footcandles on the sidewalk (12 fc), but with 63% less glare—measured using AGi32’s unified glare rating (UGR) output.

No more “trust us.” Just point, click, and show

At the third town hall, we didn’t hand out flyers. We brought a tablet and pulled up a live AGi32 session. When Mrs. Chen asked, “What about my daughter’s west-facing window on Sycamore?” we typed her address, clicked “view at window plane,” and showed her the lux reading—and the soft, even wash of light on the sidewalk just beyond her lawn. No spikes. No blue halo. Just amber-toned, ground-directed light. That moment shifted the room.

Talking points that stuck (and why)

• “This isn’t about dimming the street—it’s about sharpening the contrast.” Our old lights washed out shadows; the new ones preserve depth perception. Pedestrians and drivers see *shapes*, not just brightness.
• “Your window isn’t a test point—we modeled it. Literally.” We shared a QR code linking to a public folder with every home’s individual illuminance report (PDF + AGi32 snapshot). No exceptions. No abstractions.
• “Compliance isn’t a checkbox—it’s a calculation.” We printed ALA §4.2 side-by-side with our photometric report: “Maximum allowed at openings: 0.20 lux. Measured worst-case at any habitable window: 0.22 lux. Mitigation plan attached.” Transparency disarmed suspicion.

One last thing—the human part

I think what finally moved the board wasn’t the data alone. It was pairing each metric with a neighbor’s voice: *“This is Mr. Diaz’s porch light—now documented, not debated.”* *“This is the spot where Maya walks her dog at 6 a.m.—illuminated, not blinded.”* *“This is the sky your grandkids should still recognize.”* The vote passed 14–1. Installation starts next month. And yes—we’re sharing the AGi32 model files, the IES library, and the script template with three neighboring HOAs. Because dark-sky approval shouldn’t require a civil engineering degree. Just clarity. And light that knows where to land.