Commercial fleet owners: Are you losing profits?

A fleet can lose money without one large problem showing up on the books. Small fuel losses, long idle periods, missed service checks, unplanned repairs, and empty return trips can add up across dozens of vehicles.

I have seen managers focus on fuel prices while overlooking the daily habits that create higher operating costs. A van that idles for 30 minutes each day may seem harmless. Across a 20-vehicle fleet, that habit can become a steady expense with no clear business return.

The good news is that fleet costs often leave useful clues. I can find many of them by reviewing a few basic records and comparing them with driver activity.

Look beyond the fuel bill

Fuel is easy to measure, so it often receives the most attention. It is only one part of the picture.

I review:

• Fuel purchases by vehicle
• Fuel use per mile or kilometer
• Engine idle time
• Unusual changes in fuel consumption
• Route distance compared with planned mileage
• Fuel card activity outside normal work hours

A vehicle with higher fuel use may have a mechanical issue, a heavy load, poor tire pressure, or a driving pattern that needs attention. The data does not prove the cause by itself. It shows me where to ask better questions.

A simple monthly comparison can help:

Fuel cost per mile = total fuel cost ÷ total miles driven

I compare vehicles that perform similar work. A delivery van should not be judged against a light-duty service car. Similar vehicles working on similar routes give me a more useful baseline.

Track idle time as a separate cost

Idle time is easy to miss because the vehicle is not moving. The engine is still using fuel, adding wear, and producing emissions.

I look for patterns such as:

• Long idle periods at job sites
• Engines running during driver breaks
• Repeated idling before the first appointment
• Vehicles left running outside warehouses
• Idle time that does not match the work order

An HVAC company with 18 service vans found that several vehicles were idling during long customer visits. The managers did not blame the drivers. They checked the work process and learned that technicians were using the vehicle as a source of power while waiting for equipment. The company adjusted its site routine and checked whether portable power options made sense for selected jobs.

The lesson is simple: idle data should lead to a process review, not automatic punishment.

Connect maintenance records with vehicle use

A maintenance calendar alone may not show the full picture. I compare service records with mileage, engine hours, fault codes, and driver reports.

This can reveal:

• Repairs that repeat on the same vehicle
• Tires wearing faster than expected
• Batteries failing after extended idle periods
• Oil service based on the wrong usage pattern
• Vehicles spending too much time in the repair shop
• Small defects that become larger repair bills

A vehicle that returns with the same fault several times may need a deeper inspection. Replacing the same part again may only delay the underlying repair.

Preventive maintenance also affects driver productivity. When one vehicle is unavailable, another vehicle may cover the work. That replacement vehicle can create overtime, extra mileage, and schedule changes.

I prefer to measure the full cost of downtime rather than looking only at the repair invoice.

Review routes and empty miles

A route can look busy while still wasting distance. Drivers may travel between jobs, return to a depot for parts, or cross the same area several times in one day.

I check:

• Planned distance versus actual distance
• Empty miles between jobs
• Repeated travel through the same area
• Missed delivery windows
• Last-minute job changes
• Depot visits caused by poor parts planning

A small routing change may reduce mileage, but route planning should not ignore service quality. A shorter route that creates late arrivals can damage customer relationships and place more pressure on drivers.

I ask two questions:

1. Can the work be grouped by location?
2. Does the schedule give drivers the parts, time, and information they need?

Route software can help, but clean job data matters more than a complicated dashboard. If addresses, appointment times, or vehicle capacity details are wrong, the route plan will also be weak.

Measure the cost of driver turnover

Fleet profit is connected to the people who operate and maintain the vehicles. When drivers leave, the business may face recruitment costs, training time, agency fees, and lower productivity during the transition.

I review:

• Overtime linked to staff shortages
• Accident frequency by route or shift
• Driver complaints about vehicle condition
• Training hours for new drivers
• Missed work caused by poor scheduling
• Inspection issues reported by drivers

Drivers often notice problems before management sees them in a report. A loose door, weak air conditioning, poor storage, or unreliable equipment can affect daily work. I give drivers a simple way to report issues and track whether the business responds.

This can improve vehicle care without turning every inspection into a long administrative task.

Separate useful data from noise

Fleet platforms can produce large amounts of information. More data does not always create better decisions.

I start with a small group of measures:

• Cost per mile
• Fuel use by vehicle
• Idle hours
• Maintenance cost per vehicle
• Downtime days
• Unplanned repair frequency
• Empty miles
• Overtime linked to fleet issues

I review the same measures each month. This makes changes easier to spot and keeps the team focused.

A dashboard should answer practical questions:

• Which vehicle needs attention?
• What caused the cost change?
• Who needs to act?
• When will the result be checked?

If a report cannot guide a decision, I remove it from the regular review.

Build a simple fleet cost check

I use this process:

Step 1: Set a clear baseline
Record current fuel, maintenance, mileage, downtime, and overtime costs.

Step 2: Compare similar vehicles
Group vehicles by model, age, use, and route type.

Step 3: Find unusual changes
Look for a sudden rise in fuel use, repair frequency, idle time, or mileage.

Step 4: Speak with the people involved
Drivers, technicians, dispatchers, and finance staff may each hold part of the answer.

Step 5: Test one change
Adjust a route, repair process, inspection habit, or scheduling rule.

Step 6: Check the result
Use the same measures after the change. Keep the change if it helps without creating a new problem.

I avoid changing several processes at once. When too many variables move together, it becomes hard to know what worked.

A profitable fleet does not depend on cutting every expense. Some costs protect safety, service quality, and vehicle life. The aim is to find spending that brings little value, then fix the process behind it.

When I review a fleet, I look for quiet losses before they become large ones. Fuel records, maintenance history, route data, and driver feedback can show where the money is going. A regular review gives managers a practical way to act before small leaks become part of normal operating costs.

Fuel, maintenance, labor, and vehicle downtime can reduce fleet revenue before a vehicle completes its next delivery. I often see fleet operators focus on finding more work while small daily losses continue in the background.

A van that idles for 40 minutes each day uses fuel without moving a package. A missed service check can turn a low-cost repair into several days of downtime. An inefficient route adds miles, driver hours, and wear to every trip.

A practical cost review can help me find these leaks and decide which changes are worth making.

Track the costs that change every week

I start with a simple record for each vehicle:

• Fuel purchases and average fuel use
• Mileage and route distance
• Repair and service costs
• Tolls and parking fees
• Driver hours
• Unplanned downtime
• Number of completed jobs

This information does not need to begin with complex software. A spreadsheet can show patterns when the data is updated on a regular schedule.

For example, if one van travels 15% more miles than similar vehicles while completing a similar number of jobs, I have a clear reason to review its routes, loading plan, and driving pattern.

Reduce empty miles with better route planning

Empty miles create cost without producing revenue. I review where each vehicle starts, where it finishes, and how often it travels without a load.

Route planning can help me:

• Group nearby deliveries
• Limit backtracking
• Match vehicle size with job needs
• Plan return loads when suitable work is available
• Avoid routes with regular delays
• Give drivers a clear sequence of stops

A local delivery team with 12 vans may discover that several vehicles cross the same area during the same shift. Moving a few stops between routes could reduce duplicate travel without adding another vehicle.

The change needs to fit delivery windows, driver hours, vehicle capacity, and customer needs. A shorter route is not useful if it creates missed appointments.

Watch fuel use without placing pressure on drivers

Fuel costs often rise through small habits rather than one large mistake. Long idling periods, sharp acceleration, underinflated tires, heavy loads, and poor route choices can all affect fuel use.

I use fuel records alongside mileage. The key measure is not the amount spent at one fuel stop. It is the cost per mile or cost per completed job.

A simple review may show:

• Which vehicles use more fuel than similar models
• Whether fuel use rises after a maintenance issue
• Which routes create long idle periods
• Whether tire pressure checks are being recorded
• Whether load weight affects fuel use

Driver feedback matters here. A driver may know that a loading area causes long waits or that a certain route regularly creates delays. Data shows the pattern, while driver experience can explain it.

Prevent avoidable repair bills

Preventive maintenance gives me more control over vehicle costs. I schedule checks for oil, brakes, tires, lights, batteries, and other parts based on manufacturer guidance and operating conditions.

The process can include:

1. Set a service record for each vehicle.
2. Record mileage after every inspection.
3. Note small issues before they affect the route.
4. Keep a list of parts that need attention.
5. Plan service during lower-demand periods when possible.
6. Review repair costs by vehicle and age.

A tire with low pressure may look like a minor issue. It can increase fuel use and wear, then create a safety concern if it is ignored. Early attention is often easier to plan than an unexpected breakdown.

