A hotel's public and back-of-house lighting — corridors, stairwells, lobbies, meeting rooms, BOH offices, exterior and parking areas — is typically reviewed separately from guest-room controls, and the specific rules that apply (manual-on exceptions, daylight dimming, after-hours reduction) vary by jurisdiction and code edition. Rather than assume what applies, ask the project's electrical engineer of record and code consultant to confirm the sequence of operations for each space type before the control narrative is finalized. On the integration side, the practical work is making sure the installed system can be programmed, tested, and documented to whatever sequence the design team specifies — and that the paperwork handed over at closeout actually reflects what was built.
This article focuses on that second half: what an integrator needs before programming a public-space lighting system, and how a templated control platform makes it practical to apply the same tested sequence across many similar rooms. The code questions themselves — which spaces are exempt from manual-on requirements, how daylight sensors should be zoned near lobby glazing, what after-hours exterior reduction looks like — belong to the project's code consultant, not to this guide or to the integration platform.
Who decides what a hotel's public-space lighting controls must do?
The electrical engineer of record and the project's code consultant are the ones who determine which code edition applies and what each space type's control sequence must accomplish. That determination sits upstream of the integrator's work: the lighting designer sets fixture and zoning intent, the engineer writes the control narrative into the drawings, and the integrator programs and commissions the behavior that narrative specifies. Because adopted code editions and their exception language differ by jurisdiction, an owner's team should treat this as a project-specific question for every build rather than carrying forward an assumption from a prior property. Cave Group's hospitality services cover public-space lighting and control as part of a full technology scope, alongside guest-room automation, PMS integration, and networking, but the compliance determination itself comes from the design team of record.
What does an integrator need before programming public-space lighting?
Before programming begins, a lighting-control design needs a specific set of project information. Crestron's own guidance for designing a lighting control system calls for gathering the project location, a load or panel schedule indicating controlled lighting load types, the ballast types specified for dimming compatibility, which loads connect to emergency power, any spare circuits required, and other special considerations such as panel locations or breaker requirements (Lighting Control Interface). This is a pre-design checklist, not a code reference — but it is the information a commissioning agent or code official will eventually want to see tied back to as-built records, since it documents what was actually installed and how it's powered.
How does a templated system handle many similar hotel spaces?
A hotel corridor or meeting-room lighting scope usually involves applying the same control sequence to many repeated rooms, and a templated commissioning workflow is built for exactly that. On a system built on Crestron Zūm wired lighting control, a room or zone configuration can be saved as a template, then mapped and deployed to one or multiple rooms at once, edited afterward, or extracted from an existing room to reuse elsewhere (Manage Commissioning | Crestron Zūm Wired Lighting Control Manual). In practice, this means a sequence tested and approved in one corridor segment or meeting room can be applied consistently across the rest of the floor rather than reprogrammed room by room — useful once the code consultant has signed off on what that sequence should do.
What should an owner ask before signing off on the lighting-control design?
A few practical questions are worth raising with the integrator and code consultant together, before the control narrative is locked:
- Which specific spaces — stairwells, exit corridors, certain BOH rooms — does the code consultant consider exempt from any manual-on requirement, and is that documented on the drawings?
- For lobbies and public spaces with significant glazing, how does the design team want daylight-responsive dimming zoned, and how will that be tested once installed?
- For exterior and parking lighting, what after-hours schedule does the design team intend, and how will the integrator verify it once the building is occupied?
- What functional-test record will be handed over at closeout, and does it reference the same load schedule and room templates used to deploy the sequence?
These are design-team decisions that the integration platform executes and documents — not settings the platform decides on its own.
Frequently asked questions
Does the same lighting-control approach apply to guest rooms and public spaces?
Guest-room controls and public/back-of-house lighting are generally planned and reviewed separately, and guest-room PMS-driven setbacks are a distinct topic from corridor, lobby, or BOH lighting control — ask your code consultant how your jurisdiction's adopted code treats each space type.
Who determines which hotel spaces are exempt from manual-on lighting requirements?
That determination belongs to the project's electrical engineer of record and code consultant, based on the specific code edition adopted by the jurisdiction; it should be confirmed for each project rather than assumed.
What information does an integrator need before programming hotel lighting controls?
A load or panel schedule showing controlled lighting load types, the ballast types specified for dimming compatibility, which loads connect to emergency power, and any spare circuits or special panel requirements, per Crestron's published lighting control design guidance.
Can the same tested lighting sequence be applied across many hotel corridors or meeting rooms?
Yes. On a Crestron Zūm wired lighting control system, a room or zone sequence can be saved as a template and then mapped and deployed to multiple rooms, which supports applying a consistent, already-tested sequence across repeated space types.
What should a functional-test record for hotel public-space lighting include?
At minimum, it should reference the as-built load schedule and emergency-power connections documented during design and confirm that the installed controls perform the sequence specified by the design team for each space type — the code consultant or commissioning agent on the project can specify the exact format expected.