How to Match a Street Light Tender Specification Clause-by-Clause
When you receive a street light tender specification, the challenge is not simply finding an LED street light with the right wattage or lumen output. You need to determine whether the proposed product meets every applicable tender clause and whether you have the right evidence to prove compliance.
For contractors, bidders, procurement teams, lighting suppliers, and project engineers, a practical review should follow a simple chain:
Tender clause → Required value → Proposed product → Evidence → Compliance status → Action
This clause-by-clause approach helps identify technical gaps early, organize tender documentation, and reduce the risk of non-compliance during technical evaluation.
What Is a LED Street Light Tender Specification?
A LED street light tender specification defines the technical, performance, testing, documentation, and project requirements that a proposed lighting solution must meet.
Typical LED street light tender requirements may cover:
- Luminaire power and efficacy
- Photometric performance
- Electrical and driver characteristics
- IP and IK protection
- Surge protection
- Controls and dimming
- Applicable standards and certifications
- Warranty and service requirements
- Product documentation
- Project-level lighting performance
Not every requirement can be verified directly from a product datasheet. For example, rated power can normally be checked against the manufacturer's specification, while road uniformity may need to be demonstrated through a project-specific lighting calculation.
Understanding this distinction is the first step toward effective tender compliance.
How to Check LED Street Light Tender Requirements Clause-by-Clause
The most reliable way to review a street light tender specification is to work through it clause by clause rather than checking the product datasheet as a whole.
For each requirement, ask four questions:
What exactly does the tender require?
Does the proposed LED street light meet it?
What document proves compliance?
If there is a gap, what action is required?
This creates a practical workflow:
Define → Match → Prove → Resolve
Step 1: Extract and Define Each Tender Clause
Break the street light tender specification into individual, measurable requirements instead of reviewing long paragraphs as a whole.
For example:
| Tender Clause | Required Value |
|---|---|
| Rated power | ≤100 W |
| Luminaire efficacy | ≥150 lm/W |
| IP protection | IP66 |
| Surge protection | ≥10 kV |
| CCT | 4000 K |
| Warranty | ≥5 years |
Pay close attention to terms such as “minimum,” “maximum,” “shall,” “not less than,” “not exceeding,” and “equivalent or approved,” as they determine how the requirement should be evaluated.
Also identify whether each clause applies to the luminaire, a component, project-level lighting performance, documentation, or commercial conditions.
Step 2: Match the Proposed Product
Compare each requirement directly with the proposed LED street light. For example, if the tender requires a luminaire efficacy of at least 150 lm/W and the proposed product is rated at 158 lm/W, the technical value matches the requirement.
The comparison must be based on the exact tender criterion, not similar terminology. A product described as having “high surge protection” does not automatically satisfy a tender requiring a specific surge rating.
Project-level requirements also need separate consideration. A luminaire may meet the specified IP rating and electrical characteristics but still require a lighting calculation to verify performance based on the optic, mounting height, spacing, and road geometry.
Step 3: Prove Compliance With the Right Evidence
A product value alone may not be sufficient for tender submission. Important technical claims should be supported by traceable documentation.
Typical evidence includes product datasheets, photometric reports, IES/LDT files, IP/IK and electrical test reports, certificates, driver documentation, warranty letters, product drawings, and project lighting calculations.
The key principle is:
Every critical tender claim should have traceable supporting evidence.
For example, an IP66 requirement should be supported by appropriate test documentation, while a road uniformity requirement should be demonstrated through a project-specific lighting calculation rather than a product datasheet.
Step 4: Assign Status and Resolve Gaps
After matching the product and evidence, assign a clear status to each clause:
Compliant — the product meets the requirement and supporting evidence is available.
Non-compliant — the product does not meet the requirement.
Equivalent — the proposed product differs from the specified item and requires approval.
Pending — additional documentation, testing, or calculation is required.
If a gap is identified, record the action needed. This may involve changing the luminaire or optic, providing additional documentation or calculations, or obtaining approval for an equivalent product.
Resolving these issues before submission reduces the risk of technical rejection or clarification requests during tender evaluation.
Not All Tender Clauses Are Product Requirements
Product compliance does not necessarily mean complete tender compliance. Some requirements can be checked directly against the luminaire, while others depend on project conditions or require supporting documentation.
| Requirement Type | How to Verify | Typical Evidence |
|---|---|---|
| Product | Compare with product specification | Datasheet |
| Photometric | Check test data and project calculation | Photometric report / IES / LDT |
| Protection & electrical | Verify against required rating | Test report |
| Project performance | Evaluate under actual installation conditions | Lighting calculation |
| Certification | Check required certification | Certificate / declaration |
| Warranty & service | Check supplier commitment | Warranty letter / tender documents |
For example, an LED street light may meet the required IP rating and efficacy but still require a new lighting calculation if the road width, pole spacing, mounting height, or optic configuration differs from the original design.
For road and street lighting luminaires, IEC 60598-2-3 specifies particular requirements for road, street, and other public outdoor lighting luminaires. The applicable edition, national standards, and project-specific requirements should be checked against the tender.
LED Street Light Tender Compliance Matrix: The Practical Working Tool
Once the clause-by-clause review is complete, consolidate the results into a LED street light tender compliance matrix.
The matrix connects each tender requirement with the proposed product, supporting evidence, compliance status, and any outstanding action.
| No. | Tender Clause | Required | Proposed | Evidence | Status | Action Required |
|---|---|---|---|---|---|---|
| 1 | Luminaire power | ≤100 W | 100 W | Datasheet | Compliant | — |
| 2 | Efficacy | ≥150 lm/W | 158 lm/W | Photometric report | Compliant | — |
| 3 | IP protection | IP66 | IP66 | IP test report | Compliant | — |
| 4 | Surge protection | ≥10 kV | 10 kV | Test report | Compliant | — |
| 5 | Road uniformity | ≥0.40 | 0.38 | Lighting calculation | Non-compliant | Review optic |
| 6 | Driver brand | Brand X | Brand Y | Driver datasheet | Equivalent | Submit approval |
| 7 | Warranty | ≥5 years | 5 years | Warranty letter | Compliant | — |
For larger street lighting projects, additional fields can be added for clause numbers, product/model numbers, document or test-report references, responsible persons, and approval status.
The matrix can then serve as a central control document for product selection, technical documentation, engineering review, and tender submission.
A Simple Rule for Tender Compliance
A street light should not be considered fully compliant simply because its specifications look similar to the tender requirements.
A stronger compliance chain is:
Tender Requirement → Product Match → Supporting Evidence → Compliance Status → Required Action
This approach helps identify technical gaps, missing documentation, project-level issues, and approval requirements before they become problems during tender evaluation.
How to Handle Equivalent Products in a LED Street Lighting Tender
A tender may specify a particular manufacturer, component, or technical solution while allowing an equivalent product.
If an alternative LED street light is proposed, compare it against the requirements that matter to the tender rather than simply stating that it is “equivalent.”
| Requirement | Specified Product | Proposed Product | Assessment |
|---|---|---|---|
| Power | 100 W | 100 W | Meets |
| Efficacy | ≥150 lm/W | 158 lm/W | Meets |
| IP rating | IP66 | IP66 | Meets |
| Surge protection | 10 kV | 10 kV | Meets |
| Warranty | 5 years | 5 years | Meets |
If the tender requires prior approval for an alternative product, follow the specified approval procedure before submission.
The objective is to demonstrate that the proposed product meets the tender's functional and technical requirements, rather than simply showing that it has similar specifications to the named product.
Need Help Checking Your Street Light Tender Specification?
For a tender project, product availability is only part of supplier evaluation. A suitable manufacturer should also support product matching, technical documentation, and project verification.
Infralumin can support your tender review by helping you:
Match tender clauses with suitable LED street light models
Identify the technical evidence required for key specifications
Provide datasheets, IES/LDT files, drawings, and relevant test documentation
Identify potential compliance gaps before submission
Support equivalent-product evaluation where permitted
References
- European Commission — Green Public Procurement Criteria for Road Lighting and Traffic Signals
- IEC — IEC 60598-2-3: Luminaires for Road and Street Lighting
- EN 13201 — Road Lighting



