A high-bay sensor zone is too large when a single control response no longer matches the movement, work continuity, or sightlines across the area. Keep it provisionally when people move and work consistently throughout the zone. Split or redraw it when cross-aisle traffic, obstructions, different task schedules, or low-motion work create a separate detection need. Request a review when the selected configuration's coverage, grouping, timing, or compatibility is not documented. For high bay lights, start by marking where people enter, cross, turn, stop, and continue working. There is no universal rule for the number of high bay lights per sensor.

Start With the Zone Decision: Keep It, Split It, or Get It Reviewed
A zone is the group of high bay fixtures that responds together to a control signal. Keep it provisionally when movement, task continuity, sensor view, and schedules are consistent across the area. Split or redraw it when those conditions change, or request a review when the selected configuration's limits are undocumented. Smaller zones provide more refined control, while larger zones simplify setup but provide less granular control, as explained in this lighting controls guidance.
| Observed condition | Provisional decision | Evidence or measurement needed |
|---|---|---|
| Movement, task continuity, sensor view, and occupancy schedule are consistent across the area | Keep provisionally | Mark the work area and confirm the selected configuration's documented coverage and grouping |
| Cross-aisle traffic, turns, or work continues beyond the main travel path | Split or redraw | Map crossings, stopping points, and the area that must remain served |
| Racks, equipment, partitions, or stored materials interrupt the needed view | Split, move coverage, or review | Compare the documented sensor view with the actual task area |
| Adjacent areas have different schedules or task timing | Split or redraw | Record when each area is occupied and whether one response still fits both |
| The selected product's coverage, timing, grouping, or compatibility is unknown | Get it reviewed | Provide the exact fixture, sensor, and control identifiers to the manufacturer or controls vendor |
| Work is stationary or low motion, such as inspection or picking | Validate before approval | Observe the task and record any lights-off event rather than relying on entry detection |
A zone is provisionally too large when a single response would serve materially different conditions. That is a planning boundary, not a guaranteed sensor limit.