Maintenance records also help me decide whether an older vehicle still fits the fleet. Purchase price alone does not show the full cost of ownership. I look at repairs, downtime, fuel use, resale value, and the type of work the vehicle handles.

Use vehicle data with a clear purpose

Fleet tracking tools can show mileage, idle time, route history, and vehicle location. These tools are useful when the fleet has a defined problem to solve.

I may use tracking data to answer questions such as:

• Which routes take longer than planned?
• Where do vehicles spend time without moving?
• Which vehicles need more maintenance?
• Are jobs being assigned to the right vehicle?
• How much time is lost between stops?

The goal is not to collect data for its own sake. The goal is to turn a pattern into a reasonable action.

Data use should also respect privacy, local requirements, and clear workplace policies. Drivers need to understand what is being recorded and why.

Review vehicle use before adding another vehicle

A new vehicle can support growth, but it also brings payments, insurance, service, registration, fuel, and depreciation.

Before adding one, I check:

• Current vehicle capacity
• Unused hours during the week
• Average jobs per vehicle
• Seasonal demand
• Outsourcing costs
• Rental costs during busy periods
• Revenue lost through vehicle downtime

A fleet may need better scheduling rather than more vehicles. Another fleet may already be operating close to capacity and need extra support. The decision should come from job volume and cost records, not from a single busy week.

Build a cost review that people can follow

A useful fleet process should be simple enough for the team to use every day.

I suggest a weekly review that covers:

• Fuel cost per mile
• Maintenance cost per vehicle
• Total idle time
• Empty miles
• Completed jobs
• Unplanned downtime
• Customer delays linked to fleet issues

I set a small number of targets and review the results over several weeks. Cutting costs too quickly can create new problems, such as delayed service, overloaded drivers, or skipped maintenance.

Keeping more revenue does not mean reducing every expense. It means separating necessary operating costs from avoidable waste. A well-maintained vehicle, a sensible route, and a clear record can support better decisions without placing extra strain on the team.

Every mile has a cost.

Fuel, driver hours, vehicle wear, empty returns, delayed deliveries, and unplanned repairs can reduce fleet profit without drawing much attention. Many fleet owners notice the problem only after reviewing a monthly report. By then, the lost money is already tied to completed trips, idle vehicles, and missed delivery windows.

I look at fleet performance through one simple question:

Where is the vehicle spending time without creating value?

A smart fleet strategy helps answer that question with daily operating data.

Start with fuel waste

Fuel is often one of the easiest costs to track and one of the easiest to overlook.

A vehicle may consume more fuel because of:

• Long idle periods
• Heavy traffic
• Poor route planning
• Excess vehicle weight
• Low tire pressure
• Aggressive driving
• Unplanned detours

A fleet owner does not need to guess which issue is affecting performance. Telematics data can show fuel use, idle time, driving speed, and route history in one place.

For example, a delivery van that idles for 45 minutes at several stops each day may appear to be completing its work normally. Across a month, those idle periods can add up to many hours of fuel use with no added delivery revenue.

I prefer to review idle time by vehicle and by driver. A fleet-wide average can hide the real source of waste.

Plan routes around the full day

A route that looks short on a map may still create extra cost.

Traffic patterns, delivery windows, loading delays, road restrictions, and the order of stops all affect the result. A route plan should reflect what happens on the road, not only the distance between locations.

I use a simple review process:

1. Compare planned routes with actual routes.
2. Mark repeated detours.
3. Check stops that create long waiting periods.
4. Review empty return trips.
5. Adjust delivery order where practical.

A local plumbing company, for example, may send one van across town for a morning job and back through the same area for an afternoon call. Grouping nearby appointments can reduce travel time and leave more room for urgent work.

The goal is not to force every route into the shortest possible distance. A slightly longer route may save time when it avoids heavy traffic or reduces repeated crossings.

Track vehicle use between jobs

A vehicle earns money when it supports paid work. Travel between jobs may be necessary, but it should still be measured.

Fleet software can help show:

• Time spent driving without a job
• Distance between scheduled stops
• Unused vehicle capacity
• Missed assignments
• Unplanned personal or non-work trips

This information should support better planning, not create pressure for unsafe driving. Driver safety and legal road requirements remain part of the operating plan.

