LED Street Light Tender Specification: A Buyer Checklist

An LED street light tender specification should define the road geometry, lighting performance targets, photometric submission rules, product construction, controls, documentation, warranty wording and commercial terms. It should not rely on generic catalogue claims; each bidder should prove suitability with project-specific photometry and exact-model test documents.

Quick Facts

• Primary procurement goal: compare compliant lighting offers on measurable project needs, not broad product promises.
• Key technical files: IES files, luminaire datasheets, installation instructions, test reports for the exact submitted model and photometric calculations.
• Design basis: road category, pole layout, mounting height, arm length, tilt, lane width, pedestrian areas and surrounding light sensitivity.
• Performance topics: illuminance or luminance, uniformity, glare, light distribution, CCT, ingress protection, impact protection, surge protection and controls.
• Supplier caution: do not assume every fitting has the same certification, rating, lifetime, warranty or control option. Ask for model-specific evidence.
• CHZM note: CHZM site materials group products into indoor, outdoor, solar and commercial lighting. The outdoor lighting range includes street lights and floodlights, while related categories include solar lights and commercial lighting.

1. Start With Road Geometry and Use Conditions

A clear LED street light tender specification begins with site information. Municipal buyers and contractors should list the road type, lane count, carriageway width, median width, shoulder width, sidewalk location, cycle lane location, junctions, crossings, roundabouts, parking lanes, trees, building setbacks and any nearby residential windows. These details affect pole spacing, luminaire distribution and glare control.

For existing roads, include current pole coordinates if available. If the project uses new poles, state the proposed pole spacing, mounting height, bracket length, bracket angle and whether poles are single-sided, staggered, opposite or central-median mounted. If the geometry is still under design, ask bidders to submit assumptions separately so the evaluation team can compare design logic.

Do not prescribe a universal wattage as the main requirement. A wattage-only tender can lead to poor comparison because optical distribution, mounting condition and target criteria matter more than input power alone. Instead, request photometric calculations against the selected lighting class or project standard. The tender should also state whether the design is for a main road, local street, industrial access road, parking approach, port road, campus road or residential zone, because visual task and traffic risk vary.

Environmental conditions should be listed without exaggeration. Examples include ambient temperature range, coastal exposure, dust level, heavy rain, wind zone, vibration from bridges or heavy vehicles and maintenance access restrictions. If a location has dark-sky sensitivity, wildlife concerns or residential spill-light complaints, say so in the tender and ask bidders to address shielding, upward light control and CCT selection.

2. Define Performance Targets Without Guesswork

The tender should identify whether the design basis is illuminance, luminance or another project-specific metric. It should also define uniformity, glare limitation, threshold increment where applicable, surround ratio where required and calculation grid settings. These targets should come from the authority having jurisdiction, project lighting standard or the lighting designer’s approved basis of design.

Numeric examples can be useful for formatting, but they should be labeled as hypothetical. For example, a tender might say: “Hypothetical example only: average illuminance target X lux, minimum uniformity ratio Y, calculation area from curb to curb, maintenance factor Z.” This format helps bidders understand how to present data while preventing accidental adoption of values that do not fit the road class.

Ask each bidder to submit calculation reports using the exact luminaire model, exact optic, exact CCT option if photometry changes, exact tilt and exact mounting height. Reports should show calculation points, false-color or isolux views when helpful, luminaire schedule, light loss or maintenance factor assumptions and pass/fail results. If the project includes pedestrian crossings, bus stops, intersections or conflict areas, require separate calculation zones.

Distribution type is one of the most important choices. Some roads need asymmetric forward throw, while others need wider lateral spread or tighter backlight control. The tender can ask bidders to nominate the optic and explain why it fits the road geometry. Avoid accepting a single IES file for a different model, different lens or different housing unless the supplier proves it represents the offered luminaire.

CCT should be selected according to visibility needs, local policy, resident comfort, skyglow control and environmental concerns. The tender can request available CCT options and the bidder’s recommended option, but it should avoid claiming that one CCT is always best for every street. DarkSky guidance encourages thoughtful use of light, including warmer color where suitable, shielding and limiting light to the needed place and time.

3. Tender Specification Table for Bid Submission

The following HTML table can be adapted for a municipal or contractor tender. It is not a universal standard; it is a structure for asking bidders to provide comparable evidence.

4. Product Construction, Protection and Controls

Ingress protection should reflect dust, rain, cleaning practice and exposure. Impact protection should reflect vandalism risk, low mounting, pedestrian access and maintenance handling. The tender may require bidders to state IP and IK ratings and provide exact-model evidence where such ratings are part of the offer. It should not state or imply that every product from a supplier carries the same rating.

Surge protection deserves special attention in street lighting because long cable runs, switching events, lightning exposure and grounding quality can affect field performance. The specification can request built-in or external surge protection details, line-to-line and line-to-earth protection information where applicable, replaceability, status indication and coordination with upstream protection. The correct level should be selected by the electrical designer based on local conditions, not copied from an unrelated project.

