A Procurement Manager’s 5-Step Checklist for Specifying Smart Lighting Systems

Who This Checklist Is For

If you’re a facility manager, an electrical contractor, or a procurement lead tasked with upgrading a commercial space to smart lighting, this is for you. Specifically, this checklist is for the person who has to justify every line item in the budget to a finance director who doesn’t care about “ambient intelligence” but cares a lot about ROI.

I’ve managed procurement for a mid-sized property management firm for about 6 years—well, 5 years and some months, give or take. We oversee roughly 40 commercial units. In that time, I’ve specced and re-specced lighting systems more times than I can count. Some wins, some lessons. This checklist is the result of those lessons.

We’ll walk through 5 steps. Step 4 is the one most people overlook. It cost us a redo once, and I’d rather you avoid that.

Step 1: Define Your Zone Requirements, Not Just Room Requirements

This sounds basic, but I’ve seen it go wrong. Don’t just think “office” or “lobby.” Think in terms of zones that have different usage patterns and therefore different control needs.

• Open plan areas: Need occupancy-based dimming, not just on/off. A system like Panasonic’s Zigbee-based controls can handle this with individual sensor nodes.
• Corridors & restrooms: Low traffic, high need for energy savings. Motion sensors with a time delay are your friend.
• Conference rooms: This is where it gets tricky. They need multiple scenes (presentation, video call, brainstorming). A simple switch won’t cut it.
• Break rooms & kitchens: Typically overlooked. They benefit from basic occupancy control but don’t need the complexity of a conference room.

Checkpoint: Before you look at a single product spec, draw a rough floor plan and label each zone with its primary control need (on/off, dim, scene, scheduled). This prevents you from over-speccing a simple space or under-speccing a complex one.

Step 2: Separate the Wireless Protocol Hype from Reality

You’ll hear a lot about Zigbee, WiFi, Bluetooth Mesh, Thread, Matter… Honestly, it can be noise. The bottom line for a B2B spec is: what is the installed device ecosystem, and what is the long-term support path?

From my perspective, Zigbee is a solid choice for commercial retrofits right now. Why? It’s mature, has a low power footprint, and devices from different brands can talk to each other if they’re certified. Panasonic uses it in a lot of their smart downlights and controls, which is a practical advantage for a system purchase.

That said, WiFi-based controls are simpler to set up if you’re managing a small space (under 5 zones) and don’t have a dedicated IT network for IoT. But for anything larger than that, Zigbee (or a purpose-built mesh network) is usually more reliable. The conventional wisdom is “WiFi is everywhere, so it’s easiest.” In practice, WiFi interference in a dense commercial office can be a headache. Zigbee lives in a different frequency band, which helps.

Checkpoint: Ask your vendor: “Is this protocol supported for at least 5 years from installation?” Push for a written answer. One supplier’s “future-proof” is another supplier’s “we discontinued the hub last year.”

Step 3: Verify the TCO of the “Free” Hub or Gateway

Here’s where the cost control hat comes on. Smart lighting systems almost always require a hub or gateway. Some vendors include it, some sell it separately, and some bury it in the “system” price.

I recall evaluating a system from Vendor A a couple years ago. Their quoted price per downlight was lower than a competitor’s. We almost signed. Then I asked about the hub. “Oh, it’s included,” they said. Was it, though? When I pressed, turns out the base system price covered a basic hub with no remote access. The hub with cloud control and scheduling capabilities? That was $350 extra.

That ‘free setup’ offer basically cost us more in hidden fees—or rather, it would have, had we not caught it. I built a cost calculator after getting burned on hidden fees twice, and a “free” hub that isn’t the right hub is a classic example.

Checkpoint: List every single component in the quote. If the hub/gateway isn’t itemized, ask why. Calculate the total system cost including the hub, not just the cost per unit. The difference can be 10-15% on the total project.

Step 4: Plan for the Sensor Floorplan (This is the Overlooked One)

I mentioned Step 4 is the one most people miss. Here it is: Where do the sensors go, and what do they see?

Everything I’d read about smart lighting said “just put sensors in the ceiling grid.” In practice, we installed a system in a 10,000 sq ft open-plan office. The sensors were mounted in the center of each light module. Looked great on the spec sheet. Problem? The sensors were PIR (passive infrared) and their coverage pattern didn’t reach the desks near the perimeter walls. People would sit perfectly still, the sensor would think the zone was empty, and the lights would dim to 20%. Cue angry emails to facilities.

We had to retrofit additional wall-mounted sensors, which added cost and looked messy. If I could redo that decision, I’d invest in better specifications upfront—actually, I’d do a walk-through with a sensor coverage map before ordering a single fixture.

Honestly, I wasn’t expecting that to be the issue. I thought the hard part was the wireless protocol. The hard part turned out to be physics.

Checkpoint: For each zone, sketch the sensor placement and confirm the coverage pattern (manufacturers usually provide a spec sheet for this). Account for cubicle walls, tall furniture, and glass partitions. If the room has a lot of static occupants (e.g., accounting desks), consider a dual-tech sensor (PIR + ultrasonic) or a simple time-scheduled override.

Step 5: Build a Service Contract Clause, Not Just a Warranty

A warranty covers defects. A service contract covers “this thing stopped talking to the network and we don’t know why.” Smart lighting systems are great until they’re not, and when they’re not, the trouble isn’t usually a burnt-out LED—it’s a control issue.

We’ve got a system from 2022 that uses a proprietary hub. The hub died 18 months in. The warranty covered the replacement hardware, but the labor to re-pair 40 devices? Not covered. That cost us a service call fee plus an hour of a technician’s time. Not catastrophic, but it added up. I now write a clause that says “remote troubleshooting included for first year, on-site labor for control issues capped at $X.” It’s a small thing that saves arguments later.

Checkpoint: Ask the vendor: “If a single fixture stops responding to the group command, what is the diagnostic process? Is there a remote tool, or does someone need to climb a ladder?” Get it in the service agreement, not just the product manual.

Calculated the worst case: a full system re-pair could be $500 in labor. Best case: a quick reset. The expected value is somewhere in the middle, but having the clause in writing removes the uncertainty. For a $4,200 annual contract on a small building, that’s worthwhile.

Common Mistakes I’ve Seen (And Made)

• Ignoring the IT department. Smart lighting sits on the network. If your IT team doesn’t approve the hub or the WiFi band, your project stalls. Involve them at Step 1.
• Assuming “retrofit” means plug-and-play. It often doesn’t. Verify the junction box compatibility. Panasonic’s fan-light combos, for example, have specific mounting requirements that differ from a basic fixture. It’s manageable, but skip the assumption.
• Over-relying on the cheapest bid. To be fair, budget pressures are real. But the hidden costs from a poorly specced control system (labor for rework, frustrated tenants) can wipe out any savings. I learned this the expensive way in Q2 2023.

This was accurate as of February 2025. The smart lighting market moves fast—especially with Matter protocol gaining traction—so always verify current compatibility lists. But the five steps above? They don’t change. They’re about process, not about the latest tech version. And process is what saves you the rework.