I also recommend checking whether every vehicle is assigned to the right type of work. A large truck may be useful for heavy loads, but it can create extra fuel and maintenance costs when used for small local deliveries.

Repair vehicles before small issues grow

Preventive maintenance protects more than the vehicle. It protects the schedule.

A missed service can lead to:

• Breakdowns during delivery hours
• Towing costs
• Cancelled appointments
• Replacement vehicle charges
• Lost driver time
• Customer service problems

Fleet owners can monitor mileage, engine alerts, battery condition, tire pressure, and service dates through a vehicle management system.

A basic maintenance routine can include:

• Daily driver checks
• Weekly tire and fluid reviews
• Scheduled oil and filter service
• Brake inspections
• Battery testing
• Review of repeated warning alerts

I do not treat every alert as an emergency. I do treat repeated alerts as a reason to investigate. A small issue that appears across several vehicles may point to a training gap, a parts problem, or a service schedule that needs adjustment.

Give drivers useful feedback

Drivers see problems that office reports may miss. They know which locations create delays, which roads cause damage, and which vehicles feel different during a shift.

A good fleet review includes driver input.

Instead of sending a long list of complaints, I would discuss a few clear points:

• Excess idling
• Hard braking
• Repeated speeding alerts
• Route changes
• Vehicle comfort
• Delivery delays
• Safety concerns

The conversation should focus on patterns. One hard-braking alert may have a valid reason. A repeated pattern at the same intersection may show a route or traffic issue.

Clear feedback can also improve driver trust. When drivers understand why data is being reviewed, they are more likely to report faults and support practical changes.

Connect fleet data with business results

A dashboard can show many numbers. The useful ones are linked to business outcomes.

I track measures such as:

• Fuel cost per mile
• Maintenance cost per vehicle
• Delivery completion rate
• Average idle time
• Revenue-producing miles
• Vehicle downtime
• Cost per job
• Empty miles

These figures help answer practical questions.

Is one vehicle costing more to operate than similar vehicles? Are certain routes creating repeated delays? Does a new delivery zone need another vehicle, or can the current fleet handle it with better scheduling?

A report becomes useful when it leads to a decision. Data without action becomes another office task.

Use small tests before making large changes

Fleet changes affect drivers, customers, and cash flow. I prefer to test one adjustment at a time.

A business might:

• Review one depot for four weeks
• Change delivery order for one route group
• Reduce idle time in one vehicle class
• Test a maintenance reminder system
• Compare two route planning methods

The results can include fuel use, service time, driver feedback, and customer delivery performance. A small test makes it easier to see what caused the change.

For instance, if a fleet reduces idle time but delivery delays increase, the plan may need adjustment. Saving fuel should not create missed appointments or unsafe working conditions.

Choose technology that matches the operation

Fleet technology should solve a known problem.

A small service fleet may need GPS tracking, maintenance reminders, and route history. A larger operation may also need dispatch tools, fuel reporting, driver records, and vehicle health alerts.

Before choosing a system, I would ask:

• What cost problem are we trying to measure?
• Who will use the information each day?
• Can the system connect with current tools?
• How easy is it for drivers and managers to access?
• What reports can support a real business decision?

A system that produces too many alerts can make teams ignore useful information. A smaller set of clear reports may serve the business better.

Protect customer trust while reducing cost

Cost control should not make the customer experience harder.

When routes change, customers may receive different arrival times. When vehicles are reassigned, service areas may need updates. When tracking is introduced, businesses should explain how driver and vehicle information will be used.

Clear communication helps prevent confusion.

I also avoid promises such as guaranteed savings or instant results. Fleet performance depends on vehicle type, road conditions, work volume, fuel prices, maintenance quality, and driver behavior. A sound plan measures the current position, tests changes, and reviews the results.

Keep money on the road through better decisions

Fleet profit rarely disappears in one large event. It often leaks through small daily choices:

• A vehicle idles while paperwork is completed.
• A driver takes an avoidable detour.
• A service reminder is missed.
• A truck returns empty after a delivery.
• A route is planned without checking traffic or stop order.

I would start with one cost area, collect reliable data, and make a change that the team can manage. Then I would compare the result with the original numbers.

Smart fleet management is not about watching every movement without purpose. It is about knowing where time, fuel, vehicles, and driver effort create value—and where they do not.