Controls should be defined early. A small road project may need only switching by a cabinet, while another project may require photocells, dimming schedules, motion sensing, DALI, 0-10 V, NEMA receptacles, Zhaga interfaces or a central management system. The tender should ask for wiring diagrams, control compatibility statements and commissioning instructions. If future smart-city integration is possible, require physical and electrical provisions only after confirming the authority’s preferred control platform.

Glare control is both a design and product issue. A luminaire with the wrong tilt, optic or mounting location can create discomfort even if the average lighting level looks acceptable. Ask bidders to show installed tilt in the calculation report and to identify any visor, shield or lens option used. If the road is near homes, parks, observatories or coastal wildlife areas, include light trespass and skyglow concerns in the design notes.

5. Step-by-Step Procurement Checklist

1. Confirm project scope. Define whether the tender covers supply only, supply and installation, retrofit, new poles, cable work, controls, testing or maintenance.
2. Collect site data. Provide drawings, pole locations, road widths, mounting heights, bracket data, voltage, control cabinet details and site photos where available.
3. Set the lighting basis. Identify the applicable road lighting class, authority requirement or designer-approved target. State calculation zones and grid rules.
4. Request exact photometry. Require IES files for the exact offered luminaire, optic and relevant configuration. Ask for editable files plus PDF calculation reports.
5. Define product submittals. Ask for datasheets, installation manuals, wiring diagrams, material descriptions, protection ratings and exact-model reports where required.
6. Check CCT and glare. Ask bidders to explain CCT choice, shielding, tilt limits and spill-light control, especially in residential or environmentally sensitive areas.
7. Review electrical protection. Coordinate surge protection, earthing, insulation class, driver access, control interface and maintenance method with the electrical design.
8. Evaluate controls. Confirm dimming protocol, photocell arrangement, sensor logic, commissioning tools and ownership of any software or gateway.
9. Compare deviations. Require a clause-by-clause compliance statement. Any exception should be visible, priced if needed and accepted before award.
10. Verify commercial terms. Review delivery terms, packing, spare parts, documentation language, inspection process, payment milestones and defect response wording.
11. Approve samples if needed. For critical projects, request sample review or mock-up testing before mass supply, with acceptance criteria defined in writing.
12. Archive documents. Keep final IES files, reports, manuals and approved model numbers for maintenance and future replacement control.

For supplier qualification, buyers may review company background through pages such as about information, but the final technical decision should still depend on project-specific photometry and exact-model test documents. For tender discussions, drawing review or document requests, use the supplier’s official contact channel so the bid record remains clear.

6. Warranty Wording, Reports and Commercial Submittals

Warranty language should be specific and auditable. Instead of accepting a broad statement, ask bidders to define the warranted product, start date, coverage, exclusions, claim process, labor responsibility, transport responsibility, replacement method and whether accessories such as drivers, controls, photocells or surge devices are included. Do not invent or assume a warranty period. Let the tender state the required contract position, then require bidders to accept it or list deviations.

Reports should be tied to the exact model offered. A tender can require photometric files, electrical safety documents, ingress or impact test reports, thermal information, control datasheets and installation manuals where applicable. If a certificate is required by law or by the client, name the required document and jurisdiction. Avoid vague wording such as “all international certificates,” because this can create confusion and does not prove project suitability.

Commercial submittals should include a priced bill of quantities, model numbers, accessories, control nodes, brackets, surge devices, spare parts, packing method and delivery terms. Do not assume minimum order quantity, lead time or stock status unless the supplier has stated it in the formal offer. If the project has phased delivery, require bidders to confirm packing labels, batch identification and document control for each shipment.

Distributors and contractors should also clarify substitution rules. If the awarded model becomes unavailable or a design change is proposed, the replacement should be resubmitted with IES files, reports and calculations before approval. This protects the buyer from receiving a different optic or driver that changes performance.

FAQs

1. What is the most important part of an LED street light tender specification?

The most important part is the link between road geometry, lighting targets and exact-model photometry. A tender that includes clear calculation rules and requires IES files for the offered luminaire is easier to evaluate than one based mainly on wattage or catalogue descriptions.

2. Should a tender specify wattage?

Wattage can be included for energy comparison or electrical planning, but it should not be the only performance requirement. Different optics and mounting layouts can produce very different results at similar wattage levels. Use project-specific lighting targets and calculation reports for evaluation.

3. Can one IES file represent a whole street light family?

Only if the supplier proves it represents the exact submitted configuration. The safer tender rule is to request IES files for the exact model, optic, CCT where relevant and mounting condition used in the calculation.

4. How should buyers handle certifications and ratings?

State the certifications, ratings or reports required by the project and jurisdiction, then request exact-model evidence. Do not assume every product has a certification or rating, and do not accept broad family claims when the contract requires model-specific proof.

Sources

• U.S. Department of Energy: Solid-State Lighting
• Illuminating Engineering Society: Lighting Library
• DarkSky: Lighting Principles