Tender Documents & BOQ Package For EPC & Government Street Lighting
Copy-ready tender language + BOQ input checklist + submission pack structure.
Reduce spec gaps and revision cycles before bidding and approvals.
What’s Included
A tender-ready pack designed to reduce spec gaps and revision cycles.
Download Pack Template
A project-ready template pack to standardize BOQ inputs, folder structure, and submission attachments.
- ✓ Folder structure + naming rules (submission-ready)
- ✓ BOQ inputs checklist to lock assumptions and prevent gaps
- ✓ Ready for EPC review, consultant evaluation, and site acceptance
BOQ Inputs Checklist (Project-Ready)
Use this checklist to lock assumptions and prevent spec gaps before tender evaluation.
Fields to Include in Your BOQ
01Project Basics
- Project location + climate notes
- Quantity + phase plan / deadline
02Lighting Targets
- Road type/class + standard reference (if any)
- Maintained target + uniformity requirement
03Geometry Assumptions
- Mounting height + spacing assumption
- Road width / lanes + arm/tilt (if used)
04Electrical & Protection
- AC voltage / frequency (if applicable)
- SPD level + earthing requirements
05Documents & Acceptance
- Required documents (IES/LDT, drawings, tests)
- Acceptance checks + measurement criteria
Why These Fields Matter
- Prevents “same wattage, different optics” substitutions.
- Locks assumptions used in BOQ and submissions.
- Makes evaluation and acceptance checks defensible.
What you get (24H)
- Marked-up BOQ fields (missing items highlighted)
- Recommended clause set for submissions
- Short document list aligned to your checklist
Copy-Ready Tender Language
Paste these clause blocks into your RFP appendix to lock deliverables, evidence, and acceptance checks.
Photometry & Evidence Submission
Defines IES/LDT submission, naming, and maintained reporting assumptions.
- Requires IES/LDT files matching the offered variant
- Locks MF, height/spacing/tilt assumptions
- Supports evaluation and acceptance verification
View clause text +
1) Bidder shall submit IES/LDT photometric files for the offered luminaire variant(s).
2) Files must match the quoted optics / wattage / CCT and include clear naming + version ID.
3) Provide maintained results (avg/min/uniformity) under stated assumptions (MF, height, spacing, tilt).
4) Any “family” photometry must declare which model/variant it represents and its valid range.
5) Photometry evidence shall be used for evaluation and may be requested again at site acceptance.
2) Files must match the quoted optics / wattage / CCT and include clear naming + version ID.
3) Provide maintained results (avg/min/uniformity) under stated assumptions (MF, height, spacing, tilt).
4) Any “family” photometry must declare which model/variant it represents and its valid range.
5) Photometry evidence shall be used for evaluation and may be requested again at site acceptance.
Substitution Control (Same Wattage ≠ Same Optics)
Lists the deliverables required for a review-ready tender submission pack.
- Defines required attachments for evaluation and approvals
- Aligns BOQ configuration notes with submission documents
- Adds QC/traceability and acceptance checklist option
View clause text +
Bid submission shall include a tender-ready document pack containing:
(a) Deliverables list and compliance notes (documents required by the Employer).
(b) Photometry package (IES/LDT + results tables + layout screenshots for review).
(c) BOQ configuration notes (variant mapping, options, exclusions, and assumptions).
(d) Installation/interface notes (arm/bracket/wiring entry, if applicable).
(e) QC / traceability statement and acceptance checklist (on request).
(a) Deliverables list and compliance notes (documents required by the Employer).
(b) Photometry package (IES/LDT + results tables + layout screenshots for review).
(c) BOQ configuration notes (variant mapping, options, exclusions, and assumptions).
(d) Installation/interface notes (arm/bracket/wiring entry, if applicable).
(e) QC / traceability statement and acceptance checklist (on request).
Acceptance Checks & Traceability
Defines verification items, file version control, and acceptance traceability.
- Provides a “what-to-verify” checklist for evaluation
- Requires version control for submitted files and revisions
- Supports matching evidence at site acceptance
View clause text +
Bidder shall support acceptance checks and traceability as follows:
1) Provide a list of verification items (documents, photometry, configuration mapping).
2) Maintain version control for files submitted (IES/LDT, tables, screenshots, revisions).
3) Provide sample results tables aligned to targets (avg/min/uniformity) for review.
4) At acceptance, the Employer may request matching evidence for installed configurations.
5) Traceability records and QC checklist shall be provided upon request.
1) Provide a list of verification items (documents, photometry, configuration mapping).
2) Maintain version control for files submitted (IES/LDT, tables, screenshots, revisions).
3) Provide sample results tables aligned to targets (avg/min/uniformity) for review.
4) At acceptance, the Employer may request matching evidence for installed configurations.
5) Traceability records and QC checklist shall be provided upon request.
Deliverables List
Locks “equivalence” to verified optics/photometry—not wattage-only offers.
- Requires model/variant-matched IES/LDT evidence
- Maintained targets must be met under stated geometry assumptions
- Post-award changes require written approval
View clause text +
“Equivalent” offers shall be evaluated by verified performance evidence, not wattage only.
1) Optics/photometry (IES/LDT) must be provided for the exact offered model and variant.
2) Maintained results must meet the stated targets under the stated height/spacing assumptions.
3) Any change of optics/wattage/CCT/driver options after award requires written approval.
4) If photometry/evidence does not match the offer, the bid may be rejected as non-compliant.
1) Optics/photometry (IES/LDT) must be provided for the exact offered model and variant.
2) Maintained results must meet the stated targets under the stated height/spacing assumptions.
3) Any change of optics/wattage/CCT/driver options after award requires written approval.
4) If photometry/evidence does not match the offer, the bid may be rejected as non-compliant.
Need a tender-ready submission pack?
Download the Pack Template (ZIP/PDF/XLSX)
Submission Pack Structure (Folder + Naming)
A review-ready structure that prevents missing files and speeds up approvals.
Folder Structure (Review-Ready)
01
Forms & BOQ
BOQ.xlsx · Config-Mapping.pdf
02
Photometry & Results
IES/LDT · Tables · Screenshots
03
Drawings & Interface
Pole/Arm · Wiring Notes
04
Compliance & QC
Tests · Certificates · QC
Keep one PDF per topic to avoid mixed evidence packs.
Request a Pack Template →
Document Guidelines
- ✓ Use one filename pattern: Project + Zone + Rev (R0/R1).
- ✓ Keep tables, screenshots, and drawings in separate PDFs.
- ✓ Match IES/LDT names to the offered model/variant (no generic family files).
- ✓ Provide maintained results (avg/min/uniformity) under stated assumptions.
- ✓ Align BOQ items with submission attachments and acceptance checks.
Want us to mark up your BOQ and highlight missing fields?
Request a BOQ Review →
Common Tender Gaps We Catch (Before Evaluation)
These issues cause rework, non-comparable bids, or substitutions after award.
BOQ Markup (Missing Fields Highlighted)
Submission Pack (Folder + Naming)
Acceptance Notes (What to Verify)
Next Steps
Open the matching deliverables to complete your submission path.
IES / LDT Photometric Files
Get matching photometry files and a quick verification guide.
DIALux / Relux Outputs
Report + tables + layout evidence aligned to your tender criteria.
Drawings & Datasheets
CAD drawings, foundation notes, and installation interfaces.
Engineering Support Hub
See project-ready configurations by application and scenario.
Request Tender Documents & BOQ Pack (24H)
Share your BOQ draft, tender checklist, and project basics.
We’ll reply within 24 hours with copy-ready clauses, a BOQ inputs checklist, and a submission pack template (NDA/redaction available).
What You’ll Receive
- Copy-ready tender language (photometry, documents, QC, acceptance)
- BOQ inputs checklist (fields to lock assumptions and prevent gaps)
- Submission pack structure (folder + naming + required attachments)
- Common risk notes (what causes rework or substitutions)
- A short “what-to-verify” list for evaluation & site acceptance
FAQ (Tender Documents & BOQ for Street Lighting)
Quick answers to common EPC and tender questions—inputs, assumptions (MF/tilt/spacing), deliverables, and file traceability. If your submission has special rules or NDA requirements, tell us in the form and we’ll align.
What should we include in a BOQ besides wattage and quantity?
At minimum include: road type/class, maintained targets (lux or luminance), uniformity, mounting height & spacing assumptions, and photometry evidence (IES/LDT) tied to the offered optic/wattage variant. Wattage-only BOQs are the fastest way to invite substitutions and redesign cycles.
Can you provide copy-ready tender language we can paste into our RFP?
Yes. We provide clause blocks for photometry/IES submission, required deliverables, QC/traceability, and acceptance checks. You can paste them directly into your tender appendix and only adjust project-specific targets and dates.
How do we prevent “same wattage, different optics” substitutions?
We lock the evaluation to traceable performance evidence: IES/LDT file requirements per variant, maintained results tables (avg/min/uniformity) under stated assumptions, and a short “what-to-verify” list for acceptance. This shifts comparison from wattage to distribution and verified outputs.
What do you need from us to prepare the tender pack?
Country/conditions, project type (road/yard/campus), target criteria (maintained lux/luminance + uniformity), and your typical height/spacing plan. If drawings are not ready, a Google Map pin + typical height/spacing is enough to draft BOQ fields and clause language.
Can you work under NDA or provide redacted references?
Yes. We can provide NDA support and redacted samples when required, while keeping the submission pack review-ready (assumptions stated, document list clear, and deliverables traceable).
