How does lighting procurement work for office projects?
Office lighting looks commodity-simple — linears, downlights, troffers — but the package's real complexity lives in the controls layer: networked systems, daylight and occupancy response, and energy-code documentation that must all commission together at the end of a TI schedule with no float. The procurement risks are compatibility gaps between fixtures and controls bought separately, code-triggered rejections at inspection, and channel markup hiding inside integrated-fixture pricing. Owner-side procurement buys fixtures and controls as one verified package at net-plus-fee, with compliance documentation included.
The controls layer is the real package
Modern office lighting is a networked system wearing fixture costume: drivers, sensors, controllers, and software that must interoperate across every manufacturer on the schedule. When fixtures come from the EC's distributor and controls from a separate vendor, nobody owns compatibility until commissioning fails — the classic office-project lighting disaster, discovered two weeks before move-in.
Procurement is the natural place to close that gap: buying fixtures and controls under one contract means dimming protocols, driver pairings, and sensor coverage get verified at submittal, not at commissioning. Integrated fixtures also carry growing shares of package cost — and their configured pricing is exactly where channel overage hides most comfortably.
Codes set the floor — and the paperwork
Energy codes — Title 24 in California, ASHRAE 90.1-based codes elsewhere — dictate lighting power density, controls behavior, and commissioning documentation. Compliance isn't a design nicety; it's an inspection gate. A substitution that saves $30 a fixture and quietly breaks the LPD calc or drops a required control function costs a re-submittal cycle at best and field rework at worst.
This is why office substitution review needs code literacy, not just photometric comparison — and why compliance documentation should ship with the submittal package rather than being reconstructed at closeout.
TI schedules: compressed, unforgiving, repeated
Tenant-improvement work is office lighting's home turf, and TI schedules run in weeks, not quarters. There's no float for a six-week submittal relay or a surprise 12-week lead on specified linears — which is how TI specs get gutted into whatever the distributor stocks. The procurement counter: price and release fast, verify lead times before the schedule is promised to the tenant, and hold the spec with side-by-side designer-approved substitutions when a line genuinely can't make the date.
For landlords running repeated TIs, building-standard fixture schedules bought at program pricing turn each fit-out from a bespoke scramble into a repeatable package — the same portfolio effect multifamily developers capture.
How BLS runs office packages
Fixtures and controls priced together at net-plus-fee, compatibility checked at submittal, energy-code documentation included, and releases tracked line by line against the TI or core-and-shell schedule. Owner-direct structure removes the standard ~15% of channel markup — meaningful on core-and-shell, decisive across a landlord's TI program. Part of $847M procured across 2,400+ projects and 180+ manufacturer lines, with procurement timelines cut by up to 40%.
Related questions, answered
Should lighting controls be bought with the fixtures or separately?
Together, almost always. Split procurement is the root cause of most commissioning failures — mismatched dimming protocols, uncovered zones, driver incompatibilities. One buyer verifying the integrated system at submittal costs nothing extra and removes the project's ugliest late-stage risk.
Who owns lighting in a TI — landlord or tenant?
It follows the lease: landlord in turnkey and building-standard deals, tenant in allowance deals. Either way the economics are identical — whoever holds the buy captures the markup savings, and building-standard schedules bought at program pricing benefit both sides across the term.
Can specified office lighting really make a 10-week TI schedule?
Usually, if procurement starts with the design instead of after permit. Most spec-grade linear and downlight product runs 6–12 weeks — makeable with immediate release and submittals issued same-week. What breaks TI schedules is the conventional sequence, not the lead times.
How does daylighting affect the fixture buy?
Daylight-responsive zones add sensors, zone-specific drivers, and commissioning requirements that must match the fixture configuration codes on the schedule. It's a line-level detail — one more reason submittal verification should happen against the schedule by someone fluent in the catalog strings.