Driver Guide 10

How FareWorth analyses a ride offer

The problem

A ride offer arrives quickly.

The driver may only have a short time to make sense of several numbers:

  • fare;
  • pickup time;
  • pickup distance;
  • passenger time;
  • passenger distance;
  • ride option;
  • and their own idea of what counts as worthwhile.

Doing the maths by hand every time is possible, but it is not very practical.

FareWorth is designed to turn that information into a clearer decision-support view.

The high-level process

1. FareWorth reads the visible supported offer information

On currently supported driver apps, FareWorth is designed to read the offer information visible on the device.

That can include values such as the fare, pickup time and distance, and passenger-journey time and distance when they are available and successfully captured.

The Driver Guides are provider-neutral because the economic ideas apply across rideshare/private-hire work. This guide does not claim that FareWorth currently supports every driver platform.

2. It separates pickup from the passenger journey

Pickup matters because the driver has to reach the passenger before the paid journey begins.

FareWorth keeps that context visible rather than looking at the passenger segment alone.

3. It applies the driver’s own settings

Different drivers have different vehicles, costs and targets.

FareWorth uses the driver’s configured settings rather than relying on one universal definition of a good ride.

4. It can include vehicle-cost context

FareWorth can use configured vehicle and fuel or energy settings to estimate relevant running-cost context.

That can support measures such as an estimated fuel cost and After Fuel estimate where the required data exists.

After Fuel is not the same as net profit.

5. It applies the selected Dead Miles treatment where relevant

The driver can choose how FareWorth treats the road after drop-off using the current Never, Smart or Always modes.

That can change the analysed time, distance and cost context.

6. It calculates analysed £/hour and £/mile

FareWorth turns the analysed fare, time and distance into rates that are easier to compare.

The hourly figure helps show the value of the driver’s time.

The distance figure helps show the value of the miles included in the analysis.

7. It compares the result with the driver’s own thresholds

FareWorth supports driver-configured minimum and preferred targets.

The driver can also choose whether hourly or distance rate is the leading measure.

8. It presents clear guidance

The current product uses Green, Amber and Red guidance:

  • Green — preferred target or above;
  • Amber — between minimum and preferred;
  • Red — below the configured minimum.

The colours make the comparison easier to read. They do not make the final driving decision.

9. The driver decides

FareWorth does not automatically accept rides.

FareWorth does not automatically reject rides.

It provides decision support. The driver remains responsible for every ride decision.

Simple worked example

The public FareWorth website already shows genuine redacted examples of Green, Amber and Red guidance.

A simplified educational example might look like this:

  • Fare: £11
  • Pickup: 6 minutes, 2 miles
  • Passenger journey: 18 minutes, 7 miles
  • Analysed time before any extra Dead Miles allowance: 24 minutes
  • Analysed distance before any extra Dead Miles allowance: 9 miles
  • Analysed hourly rate: £27.50/hour
  • Analysed distance rate: about £1.22/mile

FareWorth would then use the driver’s actual configured settings and any relevant Dead Miles/vehicle-cost treatment rather than the fixed illustrative assumptions in this article.

The final guidance depends on the driver’s own thresholds.

What to watch out for

Capture can be incomplete

If information is missing or cannot be read reliably, the product must not invent values.

The offer can change after acceptance

Traffic, waiting and real-world journey conditions can differ from the original offer estimate.

FareWorth does not know every business cost

Its current vehicle-cost context should not be confused with complete accounting profit.

Guidance is personal configuration, not a market rule

A Green result means the offer cleared the configured FareWorth threshold. It does not mean the offer is universally good for every driver.

Platform support is separate from the economic method

The maths in these guides is provider-neutral. Actual FareWorth platform/device availability should always be taken from the current product information rather than assumed from the guide.

How FareWorth helps

This entire guide is the FareWorth use case in one sentence:

Turn the fare, pickup, journey and your vehicle costs into one clear view, then compare it with the targets that matter to you.

The product is there to reduce the amount of mental maths needed at the point an offer appears.

It also keeps History, Driver Day and descriptive analytics available so the driver can review what was recorded later.

FareWorth shows useful recorded facts. These guides do not treat recurring historical evidence as proof of what will happen next or as a personalised recommendation.

Practical takeaway

FareWorth’s offer analysis is built around four ideas:

  • include the parts of the offer that actually use the driver’s time and vehicle;
  • use the driver’s own settings;
  • show clear analysed rates and costs;
  • leave the final decision with the driver.

Your thresholds. Your call.

1Visible supported offer information
2Pickup and passenger split
3Driver settings
4Vehicle-cost context
5Dead Miles mode
6£/hour and £/mile
7Driver thresholds
8Green / Amber / Red guidance
9Driver decision
“FareWorth reads supported visible offer information, separates pickup and passenger journey, applies the driver’s settings, adds vehicle-cost and Dead Miles context where relevant, calculates £/hour and £/mile, compares them with the driver’s configured thresholds, shows Green/Amber/Red guidance and leaves the final decision with the driver.”