01
Photometric context
Clarify whether the team needs optical distribution, measurement context, a layout input or another lighting-design reference.
ProductsRequest the specification set that matches the model.
Products / technical access
Request the specification set that matches the model.
Technical review is more useful when the model, configuration, market and requested file types stay connected from the first request.
Procurement question
Make the document request specific.
Name the product family or model, the application, the destination market and the decision the document needs to support. This avoids sending a generic file list that cannot answer the project question.
01Request the specification set that matches the model.Products / technical access
Decision evidence
What a technical pack should help you review.
The public reference explains the request path. The exact files and values depend on the selected configuration and must be confirmed by the team.
02
Mechanical and installation context
Identify dimensions, mounting, wiring and installation details that matter to the project review.
03
Market and compliance context
State the destination market and any required documents so the request can be checked against the selected model.
Keep these facts connected
Avoid a document request with no decision attached.
A file is valuable when the project team knows what it will confirm and what remains open after review.
- 01
Selected model
Record the family, model and any known options instead of requesting data for an undefined luminaire.
- 02
Required answer
Explain whether the file is needed for design, approval, procurement, installation or after-sales.
- 03
Confirmation boundary
Treat public descriptions as a starting point and ask the team to confirm project-specific values.
Questions to carry forward
Keep the next questions visible.
Use the answers as a starting point. Model, market and project-specific details still need written confirmation.
Are all technical files public downloads?
No. Available files and access depend on the model, configuration and request. Use the enquiry path to ask for the relevant technical pack.
Can I request documents before choosing a model?
Yes, but include the application and the families under consideration so the team can direct the request to useful reference material.
Your next step
Ask for the documents your project can use.
Share the application, product context, target market and documents you need reviewed. The final configuration remains subject to the selected model and project brief.