Pick the in-scope bay where your project's hardest rack geometry, mounting constraints, and real work tasks all show up in the same place. Don't pick a bay just because it's easy to reach. A warehouse lighting pilot can only tell you about the conditions it actually contains, so an easy bay can make a plan look ready before it has faced the aisles that matter.
Sometimes no single bay has all three hard conditions. In that case, pilot complementary zones or narrow what the pilot claims to cover. Either way, write down what the chosen area represents and what it leaves out.
Choose the in-scope bay with the hardest combined conditions
Choose the candidate where the toughest in-scope conditions overlap. When evaluating fixtures such as linear high bays, compare every bay on all three factors together. One extreme feature, like the tallest racks, doesn't make a bay representative if the mounting and tasks there are easy.
For the task factor, look at where the work actually happens. A warehouse lighting survey can check the task point and plane where work is done, and the vertical plane matters when goods are stored on stacks. So rack faces where workers read labels or handle stock belong in your comparison, not just the floor. The same guidance also judges lighting quality: glare, shadows, extreme contrasts, direction, and distribution. Talking with the people who work in each bay can surface problems a quick walkthrough misses. If rack faces decide your comparison, whether evaluating linear fixtures or UFO high bay models, our guide on vertical light for aisles covers that surface in more depth.
When planning layout choices across your commercial lighting areas, use this matrix to walk each candidate bay:
| Condition | What to observe | How it changes the choice |
|---|---|---|
| Rack geometry | Rack height, aisle width, and layout in the bay | Favor the bay with the project's toughest rack and aisle setup |
| Mounting constraints | Mounting positions and restrictions actually available | Favor the bay where the project's real mounting limits apply |
| Actual work tasks | Real tasks, where they happen, floor or rack face | Favor the bay where demanding tasks meet hard-to-light surfaces |
| Overlap | Whether the hard conditions share one bay | Yes: select it. No: use the split-zone path below |
Treat the matrix as a planning rule, not a scoring formula. Adding points or weights creates false precision and hides why a bay was picked. Write a short reason for each "favor" call instead. The bay with the most in-scope "favor" calls, backed by clear reasons, is your strongest pilot candidate.
Mounting height and available mounting points also affect fixture spacing later on. Once the pilot bay is set, our high bay spacing and layout guide picks up that next step.
When the hard conditions occur in different bays
When no single bay holds every demanding condition, spread the pilot across complementary zones or state a narrower claim. What you should never do is call an easier, convenient bay representative of conditions it doesn't contain. Follow the branch that matches what you found:
- Conditions overlap in one in-scope bay: Select that bay as the primary pilot zone.
- Conditions are split across in-scope bays: Select complementary zones and name the condition each one adds.
- Only one zone is feasible: Pilot it, but state the narrower scope and exactly which conditions stay untested.
- The hardest area is an out-of-scope exception: Leave it out, record the boundary, and don't apply the pilot results to it.
Here's an illustrative example. A facilities lead finds the tallest racks and narrowest aisles in the back bays. The most restricted mounting sits under a mezzanine near shipping. Neither area covers both conditions, so the pilot uses one zone from each, and each zone is labeled with the condition it contributes. If your facility already has distinct areas, a commercial lighting zone worksheet can help you map which zone holds which condition.
Record what the pilot represents
Write a short record of the selected area so later conclusions stay inside the pilot's real scope. Capture the actual site conditions, not just a bay number or a general description:
- Selected zone or zones: Bay IDs and why each was chosen.
- Rack geometry: The rack layout and aisle arrangement that made the bay a candidate.
- Mounting constraints: The real mounting positions and limits in the pilot area.
- Real tasks: What work happens there and on which surfaces, including rack faces.
- Included conditions: The project conditions this pilot actually tests.
- Unrepresented conditions: Important in-scope conditions missing from the pilot, marked as excluded or assigned to another zone.
- Reason for any scope limit: Why a condition or area was left out.
Keep the record focused on how representative the pilot is. Fixture specs and installation details belong elsewhere. When the pilot results come in, this record shows reviewers which conclusions carry over to the rest of the project and which need another look. For deciding when to scale, revise, or pause after the test, our guide to sample-zone planning covers the next phase.
FAQs
Should I choose the largest bay or the hardest one?
Choose the hardest one within scope. Size alone doesn't make a bay representative. A large, open bay with easy mounting and simple tasks can hide the problems your project actually has to solve. Pick the candidate where tough rack geometry, real mounting limits, and demanding tasks come together, even if it's smaller.
What if the difficult conditions are split across bays?
Use complementary pilot zones when each difficult condition sits in a separate area that's part of the project. Label each zone with the condition it adds. If budget or access limits you to one zone, run it anyway, but state clearly which conditions the pilot leaves untested so nobody assumes full coverage.
Should the pilot reflect real work tasks?
Yes. Compare candidate bays using the tasks people actually do there, such as picking from upper rack faces or reading labels in a narrow aisle. A staged or easier task can make results look better than daily operations will. Asking workers what they struggle to see helps confirm you're testing the right task.
