This is an illustrative example scenario, based on common challenges we see in transport and logistics environments. It is not a case study from a specific client, but reflects the types of findings a diagnostic typically produces.

Data Governance Failure in Route Cost Allocation: When Telematics Becomes Disputed Evidence

Technology Was Not the Problem

The regional transport operator had done what many peers had not.

It invested in telematics across its fleet. Vehicle location, fuel consumption, idling time, speed patterns, and driver behaviour were captured in near real time. Weekly performance reports were automatically generated. Exception alerts were configured.

On paper, it appeared data mature.

In practice, the information was not trusted.

Finance relied on fuel card reports and month-end reconciliations.
Operations referenced telematics selectively when it supported operational arguments.
Depot managers maintained manual logs “for safety.”

When route profitability discussions became tense, telematics data was not treated as authoritative evidence. It was treated as one input among many — and often set aside.

The question was not whether data existed.

It was whether governance existed.


The Surface Issue: Inconsistent Fuel Figures

The diagnostic was triggered by repeated disputes over route cost allocation. The largest driver was fuel.

Three systems reported fuel consumption:

  1. The telematics platform (fuel burn estimates based on engine data)
  2. The fuel card provider (litres purchased at point of sale)
  3. The depot log (manual allocation by vehicle and shift)

Each system produced different figures.

Each figure was internally logical.

None had been formally designated as the authoritative record.


The Root Cause: No Master Data Governance

Fuel consumption is not simply a variable cost. It underpins:

  • Route profitability
  • Pricing decisions
  • Client contract renewals
  • Driver performance evaluation
  • Emissions reporting

Yet there was no formal master data governance framework defining:

  • What constituted “actual fuel consumption”
  • How discrepancies between systems should be resolved
  • Which system had precedence in which context
  • Who had authority to approve adjustments

In effect, fuel was critical financial data without ownership.


Manual Reconciliation Without Governance

At month-end, fuel figures were reconciled manually.

Adjustments were made in a spreadsheet to align telematics consumption with fuel card purchases. The logic behind these adjustments was undocumented. No approval workflow existed. No audit trail was maintained.

When the individual who originally designed the reconciliation left the organisation, the process continued unchanged — but without institutional understanding.

This was not malicious behaviour.

It was an inherited workaround compensating for absent governance.

From a data governance maturity perspective, the organisation had advanced data capture but low governance discipline.


Why Data Was Not Trusted

Trust in data depends on three conditions:

  1. Clear ownership
  2. Documented definitions
  3. Controlled reconciliation

None were present.

Operations questioned telematics accuracy when it conflicted with on-the-ground experience.
Finance questioned telematics reliability because it did not align with purchase records.
Neither function had agreed criteria for adjudicating discrepancies.

As a result:

  • Telematics became advisory rather than authoritative
  • Finance retained control through manual adjustments
  • Route cost allocation remained open to negotiation

The technology investment did not fail. The data governance and data quality approach failed to mature alongside it.


The Governance Gap in Route Cost Allocation

Route-level margin decisions depended on fuel cost accuracy.

However:

  • No documented rule defined how fuel variance should be treated
  • No threshold existed for acceptable discrepancy
  • No escalation path was defined for unresolved mismatches
  • No data governance plan addressed cross-system reconciliation

This created several risks:

  • Pricing decisions based on inconsistent inputs
  • Internal disputes consuming management time
  • Potential audit exposure due to undocumented adjustments
  • Erosion of confidence in automated reporting

The organisation believed it had a route costing system.

In reality, it had a negotiation process.


Assessing Data Governance Maturity

The diagnostic evaluated governance approach and maturity across three dimensions:

Definition

  • No single definition of “actual fuel consumption”
  • No policy on variance resolution
  • No documented cost allocation standards

Ownership

  • IT supported telematics
  • Finance controlled ERP adjustments
  • Operations interpreted vehicle data

No executive had end-to-end accountability.

Control

  • Manual month-end reconciliations
  • No documented approval
  • No audit trail
  • No review of reconciliation logic

This profile indicated functional data capture with immature governance control.


What Changed Before Any Technical Action

The solution was not system replacement.

Before considering integration or automation enhancements, leadership addressed governance foundations:

  1. A single authoritative fuel definition was agreed at executive level
  2. Clear precedence rules were established between telematics and fuel card data
  3. Reconciliation logic was documented and formally approved
  4. Ownership of fuel master data was assigned to a named role
  5. Variance thresholds and escalation paths were defined

This constituted the organisation’s first formal data governance plan specific to route cost allocation.

Only after authority was clarified did telematics regain credibility.


Broader Lessons for Logistics Operators

Many transport operators assume that installing telematics improves visibility automatically.

In reality, visibility without governance creates ambiguity at scale.

Advanced capture systems increase the volume of data.
Without clear master data governance, they also increase the volume of disagreement.

Route costing depends on disciplined definition, not just measurement.


Closing Perspective

This case was not about inaccurate fuel data.

It was about undefined authority.

When multiple systems produce defensible but conflicting outputs, the absence of governance becomes the primary risk.

By stabilising definitions, assigning ownership, and formalising reconciliation controls, the organisation restored confidence in route-level cost allocation.

The technology did not change.

The maturity of governance did.