The EV is in the lot — now what?

A growing number of field operations are putting their first electric van or truck into service, and most of them discover the same thing within a month: the vehicle is great, and their whole system for tracking vehicles suddenly doesn't fit it. The fuel log assumes gallons. The cost-per-mile math assumes a pump receipt. Dispatch assumes you can top up anywhere in five minutes. None of that is true for the EV, and if you keep treating it like a diesel with a quieter engine, you'll dispatch it onto routes it can't finish and report a cost-per-mile that's pure fiction.

This isn't an argument for or against electrifying — that decision depends on your routes, your local energy prices, and incentives that change constantly, and it's yours to make. This is about the operational reality after the EV arrives: what genuinely changes about scheduling, charging, and costing it, and what stays exactly the same. Because the parts that change will bite you if you ignore them, and the parts that don't are where most of the fear turns out to be unfounded.

Range is a dispatch constraint, not a fuel gauge

The single biggest mental shift is that range stops being a background fact and becomes a dispatch input. With a diesel van, range is effectively infinite — you can always find a station, and a fill-up costs five minutes. With an EV, the day's route has to fit inside the battery, because a fast charge is twenty to forty minutes and a depot charge is hours. That changes how you build the day.

  • Match the vehicle to the route, not the tech's preference. A dense, in-town day of short hops is the EV's best case. A day with a 90-mile leg to a rural site and back is where you reach for the diesel. This is the same skill-based matching discipline you already apply to techs, extended to the vehicle: the EV has a "skill" — its realistic range today — and the job has a requirement.
  • Plan the charge into the schedule. If the EV needs to top up mid-day, that window is a scheduled event like a lunch or a PTO block, not a surprise. The worst EV days are the ones where nobody planned the charge and the tech burns an hour hunting for a working charger between jobs.
  • Respect winter and load. Cold weather and a fully loaded van both cut real range below the sticker number. The operations that get burned are the ones that dispatch to the optimistic figure in January. Build in a margin and revisit it seasonally, the same way you'd adjust for seasonal demand.

Treat range as a hard constraint on which jobs the EV can take, and it's a perfectly reliable vehicle. Pretend it's infinite, and you'll strand a tech.

Cost-per-mile: the numbers don't transfer

The other place an EV breaks your existing system is costing. A diesel's cost-per-mile comes from pump receipts and is easy to capture. An EV's cost is messier and lives in three different buckets that you have to capture differently or you'll never know what the vehicle actually costs:

  1. Depot charging — electricity billed to your shop's meter, often at a different rate than home or public charging, sometimes time-of-use. This is usually the cheapest energy and the bulk of the miles.
  2. Public DC fast charging — the expensive stuff, billed per kWh or per minute, captured as a session with a receipt like any fuel stop.
  3. The tech charging at home — a reimbursement question that doesn't exist for diesel and surprises every operation that electrifies. You need a per-kWh policy and a way to log it.

The temptation is to wave at "it's cheaper to charge than fuel" and skip the tracking. Don't — that's how you end up unable to answer whether the EV is actually saving money or whether public fast-charging is quietly eating the savings. In Hosting Field the fuel log is unified across gas, diesel, LPG, and electric: an EV charge session is logged with its energy and cost and receipt the same way a fill-up is, and the system rolls a per-vehicle efficiency figure — MPG for the diesel, MPGe for the EV — so the two sit side by side in the same trip-cost rollup. That's what lets you compare a real cost-per-mile across the mixed fleet instead of guessing. For shops that run a charge controller, an optional evcc integration can feed session data in, but the log stands on its own without it. Be clear on the boundary: Hosting Field captures the charge sessions and computes the efficiency; deciding what your blended energy cost should be, and whether the EV is winning, is your analysis to run on top of clean data.

What stays exactly the same

Here's the reassuring part, and it's most of the system. Almost everything you already do to run a vehicle carries over to the EV unchanged:

  • Service intervals still apply — fewer oil-type items, but tires, brakes, cabin filters, and software still need a preventive-maintenance schedule, and an EV that misses service strands a tech exactly like a diesel that does.
  • Document expiry doesn't care about the drivetrain. Insurance, registration, and inspection still lapse if nobody watches them, and tracking document expiry is identical for an EV.
  • Mileage capture for tax deductions works the same — the miles are miles, captured off the job's drive legs, regardless of what's turning the wheels.
  • The EV is just another row in the roster — VIN, plate, make/model, odometer, and now a fuel type of electric. It dispatches, gets assigned to jobs, and reports up alongside the rest of the fleet.

The drivetrain changes range planning and how you capture energy cost. It changes almost nothing about the discipline of running vehicles as first-class data, which is the part that actually keeps a fleet healthy.

What to measure

  • Real MPGe versus the sticker — your logged charge energy against actual miles driven, per vehicle. The gap between the rated figure and your real-world number is your true planning range, and it's the number dispatch should actually use.
  • Blended energy cost-per-mile, by charging source — depot versus public versus reimbursed home charging. This is the number that tells you whether the EV is saving money or whether fast-charging is eating the win; you can't see it without logging the three buckets separately.
  • EV utilization on EV-suitable routes — how often the electric vehicle got the dense, short-hop day it's good at versus sitting while a diesel ran a route the EV could have handled. Low utilization usually means dispatch doesn't trust the range, which is a data problem you fix by measuring the real one.

An electric vehicle rewards an operation that treats it as a genuinely different machine and punishes one that treats it as a diesel with a plug. The differences are real but bounded: range becomes a dispatch constraint, energy cost splits into buckets you have to capture deliberately, and that's most of it. Log the charge sessions the way you log fuel, let the efficiency numbers sit side by side, match the vehicle to the route it can actually finish — and the EV stops being a science experiment in the corner of the lot and becomes just another well-understood truck on the board.