EV Charger Commissioning Acceptance Checklist: What to Include in a Handover Package

Commissioning is not complete when equipment is energized. The project still needs evidence that the installed configuration matches the approved baseline, required functions were tested, faults can be recovered and open deviations have an owner. For teams delivering DC charging solutions, an EV Charger acceptance package should make the final decision auditable without becoming a promise of ongoing field service.

Use one primary artifact: an Acceptance Package Checklist. It defines the evidence, owner and scope needed for a controlled sign-off.

Set the acceptance boundary

Name the object and project scope before testing: charger, site, network, vehicle-side interface and handover owner. State what is outside the current sign-off, such as a future expansion, third-party network service or later vehicle pairing. This keeps an accepted installation from being read as a guarantee for every later configuration.

Owner names are a starting allocation tool, not an assumption about which supplier performs the work.

Freeze the installed baseline before testing

Capture the equipment identity, firmware or software version, option codes, connector arrangement, network settings, metering configuration and relevant site-input references. Link the baseline to approved drawings, installation records and change notices. If a readiness input changed after planning, record the change before interpreting the test result.

The baseline should answer what was installed, which revision was tested, which site and network conditions applied, which deviations were accepted temporarily and who can change the configuration. A test against an unknown state is not a reliable handover record.

Record functional, safety and communication evidence

Use the agreed acceptance criteria for startup, stop behavior, output control, alarms, protection responses, connector handling, metering signals and expected operating sequences. Keep electrical and safety evidence separate from power-conversion results. Record the method, instrument or log source, conditions, result, witness and deviation rather than relying on a single pass/fail cell.

Communication evidence has distinct layers. A protocol conformance result concerns a defined implementation and scope. An end-to-end interoperability check concerns the selected station, controller or CSMS, vehicle or partner, network and configuration working together. Record the protocol name, version and profile, tested implementation, assumptions, selected pairing, logs, exceptions and owner of any remaining check. A protocol listing or component record is not proof that every project pairing works.

Make recovery and open deviations visible

For each controlled fault or interruption, record the trigger, expected behavior, observed result, reset or recovery path and open deviation. Metering and network rows should identify the source, timestamp, configuration, data path and reviewer. If a result depends on a site input, link it to the baseline used for the test and record any deviation before acceptance.

Use explicit states: Ready to test when the baseline, procedures and witnesses are available; Tested when logs and observations support a result; Conditional when an open item has an owner, due date and risk treatment; Handover-ready when documents and responsibilities are complete; and Accepted / Held when the authority records scope and exclusions.

Keep one record for each deviation rather than hiding several issues in a general note. State the affected configuration, immediate risk, interim treatment, owner and closure evidence. If the deviation changes a site input, connector option, network path or test case, link it back to the baseline and reopen the relevant acceptance row. The package then remains usable when the same equipment is reviewed after a controlled change.

Keep project responsibility evidence-based

Training records, operating documents or O&M references in an acceptance package mean that the project recorded what was delivered, by whom and under which agreement. They do not establish that a particular supplier promised those services. The contract, project RACI and acceptance record must establish responsibility.

If UUinside material is used for architecture context, keep it separate from a project-specific delivery obligation. Likewise, UUGreenPower product-material context can identify a named product row to verify, but it does not prove onsite acceptance, commissioning, training, O&M or SLA responsibility.

Release the handover package

Before sign-off, confirm that the installed object and configuration are named; site and network assumptions are attached or referenced; functional, electrical, safety, protocol and interoperability evidence are separated; faults, recovery and metering are recorded; applicable documents and open deviations are included; each unresolved item has an owner and closure rule; and the sign-off states what was accepted and excluded.

An EV charger commissioning acceptance checklist is complete when the next decision-maker receives a traceable record of the tested configuration and its limits. It is a handover method; project responsibilities should remain tied to the agreed contract, RACI and acceptance scope.