Operating control layer · Fuel logistics

Every tripstarts readyand closesreconciled.

Tanka decides whether a truck can be assigned, records what happens while it runs, and ties depot volumes to station volumes when it lands. One record, from the gantry to the ledger.

Book a fleet leakage auditSee the model
Side elevation of a four-compartment fuel tanker with compartment volumes and hazard placardsAssignment blocked · checks pending33,000 L · 4 comp.Calibration validLicence currentInspection passed→ LC1AGO301202C2PMS331203C3IK301223C4AGO3012029,000 L8,996 L−4 L9,000 L9,001 L+1 L6,000 L5,998 L−2 L9,000 L8,907 L−93 LLOADED @20°C
Fig. 00 — One trip through the record.01 READY · 1/4
  1. 01ReadyTruck, driver and papers cleared before assignment
  2. 02ExecuteLoading, drops and events captured as they happen
  3. 03CloseDepot and station volumes tied out per compartment
In production withDikus Transporters Ltd
“We finally have clear visibility on trips, vehicles, drivers, and compliance in one system. It’s cut down manual work and paperwork and improved accountability across the team.”
Abdullahi Adan · Operations Manager · Dikus Transporters
The operating model

Ready. Execute. Close.

Three stages. Each one decides something the next depends on, which is why a gap in the first shows up as a loss in the third.

  1. 01

    Ready

    A truck is assigned only when the record says it can be.

    • Vehicle, trailer and calibration status
    • Driver licences and certifications
    • Maintenance and inspection standing
    • Assignment blocked when something fails
  2. 02

    Execute

    What happens on the road is written down as it happens.

    • Loading captured at the depot
    • Products, compartments and drops
    • Fuel, expenses, delays, incidents
    • Missing document numbers flagged
  3. 03

    Close

    The delivery reconciles compartment by compartment.

    • Depot and station volumes at 20°C
    • Loss or gain on every compartment
    • Status history and linked dispatch
    • Open until each compartment ties out
Close

A delivery isnot one number.

Volumes are measured compartment by compartment and corrected to 20°C at both ends. The delivery reconciles only when every compartment does, so a bad compartment cannot hide inside a good total.

Side elevation of a four-compartment fuel tanker with compartment volumes and hazard placardsCalibration validLicence currentInspection passed→ LC1AGO301202C2PMS331203C3IK301223C4AGO3012029,000 L8,996 L−4 L9,000 L9,001 L+1 L6,000 L5,998 L−2 L9,000 L8,907 L−93 LLOADED @20°C
Fig. 01 — Four-compartment tanker, side elevation.Sheet 01 · Rev C
Comp.ProductDepot @20°CStation @20°CLoss (L)Status
C1301202AGO9,0008,9964Ties out
C2331203PMS9,0009,001−1Ties out
C3301223IK6,0005,9982Ties out
C4301202AGO9,0008,90793Delivery open

Delivery DN-4471 · illustrative figuresHazard identification over UN substance number, as plated on the tanker: 1202 gas oil, 1203 motor spirit, 1223 kerosene.

The console

One dashboard for the operating truth.

Loaded trips, client activity, fuel signals, exceptions, compliance status and management reports — without waiting for manual consolidation.

Tanka dashboard showing dispatch, exceptions, fuel volume, compliance, and trip status
Fig. 02 — The operations console: dispatch, exceptions, fuel volume, compliance and trip status on one record.
Where profit leaks

Control the gaps between loading, delivery, and finance.

Fuel logistics margins leak through small operational gaps: undocumented trips, delayed POD, unexplained fuel variance, expired compliance records, disconnected maintenance data, and manual reconciliation.

01

Undocumented trips

Movements captured in paper, WhatsApp, or Excel are easy to delay, misattribute, or miss during reconciliation.

02

Delayed delivery proof

Missing POD, delivery notes, approvals, and exceptions slow finance down and weaken customer dispute resolution.

03

Unexplained fuel variance

Fuel usage, route distance, driver behavior, and vehicle context stay disconnected until leakage becomes normal.

Where to start

Find where trips stop being ready, controlled or reconciled — and what it costs.

The fleet leakage audit reviews eight to twelve weeks of your trip, fuel and reconciliation records against your actual workflow, stage by stage, and puts a number on each gap.

Deliverable 01

Loading-to-invoice workflow map

How information moves today, from loading advice through assignment and delivery to the invoice.

Deliverable 02

Leakage and control-gap register

Every gap found across fuel variance, missing POD, open trips, compliance and manual reconciliation — with its evidence, frequency and owner.

Deliverable 03

ROI hypothesis in KES

Built from fleet size, fuel spend, admin effort and delayed billing risk, with every input labelled known, inferred, assumed or missing.

Deliverable 04

Phased rollout recommendation

What to digitise first, what to baseline, and the implementation scope — confirmed after discovery. Enough to decide with, or to walk away from.

The audit is scoped with you before any work begins, and it stands on its own whether or not you go on to license Tanka.

Qualification

Who this is for

A good fit when
  • You run multiple depots, sites or operating entities
  • Volume has grown faster than the team coordinating it
  • Billing depends on evidence the operation struggles to produce
  • Leadership already suspects where control is being lost
Not the fit today
  • Single-vehicle or owner-driver operations
  • Buyers who only want GPS or asset tracking
  • Anyone shopping for the cheapest per-vehicle subscription

Start with thelosses alreadyinside your data.

Bring eight weeks of records. We will tell you what is recoverable, what is not, and what it would take.

Book a fleet leakage audit