
Fuel Management Software for Heavy Fleets in Ghana
The pump says one thing. The machine says another.
Fuel management software means knowing exactly where the diesel went. If you run heavy equipment in Ghana, fuel is your biggest variable cost and the one issued furthest from the office. Darikoda records the dispense at the bowser, attributes it to the asset and the operator behind it, reconciles it against the hours the machine actually worked, and surfaces the variance to management.
At a glance
Fuel management software helps heavy fleet operators record, reconcile and investigate fuel usage across assets and sites. Fuel reconciliation is the structured process of matching the volume dispensed from the bowser to the volume consumed by a specific asset, tied to the hours it worked and the operator on duty. Darikoda holds that as one operating record, captured in the field and visible from the office. Captured at source.
Representative product workflow · Illustrative data
See how the operating record captures this workflow
Log Fuel
Saved locallyWheel Loader 04
WL-04
Fuel quantity
215.0 L
Hour meter
Dispense evidence
Photo of the meter at the machine, taken now. Logged with GPS and shift so the dispense can be trusted.
The definition
What is fuel management software?
Fuel management software is the system that records how fuel enters an operation, where it goes, and what it produced. For a light vehicle fleet that is largely a fuel-card question, answered by a statement at the end of the month. For a heavy fleet it is not.
A mining, construction, plant hire or civils operation issues diesel from bowsers and bulk tanks into mixed assets, across shifts, operators, sites and contracts. The fuel is not bought at a station with a receipt attached. It is dispensed in the field, often at a remote pit edge, often with no signal. So fuel management for heavy industry is not a measurement problem. It is a chain-of-record problem, and the chain runs like this:
- Fuel delivered into the site, the bulk tank or the bowser.
- Fuel dispensed, captured as an event at the moment it happens.
- Asset assigned, so the litres land against the machine that took them.
- Operator attributed, so the record names the person on duty.
- Operating hours recorded, so the consumption has a denominator.
- Consumption calculated against those hours.
- Variance surfaced, in litres and in cedis.
- Variance investigated, with an operational cause attached.
- Action approved by a responsible manager.
- The result reported to operations and finance.
Reading a tank level is not fuel management. Counting litres is not fuel management. Tracking a bowser around a site is not fuel management. Recording a dipstick is not fuel management. Each of those produces one number in isolation. Fuel management is the chain that connects them, so a litre issued at the bowser can be followed to the hour it burned and the work that hour did.
That chain matters more in mining, construction, plant hire and civils than almost anywhere else, because fuel is the largest variable cost line in the operation and the most weakly evidenced at the moment it is spent. It is one part of Darikoda's wider operational intelligence model, not a separate system bolted to the side of it.
The problem
Why the fuel never reconciles
Fuel is the cost line that walks the quietest.
Fuel logs are written on paper, then lost or altered.
Fuel monitoring relies on trust instead of evidence.
Month-end fuel reconciliation becomes a screaming match between the site and finance.
The business eats the cost of the variance.