Use this four-step first pass:
- Mark occupied areas, including travel lanes, task points, staging, picking, packing, and inspection locations.
- Trace the paths people actually use, including crossings, turns, and work beyond the expected travel route.
- Compare those paths and tasks with the documented sensor view, obstructions, and proposed zone boundaries.
- Label the result keep, split or redraw, or review, and record the reason.
For symptoms such as missed activations, use this motion sensor troubleshooting flow without treating a general troubleshooting guide as proof of a product-specific fix.
Check the Movement and Sightlines That Define the High Bay Lighting Boundary
The best boundary follows a meaningful change in movement, task continuity, or visibility. It does not necessarily follow the end of a fixture row. Map the actual work pattern first, then compare it with the area the selected sensor documentation says it can serve.
Trace the Paths People Actually Use
Put these features on a plan view before deciding how to group the high bay fixtures:
- Primary travel paths through long aisles or open bays.
- Cross-aisle entries, turning points, and routes between storage and work areas.
- Stopping locations for picking, staging, packing, inspection, or equipment use.
- Low-motion tasks where a person may reach, sort, read, or inspect without traveling.
- Zone boundaries and the occupancy schedule of each adjacent area.
A long aisle with continuous movement may support one provisional zone when the work, schedule, and sensor view remain consistent. A cross-aisle that feeds a separate task area deserves a boundary check because entry detection does not prove that the deeper work area remains reliably served. In mixed picking and packing layouts, separate task zones from aisles when their occupancy behavior or task continuity differs.
Compare Visibility With the Needed Work Area
Sensor placement should account for entries, task areas, and unobstructed sightlines to the places where work continues. The wireless occupancy sensor placement guide supports checking entry points and task areas rather than assuming that a fixture row or aisle entrance defines coverage.
| Layout signal | Why it matters | What to do next |
|---|---|---|
| Cross-aisle traffic or multiple entry directions | People may approach the work area from a different path than the fixture layout suggests | Mark each approach and compare it with the documented sensor view |
| Long, straight aisle | Travel may be consistent, but work can continue at a stopping point or beyond the main route | Record turns, stops, and task locations before keeping the zone together |
| Open bay with shared activity | A larger zone may fit when movement and schedules are consistent | Keep provisionally, then validate representative work |
| Racks, equipment, partitions, or stored materials | The expected sightline may not reach the occupied task area | Treat the obstruction as a boundary-check signal and request a configuration review if needed |
| Continuous task area | One response may fit if people remain within the reliably served work area | Compare the full task area, not just the entrance |
| Intermittent staging or pickup area | Occupancy may change separately from the main aisle | Consider a separate zone or a documented review |
| Different schedules in adjacent areas | One control response may not match both areas | Record schedules and redraw the boundary if they diverge |
Lights-off events can result from inadequate coverage, poor sensor location, or sensitivity settings. The controls guidance supports treating these as possible causes, not as a diagnosis. Record the event and compare it with the task area, sensor location, and zone boundary.
Test the Zone Where Work Continues, Not Just Where People Enter
A representative walk-through shows whether the proposed zone matches real work. It does not validate a particular product's calibration or control response, so keep model-specific questions for the documentation review.
- Observe a representative task. Follow normal entry, aisle travel, cross-aisle movement, turning, stopping, picking, staging, packing, or inspection. Include a low-motion task where someone remains in one place. Depending on the sensing method, motion-based sensing may miss continued occupancy when a person remains still. The DOE review of occupancy sensors explains why stationary work belongs in the validation plan.
- Mark the last reliably served location and the needed work area. Note where the person enters, where the task continues, and whether the work extends beyond the expected travel path. Record every location where the lights turn off while work is still underway.
- Compare the event with the proposed zone. On the plan, mark the sensor location, zone boundary, task point, travel path, and any rack, equipment, partition, or stored material between them. Record the observed control response and timing without assuming that changing a setting will solve the problem.
- Choose and document the provisional result. Keep the zone when the observed work and proposed coverage align. Split or redraw it when the task or occupancy pattern changes across the boundary. Escalate when coverage, timing, grouping, placement, or compatibility depends on an undocumented product detail.
Use representative operations rather than a paper-only fixture plan. The DOE measurement and verification guidance describes measurement and verification as a way to assess performance under actual operating conditions. If the walk-through produces repeated unexplained events, include the records in the handoff instead of promising a fix through sensor movement, timeout changes, or control regrouping.
Prepare a Zone Map for Manufacturer or Controls Review
A useful handoff lets the reviewer see the proposed boundary, the work it must serve, and the exact questions that remain open. Document the layout in plan-view order so the manufacturer or controls vendor does not have to infer the relationship between fixtures, sensors, and tasks.
Mark the Layout and Observed Behavior
Use one map and supporting notes for each proposed zone. Include:
- Facility area and project status, such as retrofit or new layout.
- Fixture, sensor, controller, and control-group identifiers, when known.
- Sensor locations, fixture locations, aisle directions, crossings, and zone boundaries.
- Travel arrows, turning points, work points, staging, picking, packing, and inspection areas.
- Racks, equipment, partitions, stored materials, and other sightline obstructions.
- Occupancy patterns and schedules for adjacent zones.
- Every location where work continued after the lights changed state, plus the task being performed.
The GSA controls guidance includes documenting sensor and controller locations as part of the controls design process. The same map structure makes a warehouse or shop review more precise.
Ask for the Missing Product-Specific Answers
Attach the exact fixture, sensor, and control identifiers and ask for written answers to these questions:
- What documented coverage applies to this mounting condition and work area?
- What control-group limit applies to this exact configuration?
- How should timing and occupancy response be interpreted during low-motion work?
- Are there placement constraints related to the proposed sensor location, obstructions, or high-bay mounting condition?
- What compatibility assumptions apply among the fixture, sensor, controller, and control method?
- Does the documented sequence of operations include any daylight or emergency-lighting interaction that affects the zone decision?
There is no universal answer to how many high bay lights per sensor. Fixture count must be compared with the selected system's documented grouping, coverage, timing, and compatibility, along with the actual task layout. If one of those fields is missing, the correct result is a review, not an assumed count.
A completed map should end with one explicit status: keep as designed, split or redraw, move or adjust coverage for review, or hold the decision until the undocumented limit is answered. That gives the reviewer a concrete layout to assess and gives the facility team a record for the next design change.
Frequently Asked Questions
These answers address fixture grouping, sensor placement, lights-off events, and when a proposed zone needs a documented review.
How Many High Bay Lights Can One Motion Sensor Control?
No universal fixture count is supported for a motion-sensor light zone. The answer depends on the exact control-group limit, sensor coverage, timing behavior, compatibility, and task layout documented for the selected configuration. If any of those fields is missing, submit the zone map for review instead of using a fixture-count rule.
Where Should Sensors Go in Warehouse Aisles?
Plan high bay motion sensor placement around the movement that leads into the area needing light, including entries, turns, stopping points, and task areas. Racks, equipment, and partitions can change the needed sightline. Use the selected model's placement documentation to confirm the proposed location rather than assuming one standard position works for every high-bay layout.
Why Do Warehouse Lights Turn Off While People Are Still Working?
Possible causes include missed movement, an obstructed or poorly located sensor, a boundary that separates the worker from the detecting sensor, sensitivity behavior, timing, or another configuration issue. First record the person's task, location, sensor, boundary, obstruction, and observed response. That record shows whether the next step is a boundary change or a product-specific review.
When Should a High-Bay Sensor Zone Be Split?
Split or redraw the zone when adjacent areas have different occupancy patterns, work continues beyond the reliably served path, or obstructions interrupt the needed view. Keep the result provisional when the decision depends on undocumented coverage, grouping, timing, placement, or compatibility. A review is preferable to assuming that the same response fits both areas.