Picture a single truckload of ore. By the time it's gone from the pit to the crusher, it has three different weight readings attached to it, recorded by three different people, on three different paper forms, none of which talk to each other. That's not a hypothetical — it's the default state of ore flow accounting at most mine sites, and it's a surprisingly clean example of a distributed data consistency problem playing out with clipboards instead of databases.
Here's the setup, why it breaks down, and what fixing it actually looks like.
Why end-to-end ore data matters
For any mineral resource company, reliable ore flow data isn't a reporting nicety — it's the input to real decisions: how you value reserves by site and deposit, what your actual extraction volumes and grades are, how much you're losing in-situ during mining and re-evaluation, and how much ore is genuinely available for downstream processing. Get the data wrong and every decision built on top of it inherits the error.
The pipeline, as it actually exists
Ore flow accounting happens across several stages: appraising explored and newly discovered resources, estimating reserves before extraction, adjusting for losses during haulage and handling, and assessing ore prepared for blasting and fragmentation, among others.
In practice, the same underlying event — one truckload of ore moving from point A to point B — gets recorded manually, independently, in separate paper logs at every stage, from the moment a loaded haul truck leaves the pit to the moment it discharges at the crusher. Nothing links those records together. Nothing reconciles them. Each log is its own silo, filled in by a different person, at a different point in the workflow, with no shared source of truth.
Where it actually falls apart
This is the part that'll be familiar to anyone who's dealt with eventually-consistent systems that never actually converge. Here's a single load, tracked through three independent writers:
- A mine surveyor at the pit logs 42 tons for a load from Block 7, based on the excavator's onboard scale.
- The dispatcher at the plant gate logs the same haul at 43.5 tons on the weighbridge — because the truck came in with its body still raised.
- The driver writes down 40 tons on the waybill, because that's what keeps them under the axle load limit.
Three sensors, three contexts, three numbers, zero reconciliation. By end of shift, accounting is manually trying to figure out which of three conflicting values to trust for a single event. Multiply that across a month of loads and the discrepancy compounds to 3–5% — and because nothing traced the individual events, there's no way to go back and pinpoint where the actual shortfall happened. You just know the totals don't add up.
What an actual fix looks like
The fix isn't "get people to be more careful" — it's giving the data a single, structured, traceable path instead of three disconnected paper trails. That's what an electronic log (we used logsheet.ai) is actually solving: a single-page form with clearly labeled fields, filled in at each transfer point, that becomes the one record of the event instead of a new, independent one every time.
Concretely, that gets you:
- One continuous data thread from the block to the crusher, instead of three unlinked logs.
- Automatic reconciliation between transfer points — if two readings for the same event don't match, the system flags it immediately instead of surfacing the gap a month later in a totals report.
- Real-time visibility into the data, not end-of-shift paper collection.
- Fewer disputes, because "42 vs. 43.5" gets resolved against a system of record instead of three people's memory of whose scale was right.
- Production reports generated directly from the log data, on demand, instead of hand-assembled from multiple sources.
What rolling it out actually takes
This isn't a multi-month systems integration project. The rollout is three steps: set up the logs using ready-made templates configured for your blocks, equipment, and warehouse; train the team to work from tablets they carry to the actual measurement point instead of a clipboard; run one trial shift to confirm it holds up under real conditions. In practice that's a three-day turnaround to a working system tailored to a specific quarry.
The actual payoff
The real shift isn't "digital instead of paper" — it's moving from average, backfilled indicators to real, event-level data you can trust. That changes what you can actually do with it: supply planning based on real numbers instead of estimates, an accurate read on subsurface balances, and processing efficiency gains that come from finally knowing where the material actually is instead of reconstructing it after the fact.
Top comments (0)