The record begins where the diesel leaves the bowser.
Every dispense tied to an asset and a person, logged at the moment it happens, not reconstructed at month-end.
The distinction
Fuel tracking is not the same as fuel accountability
Both approaches watch the same diesel. They are built to hold different things. A tracking-first system is designed around the volume. An operating record is designed around the event and everything attached to it. The difference is the completeness of the record, not whether a given number can be produced.
| What is held | Basic fuel tracking | Darikoda fuel accountability |
|---|---|---|
| Litres recorded | The volume issued is captured, usually as a total per fill or per period. | The volume is captured as an event, with everything that gives it meaning attached to it. |
| Asset attribution | Litres are commonly assigned to a vehicle or a tank at the point of entry. | Litres are assigned to the asset and its asset ID at the dispense, in the field, before anything is written up. |
| Operator attribution | The person on the machine is often outside the fuel record. | The operator on duty is attributed at the event, including when it is the standby operator. |
| Time | The date of the entry is recorded, which may be the day it was keyed in. | The timestamp is the moment of the dispense, not the moment of the write-up. |
| Operating hours | Hours usually live in a separate system from the fuel. | Hours sit in the same record, so litres per operating hour is a reading rather than a calculation somebody has to assemble. |
| Project and site | Fuel is typically costed to the site in aggregate. | Each dispense carries the project or site it is charged against, so project-level fuel cost is sourced. |
| Variance | Variance appears as a difference between two totals. | Variance is surfaced per asset, per operator and per site, in litres and in cedis. |
| Approval | Exceptions are handled outside the system, often verbally. | Exceptions are flagged, reviewed and approved on the record by an authorised reviewer. |
| Investigation | Investigation starts by rebuilding the context around the number. | The context is already there, so investigation starts at the cause. |
| Reporting | Reporting shows what was issued. | Reporting shows what was issued, what it produced, and where the gap sits. |
| Audit trail | The trail is as strong as the paper behind the entry. | Every litre traces back to a timestamped event with an asset, a person and a place on it. |
This is a difference of completeness, not capability. Plenty of systems can produce any single row above. The question is whether they hold all of them against the same event. The full comparison against trackers, ERPs and spreadsheets is on how Darikoda compares.
The control chain
How fuel accountability works
Fuel accountability is a sequence, not a feature. Each step exists because the step before it can drift. Run the whole chain and the variance has somewhere to be explained. Break it anywhere and the number goes back to being an opinion.
- 01
Fuel arrives
Fuel received into the site, the bulk tank or the bowser is recorded against the delivery, so the operation knows what it has before anything is issued.
- 02
Fuel is dispensed
The dispensing event is captured as it happens, in the field, with the litres issued and the source it came from.
- 03
Asset is assigned
The dispense is tied to the specific machine or vehicle that took the fuel, by asset ID rather than by description.
- 04
Operator is recorded
The operator who received the fuel or was on the asset is attributed to the event, so the litres carry a person and not just a machine.
- 05
Machine hours are recorded
Operating hours are captured against the same asset over the same period, which is what turns litres into consumption.
- 06
Fuel is reconciled
Fuel issued is compared with the consumption the recorded activity accounts for, at asset level rather than fleet average.
- 07
Variance is surfaced
The gap is shown in litres and in cedis, against the asset, the operator and the site it belongs to.
- 08
Variance is investigated
The record is worked through until the variance has an operational cause attached to it, or is confirmed as unexplained.
- 09
Approval and action
A responsible manager authorises the follow-up or the correction, and the decision sits on the record next to the exception that prompted it.
- 010
Management reporting
The result reaches operations and finance as a summary of decisions already made, not as a pile of logs waiting to be reconciled.
What management sees
Every litre, assigned
- Fuel received into site, tank or bowser
- Fuel dispensed, per event
- Fuel by asset
- Fuel by operator
- Fuel by site and project
- Litres per operating hour
- Historical consumption per asset
- Fuel variance, the gap in cedis and litres
- Variance by asset
- Variance by site
- Exception events and their status
- Approval status against each exception
- Timestamped dispensing evidence

The gap between issued and burned is the leak.
Darikoda surfaces it in cedis and litres, per asset, per hour worked.
By industry
Where the fuel gap actually sits

Mining
Haul trucks, excavators, loaders and the bowsers that follow them to the pit edge, on remote sites where the storage is often controlled by the mine rather than the contractor. Fuel per hour sits next to the production context that hour produced, which is what makes a cost per tonne defendable. Views for mining contractors and full mine operators.

Construction
Mixed equipment on one site tank. Excavators, graders and loaders drawing from the same bulk store, with the fuel charged to the project that burned it rather than to the site in aggregate. That is what makes project-level cost accountability sourced. Read the main contractor view.

Plant Hire
Hired-out equipment where the agreement bills the machine and supplies the fuel. Customer attribution, operating hours and the dispense record behind every litre, which is the whole of your deduction defence when the month-end statement is disputed. Read the hire firm view.

