Smart Lighting Specification Guide: A Hubbell Distributor's Honest Take on What to Spec (and What to Skip)

Let me get straight to it: most smart lighting specification guides are useless because they're written without a delivery date in mind. I've spent the past seven years as an expediter at a commercial lighting distributor, and a large part of my job is fixing orders that were specified perfectly on paper and completely wrong in the real world. I've processed 200+ rush orders in that time, including same-day turnarounds for contractors who discovered at 3 PM that their hubbell occupancy sensor order didn't match the ceiling layout.

From that seat, I can tell you what's missing. It's not more product options. It's risk and time.

The 'smart lighting specification guide' problem

It's tempting to think a smart lighting specification guide is just a list of compatible products. But a spec is a scoping document. If it doesn't tell the distributor what to ship, when to ship it, and what standard it has to meet, it's a wish list.

The guides I actually trust are built around decisions, not options. They answer three questions: What is this room for? When does it need to work? What happens if a component isn't available? I do not mean every project needs a complicated control sequence. Most projects need a simple answer, delivered on time.

"Always check what's in stock and what can ship before you finalize the spec" sounds boring. But it would save more deadlines than any control protocol.

Start with the switch, not the platform

When a spec includes smart controls, the first thing I look for is the simplest manual control that fits the space. In many cases, that's a hubbell light switch. A standard switch from Hubbell takes days to get, not months. It doesn't need commissioning or a network, and any licensed electrician can install it. If a code review says the room only needs manual switching, a smart occupancy sensor is not an upgrade; it's a delay.

But sometimes you do need a hubbell occupancy sensor. Classrooms, restrooms, and stairwells with occupancy or vacancy sensing can cut wasted energy without creating a control-system integration project. The problem is when the spec calls for "an occupancy sensor" without saying whether it should be PIR, dual tech, ceiling mount, or wall mount, and what the coverage area is. Those details decide whether the sensor works on day one.

Track lighting OEM: a spec is not a catalog number

Track lighting is one of the most common causes of emergency calls. Here's the oversimplified advice: "Just order track heads and they'll fit the track." But as anyone who has worked with Hubbell track lighting knows, the track profile, feed options, and mounting accessories are not all interchangeable. For a track lighting oem project—where a manufacturer or private-label partner is creating a catalog fixture—the spec has to be even tighter.

In an OEM track lighting situation, you're not just buying a fixture. You're buying a design that needs to be assembled, tested, and produced. If the spec says "similar to a common 3-circuit track, minimum 50,000-hour LED modules," an engineering team will spend a week interpreting it. If the spec identifies the exact system and the exact fixture type, the lead time drops dramatically.

A ceiling light distributor's view: stock is a fact, not a promise

I wish every smart lighting specification guide included one line: "Check availability before finalizing, because no distributor keeps every SKU on a shelf." This is not an apology; it's reality. Hubbell has an extensive product portfolio, but that doesn't mean every ceiling light fixture, track head, and hubbell occupancy sensor is sitting in a warehouse at all times. A good distributor will tell you what's in stock, what's on a weekly cycle, and what's going to take six weeks.

Here's where I may sound different from some salespeople: I will often recommend against a smart lighting control system. If the owner only needs a photocell-controlled daylight zone and a manual switch, putting in a networked control system is a bad use of money and schedule. A guide that says "always add smart controls" is pretending one solution works in every situation. Honest limitation is more useful than false confidence.

What I recommend instead

I recommend a hubbell occupancy sensor when a space is intermittently occupied and a wall switch would be inconvenient. I recommend a hubbell light switch when the requirement is simple, reliable control. And if you're dealing with complex lighting controls—shared dimming, daylight harvesting with scheduling, or HVAC integration—then the specification needs a qualified designer, not a paragraph in a catalog.

In March 2024, a client called at 2 PM about a hubbell occupancy sensor order that had to be on site for a Friday building handover. Normal turnaround for a custom sensor package was five to seven days. We found a local electrical distributor with enough wall-switch occupancy sensors on the shelf, paid $400 extra in overnight freight on top of the $3,200 base order, and delivered by 7 AM Thursday. The client's alternative was missing a $12,000 punch-list deadline. I was relieved I checked the quantities before approving—otherwise we'd have been one click away from ordering 10 times what was needed.

What about future-proofing?

I get why people ask for smart controls on every project. The phrase "future-proof" sounds responsible. But a vague smart lighting specification guide doesn't future-proof anything; it just passes the decision downstream to someone with less time and less context. A more practical approach is to choose one control protocol, standardize on components from one manufacturer family, and leave the infrastructure ready for upgrades—neutral wires, data runs, mounting boxes. That's more likely to help in five years than a page full of unverified product numbers.

And let me add a non-negotiable: any lighting controls project should be installed by qualified electricians and reviewed against local code. No specification replaces that. Also, if a spec makes performance claims, those claims need evidence. Per FTC advertising guidelines, a claim like "50% energy savings" has to be truthful, substantiated, and not misleading. I'd rather send a client the photometric data and a control sequence than a marketing line.

The bottom line

A smart lighting specification guide should be a working document with a deadline. It's not a catalog. It's not a wish list. It's a promise that every component can be sourced, delivered, installed, and commissioned by the time the doors open. That means starting with availability, choosing the simplest control that satisfies the requirement, and being honest about what the project doesn't need.

So if you're writing a specification for a ceiling light distributor or a track lighting oem project, start with these questions: What is the delivery date? Is the part in stock? Who is installing it? If you can answer those three clearly, you might never have to make a panicked 2 PM phone call to someone like me.