Overview
Solar street lighting acceptance should not begin after the project is already installed. A reliable handover process starts before shipment, continues during site installation, and ends with a clear O&M document pack.
This checklist is written for EPC contractors, municipal owners, engineering consultants, UN / NGO project teams, and local installers who need to verify that the delivered solar street lights match the approved configuration and can be handed over without confusion.
Request an Acceptance & Handover Document Pack
Send your BOQ, approved configuration, project location, pole layout, installation responsibility, and handover document requirements. Sunlurio can help prepare datasheets, drawings, IES/LDT files, DIALux support when applicable, configuration notes, and an acceptance checklist.
For related project preparation, you can request a DIALux lighting simulation, review the datasheets and drawings pack, compare this checklist with the solar street light tender guide, or request an acceptance and handover document pack.
Who This Page Is For
- EPC contractors preparing site acceptance documents.
- Government or municipal teams checking delivered street lighting assets.
- Engineering consultants reviewing installation and performance.
- UN / NGO project teams that require transparent handover records.
- Distributors or agents coordinating supplier documents with local installation teams.
Project Situation
Many acceptance issues come from missing documents rather than failed products. The project may receive lights, poles, brackets, batteries, and controllers, but the site team may not have the approved datasheet, wiring details, DIALux assumptions, IES files, BOQ matching record, or installation checklist in one place.
For a municipal solar street light project, acceptance should verify three things: the supplied configuration matches the purchase documents, the installation follows the agreed technical requirements, and the final handover gives the owner enough information to operate and maintain the system.
Common Project Risks
- Shipment arrives without a complete packing list or configuration record.
- Battery, panel, or controller specifications are not matched to the approved BOQ.
- Pole foundation or anchor bolt details are checked too late.
- Site teams test lights during the day without understanding controller logic.
- Lighting performance is judged visually without reference to the layout assumptions.
- O&M documents are incomplete, making future maintenance difficult.
- Acceptance forms do not separate product, installation, and performance issues.
Required Information Before Recommendation
| Required Input | Why It Matters | Who Should Provide It |
|---|---|---|
| Approved BOQ and quotation | Confirms what was purchased | Buyer / EPC / supplier |
| Product datasheets | Confirms lamp, battery, panel, controller, pole, and bracket details | Supplier |
| Project layout or DIALux report | Defines pole spacing and lighting expectations | Consultant / supplier |
| IES / LDT files | Supports lighting simulation and future review | Supplier |
| Installation drawings | Guides pole, bracket, wiring, and foundation work | Supplier / EPC |
| Site inspection form | Records installation quality | EPC / installer |
| O&M handover documents | Supports long-term operation and maintenance | Supplier / EPC |
Technical Document Checklist
The acceptance file should be easy for a project owner to audit. It should connect the purchased item, the delivered item, the installed item, and the handover responsibility.
Pre-Shipment Document Checklist
| Document | Acceptance Purpose | Check Before Shipment |
|---|---|---|
| Final quotation or contract BOQ | Confirms item list and quantities | Model, quantity, configuration, accessories |
| Product datasheet | Confirms technical configuration | Lamp power, solar panel, battery, controller, enclosure |
| Packing list | Supports quantity and logistics verification | Carton count, pole parts, brackets, spare parts |
| IES / LDT files | Preserves lighting simulation basis | File version matches selected fixture |
| DIALux report, if required | Confirms layout assumptions | Road width, pole spacing, height, tilt, optics |
| Drawings | Supports site preparation | Pole, bracket, foundation, wiring or assembly drawings |
| Certificate or compliance documents | Supports tender and project file | Only include relevant, verifiable documents |
Site Installation Inspection Checklist
| Inspection Item | What to Check | Common Issue |
|---|---|---|
| Pole foundation | Anchor bolt position, concrete condition, leveling | Misalignment or weak foundation preparation |
| Pole and bracket | Height, arm direction, tightening, corrosion protection | Incorrect orientation or loose bolts |
| Solar panel | Tilt, orientation, shadow-free position | Shadow from trees, walls, signs, or adjacent poles |
| Battery and controller | Correct connection, enclosure condition, labeling | Wrong polarity or unclear wiring |
| Lamp head | Optic direction, fixture angle, gasket condition | Incorrect tilt or water ingress risk |
| Grounding / safety | Local requirement and installation quality | Missing or inconsistent grounding |
| Site record | Photos, location, pole number, issue log | No traceable acceptance evidence |
Lighting Performance Acceptance Items
| Item | Verification Method | Notes |
|---|---|---|
| Lamp operation | Night test or simulated darkness | Confirm controller mode and wake-up process |
| Operating profile | Compare with agreed dimming or timing logic | Avoid random pole-by-pole settings |
| Lighting coverage | Visual check plus layout reference | For formal projects, compare against DIALux assumptions |
| Uniformity concerns | Inspect road sections with dark zones | Check pole spacing, optic direction, and fixture angle |
| Autonomy expectation | Review configuration assumptions | Do not verify cloudy-day autonomy from one night only |
| Failure records | Record product, installation, or site cause separately | Helps decide warranty or corrective action |
O&M Handover Documents
| Handover Document | Why It Is Needed | Owner Benefit |
|---|---|---|
| Final approved datasheet | Defines the installed system | Easier future replacement and maintenance |
| As-built quantity list | Confirms installed assets | Clear project inventory |
| Installation photos | Provides traceable evidence | Faster dispute resolution |
| Controller setting note | Records operating mode | Avoids inconsistent future adjustments |
| Spare parts list | Supports maintenance planning | Less downtime |
| Troubleshooting guide | Helps local maintenance team | Faster first-level diagnosis |
| Warranty and contact path | Clarifies support workflow | Clear responsibility after handover |
Configuration / Acceptance Table
| Acceptance Level | Main Focus | Recommended Evidence |
|---|---|---|
| Document acceptance | Product and tender file match | BOQ, datasheet, certificates, drawings |
| Shipment acceptance | Delivered goods match order | Packing list, photos, serial/label records |
| Installation acceptance | Site work follows requirements | Inspection checklist, photos, issue log |
| Performance acceptance | Lighting result is reasonable for the design | DIALux reference, night inspection, operating mode record |
| Handover acceptance | Owner can maintain the system | O&M file, spare parts list, warranty contact |
Engineering Notes
Acceptance should separate product issues from installation issues. A lamp that does not turn on may be caused by wiring, low battery protection, controller mode, wrong test conditions, or product failure. A dark zone on the road may be caused by pole spacing, optic direction, fixture angle, or an unsuitable lighting layout.
For project teams, the acceptance checklist should be prepared before shipment and adapted to local site responsibility. This prevents the handover from becoming a late-stage argument about what was included, what was installed, and what evidence is required.
Product Issue or Installation Issue?
| Symptom | First Check | Possible Cause | Suggested Action |
|---|---|---|---|
| Light does not turn on | Controller mode, battery connection, panel darkness simulation, wiring polarity | Low battery protection, wrong test condition, loose wiring, controller setting, or product fault | Record pole number, wiring photo, controller status, and test condition before warranty judgment. |
| Dark zone on road | Pole spacing, fixture angle, optic direction, mounting height | Layout mismatch, wrong aiming, unsuitable optic, or blocked light path | Compare with layout assumptions and adjust angle/optic before blaming lamp output. |
| Short runtime | Battery charge state, dimming profile, local weather, panel orientation | Undersized autonomy, shading, wrong controller profile, or battery issue | Review configuration assumptions and site photos; test over multiple nights if needed. |
| Water ingress | Gasket, cable entry, enclosure, installation angle | Damaged seal, incorrect cable routing, loose cover, or fixture defect | Photograph ingress point and separate installation handling from product sealing issue. |
| Uneven pole-by-pole operation | Controller settings and commissioning record | Different dimming profiles, sensor mode differences, wiring inconsistency | Standardize settings and keep a commissioning record by pole number. |
Site Photo Record Checklist
A practical acceptance file should include traceable photo records for each inspection area:
| Pole number | GPS/location | Foundation photo | Panel orientation photo | Wiring/control box photo | Night lighting photo | Issue log |
|---|---|---|---|---|---|---|
| Record each pole ID | Map point or site reference | Before backfill and after completion | Confirm orientation and tilt | Record polarity, controller, and waterproofing | Record lighting result after dark | List issue, owner, and close date |
FAQ
Should solar street lights be tested before shipment?
Yes. Pre-shipment checking should verify the product configuration, packing list, and key documents. For project orders, a simple photo record and document pack can prevent many handover disputes.
Can lighting performance be accepted by visual inspection only?
Visual inspection is useful, but it should be compared with the project layout and DIALux assumptions when those documents are part of the tender. Visual checks alone can miss uniformity and spacing issues.
What should be checked first if a light does not turn on after installation?
Check controller mode, battery connection, panel darkness simulation, wiring polarity, and charge condition before concluding that the fixture is defective.
Who should keep the IES files and DIALux report after handover?
The owner, consultant, EPC contractor, and maintenance team should all have access to the final document pack. These files help with future expansion, replacement, and dispute review.
Is an acceptance checklist needed for small projects?
Yes, but it can be shorter. Even small municipal or donor-funded projects benefit from clear quantity, installation, and O&M records.
Request an Acceptance & Handover Document Pack
Send your BOQ, approved configuration, project location, pole layout, installation responsibility, and handover document requirements. Sunlurio can help prepare datasheets, drawings, IES/LDT files, DIALux support when applicable, configuration notes, and an acceptance checklist.
