Outdoor Garden Streetlight EPC: What Should the Contract Cover?

Nov 03, 2026

Outdoor Garden Streetlight EPC: What Should the Contract Cover?

An outdoor garden streetlight EPC contract should define who designs, supplies, installs, tests, and hands over the lighting system—and how each obligation will be accepted and paid for. It should also allocate responsibility for site conditions, utility connections, controls integration, changes, and defects. A fixture schedule alone is not enough.

Consider a garden project where the luminaires arrive on time but the power connection, pole foundations, or control network is not ready. Installation can stall even though the equipment supplier has performed its part. Clear interfaces and measurable completion criteria help the project team identify who must act, what the delay costs, and when payment is due.

Start with the scope and its boundaries

EPC generally combines engineering, procurement, and construction under one contract, but the actual division of work depends on the agreement. Attach a scope matrix and drawings that identify every lighting area, equipment item, and associated activity. Distinguish between work included in the contract, owner-supplied items, and work assigned to other contractors.

For garden and pedestrian areas, the scope may include surveys, lighting calculations, poles, foundations, luminaires, cabling, distribution equipment, controls, installation, testing, and reinstatement. State whether excavation, disposal, landscaping repairs, traffic or pedestrian management, and permits are included. These items are easy to overlook when comparing bids focused on luminaire prices.

Define the connection points for power and communications. The contract should say who obtains the supply, provides the feeder and protection equipment, pays connection charges, and coordinates energization. Apply the same discipline to interfaces with landscape, civil, building management, and network contractors.

Turn design intent into deliverables

Require the contractor to submit a design package before equipment is ordered. Depending on the site, this may include fixture layouts, lighting calculations, pole and foundation details, cable routes, electrical diagrams, control architecture, and a load schedule. Identify the information the owner must provide, such as site levels, existing utilities, landscape plans, and available power capacity.

Lighting criteria should be tied to the use of each area rather than a single site-wide figure. Paths, gathering areas, entrances, planting beds, and vehicle routes can have different needs. Specify the applicable project requirements for illumination, uniformity, glare control, color appearance, and operating hours. Identify the governing standards and local requirements in the contract documents rather than leaving the contractor to select them after award.

Set review periods and a procedure for resolving comments. Owner review should not silently transfer design responsibility: the agreement should state what approval means and whether the contractor remains accountable for meeting the agreed performance criteria.

Specify equipment without closing off verification

The equipment schedule should identify quantities, locations, electrical ratings, optical distributions, finishes, mounting arrangements, and environmental protection requirements. Request manufacturer data and drawings for approval, and define whether alternatives are permitted. An equivalent product should be assessed against the whole specification, including dimensions, electrical compatibility, maintenance access, and control functions—not just wattage.

Where architectural lighting is part of the same package, describe it separately from pathway lighting. For example, the LED Wall Washer, model XQD-017, is listed for building facades and landscapes, with a 36 W option, IP66 protection, and several beam-angle and color choices. If such a fitting is proposed, the schedule should identify the selected voltage, beam, color option, mounting details, and control arrangement. Flexible RGB/DMX control is relevant only where the design actually includes compatible controls.

Also establish a substitution process for unavailable components. Require a proposed replacement and its cost and schedule effects to be submitted before purchase; installation should not become the first opportunity for the owner to discover a change.

Make controls and integration a defined work package

A smart control system can introduce separate responsibilities for controllers, communication networks, software configuration, and third-party interfaces. The contract should identify the functions required at handover: for example, scheduled switching, dimming groups, alarms, or remote monitoring, if included in the project design.

Specify who provides network access, communication services, user accounts, configuration, and any software licenses. List recurring charges separately from the EPC price and state their duration and renewal responsibility. Where the system must connect to an existing platform, define the interface, information to be exchanged, and the party responsible for testing both sides. Avoid treating “smart-ready” as an acceptance criterion unless its hardware and functional meaning are defined.

Compare prices on the same scope

A lump-sum offer gives the owner a clearer initial price, but exclusions and assumptions still determine the final exposure. An itemized schedule helps compare bids and value changes; it does not by itself make uncertain quantities fixed. Ask bidders to identify allowances, provisional sums, unit rates, taxes, freight, commissioning, training, spare parts, and any recurring control-system costs.

Examine groundworks and power supply assumptions in particular. The contractor may price from incomplete information about buried services, soil, or existing electrical capacity. Record the baseline information available at tender and agree how unforeseen conditions will be reported, verified, priced, and approved. Require written authorization before changed work proceeds, except for a clearly defined emergency procedure.

Payment milestones should correspond to verifiable progress, such as approved design submissions, delivery of identified equipment, installation, successful testing, and handover. For equipment stored off-site, specify the evidence needed for payment, ownership and insurance arrangements, and the owner’s right to inspect it. Retention or other security, where agreed, should be linked to clear release conditions.

Schedule the interfaces, not just the installation

The programme should show design approvals, procurement lead times, access dates, civil readiness, utility connection, commissioning, and owner inspections. Identify which dates depend on information or actions by the owner and other contractors. Require notice when an interface threatens the schedule, together with the effect on subsequent work and a recovery proposal.

Define the process for extensions of time and delay-related costs, including notice periods and supporting records. Any delay damages or caps are commercial and legal decisions; they should be drafted consistently with the applicable contract terms and project jurisdiction rather than copied from an unrelated project.

Define completion through tests and records

Acceptance should be based on a documented test plan, not simply on switching the lights on. Agree who supplies instruments and labor, who witnesses tests, and how failures are corrected and retested. Depending on the design, the plan may cover electrical safety checks, control functions, circuit identification, visual alignment, and nighttime lighting measurements against the agreed criteria.

Site measurement conditions matter: define test locations, operating settings, and the method for dealing with temporary obstructions or ambient light. Separate substantial or practical completion, if used in the agreement, from final acceptance. State which outstanding items can remain on a punch list and which defects prevent the system from being accepted.

Handover deliverables should include as-built drawings, equipment schedules, test records, operating instructions, warranty documents, control-system configuration and access details, and maintenance information. Include training and spare parts only with specified quantities, content, and delivery obligations.

Protect operation after handover

Set the warranty start date and duration for the installation and identify any different manufacturer warranties for equipment. The contract should explain how defects are reported, response and repair obligations, access arrangements, and who bears removal, reinstallation, transport, and retesting costs. Manufacturer coverage alone may not resolve an installation defect or an interface fault.

Finally, assign routine maintenance responsibilities after acceptance: cleaning, inspection, replacement parts, control software administration, and communication-service payments. If maintenance is excluded, request the procedures and parts information needed to procure it separately. Before award, reconcile the contract, specifications, drawings, and bid exclusions under an agreed order of precedence; otherwise, conflicting documents can turn a small omission into a costly variation.

◉ MESSAGE

Submit