-
1. What's the mistake that costs the most on exterior lighting orders?
-
2. Is a model number enough on a BEGA wall luminaire spec?
-
3. Outdoor downlights: what actually goes wrong in a soffit?
-
4. Why do spotlights look right in the catalogue and wrong on site?
-
5. What size flood light do I actually need?
-
6. What's the question almost nobody asks?
-
7. How do I stop repeating these mistakes?
I've handled BEGA orders for nine years. In that time I've made three mistakes that cost real money — about $4,100 total across them — and every one of them was avoidable. Now I keep the team's pre-order checklist, and these are the questions that come up most often from people who are about to make one of the same mistakes.
1. What's the mistake that costs the most on exterior lighting orders?
Finish and environment mismatch. Not model numbers, not lead times. Finish.
In the spring of 2021 we supplied about 40 wall luminaires to a project roughly 300 meters from open water. On the order I wrote "standard finish." The architect read "standard finish" and assumed marine-grade, because it's a beachfront project and that's obvious. We both thought the other person had specified it. Nobody had.
Fourteen months later the backplates were pitting. That ran $2,300 to recoat and reinstall plus a week of site time, and it cost me more credibility than the dollar figure suggests.
Here's the thing about corrosion: ISO 12944 classifies environments from C1 (very low) to C5 (very high), with C5-M specifically for coastal and marine exposure. A standard polyester powder coat isn't the same conversation as a C5-M-rated system. Salt spray doesn't care that the project is "near the ocean" in a marketing deck. It cares what's on the metal.
If a project is within a few kilometers of salt water, put the corrosion class in writing on the order. Not "coastal," not "marine environment" — the actual class.
2. Is a model number enough on a BEGA wall luminaire spec?
No. A model number tells you the housing and the distribution. It doesn't tell you whether the thing will actually mount on the wall you've got.
Four things I check every time now:
- Backplate vs. junction box. The backplate footprint has to cover the box and land on flat substrate. On a ribbed metal panel, it won't. You need a mounting plate or a spacer, and that's a separate line item nobody puts in the quote.
- Up/down distribution. "Wall luminaire" covers everything from a soft asymmetric wash to a hard two-way graze. Get the photometric file, not the catalogue photo. Catalogue photos are lit for drama.
- Driver location. Integrated drivers are easier to install and harder to service. Remote drivers are the opposite. Decide which problem you'd rather have — before the wall is closed up.
- Color temperature and dimming protocol. 2700K vs. 3000K vs. 4000K on the same facade reads very differently at night. And "dimmable" means nothing until you say 0-10V, DALI, or phase-cut.
3. Outdoor downlights: what actually goes wrong in a soffit?
Three things, in order of frequency: heat, water, and access.
Heat. Recessed downlights go into cavities that are sometimes insulated and sometimes not. If the fixture isn't rated for insulation contact, you've got a thermal problem that shows up as premature lumen depreciation — the fixture works, it just gets dimmer faster than the LM-80 data suggested. LED lumen maintenance is tested per IES LM-80 and extrapolated under TM-21, and both assume the thermal conditions the fixture was designed for. Bury it in insulation and that assumption is gone.
Water. IP ratings work in one direction. An IP65 downlight in a soffit is protected against jets from below. It isn't automatically protected from condensation forming on the cold side of the housing in an unventilated cavity. I've seen water sitting inside a perfectly good IP66 fixture because the soffit had no ventilation and the temperature differential did the rest.
Access. If the driver fails in year four, can someone reach it without cutting drywall or scaffolding a three-story facade? Ask that question before you approve the submittal. I didn't, once. Once was enough.
4. Why do spotlights look right in the catalogue and wrong on site?
Beam angle and distance. That's almost always it.
A 10° spot at 3 meters covers a circle roughly 0.5 m across. The same fixture at 6 meters covers about 1 m — and delivers a quarter of the illuminance, because the inverse square law doesn't negotiate. So the fixture that looked dramatic on a 2 m mockup looks like a faint dot on the actual 7 m facade.
Two more things that bite people:
Voltage drop on low-voltage runs. Landscape systems under NEC Article 411 run at 30V or less, and DC voltage drop is not a rounding error. On a long 24V run at high current, the last fixture in the chain can be visibly dimmer than the first. Size the conductor for the load at the end of the run, not the beginning. And use UL 1838-listed fixtures for low-voltage landscape — that listing isn't decorative.
Glare control. A spotlight aimed at a facade is also aimed at somebody's eyes if the accessories aren't specified. Glare shields, honeycomb louvers, snoots — these aren't upsells. They're the difference between a design that gets approved and one that gets a complaint. IES RP-33-14 on exterior lighting environments is a reasonable place to start the shielding conversation.
5. What size flood light do I actually need?
Do the math. It takes four minutes and it prevents the most common sizing error, which is buying by wattage.
The formula:
Delivered lumens = (target foot-candles × area in sq ft) ÷ (coefficient of utilization × light loss factor)
Say you want 2 fc average across a 30 × 20 ft area — 600 sq ft. Use a CU of 0.75 and an LLF of 0.8 (both conservative for outdoor flood).
(2 × 600) ÷ (0.75 × 0.8) = 1200 ÷ 0.6 = 2,000 delivered lumens.
Now here's the part people skip: 2,000 delivered lumens, not 2,000 lumens from a spec sheet written in a language nobody verified. Delivered lumens should come from an LM-79 test report for that specific fixture. "Equivalent to 250W" is not a photometric claim. It's marketing.
And if the area is 1.5 fc instead of 2 fc, you need 25% less light. If your surfaces are dark asphalt instead of concrete, you need more. There's no universal answer — which is why "what size flood light do I need" has no universal answer either.
6. What's the question almost nobody asks?
Driver and control compatibility. It's the least glamorous question in the whole project and it's the one that generates the most site visits.
Specifically: what protocol is the control system actually running? I've seen a spec call out "DALI dimming" on the fixture schedule and "0-10V" on the controls schedule, on the same project, one page apart. Both were approved. Neither worked together.
Also worth asking: how many drivers per circuit, and what's the inrush current? Put twenty fixtures with high-inrush drivers on one breaker and it'll nuisance-trip, and the electrician will blame the fixtures for a week before anyone checks the numbers.
And order the spare drivers with the original PO. Not later. Lead times on drivers don't improve with age.
7. How do I stop repeating these mistakes?
I built a checklist. It's unglamorous and it works.
Six items, applied to every order before it's released:
- Corrosion class stated in writing, matched to site distance from salt water.
- IES photometric files requested — not PDFs, not catalogue images — and aimed on a mockup or a quick calc.
- Control protocol confirmed against the controls schedule, not the fixture schedule.
- Mounting surface and junction box verified dimensionally against the backplate drawing.
- Driver accessibility confirmed with whoever has to service it in year five.
- Delivered lumens and wattage taken from LM-79 data, not from a marketing page.
That's it. Six lines.
The measurable part: our order-to-release turnaround went from about five days to two, because we stopped cycling submittals back and forth over questions that should have been answered on day one. The errors didn't get caught faster. They stopped happening. We've used this list on roughly 200 orders since mid-2022 and I can count the rework incidents on one hand.
Efficiency in this business doesn't come from working faster. It comes from not doing the same job twice. Looking back, I should have built the checklist after the first costly mistake instead of the third. At the time, each one felt like a one-off. They weren't. They were all the same failure — something important stayed implied instead of getting written down.
Write it down. Then you can stop being the person who learns the hard way.