Quick Answer (30 seconds):
To avoid technical rejection and redesign loops in EPC & government tenders, submit one consistent Tender Pack (not scattered files) that includes:
1) a clean BOQ (with exact model mapping), 2) correct IES photometric files (matched to optics + mounting), and 3) a complete DIALux/Relux report (lux + uniformity + layout proof).
If you share the available BOQ template, road drawing or site reference, our engineering team can review the submitted information, identify missing inputs and confirm the appropriate tender-document path.
Submit BOQ for Preliminary Review →
Important: This page is a Tender Pack checklist (BOQ + IES + DIALux).
If you need a reviewer-style DIALux rejection checklist, use this guide:
DIALux Report Tender Review Checklist & Rejection Fixes →
What’s Inside a Tender-Ready Deliverables Pack
| Deliverable | What reviewers check | Most common failure |
|---|---|---|
| BOQ + mapping | Model/qty/specs are auditable | BOQ cannot map to IES/DIALux |
| IES photometric files | Exact model + optics + tilt | Generic / wrong optics / wrong mounting |
| DIALux/Relux report | Lux + uniformity + layout proof | Assumptions not stated / no IES reference |
| Datasheets & drawings | Spec proof + install feasibility | Missing key attachments for due diligence |
| Compliance snapshots (on request) | Tender-required docs list | Wrong set for the buyer type |
Note: final criteria always follow the tender’s stated standard and reporting format.
Who This Checklist Is For
Use this checklist if you are:
- Preparing a tender submission for solar street lighting (roadway / municipal / rural).
- Requesting design approval (lux + uniformity) from a consultant or authority.
- Comparing suppliers and need audit-proof documents, not marketing claims.
- Building a BOQ and want to prevent hidden costs caused by wrong assumptions.
Step 0 — Inputs You Should Gather First
Even strong suppliers cannot produce a valid IES/DIALux/BOQ pack without basic inputs.
A) Site & geometry
- Road type and cross-section (lanes, width, median, sidewalks)
- Pole height target + rough spacing (or your concept)
- Intersections, curves, bridges, trees/shading risks
- Any boundary limits (spill light restrictions near houses, airports, ports)
B) Targets & standards (if specified)
- Target illuminance (lux) and uniformity
- Any glare/spill/uplight requirements
- Tender standard reference (if stated)
Standards note (global):
Criteria vary by country and authority. Common references include EN 13201 (Europe) and IESNA RP-8 (North America). If your tender specifies a local standard, calculations and reporting should match it (targets, grid, assumptions, output format).
C) Practical constraints
- Rainy season / cloudy days expectations (autonomy assumptions)
- Anti-theft requirements (battery/panel risk)
- Maintenance model (local team vs outsourced O&M)
✅ Fast start: you can begin with a Google Map link and spacing concept.
Upload BOQ / drawings →
Step 1 — BOQ Checklist (BOQ = Mapping + Proof)
Caption: Example BOQ mapping table (blurred for privacy).
A BOQ that wins is not just “quantity + price”. It must be auditable.
BOQ should include
- System type (All-in-One / Split / Hybrid / High Mast / Smart Pole)
- Pole height + spacing basis (or design basis if pending)
- Luminaire wattage + optics distribution (roadway optics matters)
- Solar panel & battery basis (chemistry + capacity + autonomy basis)
- Controller features (dimming profile, protections, monitoring option)
- Accessories: brackets, anchor bolts, foundation kit (if required)
- Spare parts plan (critical parts + recommended percentage)
- Warranty statement (system vs components) + delivery schedule
The BOQ Mapping Rule (most important)
Every BOQ line item should map to:
- a datasheet (spec proof)
- an IES file (photometric proof)
- a DIALux/Relux report (performance proof)
If your BOQ cannot map to IES + DIALux outputs, reviewers often treat it as incomplete.
✅ Request Tender Documents & BOQ →
Step 2 — IES Photometric Files Checklist
IES files are the bridge between a luminaire model and measurable roadway lighting results.
Caption: IES naming convention example for audit traceability.
Request IES files that match
- The exact luminaire model (not a “similar” product)
- The exact optics / lens distribution
- The mounting tilt (0° vs tilted can change results and uplight)
- The correct wattage/CCT configuration used in the BOQ
Minimum IES pack for tender submission
- IES for each model + each optics option used
- Reference naming: model + optics + wattage + CCT
- Optional: optics selection notes for roadway type
Common IES mistakes that lead to rejection
- Generic IES from a different product family
- IES not matching the optics stated in BOQ
- Ignoring tilt/mounting assumptions (especially high mast / area lighting)
✅ Request IES Photometric Files →
Step 3 — DIALux / Relux Report Checklist
Need a reviewer-style DIALux rejection checklist (what committees check first)?
→ DIALux Report for Solar Street Lighting Tenders: Reviewer Checklist →
Caption: False color map + isolux contours example (roadway calculation).
For EPC and government review, a DIALux/Relux report is your proof-of-performance.
A complete tender report should include
- Project geometry and pole arrangement summary
- Luminaire selection with IES reference
- Calculation settings (maintenance factor, grid, assumptions)
- Illuminance results (lux) and uniformity
- Layout screenshots (pole positions + calculation area)
- False color map / isolux contours
- A clear pass/fail summary vs target criteria
High mast / area lighting (extra)
- Aiming concept and commissioning notes (tilt/rotation guidance)
- Uniformity focus + boundary spill control (if required)
✅ Request DIALux Simulation Outputs →
Step 4 — Datasheets & Drawings (Audit layer)
Tender reviewers often ask: “Show the specification proof and installation details.”
Common attachments
- Luminaire datasheet (optics, wattage, protections, IP/IK if applicable)
- Controller datasheet (dimming, protections, monitoring option)
- Battery & panel basis (chemistry, capacity, safety notes)
- Pole specification sheet (if poles are included)
- Installation/assembly notes (optional but helpful)
Step 5 — Engineering White Papers (When you must prove key claims)
If your tender committee is technical, white papers help make claims explainable and verifiable, such as:
- Efficacy proof chain (chip vs luminaire vs system, real conditions)
- Smart monitoring value (fault alarms, SOC trend, scheduling)
- Autonomy logic for cloudy season (what changes, what doesn’t)
Due diligence links (for tender reviewers)
If your committee requires factory verification and project references:
The most common reasons tenders fail (and how to prevent them)
1) BOQ and design do not match
Fix: enforce BOQ mapping to IES + DIALux outputs.
2) IES files are generic or incorrect
Fix: request IES “by model + optics + mounting tilt”.
3) DIALux assumptions are unclear
Fix: list pole height, spacing, maintenance factor, targets, and IES reference.
4) Missing attachments for due diligence
Fix: include datasheets, warranty, spares plan, and requested compliance snapshots.
5) No proof path for key claims
Fix: include white papers and “what reviewers can verify”.
Hidden costs (why this matters)
An incorrect IES file or unclear DIALux assumptions creates hidden costs: redesign cycles, delayed approvals, re-installation, and sometimes replacement after site verification. A tender-ready pack prevents these failures before procurement.
What to ask a supplier (copy-paste RFQ template)
Please provide a tender-ready deliverables pack for our solar street lighting project:
1) BOQ mapping (models + quantities)
2) IES photometric files (by model + optics + mounting tilt)
3) DIALux/Relux report PDF (lux + uniformity + layout screenshots)
4) Datasheets pack (luminaire/controller/battery/panel/pole if included)
5) Warranty + spare parts plan + requested compliance snapshots
Inputs attached: [BOQ template / road drawing / Google Map link], target: [lux/uniformity], pole height: [ ], spacing: [ ].
Please confirm delivery time and any missing inputs needed.
Submission Control: A Traceable BOQ-to-Document Register
Use this working register before freezing an EPC submission. It connects each offered configuration to its evidence and keeps missing inputs visible rather than treating a folder of generic files as a completed pack.
| Register field | What to record | Review condition |
|---|---|---|
| Tender / BOQ line | Clause reference, quantity, application and proposed model | Scope agrees with the quotation and exclusions |
| Configuration | Optic, power, mounting arrangement and control profile | Datasheet and simulation use the same offered variant |
| Evidence revision | File name, revision/date and applicable report reference | Superseded files are removed from the issue set |
| Site assumption | Geometry, criteria, maintenance factor, solar or structural inputs | Assumptions are identified and assigned for confirmation |
| Deviation / open item | Requirement, proposed response, owner and decision status | Unaccepted deviations remain visible to the designated reviewer |
| Release decision | Reviewer, approved-for-use purpose and submission date | The issue set is frozen for the stated review stage |
For photometric attachments, follow the IES/LDT verification workflow. For solar operating assumptions, record the dimming profile and battery-energy calculation basis. A supplier document review supports coordination; eligibility, compliance acceptance and award remain subject to the tender requirements and designated authority.
Request a Preliminary Tender-Document Review
✅ BOQ mapping
✅ IES photometric files
✅ DIALux/Relux report (PDF)
✅ Datasheets + tender attachments list
Submit BOQ for Preliminary Review →
Send the available BOQ, pole height and spacing, road drawing or site reference. The engineering team will review the submitted information, identify missing inputs and confirm the applicable document path.
Or go to specific service pages:
- Tender Documents & BOQ →
- IES Photometric Files →
- DIALux Simulation Outputs →
- Lighting Design Service →
