A Practical Decision Framework (Structure, Glare, Maintenance)
Most handover disputes are evidence disputes. This guide defines a practical sign-off pack that links acceptance criteria → commissioning records → as-built documentation—so acceptance becomes predictable.
Answer: Make handover predictable by defining a sign-off pack that includes acceptance method, calculation evidence, IES/LDT version control, commissioning logs (aiming + scenes), and as-built documentation.
Use checklists and templates during installation and commissioning so evidence is collected once—correctly—and disputes are avoided.
Key takeaway #1: If it isn’t documented, it didn’t happen—sign-off depends on evidence.
Key takeaway #2:Aiming tables and commissioning logs are the core of acceptance, not optional extras.
Use this guide when you want predictable acceptance for stadium/sports lighting—especially for retrofits, multi-scene controls, or projects with strict constraints.
Typical scenarios
Owner sign-off: needs clear evidence and repeatable method.
Multi-scene controls: commissioning records are essential.
Auditable projects: public-sector or consultant-led approvals.
Key requirements / metrics
These pack elements turn “handover” into a controlled process.
Pack item
What it affects
Why it matters
Minimum evidence
Acceptance method
How pass/fail is determined.
Prevents disputes.
Grid + scenes + rules.
Calculation evidence
Design intent.
Aligns tender to design.
Report + assumptions.
IES/LDT register
Traceability of optics
Prevents wrong files/versions
Register + versions.
Aiming table
As-built aiming.
Controls glare/spill
Tilt/azimuth + photos
Commissioning logs
On-site verification.
Records deviations and fixes.
Scene tests + approvals
Definitions
A sign-off pack is the evidence bundle that proves compliance and makes future operation maintainable. It links what was required → what was designed → what was installed → what was verified.
Typical target ranges
Minimum pack target: everything required for acceptance and maintenance.
Include as-built BOM/version list and route documentation for long-term maintainability.
Include photos at key interfaces (aiming, glands, JBs) to reduce future troubleshooting time
Step-by-step workflow
Engineering diagram (workflow).
Workflow: define tier → map constraints → test 4/6/8 pole options in calculation → choose option with best risk profile → lock aiming limits and sign-off deliverables.
Inputs to collect
Tender acceptance method and targets
Site boundaries and spill/glare constraints.
Access method and safety rules.
Design decisions
Define the pack as a tender requirement
Standardize templates used by installers and commissioners.
Define who signs off each part and when.
Verification & sign-off
Complete checklist + signed logs + as-built documentation delivered.
Common mistakes
Collecting evidence after the fact (missing photos/logs).
No IES/LDT version control.
Aiming adjusted on site without records.
No as-built BOM/routes for future maintenance
Checklist / Template download
These downloads are generated in-browser (TXT/CSV) and can be replaced later with gated assets.
Sign-off Pack Checklist (CSV)
A master checklist for handover documents and evidence.
