If you’re delivering a solar street lighting project for an EPC client or municipality, the fastest way to avoid disputes is simple:
Don’t hand over “lights”. Hand over auditable evidence.
A site can look bright and still fail acceptance if any of these are missing:
- Lux/uniformity proof vs the approved criteria
- Aiming & installation consistency vs the approved layout
- Dimming profile & operating plan consistency
- Traceable serial/packing/as-built documentation
- O&M plan + spares + commissioning record
This guide gives you a review-safe acceptance & handover checklist you can copy/paste into your project close-out process.
✅ Need a tender-style pack in 24H (DIALux/Relux + IES/LDT + BOQ mapping + acceptance pack)?
Request here →
Acceptance-ready = measured performance + as-built proof + operating profile + traceable handover pack.
Quick Answer (30 seconds)
A solar street lighting project is “acceptance-ready” only when you can prove four things:
1) Measured performance meets the approved target (Avg/Min + uniformity)
2) As-built installation matches the approved layout (height/spacing/tilt/aiming)
3) Operating profile is correct (timer/dimming schedule + autonomy assumption)
4) Handover evidence is complete (BOQ mapping + serial/packing + O&M + sign-off forms)
If any one is missing, acceptance becomes a delay loop.
The Top 3 Reasons Acceptance Gets Delayed (In Real Projects)
1) No measured table (only photos or “looks bright”) → reviewers cannot sign off.
2) As-built differs from approved layout (spacing/height/aiming) → uniformity fails, disputes start.
3) No traceability (BOQ ↔ installed qty ↔ packing/serial) → the owner can’t audit what was delivered/installed.
Here’s the blunt version: if it can’t be audited in 10 minutes, it will be questioned for 10 days.
And in government jobs, “questioned” quickly becomes “held”.
One real-world pattern we see again and again: the site looks fine, but the owner refuses to sign because there’s no Avg/Min/Uniformity table—only photos. That one missing table can cost weeks.
Standards Alignment (International Reference)
This checklist is aligned with common international frameworks for lighting performance and system commissioning documentation. Final acceptance must always follow your tender/authority’s stated criteria.
Non-negotiable rule: If the tender states a standard, the acceptance record must cite it and show pass/fail.
If it’s not cited, it’s treated as non-compliant evidence.
| Parameter / Evidence | Reference Standard (Common) | What you verify on site |
|---|---|---|
| Road lighting performance (targets & uniformity) | EN 13201 / IES RP-8 / CIE 115 | Measured Avg/Min/Uniformity vs approved criteria |
| Ingress protection rating | IEC 60529 (IP) | Sealing integrity checks; water/dust ingress signs |
| Impact protection rating | IEC 62262 (IK) | Lens/cover integrity; damage after transport/installation |
| PV module safety/performance (if required by tender) | IEC 61215 / IEC 61730 | Supplier evidence pack; labeling/traceability |
| Solar system test & documentation (handover discipline) | IEC 62446 (PV commissioning documentation) | Clear commissioning record + as-built + O&M archive |
| Corrosion resistance (coastal projects) | ISO 9227 / ISO 12944 (environment class) | Coating system proof + fastener material + site condition notes |
Practical rule: Standards don’t help if the evidence isn’t traceable.
Every acceptance item must map to a document, a photo, a measurement record, or a signed form.
Technical Qualification Gate (Hard Rule Before Sign-Off)
Do NOT sign acceptance if any of the following are missing:
- Lux/uniformity record (measurement method + points + results table)
- As-built layout (pole positions, heights, spacing, setbacks, aiming notes)
- Operating profile proof (timer/dimming schedule + commissioning confirmation)
- Traceability pack (BOQ mapping + serial/packing list + delivered qty reconciliation)
No record. No mapping. No acceptance.
If the report has no IES/LDT filename (where photometrics are relevant to approval), it’s not a report—it’s marketing.
Download: Commissioning & Site Acceptance Template (PDF)
Use this as your close-out attachment (commissioning + site acceptance style). It’s designed for print + signature + archive.
Download (PDF) →
This PDF matches Section C/F/H of this blog
What’s inside (so you know it’s worth downloading):
- Commissioning confirmation block (timer/dimming/settings)
- Site acceptance checklist format (sign-off ready)
- Record-friendly layout (easy for EPC / municipality / consultant)
Acceptance & Handover Checklist (Copy/Paste)
A) Pre-Acceptance Document Check (Before Site Visit)
- Approved design basis available (targets + layout + operating plan)
- BOQ mapping is available (BOQ → model → IES/LDT → layout qty)
- Delivered scope is defined (lights / poles / brackets / anchor bolts / spares)
- As-built deviations log prepared (if spacing/height changed on site)
- Safety method statement for night testing prepared (traffic control, PPE)
B) Site Installation Verification (As-Built Reality)
Poles & mounting
- Pole height matches as-built drawing (record any deviation)
- Pole spacing and setbacks match the approved layout (or documented deviation)
- Bracket/outreach length matches design assumption
- Tilt/aiming is consistent across the section (note any outliers)
- Foundation/anchor bolt installation conforms to drawing and torque guidance (if applicable)
Luminaire integrity
- No water ingress/fogging under lens
- No cracked lens, damaged gasket, or loose fasteners
- Cable routing and connectors are secure (no exposed copper, no corrosion)
C) Photometric Acceptance (Lux / Uniformity)
What to measure
- Measurement area and grid points defined (avoid cherry-picked “bright spots”)
- Use worst-case evaluation: between poles and edge areas
- Record ambient conditions (surface condition, traffic, weather, time)
What to record
- Target criteria referenced (tender/authority requirement)
- Results table: Avg / Min / Uniformity (metric per spec)
- Pass/fail statement with signature lines
If you cannot produce a clean results table, the project is not “tested”—it’s just “observed”.
Avoid “pretty screenshots”. Acceptance requires a grid method + results table (Avg/Min/Uniformity).
Anti-cheat check (simple): If the measurement points are placed only under the brightest spot, the test is meaningless. A real acceptance grid must cover the darkest areas between poles.
D) Aiming & Commissioning (High-Impact, Often Missed)
- Aiming reference method documented (rotation marks / tilt method / aiming tool)
- High-mast (if applicable): aiming plan and verification photos included
- Commissioning checklist completed (per section/site)
Typical failure pattern: one section is aimed differently → uniformity collapses → disputes start.
Aiming inconsistency is a common reason uniformity fails after installation.
Here’s the harsh truth: aiming errors don’t show up in a daytime walk-through. They show up in the owner’s night inspection—when it’s too late and everyone starts blaming “product quality”.
E) Operating Plan Verification (Timer / Dimming / Autonomy)
- Correct ON/OFF schedule verified (controller setting + on-site observation)
- Dimming profile verified (time segments + % power)
- Any motion/remote control function tested (if included)
- Autonomy basis documented (backup days; behavior after cloudy days)
Hard rule: If the bid assumes 100% power all night with no energy profile, ask for clarification before acceptance.
Solar projects live or die on the operating profile. No profile = no trustworthy autonomy claim.
F) Traceability & Quantity Reconciliation (BOQ ↔ Layout ↔ Delivered)
- Delivered quantity matches BOQ and as-built layout
- Each model/optics configuration is traceable (label/serial → model code)
- BOQ mapping table attached (review-safe audit trail)
- Packing list includes:
- model codes
- quantities
- serial numbers (where applicable)
- carton/packing marks
Traceability prevents disputes: what was approved, delivered, installed, and signed off.
Blunt rule: If BOQ qty cannot reconcile with installed qty, do not sign. Period.
G) Handover Pack (Documents the Owner Must Receive)
Minimum handover pack (one-table rule):
| Pack item | What it proves | Typical dispute it prevents |
|---|---|---|
| As-built layout (with deviations) | Installed reality matches the signed plan | “You installed different spacing/height” |
| Lux/uniformity record (grid + table) | Measured performance meets criteria | “It looks bright but fails in dark spots” |
| Operating settings record (timer/dimming) | Night behavior matches the agreed plan | “Runtime/autonomy doesn’t match promise” |
| BOQ mapping + delivered qty reconciliation | What was quoted = what was delivered/installed | “Wrong model/optics/quantity delivered” |
| Warranty + spares plan | Risk ownership is defined | “Who pays for failures/spares?” |
| O&M plan + troubleshooting basics | Maintenance can be executed locally | “No one knows how to maintain it” |
Also include as applicable:
- Datasheets and installation instructions
- IES/LDT references (if relevant to approval)
- Training/briefing record (if included)
A review-safe handover pack is a structured archive, not scattered files.
H) Owner Sign-Off (Clean Acceptance Closure)
- Punch list created (if any) with deadline and responsibility
- Final acceptance certificate signed
- Handover pack delivered and archived
- Training/briefing completed (if included)
Close-out = punch list cleared + signed acceptance + archived handover pack.
What to Upload for a 24H Engineering Review (If You Want Us to Audit Your Pack)
Send any ONE item to start:
- BOQ template (even incomplete)
- Road drawing / cross-section
- Google Map pin + basic notes
What you will receive from us within 24H (so you know what happens next):
- A gap list (what is missing to pass acceptance cleanly)
- A minimum handover pack outline (documents + naming + sign-off items)
- A measurement & photo checklist (what to capture on site for traceability)
Helpful proof pages:
FAQ (EPC / Government Acceptance)
1) What is the most common reason acceptance gets delayed?
Missing auditable evidence: no results table (Avg/Min/Uniformity), no as-built deviation log, or BOQ/layout quantities cannot be reconciled.
2) Do we really need uniformity, not just “average lux”?
Yes for most public lighting specs. A bright average can still hide dark spots. Reviewers and owners often care about worst-case areas.
3) Can we accept screenshots instead of a proper report/record?
For formal acceptance, usually no. Screenshots are not traceable. You need a record: method, points/grid, results table, and sign-off.
4) How do we handle on-site spacing/height changes versus the approved design?
Document deviations and re-verify performance (or update the simulation/assumptions). Acceptance should be based on as-built reality, not the original plan.
5) What operating settings must be confirmed before sign-off?
Timer schedule + dimming profile + any special behaviors (after cloudy days / low SOC) must match the agreed operating plan.
6) What should the owner receive as the minimum “handover pack”?
As-built layout + commissioning record + settings + warranty + O&M plan + traceability/packing list. Without these, future disputes are guaranteed.
Next Step (High-Conversion CTA)
Don’t gamble with tender timelines or public safety.
If the acceptance pack cannot withstand a traceability audit, don’t sign it.
✅ Upload BOQ/drawings/report for a 24H audit reply:
Request here →
Contact your team directly →
Factory & quality due diligence →