Many fleet owners focus on fuel, repairs, and driver schedules. Those costs matter, but they do not show the full picture. A vehicle can look busy on paper while still spending too much time parked, returning empty, or serving low-margin routes.

I have seen fleet operators improve their numbers by studying how each vehicle is used across the day. The goal is not to add more vehicles. The goal is to help the current fleet produce better results through stronger planning, clearer pricing, and fewer wasted miles.

Start with the numbers behind each vehicle

I begin with a simple vehicle-level review. For every van, truck, or car, I check:

• Total working hours
• Paid miles and empty miles
• Fuel and maintenance costs
• Revenue by route or customer
• Time spent waiting
• Missed or delayed jobs
• Average income per mile
• Average income per working hour

This review can reveal problems that are easy to miss. A vehicle may complete many jobs but bring in less profit than another vehicle with fewer bookings. A route may look popular while creating long return trips with no paid load.

A basic spreadsheet can help. Fleet management software can provide more detailed reports when the business has a larger number of vehicles.

Reduce empty miles

Empty miles are one of the clearest areas to review. A vehicle may deliver a load to one area and return without work. That return journey still uses fuel, adds mileage, and takes up driver time.

I look for jobs near the destination of an existing route. Local delivery networks, return-load platforms, customer referrals, and partnerships with nearby businesses can help fill gaps.

For example, a small delivery company in Manchester operated 12 vans. Several vans returned empty after morning deliveries. The owner reviewed destination data and contacted businesses along those return routes. Some return trips were matched with small scheduled collections. The company did not need to purchase more vans. It used the same vehicles across more paid miles.

The result will vary by market, service type, and customer demand. The useful lesson is simple: every route should be reviewed in both directions.

Price jobs by cost, not guesswork

Many operators set prices by copying competitors or using a flat charge. This can leave high-cost jobs underpriced.

I calculate the cost of a typical job by looking at:

• Fuel use
• Driver time
• Vehicle wear
• Tolls and parking
• Insurance and operating costs
• Empty travel before or after the job
• Administration time

A short job with heavy traffic and long waiting periods may cost more than a longer job on a clear route. Pricing should reflect the full task rather than distance alone.

Clear service tiers can also help customers choose the right option. A standard delivery, a scheduled route, and a time-sensitive service may need different prices. The wording should explain what each option includes without making claims that cannot be supported.

Improve vehicle utilization

A fleet loses earning potential when vehicles sit unused during workable hours. This does not mean every vehicle must run all day. It means the schedule should match vehicle capacity with actual demand.

I review demand by:

• Day of the week
• Time of day
• Service area
• Vehicle type
• Customer type
• Seasonal patterns

A company may have strong demand for small vans in the morning and weak demand for them later in the day. Another business may need larger vehicles only on certain days. Data can guide decisions about staggered shifts, shared vehicles, subcontracting, or short-term rentals.

Adding another vehicle may feel like the natural answer to more bookings. A utilization review may show that better scheduling can handle the workload with the current fleet.

Keep vehicles available for paid work

Repairs are part of fleet operations, but poorly planned maintenance can create avoidable downtime.

I use a maintenance calendar based on mileage, vehicle age, service history, and known warning signs. Drivers can complete a short inspection before each shift, covering tires, lights, fluid levels, brakes, and visible damage.

Small issues are easier to plan around than sudden breakdowns. Maintenance records also help identify vehicles that are becoming expensive to operate. A vehicle with repeated repair costs may need a replacement review, while another may only need a change in service timing.

Use route data to support driver planning

Route planning affects fuel, delivery time, and customer communication. I compare planned routes with actual journeys to find repeated delays, difficult access points, and locations that create long waiting periods.

Drivers often know details that software cannot show, such as loading restrictions, narrow access roads, or regular parking problems. Their feedback should form part of the planning process.

A route that saves a few miles but creates more waiting may not be the better choice. The best route supports the full job, not only the distance between two points.

Focus on customers that fit the fleet

Not every booking supports healthy fleet performance. Some customers create repeated delays, low margins, or complex requirements that are not reflected in the price.

I group customers by:

• Revenue
• Service cost
• Payment reliability
• Route fit
• Booking frequency
• Vehicle capacity needs

This helps me see which accounts support steady work and which ones need revised terms. A customer may be valuable because bookings are predictable, even when the individual job value is moderate. Another may generate high revenue but require too much unpaid time.

