
Name the lighting task
Separate road, civic, landscape, facade and broad-area requirements before comparing product families.
ProductsChoose a product family from the project question.
Products / selection
A useful shortlist starts with the place, lighting task, mounting context and documents the project team needs to review.

Procurement question
Identify the application, target market, approximate quantity and the lighting outcome the brief must support. Product and configuration decisions can then be narrowed without guessing at missing specifications.
Decision evidence
Use the same information path whether you are comparing a road luminaire, a landscape family or a floodlighting option.

Separate road, civic, landscape, facade and broad-area requirements before comparing product families.

Record mounting, site exposure, electrical context and control expectations that may change the shortlist.

Ask for the applicable drawings, optical data and commercial information for the selected model and market.
Keep these facts connected
A shortlist is useful only when the reasons behind it remain visible to the technical and purchasing teams.
Keep the intended place and lighting task beside every proposed family.
Mark unknown mounting, controls, quantities and market requirements rather than filling them with assumptions.
Define the exact document or confirmation needed to move the review forward.
Questions to carry forward
Use the answers as a starting point. Model, market and project-specific details still need written confirmation.
No. It structures the first shortlist. Model-specific performance, configuration, files and commercial terms still need confirmation for the actual project.
Include the application, approximate quantity, destination market, mounting context and any drawings or control requirements already available.
Your next step
Share the application, product context, target market and documents you need reviewed. The final configuration remains subject to the selected model and project brief.