Outdoor-lighting RFQ checklist
Build the first project brief across application, geometry, operation, product scope, evidence, sample and shipping context.
Checklists and briefs for planning, quoting, sampling and handing over solar and LED outdoor-lighting projects. Start with the RFQ checklist, then pick a focused guide when one decision needs closer review.
Plan, compare, verify and hand over. Owners, designers, procurement teams and suppliers share one sequence: define the decision, compare like with like, check what supports the answer, then record the accepted result.
Describe the place, task, geometry, operating schedule, energy access, environment and maintenance context before selecting a product family.
Put alternative architectures and proposals against the same requirements. Record assumptions, exclusions and deviations instead of comparing isolated labels.
Match the proposed model and configuration to the relevant drawing, photometric file, report or destination document. Keep unresolved points explicit.
Carry installed asset identity, controller settings, witnessed checks, exceptions, closure evidence and maintenance ownership into one site record.
Begin with the broad RFQ checklist, then use a focused guide for site geometry, document scope, files, tender comparison, sample approval or handover.
Build the first project brief across application, geometry, operation, product scope, evidence, sample and shipping context.
Organize the site drawing, mounting arrangement, calculation target, operating assumptions and requested outputs before discussing a study.
Ask which exact luminaire, optic, configuration and revision a file represents before using it in a project comparison.
Place each requirement beside the offered response, supporting evidence, stated deviation and open question so bids remain comparable.
Record identity, appearance, mounting, controls, labels, packing, agreed checks and unresolved deviations before a sample becomes a production reference.
Carry installed asset identity, controller settings, witnessed checks, exceptions, closure evidence and maintenance ownership into one site record.
Frame questions about exposure, materials, finish, fasteners, sealing, maintenance access and evidence without assuming a photograph proves suitability.
Separate deck or task illumination from fish-attracting use, then define the power, mounting, operating and environmental interfaces that need review.
Compare the two approaches through site constraints and requested evidence rather than carrying broad energy, weather or maintenance claims into a project.
Capture road, off-grid, site, operating and evidence inputs before a configuration discussion.
Map landscape zones, placement context and open evidence questions for an enquiry.
Turn a linear landscape route into an annotated enquiry record.
Capture remote-site operating, interface and acceptance context without assuming a tower configuration.
Preserve vessel, purpose, interface and document questions in a shared record.
Organise geometry, task, file and evidence inputs for an area-lighting request.
Prepare the site, load and interface record before comparing project options.
Request document identity and scope instead of treating a badge as universal proof.
Compare Xiuben project lighting, Weichun solar outdoor fixtures, TUODI furniture lighting and controls, and iLamp decorative strings by buyer brief.
Take a guide straight to a named model. Each family page compares its models side by side.
Share what is known and label what is still open. Keep the relevant guide beside the enquiry so the reply addresses the same decision.
A planning guide helps you ask better questions; the quoted model, project inputs and destination requirements decide the answer. Model availability, photometric performance, solar autonomy, environmental suitability, market conformity and shipment scope remain project-specific, and the exact-model drawing or file, any reviewed sample, local professional requirements and the written order description govern. Where a value or document is missing, ask for it for the proposed configuration and destination.