Tender Documents & BOQ Review for Lighting Projects
Upload your available BOQ, tender specification, lighting layout, or required-document list. Sunlurio can conduct a preliminary review to identify missing inputs, flag compliance or technical-deviation points, confirm the proposed product scope, and map an appropriate document path.
This is a preliminary supplier-side review. Final tender interpretation, acceptance, and approval remain with the buyer, consultant, project engineer, or relevant tender authority.
Scope note: Document availability depends on the confirmed scope, product configuration, tender requirements, and document stage.
A Controlled Path from Tender Inputs to Document Direction
The review starts with the files you already have. Missing information is listed before any product or document path is treated as confirmed.
1 — Upload BOQ / Specification
Send the available BOQ, technical specification, drawings or layout, required-document list, and tender deadline.
Review output: received-file summary and initial review scope.
2 — Identify Missing Inputs
Check project data affecting configuration and document matching, including location, geometry, pole height, spacing, lighting target, operating schedule, power, wind, and standards.
Review output: clarification list.
3 — Review Compliance Gaps
Compare requested clauses and evidence with available product information and document status.
Review output: compliance-gap and confirmation notes.
4 — Confirm Product Scope
Review the proposed product family, configuration, quantities, optics, pole interfaces, controls, and accessories against the BOQ.
Review output: preliminary scope direction.
5 — Prepare / Map BOQ Matching
Map BOQ lines to proposed product descriptions, model direction, key parameters, and permitted alternatives or deviations.
Review output: BOQ matching notes.
6 — Map Required Documents
Group datasheets, photometric files, simulations, drawings, compliance evidence, installation, packing, inspection, and handover files by purpose and availability.
Review output: document map.
7 — Release the Appropriate Document Path
Provide suitable available materials, request remaining inputs, or route the request to product, photometric, drawing, or engineering review.
Review output: document path or clarification list—not tender approval.
Built for Project and Tender Teams
For EPC, public-sector, humanitarian, consultant, and tender-driven teams coordinating product scope, technical review, and document requirements.
EPC Contractors
For teams coordinating BOQ lines, product scope, drawings, technical submissions, installation requirements, and handover documents across work packages.
Government / Municipality
For public-lighting procurement teams reviewing technical clauses, maintenance needs, acceptance requirements, and supplier document scope.
UN / NGO
For humanitarian and development-project teams needing a clear product, delivery, installation, inspection, and handover document path.
Engineering Consultants
For consultants checking lighting inputs, photometric matching, technical deviations, pole or foundation interfaces, and evidence required for project review.
Tender-Driven Buyers
For procurement teams, distributors, local agents, and project owners working from a tender specification or required-document list before quotation or submission.
Send What Is Available
A complete tender package is helpful, but it is not required to begin a preliminary review. Send the available files and identify what is still pending.
Buyer and Project Context
Company name, buyer role, project country and city, application, procurement stage, and intended submission or review purpose.
BOQ and Tender Specification
BOQ lines, technical clauses, material requirements, permitted alternatives, applicable standards, requested evidence, and accepted file formats.
Lighting Layout and Geometry
Road width or area dimensions, pole positions, mounting height, spacing, carriageway arrangement, and available CAD or PDF drawings.
Performance and Operating Requirements
Target illuminance and uniformity, operating hours, dimming, solar backup days, AC power conditions, and control requirements.
Structure and Site Conditions
Wind speed, corrosion environment, pole material, flange, anchor-bolt and foundation expectations, civil information, and installation constraints.
Document Requirements and Priority
Required datasheets, photometric files, reports, drawings, compliance evidence, packing, installation, inspection, acceptance and handover files, plus tender deadline and priority.
Important: Do not delay the first contact because one input is missing. The preliminary review can identify the next clarification items.
Gaps That Can Change Product or Document Matching
These common gaps can change the proposed configuration, quotation basis, or document path and should be clarified before tender use.
Unclear Product Scope
The BOQ may not distinguish solar or AC street lights, smart lighting, high mast systems, poles, floodlights, controls, accessories, or civil works.
Geometry or Quantity Conflict
Road width, area dimensions, pole height, spacing, mounting arrangement, or quantities may be missing or inconsistent.
Lighting Target Not Defined
Target illuminance, uniformity, road class, calculation grid, maintenance assumptions, or acceptance method may be unclear.
Solar Operating Conditions Missing
Country and city, working hours, dimming, backup days, seasonal solar conditions, or sizing assumptions may be absent.
Photometric File Mismatch
IES or LDT evidence must match the proposed model, wattage, optics, and mounting conditions; a generic file is not model-matched evidence.
Pole / Foundation Inputs Missing
Pole height, material, arm, flange, anchor bolts, wind speed, corrosion category, and site conditions affect drawing and foundation review.
Map Documents by Tender Purpose
No single pack is assumed to cover every tender. Documents are mapped to the confirmed product scope, requirements, intended use, and document stage.
Product and BOQ Files
Matched datasheets, product descriptions, preliminary model direction, BOQ matching notes, and a compliance or deviation matrix where applicable.
Photometric and Lighting-Design Files
Model-matched IES/LDT files, DIALux/Relux input review, confirmed project simulations, layouts, and calculation assumptions.
Drawings and System References
Product, pole, arm, flange and anchor-bolt drawings; foundation review path; wiring and smart-control architecture where applicable.
Compliance and Quality Files
Applicable certificates or reports matched to scope, suitable inspection or quality records, and technical clarification records.
Delivery, Installation, and Handover Files
Packing references, installation and wiring guidance, inspection and acceptance checklists, and commissioning or handover direction.
Availability boundary: The final document list depends on confirmed product scope, tender requirements, intended use, and document stage.
Controlled Access Based on Project and Document Stage
Release depends on intended use, confirmed project context, product scope, configuration, tender requirement, and document stage.
Level 1 — Public Preparation Materials
General checklists, input sheets, sample file structures, and non-project-specific guidance may be available for early tender preparation.
Release condition: public and suitable for general use.
Level 2 — After Basic Project Information
Selected or redacted preparation materials may be shared after the buyer role, project context, intended use, and document purpose are clear.
Release condition: legitimate purpose confirmed.
Level 3 — After Tender / Engineering Review
Model-matched files, project-specific outputs, BOQ matrices, deviations, drawings, compliance evidence, and full document paths require scope and configuration review.
Release condition: confirmed scope, requirement, and stage.
Document access is controlled by scope and stage. Submission does not guarantee release of every requested file.
Compare the Requirement, Proposed Scope, Evidence, and Remaining Decision
A supplier-side review records each tender requirement, proposed product scope, supporting evidence or deviation, and the confirmation still required.
Tender Requirement
Record the exact BOQ line, clause, standard, performance target, or document requirement being reviewed.
Proposed Product Scope
State the proposed family and configuration, including relevant model, optical, structural, control, component, or accessory assumptions.
Supporting Evidence or Deviation
Map the available datasheet, drawing, report, certificate, photometric file, simulation, or clarification note; describe any deviation without implying acceptance.
Required Confirmation
Identify what still requires buyer, consultant, local engineer, laboratory, certification body, or tender-authority confirmation.
Route Each Request to the Correct Engineering Path
Use the specialist route that matches the evidence or engineering work required by the tender.
DIALux / Relux Support
Submit target lux, uniformity, layout, pole height, and product direction for simulation support review.
IES / LDT File Support
Request photometric files after product model, optics, wattage, and mounting conditions are confirmed.
Drawings and Datasheets
Use this path for datasheets, product drawings, and drawing-related document direction.
Pole / Foundation Reference
Submit pole height, wind speed, flange, anchor bolt, corrosion, and site condition requirements.
Prepare the Inputs That Control the Review
Use this checklist to organize the available project, BOQ, lighting, structural, site, delivery, and handover inputs before submission.
Project: company, buyer role, location, application, stage, and deadline.
BOQ / Specification: BOQ, clauses, standards, alternatives, evidence, required documents, and formats.
Lighting / Product: layout, dimensions, pole height, spacing, quantity, targets, optics, operating schedule, power, solar backup, and controls.
Structure / Site: wind, corrosion, pole, foundation, civil, electrical, and installation interfaces.
Delivery / Handover: packing, inspection, installation, commissioning, acceptance, and priority documents.
Tender and BOQ Review FAQ
Scope, evidence, access, timing, and approval boundaries for preliminary supplier-side tender support.
Submit Your BOQ for a Preliminary Review
Send the available BOQ, tender specification, drawings or layout, required-document list, and deadline. Sunlurio will identify the suitable next document path or remaining clarification items.
Review boundary: Preliminary supplier-side review only. Final tender interpretation, compliance acceptance, and approval remain with the relevant buyer, consultant, project engineer, or tender authority. Document availability depends on confirmed scope, configuration, tender requirements, and document stage.