Every number a driller writes in the field book has to reach the invoice. Most of the time, it gets there by being retyped: field book to shift report, shift report to daily cost sheet, cost sheet to invoice. If the accounting software runs separately, one more pass. The same value, written three or four times by different people in different documents.
That chain is common enough that most operations treat it as how invoicing works. But each handoff is a chance for the number to change, and the aggregate time adds up before anyone notices it.
The question is not whether double data entry is happening. It almost certainly is. The question is what it costs per week in a specific operation, and where the first error is most likely to enter.
Worked example
A 3-rig underground drilling contractor runs 2 shifts per day across 6 working days per week. Each shift report carries 12 entries worth billing or tracking: meters drilled, downtime hours (split across two delay codes), standby hours, bits used, steel joints used, water, fuel, and 4 consumable line items. Each entry starts in the driller's field book and crosses 3 handoffs before it reaches the invoice: field book to shift daily, shift daily to office cost sheet, cost sheet to invoice. Say each transcription - locating the source value, finding the correct destination row, typing, and checking - takes 40 seconds.
| Step | Calculation | Result |
|---|---|---|
| Field entries written per week | 3 rigs x 2 shifts x 6 days x 12 entries = 432 entries | 432 original entries per week |
| Total transcriptions across 3 handoffs | 432 entries x 3 handoffs = 1,296 transcriptions | 1,296 individual transcriptions per week |
| Time at 40 seconds per transcription | 1,296 x 40 seconds = 51,840 seconds = 864 minutes = 14.4 hours | 14.4 hours per week |
| Dollar cost at $40/hr office rate | 14.4 hours x $40 = $576 | $576 per week in transcription time alone |
Answer: On these assumptions, a 3-rig operation runs roughly 1,296 individual transcriptions per week, consuming about 14.4 hours and $576 in office time - and that excludes any time spent tracing discrepancies when numbers do not match.
The Chain from Field to Invoice
For most drilling and mining contractors, the same number travels through at least four distinct documents before a client sees it.
It starts in the driller's field book: meters drilled, downtime hours, bit changes, standby reason, consumable quantities. That is the original record. From there, a supervisor writes it into the daily shift report. The office receives the daily and copies relevant numbers into a cost sheet or running spreadsheet. At month end, someone pulls from that spreadsheet to build the invoice. If the company runs accounting software separately, there is a fifth copy.
This chain is common enough that most people working inside it have stopped seeing it as a choice. It feels like how invoicing works. The field book does not connect to the daily report. The daily report does not connect to the cost sheet. The cost sheet does not connect to the invoice. Each connection is a person, a desk, and a decision about which value to write in the next document.
Where Transposition Errors Enter
Any time a number is retyped, there is a chance it changes. A transposed digit, a mis-read column heading, a value pulled from the wrong row or the wrong rig: none of these require carelessness. They require only that a person is copying instead of reading from a structured source.
The SME Mining Engineering Handbook addresses this directly in its treatment of geological data collection: data entry programs are designed specifically to "minimize transposition errors" and to "ensure that drill-hole data are entered sequentially from top to bottom," with automated checks flagging values that appear out of range (4.1.2.1 General Comments, p. 146). The concern is not theoretical. Transposition is a documented failure mode, consistent enough to warrant algorithmic controls on data that moves from paper to a database.
Field-to-invoice data is the same category of problem. The numbers are different - billing codes and meters rather than assay values - but the failure mode is identical: a value entered in one place gets copied to another by a person who has no system alerting them to the mismatch.
The most common mismatch point, in practice, is the shift report. Most shift supervisors write their reports at the end of the shift or the beginning of the next one, working from memory and a glance at the field book rather than a structured hand-off. If the field book is in the cab and the supervisor is in the crib, the meters go in from recall. A 40-meter hole becomes 400 meters. An 8-hour downtime becomes 80 hours. These do not always look wrong when you are reading quickly through a page.
It is worth noting that 30 CFR Part 50 requires production and employment records from the same daily figures that feed the invoice. An error that makes it past the daily review often makes it into the MSHA submission as well, which creates a compliance exposure that has nothing to do with billing and everything to do with the same copy-paste chain.
What the Double Data Entry Load Costs Beyond the Clock
The worked example sizes the total transcription volume for a 3-rig operation at around 1,296 individual number-copying steps per week. The time and dollar cost depend on how fast those steps happen and what the person doing them earns, which is why the reporting-chain-cost calculator is built around your own inputs: rig count, shifts per week, entries per report, time per transcription, hourly rate.
What the transcription count does not capture is the correction loop. When a number at the invoice stage does not match the number on the daily, someone has to trace it back. That trace - pulling the daily, checking the field book, confirming with the supervisor, correcting the cost sheet, correcting the invoice, notifying the client if needed - can take an hour for a single discrepancy. Operations that have never run a formal reconciliation often find several per month they did not know existed.
The real cost is not mainly the transcription time. It is the correction time, the dispute time, the time explaining to a client why the numbers do not match, and the revenue that leaks when a shift never makes it through the chain at all. Those costs do not appear on a timesheet because they are distributed across everyone who touches the chain: the supervisor who fields a call about a discrepancy, the office manager who rebuilds a daily from memory, the owner who writes a credit note.
Getting the Chain Down to One Write
The goal is not faster retyping. The goal is eliminating the handoffs where the number changes.
That means the field record has to flow directly into downstream documents without a person copying it in between. This happens at different levels of effort:
At the simple end: the field form is structured to match the invoice line items from the start. The driller fills out a form with fields that map one-to-one to the invoice codes. The office manager reviews rather than transcribes. This alone removes two handoffs and the most common error point.
At the next level: the daily report is generated from the field form rather than written separately. The supervisor reviews and approves the values; they do not retype them. The original entries travel forward instead of being rewritten.
At the connected end: the cost sheet and invoice pull from the same source. Month-end invoicing is an export, not a retyping session. The accounting software ingests a file from the same spreadsheet the office manages throughout the month. There is no fifth pass.
Each level reduces how many times a value is copied, and each reduction cuts both the time cost and the probability of a mismatch reaching the client.
Mid-Month Visibility as the Payoff
A client who receives a mid-month billing summary is rarely surprised at month end. They have seen the numbers accumulating; they have raised questions while there is still time to resolve them; the invoice arriving at the end is a confirmation rather than the opening of a negotiation.
This is only possible if the chain is clean. A mid-month total requires knowing, in real time, how many meters have been drilled, how many standby hours have been coded, and what the delay reasons are. That knowledge lives in the field book. If the field book is on paper and the office sees it two weeks later in a batch of dailies, mid-month visibility is not available as an option.
If the chain runs cleanly from field to cost sheet, the office has a running total at any point in the month. Disputes become smaller because they get handled before the invoice exists rather than after it arrives. A client who pays on time will pay an invoice that was invoiced correctly, and will also pay an invoice that was six thousand dollars light. Paying on time is not the same as being billed right.
That shift - from a month-end surprise to a running total - is what a one-write chain enables. The number gets entered once, in the field, and every document downstream reads from 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
Can I generate the invoice straight from the daily cost sheet?
You can if your daily uses the same line items and codes as your contract. Most operations find the daily was designed for site reporting rather than billing, so some items translate directly and others need interpretation. Restructuring the daily to match invoice categories is a one-time fix; once it does, generation is close to automatic.
Can QuickBooks take our line items directly, or does someone retype them?
QuickBooks imports from CSV, which means a spreadsheet-built invoice can feed it directly without retyping once the import template is set up. Most offices type line items manually because they have never built the export. The setup takes a few hours once; after that the import takes minutes instead of a half-day at month end.
What do I do when the meters on the daily do not match the meters on the invoice?
Go back to the field book before changing anything else. The daily is the most common error point because it is often written from memory rather than directly from the original record. Correct at the source, then trace forward. Never adjust the invoice without correcting the daily to match, or the backup will contradict itself at the next dispute.
How much revenue leaks because a shift never made it onto an invoice?
Most operations have no way to answer this without a reconciliation they have not done. Running it once - comparing field entries against invoice line items month by month - typically surfaces one to three unbilled shifts in a three-to-five rig operation. The dollar value depends on your rate, but the leak is almost always there once someone looks.
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.
