Before you ask for a commercial lighting layout, decide three things. First, the primary task each zone must support. Second, which outcomes are must-haves and which are preferences, plus the trade-offs you want the designer to test.
Those commercial lighting priorities tell the designer what to optimize. Without them, a plan can be technically complete and still be built for the wrong use of the space. Measurements, fixture choices, and code review come later. The decisions below shape the request itself.
Set a Primary Task for Each Zone
Name one primary activity and one desired outcome for every area the layout covers. Start there, not with a fixture type or one brightness goal for the whole building. A picking aisle, a showroom floor, and a break room each ask the layout to do a different job.
Split priorities only when the job changes. Ask one question about each area or time period: if it had its own goal, would the designer optimize for something different? If yes, list it separately. If no, group it with its neighbors so the request stays short.
Operating time can change the question as much as location does. The DOE parking-structure lighting guide gives a garage example. It separates basic parking areas, ramps, and entrances. It describes higher light levels at ramps and entrances during daylight hours, and it calls for controls to reduce those levels at night. In that kind of building, a request that just says "light the garage" hides three areas and two operating periods. Your project may split along other lines, such as open hours versus cleaning shifts.
Write each zone as one line: area, activity, outcome, and when it operates. An illustrative example: "Loading dock, overnight trailer loading: staff can see the dock edge and the trailer interior during the night shift." If you are revising a layout that already disappoints, first audit the existing lighting estimate so each zone line reflects the task that was actually missed.
Rank Must-Haves Above Preferences
Put the outcomes the project cannot give up at the top, and list everything else below them as preferences. No single order fits every building, so the ranking has to come from your project's use.
- Write the must-have outcome for each zone. Test it this way: if a layout missed this result, would you reject the layout? If yes, it is a must-have.
- List secondary preferences separately. Examples might include a fixture look that matches the brand, fewer fixtures to service, or lower energy use in storage areas.
- Put the preferences in order. A ranked list tells the designer where to spend effort first.
- Name what yields when two goals conflict. For example, appearance might win in the lobby while energy savings win in back-of-house storage.
Several goals can be valid at once, which is why the order matters. The 2021 GSA PBS P100 standard for federal public buildings asks lighting systems to be sensitive to the architectural design, provide adequate quality and quantity of illumination, minimize maintenance, and cut electrical energy use. That list shows how many lighting project goals one building can carry. It does not rank them for your store, office, or warehouse. You still have to decide which one wins in each zone.
Separate Fixed Conditions From Flexible Preferences
A fixed condition is one the project owner has confirmed cannot change, while everything else remains flexible. Mark an item fixed only after someone with authority confirms it and write that person's name beside it.
A lease that bars new mounting points or a firm budget cap can be fixed. "We probably can't touch the ceiling" is still an assumption.
For each flexible item, write two things: the change you will accept and the outcome that must stay protected. One illustrative line: "Flexible: fixture count. Acceptable change: more fixtures if the aisle task is met. Protected: maintenance access from the existing lift." This tells the designer how far a preference can bend before it costs something you care about. Also name who can approve that trade-off, so the designer knows whose sign-off a revised option needs.
Some conditions will still be open when you send the request, such as whether a second shift will start or whether part of the space will be re-leased. Label these "open" rather than guessing. Note who will confirm each one and when. A visible open item lets the designer show how the layout changes under each answer. A hidden one quietly decides your priorities for you.
Turn Priorities Into a Request Card
Combine your decisions into one short card per zone and attach the cards to your commercial lighting layout request. Each card ends with a specific option or question the designer can test.
- Zone / task: the area or operating period and its primary activity.
- Must-have outcome: the result that decides whether a layout passes.
- Negotiable trade-off: the preference that can give way, and the change you accept.
- Option or question to test: the comparison or open condition the designer should resolve.
The last field is where a trade-off becomes a design question. The DOE parking-lot lighting guide gives a concrete case for parking-lot retrofits. For periods of inactivity, it describes reducing the output of certain luminaires or turning them off. It also says luminaire selection, controls, and installation should be considered during design to get both energy savings and user satisfaction.
A card for that kind of lot might read like this. Zone / task: customer lot after closing, with staff walking to their cars. Must-have: a lit route from the door to the staff parking row. Negotiable: energy use during inactive hours. Test: compare reduced output with switching off selected luminaires, and show how each option affects the staff route. You would also define which hours count as inactive for your site. Other projects will have their own options to compare. Use this example to see the format, not as a recommendation for your site.
Ask for a comparison only where the answer could change your ranking. If both options would leave your must-haves intact and you would accept either one, skip the test. When your must-haves depend on real site conditions, ask for a photometric layout instead of a simple estimate. Our guide on when a lumens estimate falls short explains that choice. Then attach the finished cards when you submit a lighting design request.
FAQs
What if decision-makers disagree about the top priority?
Write down each competing outcome and who is backing it. Then have the person authorized to set project priorities decide which outcome is the must-have, and send the request with one ranked position. If you send the disagreement unresolved, the designer has to pick a winner, and the layout may favor whoever spoke last. Keep the losing goal on the card as a ranked preference so it still shapes the options.
Should I choose fixtures before requesting a layout?
Usually not. Fixture choice works best after the designer knows what each zone has to achieve. If you already have a required fixture family, maybe to match existing stock or a brand standard, list it as a fixed condition or a ranked preference. Once the layout options are compared, you can match them against commercial lighting categories.
Does a priority card replace measurements or code review?
No. The card tells the designer what to optimize. They still need site information such as dimensions, mounting conditions, and existing controls to build the layout. Code requirements depend on your project's jurisdiction. Confirm them with the local authority having jurisdiction or a qualified designer rather than treating the card as proof of compliance.
Can priorities change after the first layout comes back?
Yes. A first layout often shows a trade-off that looked minor on paper. Update the affected card, note which result triggered the change, and have the same approver sign off before asking for a revision. If cost over the fixtures' life becomes a deciding factor, our overview of photometric layouts and TCO planning can help you frame that next question.
