Paper logging persists on more programs than most geologists would admit. Partly inertia, partly budget constraints, partly the genuine comfort of a system that’s worked for decades. A paper form doesn’t crash, doesn’t need charging, and doesn’t require a login. That’s not nothing.
But the cost of paper isn’t what you pay at the stationery supply store. It accumulates in transcription time, in verification backlogs, in errors that reach the resource model six months after the hole is complete, and in the uncomfortable truth that your core data is one flooded core shed away from being gone forever.
This is a direct comparison. Time, cost, data quality — what paper actually costs against what digital actually requires. Including where paper still has a legitimate case.
The paper workflow: what it actually looks like
On a paper-based program, the geologist logs on pre-printed forms. Field observations go onto paper in the core shed, often at the end of a long shift. Those forms then travel — physically or as scanned files — to someone who enters them into a spreadsheet or database. The data entry step is usually done by a data technician, a junior geologist, or the logging geologist themselves during evening downtime.
This is the two-step problem. Data is collected once and entered twice. Every pass introduces error opportunities: illegible field notation, transposed numbers, a depth call that gets rounded differently between paper and screen, an alteration code that gets misread. On a two-month, 10,000-metre program with five geologists, those errors accumulate into a verification problem that can take weeks to sort out.
One Galore Creek Mining Corporation geologist described the experience directly: before moving to digital logging, the team was doing paper capture followed by a data verification process at the end of season that ran approximately six weeks. After switching to direct digital data entry, that verification period dropped to around five days. Same data volume, same geological complexity — the difference was eliminating the transcription layer.
That’s not a marginal improvement. Six weeks of senior geologist time, applied to model updates and resource estimation instead of chasing transcription errors, is a meaningful change in how a program operates.
Time comparison: where the hours actually go
Data entry
A competent geologist logging lithology and alteration on a moderate-complexity program can work through 20–30 metres of core per hour. That rate doesn’t change much between paper and digital — the geological observation itself takes the same amount of time regardless of what you write it on.
What changes is everything after the observation.
Paper: Logging pass (20–30 m/hr) → review for legibility → batch scan or manual carry → data entry by technician or evening self-entry (often adds 30–60 minutes per 8-hour shift) → verification against paper originals when discrepancies surface.
Digital: Logging pass (20–30 m/hr) → data is in the database. Done.
The logging speed is identical. The administrative overhead is not. On a program running 200 metres of core per day across a five-person team, digital logging saves roughly 1–2 hours of total labour per day on data entry alone. Over a 60-day program, that’s 60–120 hours of recovered time.
Data verification
Paper-based programs accumulate a verification backlog. Intervals logged in week one don’t get checked against the database until week three, when the data technician has caught up. Errors discovered then require going back to paper forms — if they’re legible, and if the form is findable.
Digital logging with built-in validation doesn’t accumulate this backlog. Validation rules run at the point of entry: overlapping depth intervals are flagged immediately, required fields block submission if left blank, dropdown columns prevent code inconsistencies from ever entering the database. The error is caught when it’s cheapest to fix — in the field, while the core is still on the table and the geologist’s memory is fresh.
The distinction matters most in the weeks before a resource estimate is due. On a paper-based program, that period often involves a data cleanup sprint — geologists reviewing the database against original forms, hunting down suspect intervals, reconciling codes that don’t match across holes. On a digital program with consistent validation, that sprint is largely unnecessary.
Export and modelling handoff
On a paper-to-database program, the chain from field to model looks like this: paper form → data entry → spreadsheet → reformat → Leapfrog import. Each handoff step takes time and introduces further error risk. Teams report reformatting assay and lithology exports for Leapfrog as a recurring half-day task each time the geologist needs a fresh model update.
Digital logging with a configured export workflow eliminates the intermediate steps. Define the column mapping once; run the export whenever you need it. The data arrives pre-formatted and ready to import. No Excel in the middle.
Cost comparison: the numbers that matter
Drilling costs $50 to $500 per metre depending on depth, method, and location. A 300-metre diamond hole at a remote Canadian site costs $90,000–$120,000 before assay. That’s the front-end investment your core logging data is supposed to protect.
The cost of getting it wrong compounds through the system:
Transcription error discovered late. A misread lithology contact in week one shifts a wireframe boundary in the resource model. The error surfaces during model review in month three, after the wireframe has been built and composited. Correcting it requires rebuilding the solid — a multi-day exercise at senior geologist rates ($100–$150/hr for a P.Geo or RPGeo) — plus a verification pass to check for similar errors in adjacent holes. A single bad depth call can cascade into a week of rework.
Data cleanup at end of program. Industry testimony is consistent: data cleaning on paper-to-database programs regularly costs hundreds of thousands of dollars on programs with significant data volumes. The cost isn’t just labour — it’s delayed resource updates, deferred decision-making, and the risk that investors receive resource estimates built on data that hasn’t been fully verified.
Data loss. Paper is physically vulnerable in ways databases are not. Core sheds flood. Forms get wet. Fires happen. Scan quality degrades. A physical well log lost to environmental damage may require re-drilling to recover the information — if it can be recovered at all. Physical paper deterioration resulting in data loss has been documented as a material risk in the O&G sector, and the same risk applies to mineral exploration data. A database with regular backups is not vulnerable to a leaky roof.
The cost of 60% of geoscientist time spent on data management. Research consistently finds that geoscientists spend roughly a fifth of their working time managing data rather than interpreting it. On a $15,000/month senior geologist, that’s $3,000/month of salary allocated to data housekeeping. Digital logging with proper validation and export workflows directly reduces that burden — not to zero, but meaningfully.
What digital logging actually costs
The direct cost of digital logging is the software subscription plus the initial setup time for template configuration and team training. On Blue Butterfly, that’s per-project pricing with no per-seat licensing math. Setup for a standard exploration project runs half a day to a full day, not a week. Training a new field geologist on the logging interface takes an hour or two, not a course.
The initial learning curve is real but shallow. Most geologists are comfortable with the software by their second or third day of active logging.
Data quality comparison
Consistency across the team
On a paper program, five geologists produce five slightly different logging styles. One uses “GRP” for granite porphyry, another writes “Gr Porph,” a third records “granitic porphyry.” All three mean the same rock. None of them match when you try to sort or filter the database later.
Digital logging enforces consistency through dropdown columns. The list of valid values for rock type, alteration, mineralisation, and any other coded field is defined once in the template. Every geologist on the project sees the same options and selects from the same list. Terminology drift across a multi-person team doesn’t happen.
Validation at entry
Paper validation is retrospective by nature. You check the form after it’s been logged, after it’s been entered, after the hole is completed. Errors caught at each stage are cheaper to fix than errors caught later, but they’re all caught after the fact.
Digital validation is prospective. The depth-interval check runs the moment you try to enter an interval that overlaps with the one above it. The required-field check fires when you try to move to the next row without filling in a mandatory column. The dropdown constraint prevents the code typo from ever reaching the database. Errors are caught when they cost nothing to fix — before they’ve been recorded anywhere.
Audit trail and attribution
A paper form tells you what was recorded. A digital log with proper timestamping tells you who recorded it, when, from which device, and what the sync status was. That attribution matters for QP sign-off under JORC and NI 43-101, where the Qualified Person must attest to the chain of custody of geological data. “The form was filled out at site sometime in August” is a weaker audit position than “logged by J. Smith, 14 August 2025, 14:32, site device 003, synced to database 14:35.”
Multi-user integrity
Two geologists logging simultaneously on the same paper-based project produce two sets of forms that need to be reconciled. Two geologists logging simultaneously on a digital platform with real-time sync share a single live database — there’s nothing to reconcile because there’s only one version of the data.
The version-conflict problem — multiple copies, no canonical source, no one certain which spreadsheet is current — is endemic to paper-based workflows and disappears entirely with cloud-native logging.
Where paper still makes sense
Honest answer: a few situations legitimately favour paper.
No device, no power, no option. Some sites are genuinely too remote, too wet, or too rugged for electronic devices, and setup doesn’t allow for rugged tablets. A paper form in a waterproof sleeve is more reliable than a tablet with a flat battery.
Very small programs with immediate entry. A single geologist logging a one-week campaign who enters data into the database the same evening has minimised the transcription error risk. This isn’t ideal, but it’s not the multi-month disaster that emerges on larger programs with dedicated data entry staff.
Historical comparison with paper-logged legacy data. When extending a historical paper-based program, there can be value in maintaining format continuity for the first part of the campaign before migrating, to avoid mixing logging conventions mid-program. Though in most cases, setting up a proper digital template from the start and importing the historical data is the cleaner approach.
Outside these situations, paper’s practical advantages over digital are mostly habit. The risk profile is fundamentally different: paper requires human error to produce good data; digital systems prevent most of the common error modes by design.
Making the switch: what it actually takes
The transition from paper to digital logging doesn’t require a major technology project. The practical steps:
1. Define your dictionary before you start drilling. The most important preparation is agreeing on logging codes before the first hole. What are the rock type codes for this deposit? What alteration assemblages are you tracking? What mineralisation categories are relevant? Build the dropdown lists during project setup, before the drill turns.
2. Configure a template from an industry-standard preset. Most logging platforms offer standard collar, survey, lithology, alteration, and assay templates that can be adapted to the project in a few hours rather than built from scratch.
3. Run a parallel logging day if the team has no digital experience. One day of paper-and-digital in parallel, followed by comparison and debrief, is usually enough to surface any template issues and build team confidence. This isn’t a week-long training program.
4. Set up the Leapfrog export workflow before you need it. Configure the column mapping from day one. Running the export on day three of the program — before there’s any pressure to update the model — confirms the pipeline works and means the first real export goes smoothly.
5. Back up regularly. Even with cloud sync, download a full project backup weekly. Most platforms support this in one click. Keep it somewhere other than the site.
The upfront time investment is a few hours for setup and a day or two for the team to reach comfortable logging pace. The return is a program that doesn’t end in a six-week verification sprint.
The honest version of the paper-versus-digital comparison is this: paper logging worked for decades, and the programs that use it are not failing. But the hidden cost of paper — in verification time, in transcription error, in data cleanup, in the risk of physical loss — is real and consistent across every program that tracks it carefully. The shift to digital isn’t painless, but it’s not a large lift. And the data you get out the other side is materially better.
Blue Butterfly is geological core logging and data management software for exploration programs. One database. Works offline. Set up by a geologist in an afternoon.