Monitor your electric fleet’s state of charge: turn SOC into clear operational decisions

State of Charge, or SOC, describes the current level of the vehicle battery on the scale used by the vehicle. For fleet planning, this percentage only becomes useful alongside the vehicle ID, capture time and next assignment. A good SOC overview also shows where current information is missing.

The aim is a traceable decision before an assignment: is the known energy level sufficient, does the vehicle need charging, or is an update required first? A blanket green status based on a percentage alone does not answer this question.

Clarify where the state-of-charge value comes from

For each vehicle, record whether SOC comes from a connected vehicle source, another explicitly confirmed integration or a manual report. Check the meaning of the value and document when it was captured.

A charging transaction with a date and kilowatt-hours does not, by itself, provide an ongoing state of charge. The government guidance on measuring vehicle charging energy treats vehicle data and charging-session data as different collection methods. Their source and intended use must remain identifiable in your overview accordingly.

If a manual report is used, also store the reporting role and reason. A confirmed reading can support an agreed fallback process. It must not subsequently appear as a vehicle connection that continues to update.

Show freshness alongside the percentage

An overview should display the last known SOC and its capture time together. Add a data status that changes independently of the charge level. This makes an old value visible even when its percentage initially looks reassuring.

A simple structure is suitable for the display:

Set freshness requirements according to the workflow. A vehicle that has been driven since the report needs another check. Even a period parked must be known and reliably documented if you use it to draw conclusions.

Define the target state for the specific assignment

An SOC target follows from the required energy demand, a justified operational reserve and vehicle-specific requirements. Record these foundations separately. The percentage alone does not yet say how many kilometres are possible under the conditions of the next assignment.

Do not use a uniform minimum charge simply because it is easy to configure. Different assignment lengths and vehicle specifications need a traceable allocation. Range planning for electric fleets explains how energy demand and reserve feed into a planning decision.

The permitted or recommended charging target must also suit the vehicle. The government guidance on EV battery care refers to the relevant vehicle documentation for the appropriate charging range. A general fleet rule does not replace this check.

Example: three vehicles before departure

Illustrative dispatch example: Three vehicles are scheduled for 8 am. Targets for their respective assignments have been set using documented assumptions. At 7:40 am, Vehicle A reports an SOC of 72 percent against a target of 65 percent. Vehicle B reports 48 percent against a target of 60 percent. For Vehicle C, only an 80 percent reading from the previous evening is available.

A passes the defined energy check, provided the other operating conditions are unchanged. For B, the charging or assignment plan is reviewed. For C, the freshness of the data must be clarified first. The high but old percentage does not lead to automatic release.

The responsible person confirms that B and C have been handled. The completion record includes the checked value, timestamp and decision made. This keeps the reason for using or rescheduling a vehicle traceable after the shift.

Establish a daily review workflow

Choose a time before dispatch when all scheduled vehicles are considered. The overview should show outstanding cases first. Link each case to a responsible role and a response deadline that fits the departure time.

Five questions help with implementation:

• Are the source and capture time visible for every value?

• Do planned assignments have a documented energy requirement?

• Is missing data distinguished from insufficient charge?

• Is there a confirmed fallback process?

• Is the decision recorded after the case has been handled?

Suitable notifications for EV fleets can complement the workflow. Explicitly check which signals are actually available in your software and how they are triggered.

At StromNow for fleets, you can discuss requirements around charging visibility and operational preparation. An ongoing SOC connection must be clarified separately for your vehicles.