
Place and task
Name the application, site conditions, operating context and intended lighting outcome.
ResourcesCheck the brief before it reaches the quotation queue.
Resources / project brief checklist
A short, complete project brief makes it easier to identify the right product path and the documents that still need to be confirmed.

Procurement question
The checklist is designed for the details procurement teams can gather early, even when the final design or quantity is still changing.
Decision evidence
Keep the check focused on useful facts rather than creating a long form that hides the real project question.

Name the application, site conditions, operating context and intended lighting outcome.

Add a preferred family or selection question, approximate quantity and the project stage.

List required drawings, optical data, testing evidence, language and destination-market needs.
Keep these facts connected
The point is to expose the next question, not to turn early project information into a false approval.
Record the information the team can already verify.
Mark missing quantities, drawings, controls, market requirements or installation details.
Name the next document, response or conversation that will close the gap.
Questions to carry forward
Use the answers as a starting point. Model, market and project-specific details still need written confirmation.
Yes. Mark the missing information clearly so the team can focus the next response instead of guessing.
Include application, approximate quantity, target market, product direction and the specific technical or commercial question.
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.