Use one shared zone when the same control response works for every area in it. Split an area into its own zone when its schedule or task means its lights need to work on their own. If you can't name that reason, keeping the areas together is usually the simpler plan.
The "one or two" framing is a starting point, not a cap. A larger facility may need several lighting control zones. Each split should still trace back to a schedule or task difference you can name.
When Should Areas Share or Separate Lighting Control Zones?
Ask one question about each pair of areas: would one control response serve both of them? If yes, keep them together. If one area needs its lights on, off, or set differently because of when or how it is used, it's a candidate for its own zone.
The hypothetical cases below show how that test plays out.
| Area pattern (hypothetical) | Proposed grouping |
|---|---|
| Two office sections, same hours, same desk work | Keep in one zone |
| Two rooms split by a wall, same hours and tasks | Keep in one zone |
| Warehouse floor runs two shifts; front office closes in the evening | Consider separate zones |
| Shop floor and inspection bench share hours, but the bench task needs its own lighting setting | Consider a separate zone for the bench |
| Storage room used now and then among areas on one schedule | Separate only if independent control solves a real need |
The second and fourth rows matter most. A wall is context, not a reason. Two rooms with the same hours and tasks can share controls just fine. Matching hours don't settle the question either. When a task calls for a different lighting response, separating it can make sense even if the clock is the same.
We use the same zone-by-zone logic in our guide to motion sensors versus manual switches. There, each zone's use decides its control type.
Map Area Use and Schedules Into Proposed Groups
Turn the facility into a simple planning record before you select equipment. A spreadsheet, a marked-up floor plan, or our online lighting layout tool works well to map spaces. Then follow these steps:
- List every area and its task. Write down what happens there, like picking, packing, desk work, inspection, or storage.
- Record the operating pattern. Note the hours, shifts, weekend use, and whether the area is used all the time or only now and then. A useful aim is to align schedules with occupancy patterns, so that lights follow how people actually use each space.
- Describe the control response each area needs. For example: on during shift hours, off after close, or on only when someone is working there.
- Compare the responses side by side. Areas with the same response can share a group. Mark any area whose response is different.
- Draft the proposed groups. Give each group a short note explaining the schedule or task it serves.
The result is a planning map, not a circuit design. The DesignLights Consortium guide gives examples of tools that can carry out a plan like this. It describes individual time clocks that set schedules for individual lighting circuits, and networked lighting control systems that adjust lighting on preset schedules. Not every system offers both. Treat these as features to confirm in the system you pick, which the last section covers.
Weigh Independent Operation Against Added Control Complexity
A split earns its place when it fixes a mismatch you can name. Without matching controls, a system can deliver light at the wrong time or setting for an area's routine. In a planning scenario where warehouse operations run a second shift after front offices close, putting the warehouse on a separate zone is a practical way to keep lights active only where crews are working.
Every extra group also adds something to specify, program, label, and manage over time. If a proposed split has no schedule or task reason written next to it, it adds that work without a clear benefit. In that case, fold it back into the shared group.
A quick test helps here. For each proposed zone, finish the sentence "This area needs its own control because..." If the answer is only "it's a separate room," keep it with its neighbors. For schedule ideas once your groups are set, see our guide to scheduling high bays for security.
Verify System Capabilities and Local Project Requirements
Before you specify anything, run two checks. Your grouping plan only works if the equipment can carry it out and the project's rules allow it.
- Confirm the exact system can run your groups. List the model number of every control and fixture in the proposal. That includes fixtures such as a linear high bay light and control parts like the sensors and dimmers in our lighting accessories collection. Then compare the current manufacturer documentation for those exact models with each group in your map. Check that each group can get the schedule or task response you planned. For networked systems, DesignLights Consortium suggests checking the system's listing to verify its capabilities. If the documents don't show support for a planned behavior, change the plan or the equipment before you finalize.
- Confirm which local requirements apply. Ask the local authority having jurisdiction, or a qualified project professional, to confirm which currently adopted requirements apply to your specific building and project. Their answer may add controls your schedule map didn't call for.
Circuit layout, wiring, and code-compliance decisions belong to a licensed electrician, lighting designer, or engineer. Your schedule map gives them a clear brief to work from.
FAQs
Does a seasonal schedule change mean an area needs a new control group?
Not by itself. If every area in a group changes hours together, such as shorter winter hours across the whole building, the group still shares one response. You only update its schedule. A new group makes sense when one area's seasonal pattern starts to differ from the rest of its group.
Is two the maximum number of control zones for a larger facility?
No. The one-or-two question is the simplest version of the decision. A large facility can have as many groups as it has real schedule or task differences. The limit comes from what each split solves, not from a set number.
What changes should prompt a review of existing control groups?
Look again when an area adds or drops a shift, changes its main task, or goes from steady use to occasional use. The same applies when a space is repurposed, such as storage becoming a work area. Update the area's line in your planning record, then see whether it still shares a response with its group.
How should an area that's used only now and then be handled?
First decide whether following the shared schedule actually causes a problem there. If it doesn't, leave it in the group. If it does, a control that responds to people instead of the clock may fit better. Our guide to parking garage sensor strategies shows one way to pair fixtures with occupancy sensing.