Customer review should guide better agreements, not lead to careless service cuts. Clear booking rules, waiting charges, delivery windows, and cancellation terms can protect both sides.

Measure progress each month

I track a small set of figures instead of collecting reports that no one uses:

• Revenue per vehicle
• Cost per mile
• Empty-mile percentage
• Vehicle utilization
• Maintenance cost
• Revenue per driver hour
• Profit by customer or route

These figures make fleet decisions easier to discuss. They also show whether a change is helping. If empty miles fall but driver hours rise sharply, the plan may need adjustment.

A fleet can earn more without growing larger. Better results often come from seeing where vehicles lose time, where routes lose money, and where pricing does not match the work involved. When I review those areas with consistent data, each vehicle becomes easier to manage and each business decision has a clearer reason behind it.

Every trip can look profitable on paper and still leave little money in the account.

I have seen this happen with small carriers, delivery teams, and service businesses. The invoice shows revenue, yet fuel, unpaid waiting time, empty miles, tolls, repairs, and payment fees reduce the margin. A route that brings in $1,200 may leave only a small amount after the full trip cost is counted.

The problem is not always low sales. Many businesses lose profit through small costs that are not tracked together.

Start with the true trip cost

I use one simple calculation:

Trip cost = fuel + driver pay + tolls + maintenance + vehicle costs + waiting time + admin fees

A basic example:

• Revenue: $1,200
• Fuel: $280
• Driver pay: $360
• Tolls and parking: $85
• Maintenance allowance: $120
• Waiting and loading time: $90
• Admin and payment fees: $35

The remaining amount is $230 before taxes and other business expenses.

Without this breakdown, it is easy to believe the trip earned more than it did.

Track empty miles

A vehicle that travels without cargo still uses fuel, time, and parts.

I record:

• Loaded miles
• Empty miles
• Waiting time
• Pickup delays
• Return-trip income
• Extra stops

When I noticed that one regular route had a long empty return, I contacted nearby businesses along the same corridor. A small return load did not double the revenue, but it helped cover part of the fuel and driver cost. The route became easier to justify.

The lesson is simple: every mile needs a purpose, even when the vehicle is not carrying a full load.

Set a minimum price per trip

Hourly pricing alone can hide the cost of distance. Distance pricing alone can hide the cost of time.

I compare both:

Minimum trip price = fixed trip cost + variable cost per mile + driver time + target margin

The target margin should fit the business and the type of work. A short job with heavy loading requirements may need a higher price than a longer trip with a smooth pickup and delivery process.

I also separate extra charges for:

• Additional stops
• Long loading or unloading delays
• Special equipment
• Parking or tolls
• Address changes
• Failed delivery attempts

Clear terms reduce disputes and help customers understand what affects the final price.

Reduce avoidable waiting

Waiting time often receives less attention than fuel, yet it can take away several productive hours.

I ask each customer:

• Is a loading time reserved?
• Who confirms the goods are ready?
• What happens when the driver waits beyond the agreed period?
• Can documents be sent before arrival?

A delivery team that spends two hours waiting may lose the chance to complete another paid job. Better scheduling can protect income without adding another vehicle.

Review each route after completion

I keep a short trip record with the planned figures and the actual figures. One sheet is enough.

I compare:

• Planned revenue and actual revenue
• Estimated fuel and actual fuel
• Planned miles and actual miles
• Expected time and actual time
• Extra costs
• Final profit

A route that performs well once may not perform well every week. Traffic, seasonal demand, fuel prices, and customer delays can change the result.

Profit is protected before the vehicle leaves, not after the invoice is sent. When I know the full cost, price the work with care, reduce empty miles, and review each completed trip, I can make better choices about which jobs fit the business.

We has extensive experience in Industry Field. Contact us for professional advice:qingjie: 6515703@qq.com/WhatsApp 13603797839.

Fleet Management Council (2024) Practical Methods for Reducing Vehicle Operating Costs

Michael Turner (2023) Measuring Fuel Efficiency and Idle Time in Commercial Fleets

Laura Bennett (2022) Preventive Maintenance Strategies for Reliable Fleet Operations

Operations Research Institute (2024) Route Planning and the Financial Impact of Empty Miles

David Collins (2023) Improving Fleet Utilization Through Data Based Scheduling

Sarah Mitchell (2022) Calculating Trip Costs and Protecting Transport Profit Margins