What to measure in a small electric fleet pilot

Start with the decision the pilot must support

A small electric fleet pilot is easier to evaluate when its purpose is written before the first vehicle goes out. Choose one operational question that the trial can answer. Can a vehicle complete a named route, carry the required load and be ready for the next shift under the proposed charging routine? That question gives the measurements a reason to exist and prevents the review from becoming a collection of unrelated statistics.

Write down who will make the decision at the end and what options are available. The team might continue the trial, adjust the route or charging procedure, gather more evidence or consider another application. A pilot does not need to end in expansion to be useful. It needs to produce a record that explains what happened and what the operator should investigate next.

Establish the route before the trial

Describe the assigned work in ordinary operational terms. Record the departure location, expected return time, stops, typical distance, load and any equipment used during the shift. Include tasks that drivers perform between journeys. A route is more than the distance displayed on a map, and the surrounding work can affect the schedule and the time available for charging.

Keep the original plan alongside each day’s actual record. If dispatch changes the assignment, note the change. Otherwise the review may compare a vehicle’s performance against a job it was never asked to do. The Department of Energy’s electric fleet guidance treats operational and charging considerations as part of vehicle planning. A route record makes those considerations visible to the people running the trial.

Record the charging window as an operating constraint

List when the vehicle is expected to be parked, where it will charge and who is responsible for connecting it. Compare that planned window with what happens in practice. A late return, an early departure or an occupied space can change the opportunity to charge even when the equipment itself is working. Record these events with enough context to understand their cause.

The site plan should come from the appropriate professional assessment and operating arrangements. The pilot log can reference that plan and record exceptions to it. It should not substitute for electrical design or installation work. Keep the contact for site issues available to the team, along with the agreed process for reporting a problem and deciding whether the vehicle should continue its assignment.

Keep the daily driver record short

Ask the driver for a small set of observations that can be completed reliably: whether the work was finished, any unplanned stop or wait, a charging problem and a brief note about using the vehicle. Where vehicle data is available, decide who will collect it and how it relates to the daily record. Avoid asking drivers to transcribe information that another system already captures accurately.

Use plain categories and leave space for an explanation. A checkbox marked “delay” needs a note about what caused it and how the team responded. The driver may notice a loading issue, an unfamiliar control or a change in the route that the manager cannot see from a summary. Those observations help distinguish an operational adjustment from a limitation that needs a different response.

Measure completed work alongside exceptions

The core record should show what the vehicle was assigned and what it completed. Include missed stops, work reassigned to another vehicle and any additional support required. If the day went as planned, record that too. A log containing only problems can distort the review, just as a report containing only successful averages can hide the exceptions that matter to the operation.

For each exception, capture the timing, the impact and the immediate response. A short event description is enough when it is specific. “Returned after the planned charging window because dispatch added a call” is more useful than “charging issue.” The team can then decide whether the event reflects an ordinary part of the duty cycle or an unusual circumstance that should be evaluated separately.

Assign one person to reconcile the week

Choose a pilot owner who brings together the driver notes, dispatch changes and charging record. That person does not have to perform every task, but someone must resolve contradictions and identify missing information. If two records disagree about a return time, clarify it while the day is still fresh rather than carrying the uncertainty into the final report.

Hold a brief weekly review with the people who can change the process. Look first at completed work and significant exceptions, then decide whether any action is needed. Give each action an owner and a date for review. A recurring problem without an assigned response will keep appearing in the log without improving the pilot.

Separate learning from changes to the experiment

It is reasonable to adjust a procedure when the team learns something useful. Record the change and the reason. If the charging routine changes halfway through the trial, the results before and after that change should remain distinguishable. The same applies to a new route, different load or revised shift schedule.

This makes the final account more honest and useful. The operator can explain that a process worked after a specific adjustment rather than treating the whole trial as if conditions were constant. It also helps another depot or team understand what they would need to reproduce. A successful result with an undocumented workaround is difficult to use for planning.

Include training and handover observations

Ask drivers and relevant staff which parts of the routine required explanation. The Department of Energy’s fleet guidance includes driver and technician training among the planning considerations. During the pilot, note the questions that repeat and the instructions people find unclear. Those observations can inform a short handover guide for the next person who uses the vehicle.

Review the handover itself. Can another authorized driver find the operating information, understand the charging routine and know whom to contact? If the process depends on one enthusiastic person being present, record that dependency. The pilot should help the operator see the support arrangements required for ordinary work, including days when the usual pilot participants are absent.

Write the decision memo while the evidence is available

At the end, summarize the assigned work, the period observed, the major changes and the exceptions. State which parts of the original question the evidence addresses and which remain uncertain. Attach the supporting records in a form the decision maker can inspect. Avoid replacing the evidence with a single score that conceals important operating conditions.

Then set out the next action and its basis. Continuing on the same route may be justified while another route requires a separate trial. A charging procedure may need more work before another vehicle joins it. The strongest outcome is a decision tied to recorded operations, with an owner for the next step. Start that process by defining one route, one charging window and one weekly review that the team can sustain.