Digital vehicle handover in an electric fleet: record condition and responsibility

A digital vehicle handover documents which electric vehicle was handed over, when and in what recorded condition. It brings together mileage, state of charge, accessories, known defects and outstanding tasks. Both parties should subsequently be able to identify what has been confirmed and which points still need attention.

The process belongs to the vehicle history and needs a unique identifier. A digital confirmation is only as meaningful as the information recorded. A closed form alone proves neither technical readiness nor that every operational requirement has been met.

Define the reason and scope of the handover

When designing the workflow, distinguish between adding a vehicle, a permanent user change and a brief pool-car return. Each reason requires the relevant information. The shared foundation remains the specific vehicle, handover time and participating roles.

During initial receipt, documents, accessories and familiarisation may be recorded in more detail. For a recurring return, known information is already available; changes and new observations must still be easy to report.

Describe the workflow from the perspective of the person at the vehicle. They should be able to see which information they need to record themselves, which already comes from a source and which still requires confirmation. Pre-filled values must not silently appear as if they have just been checked.

Record EV-specific information with a timestamp

For state of charge, the percentage and the time it was read or captured belong together. Where necessary, note whether the vehicle was connected and what charging action has been agreed next. The statement “parked at the charge point” does not confirm an ongoing charging session.

Accessories may include the intended charging cables and assigned charging access. Describe their identity clearly enough for a missing component to be unambiguously identified. Credentials or personal secrets do not belong in generally readable handover notes.

A compact structure helps with recording:

The vehicle master data in your software provides the authoritative vehicle reference. Changes to the handover location must not create a new vehicle identity.

Document observations and outstanding issues separately

Give the person handing over the vehicle a simple way to describe issues. Suitable details are the location on the vehicle, observation time and an objective description. Photos can illustrate the condition, but should be taken selectively and show only the content required.

Define a “clarification required” status. A missing response must not automatically close the case. If the two parties record different observations, keep both traceably documented initially; a responsible role clarifies the case.

The guidance on vehicle checks by drivers explains the importance of visual and functional checks in the applicable operational context. The handover form supports documentation and does not replace the intended checks before use.

Example: a return with an unconfirmed charging start

Illustrative handover scenario: A pool vehicle is returned at 4:20 pm with 38 percent SOC. The person connects the vehicle to the intended charge point and records the connection. At this point, there is no confirmed start of energy transfer.

An assignment is planned for the following morning. The handover therefore keeps the task “Check charging start” open, with a responsible role and a response deadline. Only suitable confirmation closes this point. The original SOC and its timestamp remain unchanged as handover data.

An agreed cable is also missing from the boot. This issue receives a separate case. Clarifying the cable and checking charging can therefore be handled independently. The return is not given a blanket status indicating that everything has been resolved.

Test the form directly at the vehicle

Have several people carry out a typical process. Check whether vehicle selection, data entry and feedback work under actual conditions. These include a poor connection, interrupted entry and an issue noticed afterwards.

This checklist is suitable for acceptance:

• The vehicle and handover time are unambiguous.

• Pre-filled values show their source and data timestamp.

• Missing accessories and defects can be recorded specifically.

• Outstanding issues receive owners and deadlines.

• Both parties can view the documented status.

• Corrections remain traceable with a reason and timestamp.

• A technical outage has an agreed fallback process.

Initial receipt also requires appropriate familiarisation with vehicle operation as part of the organisational workflow. The guidance on operating electric vehicles safely emphasises preparing drivers for the vehicle's particular characteristics.

Connect recurring handovers with the process for booking pool vehicles. If charging access and charging organisation need to be coordinated, you can discuss your fleet requirements with StromNow. A digital handover function must be explicitly checked for your software environment.