Civils
Dispersed work fronts and long operating periods, with the bowser following the works down the road. Fuel allocated by project and work area, with the chainage and site context on the event, so remote equipment is not costed by estimate. Read the road contractor view.
What changes
What better fuel control changes
Fuel control does not produce a saving on its own. It produces a record, and the record is what changes the decisions taken around the fuel.
- Fewer unexplained variances, because most of them get explained at the event.
- Faster reconciliation, because month-end has nothing left to rebuild.
- Stronger operator accountability, held to evidence rather than to suspicion.
- Better project-level cost visibility, with fuel charged where it was burned.
- Better month-end reporting, sourced rather than assembled.
- Stronger auditability, with every litre traceable to a timestamped event.
- Earlier identification of unusual consumption, in the week rather than the quarter.
- Better maintenance investigation, because a fuel pattern often names a mechanical problem before the failure does.
- Less administrative reconstruction, and the hours that went into it back.
What any of that is worth to you depends on fleet size, fuel volume, operating conditions, the quality of the control you already run and how far the implementation goes. We do not publish a percentage, because the honest answer is that your number comes out of your own record. The Operational Audit is where we find it.
Why Ghana
The Ghanaian context
Diesel in a Ghanaian heavy fleet is issued in the places that make record-keeping hardest. Bowsers sit at remote pit edges and stripping benches where 4G drops out. Fleets are dispersed across sites that are hours apart by road. Each handover point between the site and the office is somewhere the number can drift, and much of the reporting still moves on paper and WhatsApp, so what reaches the office is a copy of a copy written up after the fact. Check the gaps in your own operation against the original records. On a contractor site where the mine controls the storage and dispenses the fuel, the storage point's number becomes the default if your crew has no independent dispense record, leaving one of your largest cost lines without contractor-side evidence when month-end reconciliation is reviewed. That is why the capture has to work offline first. Every fuel event saves on the device and syncs when signal returns, so the operator never waits on a spinning wheel to evidence a dispense and never falls back to paper. A failed sync surfaces as a visible issue rather than a silent gap in the record.
See what this means for your operation.
A free 30-minute audit. Your priorities, a one-page leakage map and three practical next steps.
Explore the detail
Open the topic you need for your operation.
Fuel reconciliation: from bowser to machine
Reconciliation
Fuel reconciliation compares what went in with what came out, at a level of detail that names the asset. It runs across a set of quantities that have to be real individually before the last one means anything:
- Fuel received into the site, the bulk tank or the bowser.
- Fuel dispensed out of the bowser, event by event.
- Fuel allocated to a specific asset, operator, site and shift.
- Machine operating hours across the same period.
- Expected consumption for that asset under those conditions.
- Actual recorded consumption against the hours worked.
- The variance between the two, in litres and in cedis.
The number management wants is the last one. It is only worth reading if the ones above it are sourced. Reconciliation against a fleet average tells you the fleet has a problem. Reconciliation against the asset tells you which machine, which operator and which shift, which is the only version of the number anyone can act on.
We do not publish universal consumption rates, because they do not exist. A thirty-tonne excavator on soft overburden and the same model on hard rock are two different fuel profiles. Thresholds have to be set against asset type, operating condition, workload, terrain, duty cycle, manufacturer guidance and the actual historical performance of that machine on your sites. The objective is to identify unusual variance, not to treat every difference as a loss.
When fuel does not reconcile
Exceptions
A variance is a question, not a verdict. Before anything is escalated, the record has to answer where the number came from. Confirm the physical record. Check the dispense event behind it. Confirm the asset it was attributed to. Confirm the operator and the shift. Review the machine hours. Check the conditions the machine actually worked in. Check whether a maintenance or mechanical issue explains it. Compare it against the previous fuel pattern for that asset. Then decide whether the variance is explained, and approve corrective action if it is not.
Use the records to investigate the cause. Check for:
- A recording error, at the bowser or in the hours.
- A difference between the meter reading and the dipstick.
- An unusual duty cycle on that shift.
- Idling that never showed up as productive hours.
- A mechanical problem, a worn injector or a leak.
- Fuel attributed to the wrong asset.
- A transfer between machines that was never recorded.
- Actual loss.
- Operational misuse.
- Nothing at all, once the maintenance history of the machine is read alongside it.
Evidence first. Attribution second. Action third. A record that names a pattern is worth more than an accusation nobody can defend, and it survives the conversation that follows.
Approvals sit on top of that as the exception handling. Unusual fuel requests, manual adjustments, corrections, exceptional consumption, emergency refuelling and unexplained variance can each run the same route: record, flag, review, approve, report. Who reviews is whatever your structure makes the authorised reviewer or the responsible manager. The point is that the exception is handled in the open, on the record, rather than settled in a call nobody can produce later.
Every litre needs an accountable operational context
Attribution
A litre on its own is not information. Two hundred litres issued on a Tuesday tells you nothing you can act on. The same two hundred litres becomes useful the moment it carries the context around it. A fuel event is worth reading when it links:
- The asset that received it.
- The operator on duty at the time.
- The shift it belongs to.
- The site or project it is charged against.
- The date and time it happened.
- The quantity issued.
- The machine hours worked around it.
Attribution is not accusation. Naming the operator on a fuel event asserts nothing about that operator. It makes performance patterns visible fairly, which is the opposite of what happens when every litre averages into a fleet number and the only people who get named are the ones somebody already suspected. Attribution strengthens accountability by making it evidenced rather than assumed.
The same principle runs through the rest of the operating record. Fleet management software treats hours that way, downtime tracking treats idle time that way, and maintenance treats the defect and the repair that way. Fuel, hours, downtime and maintenance roll up into operational intelligence, and the Operational Audit is where we find which of them is leaking hardest in your operation.
Month-end fuel reconciliation should be a summary, not a reconstruction
Month-end
There are two ways to close a fuel month. The first waits for month-end, collects the paper logs off the sites, keys them into a spreadsheet, and then spends a week arguing about the litres that do not add up. By then the shift is weeks gone, the operator has moved machines, and nobody can source the number. That is not a reconciliation. It is a reconstruction, and a reconstruction is only ever as good as somebody's memory of a Tuesday.
The second captures every dispense as it happens and lets month-end arrive with nothing left to rebuild:
- Every dispense captured at the event, not written up afterwards.
- Asset and operator attributed at the moment of issue.
- Reconciliation running progressively through the month.
- Exceptions investigated in the week they appear, while the shift is still recent enough to explain.
- Month-end read as a summary of decisions already made.
The difference is not effort. It is when the effort happens. Capture at the event costs seconds. Reconstruction at month-end costs a week and still ends in an argument.
The editorial version of this argument, including why the gap tends to stay hidden for about three weeks, is in the Operating Note on closing the bowser-to-engine gap. This page is the software side of the same problem.
Frequently asked questions
The questions operators ask first
What is fuel management software?Read the answerClose answer
Fuel management software records how fuel enters an operation, which asset and operator it was issued to, and what that fuel produced. For a heavy fleet it is not a measurement tool. It is the chain of record that runs from the delivery into the bowser through to the variance report on a manager's desk.
What is fuel reconciliation?Read the answerClose answer
Fuel reconciliation compares the fuel dispensed against the consumption that recorded machine activity accounts for, at asset level. It works across fuel received, fuel dispensed, fuel allocated to an asset and operator, operating hours, expected consumption, actual consumption, and the variance between the last two.
How does fuel management software work for heavy equipment?Read the answerClose answer
The dispense is captured as an event in the field, with the asset, the operator, the litres, the site and the time on it. Operating hours are recorded against the same asset. The two are reconciled, and the gap is surfaced per machine rather than averaged across the fleet. Heavy equipment needs it this way because the fuel is issued from a bowser on site, not bought at a station with a receipt attached.
Can fuel be assigned to individual machines?Read the answerClose answer
Yes. Every dispense is tied to the specific asset by asset ID at the moment it happens, so litres land against the machine that took them rather than against a site total that has to be split later.
Can fuel records be linked to operators?Read the answerClose answer
Yes. The operator on duty is attributed to the fuel event, including where a standby operator takes the machine. That is what allows performance patterns to be read fairly instead of averaging into a fleet number.
Can it track fuel across multiple sites?Read the answerClose answer
Yes. Fuel records for the whole fleet centralise into one operating record, with each event carrying the site or project it belongs to. Fuel can then be read by asset, by operator or by site without anyone reassembling it from separate logs.
Can fuel variance be measured?Read the answerClose answer
Yes. Variance is surfaced in litres and in cedis, against the asset, the operator and the site. What it should be measured against is set per asset type, operating condition, workload, terrain, duty cycle, manufacturer guidance and that machine's own history. We do not apply a universal consumption rate, because one does not exist.
How is fuel variance investigated?Read the answerClose answer
Evidence first, attribution second, action third. Confirm the physical record and the dispense event, confirm the asset and the operator, review the hours and the operating conditions, check for a mechanical cause, then compare against that asset's previous pattern. In many cases, variance traces to a recording gap, an unusual duty cycle, extended idling or a mechanical fault alongside potential fuel loss, which is why the investigation starts with the event record rather than an accusation.
Does fuel management prevent fuel theft?Read the answerClose answer
Structured fuel management supports theft prevention and investigation through better records. It improves the evidence at the dispense, attributes every litre to an asset and a person, makes unusual consumption visible in the week it happens, and supports a proper investigation instead of a suspicion.
Does this replace physical dipsticks or flow meters?Read the answerClose answer
No. It digitises the record of the dipstick or the flow meter at the moment the reading is taken, ties it to the asset and the operator, and makes it visible to the office instead of leaving it in a book on site. The physical measurement stays. The record around it changes.
How does fuel management support month-end reconciliation?Read the answerClose answer
By making month-end a summary rather than a reconstruction. Dispenses are captured as they happen and reconciled progressively, so exceptions are investigated in the week they appear. Nothing is rebuilt from paper logs three weeks after the shift.
Operating Note: closing the bowser-to-engine gapCan fuel management work on remote Ghanaian sites with no signal?Read the answerClose answer
Yes. Capture is offline first. Every fuel event saves on the device and syncs when signal returns, so an operator at a pit edge never waits on a spinning wheel and never falls back to paper. A failed sync surfaces as a visible issue rather than a silent gap.
How does fuel management support mining operations?Read the answerClose answer
Haul trucks, excavators, loaders and the bowsers that follow them are reconciled per asset and per operator, with fuel per hour sitting next to the production context that hour produced. On contractor sites where the mine controls the storage, holding your own dispense record is what stops the storage point's number becoming the default.
Mining operations in GhanaHow does it help plant hire businesses?Read the answerClose answer
The hire agreement bills the machine and supplies the fuel, so the month-end deduction is only as strong as the dispense record behind it. Fuel events tied to the customer, the asset and the operating hours are what turn a deduction argument into an evidenced position.
Plant and equipment hire in GhanaHow does an Operational Audit identify fuel leakage?Read the answerClose answer
The free 30-minute Operational Audit maps where your fuel evidence breaks. It names the dispense points and the cycles where variance is hiding, specific to your fleet and your contract structure. You keep the one-page map regardless of next steps.
Book an Operational AuditSee where your operation leaks.
The Operational Audit takes 30 minutes. You get a one-page leakage report you keep regardless of next steps.
Patterns described here are drawn from extensive field audits and industry research across Ghana's mining, construction, roadworks, and quarry sectors. No specific operator is named or identifiable.