The reporting chain runs from the driller's shift paper to the client's weekly production summary. For most underground contractors, that chain is handwritten at one end, retyped in the middle, and assembled from memory when a month-end query comes in. It works until it does not.
When a contested standby call goes to arbitration, or the mine engineer disputes 180 meters from last month's invoice, the contractor with the clean paper trail wins. The one with a folder of WhatsApp photos and a half-filled spreadsheet does not. Both drilled the same holes.
Before any conversation about software or systems, there is a simpler question: what is the manual chain costing you right now? The answer comes from three inputs you already know - your rig count, your office rate, and your monthly billing.
Worked example
2 longhole drill rigs underground, 2 shifts per day, 5 days per week. Office manager at $32/hour. Monthly billing of $280,000. Working assumption: 25 minutes to process one shift report - read the paper or photo, type meters, ring numbers and delay codes, reconcile against the plan, flag anything missing. Working assumption: 7-day gap between period close and invoice submission, driven by the time to compile and check the records. Cost of credit line: 9% per year. Substitute your own numbers for each input.
| Step | Calculation | Result |
|---|---|---|
| Reports per week | 2 rigs x 2 shifts x 5 days | 20 reports/week |
| Hours on the retype each week | 20 reports x 25 min / 60 | 8.3 hours/week |
| Weekly labor cost | 8.3 hours x $32/hour | $266/week |
| Annual labor cost | $266 x 52 weeks | $13,832/year |
| Working capital tied up at each period close | $280,000 x 7 / 30 | $65,333 |
| Annual financing cost of the delay | $65,333 x 9% | $5,880/year |
| Total annual exposure | $13,832 + $5,880 | $19,712/year |
Answer: For this 2-rig operation, the manual reporting chain costs roughly $19,700 per year in measurable labor and financing exposure, before a single disputed variation is counted.
Where the Chain Actually Breaks
The reporting chain has six steps on most longhole drilling contracts. The driller writes the shift report at the face, usually on paper. The shifter collects it, sometimes adds notes, sometimes signs it. The report moves to surface by hand or by photo. The office receives it, interprets it, types it into the tracking sheet, checks it against the plan, and files it. At period close, somebody compiles all of it into a client summary. At invoice time, somebody checks the compiled summary against the billing schedule.
Each step is a place where the chain can slow down or break.
The breaks that matter are not random. They cluster at the handoff between field and office. A daily that arrives as a wet photo of handwriting with an abbreviated delay code no one in the office has seen before will sit on someone's screen until they can call the site. That call takes hours, not minutes, because the driller is asleep and the shifter is underground. By the time the answer comes back, the chain is 12 hours behind where it should be.
The injury and incident records that sit inside the same reporting infrastructure carry their own deadlines. 30 CFR Part 50 requires contractors on mine sites to notify MSHA of accidents within defined timeframes and to maintain records available for inspection. When the reporting chain is fragmented, the same infrastructure that feeds production tracking also feeds regulatory compliance. A late daily is not only a billing problem.
The breaks compound. One late daily means the weekly summary goes out late. One late weekly summary means the period invoice goes out later than it should. By the time the invoice is submitted, the work is 30 days old and the mine's records may already show different numbers.
What Gets Lost Between Face and Invoice
Most of the information in a shift report arrives at the invoice in degraded form. Meters get rounded at the face, delay codes get interpreted by the office, and exception notes get stripped in the weekly summary because there is no field for them in the client's report template.
The degradation is not malicious. It is the natural result of a chain where each person simplifies what they pass on. The driller notes a delay as "drill down, waiting on tramming" and the code enters the spreadsheet as "standby - equipment." The mine's system reads "standby - equipment" and the contractor has lost the distinction between standby caused by the mine's haulage schedule and standby caused by their own rig. When the period summary shows standby hours that should be the mine's cost, the evidence to prove it has been through four hands and two simplifications.
This is the argument that gets lost before it starts. The contractor drilled the right hours, waited the right hours, and is correct about who caused the delay. The mine's records tell a different story because the contractor's records were not clean enough to force a reconciliation.
The Billing Delay Nobody Has Counted
The $13,832 annual labor figure in the worked example is visible because it is labor. Someone is paid to do the retype and that time can be measured. The $5,880 financing figure is invisible because it is an opportunity cost: money that was not borrowed but should have been available earlier.
Most contractors on net-30 terms are comfortable with the idea that money arrives 30 days after the invoice. What they have not counted is the gap between when the work happened and when the invoice went out. If a 4-week billing period closes on a Friday and the invoice goes out the following Friday because it took a week to compile the production records, the net-30 clock starts 7 days late. For a contractor billing $280,000 a month, that 7-day gap means $65,333 in working capital is unavailable for the full month. At a 9% credit line rate, that is nearly $6,000 per year in financing cost that does not appear on any invoice.
The financing cost does not show up as a line item anywhere. It shows up as an overdraft, a draw on a credit facility, or a deal you could not take because the cash was not there.
The reporting chain cost calculator runs the same arithmetic against your own inputs: rig count, office rate, billing volume, and your actual billing cycle delay.
Why Automate When the Old System Still Works
The honest answer is that the old system is not working. It is just not failing in a way that generates a repair bill.
A driller who rounds meters to the nearest 5 does not generate a complaint until a variation claim requires a hole-by-hole breakdown. An office manager who estimates a standby code from context does not generate a dispute until the mine audits a period of unusually high standby. A period summary compiled from a folder of photos does not cause a problem until the photos are on a phone that was lost. These are not hypothetical failures. They are the failures that show up when a contractor has a legitimate claim and cannot support it with a clean record.
The SME Mining Engineering Handbook notes that automation has "begun to demonstrate its potential value to improve the productivity and safety" of mining processes, and describes a growing industry vision for "intelligent and integrated control over all mining processes to optimize resource value" (SME Mining Engineering Handbook, 3rd edition, 9.8.1.1 Benefits of Mining Automation, p. 805). That principle applies at every level of the operation - including the administrative chain that turns drilled meters into an accurate invoice.
A reporting chain that works means a variation argument you can win in 2 hours instead of 2 weeks. An invoice that goes out on Friday, not the following Friday. A response to the mine engineer's query that takes 10 minutes, not a morning of searching a shared drive.
What Stays the Same at the Face
The objection raised every time is adoption: "My guys will not change how they work." That objection is correct and irrelevant in equal measure.
Automating the reporting chain does not ask the driller to do anything differently. The shift paper still exists. The driller still fills it out with the abbreviations and shorthand he has used for fifteen years. What changes is what happens to that paper after it leaves the face.
The retype step - from paper or photo to a structured record - is what gets automated. That step happens in the office, not underground. The field crew has no exposure to the change.
What the field crew does see is the clarifying question that arrives sooner. When the system flags a ring number that does not match the plan, the question goes back to the shifter the same morning instead of 12 hours later. The driller who is asleep when the question is asked gets a notification before his next shift starts rather than a phone call at noon.
The face is still the face. The change is everything downstream of it.
The Office Manager and the Variation File
The question nobody asks out loud is whether automating the reporting chain means automating out the person who runs it.
The answer is no, and the framing matters. The office manager who spends 8 hours a week typing shift data is not being displaced. The retype is the part of the role that cannot be done wrong with less time. It is error-prone, repetitive work that the same person then checks with the same eyes. Automating that step does not eliminate the role. It changes what the role does.
The variation file is a useful illustration. When a contractor disputes a standby call or a ground condition delay, the person who knows which shift the change happened on, which daily notes mentioned that heading, and where every supporting record is - that is the office manager. That knowledge is not created by automation. It is built by years of reading the dailies. Automation changes whether that knowledge can be acted on quickly, or whether it is buried in a shared drive waiting for someone to dig it out after the argument is already three weeks old.
A contractor with a clean reporting chain does not drill more meters. They win more of the arguments about the meters they have already drilled.
What the Payback Calculation Misses
The $19,700 figure from the worked example is a floor, not a ceiling. It counts labor and financing. It does not count the variation that was not claimed because the documentation did not support it. It does not count the tender lost because the mine's records showed late or inconsistent reporting. It does not count the credit facility that cost more than it should because the billing cycle was consistently slow.
Those costs are harder to count because they are things that did not happen, not things that did. But every contractor with ten years underground has the examples. The job that paid late because the mine disputed a period and the contractor could not produce a clean reconciliation. The standby claim that went nowhere because the delay codes were inconsistent across two crews. The renewal conversation that went badly because the mine's picture of the contract looked different from the contractor's.
The payback is not about saving 8 hours a week. It is about never walking into a variation argument without the file that wins it.
Run your own numbers
Rather than work it by hand every time, the reporting chain cost calculator does this arithmetic and shows its working. The rest of the set is on the mining calculators page.
Common questions
My guys will not adopt new software.
Nothing changes at the face. The driller still writes the shift report the same way. What changes is what happens after it leaves site. The office reads it, the system reads it, and the retype step disappears. Adoption resistance at the face is real - and it is irrelevant here because the face is not being asked to change anything.
How do I know the automated number is right?
The automated number is not generated - it is read and reconciled. The system reads what the driller wrote, matches it against the plan, and flags anything that does not reconcile. A person still approves the result. That is a stronger check than one person typing from a photo and then checking their own work, which is the current process in most offices.
Is this going to replace my office manager?
No. Automating the retype step changes what the role does, not whether it exists. The same person who spent 8 hours a week typing shift data can spend that time on exceptions, disputes, and client queries that require judgment. The retype is the most error-prone part of the job. It is not the valuable part.
What does this NOT fix?
Incomplete dailies, handwriting that cannot be read, and ground conditions that went undocumented because the shifter was too busy. It does not fix a delay code system where every driller codes standby differently. Automation surfaces those gaps faster than a manual process, but it does not fill them. The data that goes in still has to be worth reading.
Getting this off paper
Most contractors already know these numbers. The cost is in re-keying them into a report, then a timesheet, then an invoice. If that is where your week goes, book a 20-minute call and we will look at your actual paperwork.
