Commissioned Research
Top 9 Best Drill Core Logging Software of 2026

GITNUXSOFTWARE REVIEW

Manufacturing & Engineering

Top 9 Best Drill Core Logging Software of 2026

Compare drill core logging software options and fit for geology and mining teams, with tool notes on MX Deposit, WellCAD, and acQuire GIM Suite.

19 min readUpdated Editorially scoped research
How we ranked these tools
01Editorial Scope

Vendors set the topic, but our editors set the inclusion criteria and the evaluation framework before research starts.

02Source Research

AI search agents find sources, extract figures with provenance, and aggregate written reviews. They also transcribe video reviews and podcasts.

Read our full methodology →

Framework: Features 40% · Ease 30% · Value 30%

Gitnux may earn a commission through links on this page. This does not influence our reviews. Editorial policy

Drill core logging software structures photos, intervals, geotech observations, and lab metadata into a controlled data model that labs and geology teams can query and audit. This roundup helps evaluators weigh integration, configuration, and governance tradeoffs across platforms that range from cloud logging to lab-to-model data handoffs.

MX Deposit is the best choice for exploration drill teams that need repeatable interval logging tied to depth context because its depth-range templates enforce consistent sample capture across core runs and projects, while WellCAD is a strong fit for geology teams wanting depth-driven structured logging with lab attribute imports via template-linked samples.

Editor’s top 3 picks

Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.

Editor pick
1

MX Deposit

Depth-range logging templates that enforce consistent sample capture across core runs and projects.

Best for: Fits when drilling teams need repeatable interval logging tied to depth context, with controlled admin templates.

2

WellCAD

Editor pick

Template-driven interval logging that links sample numbering and coded observations to depth organization across core runs.

Best for: Fits when geology teams need structured, depth-driven core logging with reliable import of laboratory attributes.

3

acQuire GIM Suite

Editor pick

Governed, reference-data driven logging forms that enforce consistent lithology and structure coding across intervals.

Best for: Fits when geological teams need governed logging workflows tied to GIS and repeatable coding rules.

Comparison Table

1
MX DepositBest overall
SMB
9.5/10
Overall
2
vertical specialist
8.9/10
Overall
3
8.8/10
Overall
4
8.5/10
Overall
5
8.2/10
Overall
6
vertical specialist
7.9/10
Overall
7
7.5/10
Overall
8
7.1/10
Overall
9
vertical specialist
6.8/10
Overall
#1

MX Deposit

SMB

Cloud drillhole data management and core logging application built for exploration teams.

9.5/10
Overall
Features9.5/10
Ease of Use9.5/10
Value9.5/10
Standout feature

Depth-range logging templates that enforce consistent sample capture across core runs and projects.

MX Deposit organizes drilling and logging around project structure and depth-aligned intervals, so logged properties stay tied to a defined depth range. The software supports template-driven fields for lithology, alteration, and other structured observations without forcing free-text only entry. It also supports project outputs that are ready for sharing with geologists and project managers who need consistent records.

A key tradeoff is that deep custom data modeling stays bounded by the provided template and configuration mechanisms, so teams needing highly bespoke mineralization schemas may do more integration work. MX Deposit works best when a project already has reliable collar and run context and the team wants repeatable capture of structural and material observations across many core intervals.

Pros
  • +Interval-first logging keeps observations attached to depth ranges
  • +Template-driven fields support consistent lithology and attribute capture
  • +Project outputs reduce manual formatting for reviews and handoffs
  • +Admin controls centralize configuration and logging rule governance
Cons
  • –Highly bespoke logging schemas can require workflow workarounds
  • –Third-party lab import and assay interchange depth can lag specialized tools
Use scenarios
  • Geology data managers

    Standardize interval capture across crews

    Cleaner drillhole database records

  • Exploration geologists

    Review structural observations quickly

    Faster QA-focused review cycles

Show 1 more scenario
  • Project managers

    Track logging progress by project

    More reliable handoff timing

    Admin configuration and controlled logging workflows support predictable status reporting.

Best for: Fits when drilling teams need repeatable interval logging tied to depth context, with controlled admin templates.

#2

WellCAD

vertical specialist

Borehole and well-log software that supports geological, geotechnical, and drill-core documentation.

8.9/10
Overall
Features8.9/10
Ease of Use8.9/10
Value8.9/10
Standout feature

Template-driven interval logging that links sample numbering and coded observations to depth organization across core runs.

WellCAD targets the day-to-day mechanics of drill core logging with workflows organized around intervals, runs, and per-sample observations.

The system’s configuration emphasis centers on repeatable capture of coded geology attributes and consistent depth-referenced record linking.

WellCAD provides integration for bringing laboratory or external attributes into logged datasets so project teams can consolidate observations and measurements.

Admin and governance depth is present but not as pronounced as in drillhole systems built for multi-tenant enterprise RBAC and audit review.

Pros
  • +Depth-interval logging supports consistent sample-level capture across core runs
  • +Logging templates reduce rework for lithology, structure, and attribute coding
  • +External data exchange supports importing laboratory and auxiliary values into projects
  • +Project configuration enables repeatable workflows for QA/QC insertion handling
Cons
  • –Setup of logging schema and required fields requires upfront configuration work
  • –Oriented core handling and downstream orientation visualization depend on project configuration
  • –Auditability and governance controls are less explicit than in enterprise drillhole stacks
  • –Cross-project portability can require manual mapping when templates differ
Use scenarios
  • core logging teams

    Generate interval reports for regulators

    Traceable visual handoff

  • field geologists

    Run QA checks before interpretation

    Cleaner data for review

Show 2 more scenarios
  • geological modelers

    Draft 2D sections and fences

    Repeatable section drafting

    Create annotated sections and fence diagrams from formation tops, lithology, faults, and drillholes.

  • data technicians

    Digitize legacy measurements

    Searchable log database

    Convert imported field or laboratory measurements into organized, depth-consistent digital log records.

Best for: Fits when geology teams need structured, depth-driven core logging with reliable import of laboratory attributes.

#3

acQuire GIM Suite

enterprise

Geoscientific information management software for drill-hole data, core logging, sampling, and laboratory results.

8.8/10
Overall
Features8.8/10
Ease of Use8.8/10
Value8.8/10
Standout feature

Governed, reference-data driven logging forms that enforce consistent lithology and structure coding across intervals.

acQuire GIM Suite is a drill core logging workflow tool built around managing intervals, sample events, and field-to-database traceability. The core capabilities center on structured lithology and structure capture, consistent sample numbering patterns, and audit-friendly edits across runs and core intervals.

It supports automation through configurable forms and controlled reference data so repeat logging stays consistent across projects. Strong GIS integration and data exchange workflows help connect collar locations and downhole context to the logged observations.

Pros
  • +Configurable logging forms reduce variation across core intervals and runs
  • +Traceable edit history supports governance over interval and sample changes
  • +GIS integration links collar and downhole context to logged observations
  • +Reference-data driven coding helps keep lithology and structure categories consistent
Cons
  • –Deep configuration is required before teams can log consistently
  • –Advanced oriented core fields depend on project-specific form setup
  • –Complex reporting often needs data export and external reshaping
  • –Collaboration workflows can feel heavier than simple spreadsheet-style logging
Use scenarios
  • exploration geologists

    Log lithology by depth intervals

    Depth-consistent core records

  • logging supervisors

    Enforce audit-friendly edits

    Audit-ready change history

Show 2 more scenarios
  • GIS and data teams

    Connect collar location to logs

    Geospatially grounded intervals

    Link downhole context and collar coordinates to logging observations through GIS integration and exchange workflows.

  • data managers

    Automate structured form capture

    Faster standardized logging

    Use configurable forms tied to intervals and events to speed repeat logging and reduce rework.

Best for: Fits when geological teams need governed logging workflows tied to GIS and repeatable coding rules.

#4

Seequent Central

enterprise

Geoscience data management platform integrating drill core logging with 3D modeling.

8.5/10
Overall
Features8.5/10
Ease of Use8.5/10
Value8.5/10
Standout feature

Interval-first logging workflows with role-based review steps keep core records consistent during multi-round validation.

Seequent Central’s core capability is turning logging into a governed workflow using configurable forms, interval-based navigation, and role-based access to limit who can create, edit, or approve records. Central supports field and office collaboration by keeping logging artifacts in one place so subsequent review rounds do not require manual file reconciliation. The system also favors integration with the surrounding Seequent ecosystem for moving from downhole geometry inputs to sample-centric outputs and visual review of logged intervals.

Pros
  • +Configurable logging templates enforce consistent interval attributes
  • +Role-based access supports controlled editing and approval flows
  • +Centralized project hub reduces spreadsheet version drift
  • +Integration-friendly workflow links logs with related project objects
Cons
  • –Requires early alignment to project structure for smooth adoption
  • –Template changes can add overhead for already-logged intervals
  • –Advanced automation depends on available integration paths
Use scenarios
  • Core logging supervisors

    Approve logged intervals across teams

    Fewer review rework cycles

  • Geotechnical drilling managers

    Coordinate contractors and field notes

    Cleaner handoff between shifts

Show 1 more scenario
  • Geoscience modeling teams

    Maintain consistent inputs to models

    Lower modeling input mismatch

    Modeling teams reuse approved logging records tied to project interval references for consistent downstream updates.

Best for: Fits when geoscience teams need governed, repeatable core logging across locations and review rounds.

#5

Geological Data Technologies GeoBank

vertical specialist

Data management platform for geological sample and drill core logging workflows.

8.2/10
Overall
Features8.2/10
Ease of Use8.2/10
Value8.2/10
Standout feature

Geology-first drillhole database workflow keeps imported lab and interval data aligned to depth context.

GeoBank centers drillhole database management and interval organization, so core logging stays connected to the drillhole record instead of living in disconnected spreadsheets. The logging experience is configured around geology-specific attributes, which reduces rework when the same interval drives multiple downstream uses like reports and sample exports. External data exchange is handled through import mapping workflows that bring lab results and surveying data into the correct hole and depth context.

Pros
  • +Drillhole-centered workflow keeps interval data tied to collar and survey context
  • +Configurable geology field sets support consistent lithology and geotechnical logging
  • +Import mapping reduces manual retyping for lab results and external depth data
  • +Sample interval and numbering workflows support repeatable assay handoff
Cons
  • –UI flexibility for custom screens can lag behind form-first logging tools
  • –Best results require disciplined configuration of depth and interval structures
  • –API and automation surface appears less emphasized than logging and import workflows
  • –Complex programs may need specialist attention to maintain field mappings
Use scenarios
  • Geology data managers

    Maintain drillhole record consistency

    Fewer reconciliation errors

  • Core logging supervisors

    Standardize geotechnical logging

    More consistent logging

Show 2 more scenarios
  • Assay and lab coordinators

    Import lab results into intervals

    Faster assay handoff

    Import mapping aligns external laboratory data to the correct drillhole and interval structure.

  • Exploration program teams

    Manage multi-hole logging throughput

    Higher interval throughput

    Interval organization and sample numbering workflows support scalable logging and exports across programs.

Best for: Fits when geology teams need governed drillhole and interval data exchange across many holes.

#6

LogChief

vertical specialist

Geological logging software for collecting and managing drill-hole and field observations.

7.9/10
Overall
Features7.9/10
Ease of Use7.9/10
Value7.9/10
Standout feature

Depth-to-interval alignment built around collar and downhole survey context, so interval records remain coherent during edits.

LogChief drives drill core logging from depth-linked intervals to structured fields, with form-based capture for lithology, structure, and sampling events. It centers workflows around importing and managing downhole context like collar and survey data so interval records stay aligned to depth.

Pros
  • +Depth-linked interval capture keeps core notes aligned to collar-survey context
  • +Form-driven logging supports structured capture for geotechnical and structural fields
  • +Export supports drillhole database workflows that require interval-centric records
  • +QA/QC insertion fits repeating sample patterns during logging
Cons
  • –Schema rigidity can slow changes when logging codes evolve mid-program
  • –Automation depth is limited compared with tools that offer richer integrations and API-first pipelines
Use scenarios
  • core logging teams

    Capture structured attributes by depth

    Structured depth-linked logs

  • data managers

    Maintain collar and survey alignment

    Aligned interval data

Show 2 more scenarios
  • QA analysts

    Insert QA/QC materials into runs

    Consistent QA records

    Handle common sample numbering and insert QA/QC materials into the logging stream for validation.

  • geology data teams

    Export to drillhole databases

    Fewer manual data transfers

    Produce drillhole database and lab data exchange formats for downstream ingestion.

Best for: Fits when teams need interval-first drill core logging with consistent sample and depth alignment, then push exports into downstream systems.

#7

Maptek Drill Core Logging

enterprise

Core logging module within the Maptek geological modeling and mine planning suite.

7.5/10
Overall
Features7.5/10
Ease of Use7.4/10
Value7.6/10
Standout feature

Interval logging templates that enforce coded fields and depth logic tied to core runs and drillhole records.

Maptek Drill Core Logging is a geology-focused system for recording and managing drill core observations inside a structured drillhole database workflow. It emphasizes controlled coding for lithology, alteration, and structural picks while keeping depth-aligned interval data tied to core runs.

Pros
  • +Depth-aligned interval capture reduces drift between runs and records
  • +Structured pick lists support consistent lithology and alteration coding
  • +Laboratory data exchange supports bringing assay-style results into the drillhole record
  • +Template-driven forms help multiple loggers follow the same protocol
Cons
  • –Setup of logging templates and validation rules needs governance discipline
  • –Oriented core metrics depend on data entry patterns that must be standardized
Use scenarios
  • mining geologists

    Code lithology and structural picks

    Consistent geology codes

  • lab data coordinators

    Import and exchange lab results

    Connected assay and geology

Show 2 more scenarios
  • drillhole database administrators

    Tie intervals to core runs

    Reliable depth traceability

    Keep depth-aligned interval records connected to collar and survey context used for drillhole management.

  • multi-logger projects

    Enforce logging templates and traceability

    Standardized logging outputs

    Use repeatable templates to maintain audit-friendly traceability across multiple loggers and runs.

Best for: Fits when geology teams need depth-structured logging plus lab imports inside a drillhole database workflow.

#8

Maxwell Geoservices LogChief

enterprise

Drill core logging software supporting geological and geotechnical data capture.

7.1/10
Overall
Features7.1/10
Ease of Use7.2/10
Value7.0/10
Standout feature

Depth-interval logging that keeps sample numbering and coding consistent across core runs.

Maxwell Geoservices LogChief performs end-to-end drill core logging workflows from sample capture through structured lithology and structural coding. The system is built around interval-based recording and depth-aware sequencing, which supports repeatable sample numbering, QA/QC insertion, and consistent attribute entry across core runs.

Pros
  • +Depth-interval driven logging reduces mistakes when recording core segments
  • +Configurable lithology and structural coding supports repeatable logging standards
  • +QA/QC insertion workflows fit common sampling discipline patterns
  • +Export and import paths support laboratory data exchange workflows
Cons
  • –Governance and user administration capabilities are less visible than workflow features
  • –Extensibility depends on configured coding schemes instead of ad hoc scripting
  • –Oriented core attributes can require careful setup to match local conventions
  • –Complex projects may need more operator training than lighter logging tools
Use scenarios
  • core logging teams

    Sequence intervals for structured entry

    Repeatable interval workflows

  • QA/QC coordinators

    Insert QA/QC into the logging stream

    Verifiable quality samples

Show 2 more scenarios
  • assay and lab coordinators

    Exchange lab data for samples

    Reduced re-keying work

    Automate imports for laboratory data exchange tied to configured interval coding and sample tracking workflows.

  • drillhole database teams

    Export for database ingestion

    Faster downstream loading

    Produce export-ready outputs that support drillhole database ingestion and downstream field processes.

Best for: Fits when geotechnical and mineral projects need depth-aware core logging with strict coding consistency and lab sample linkage.

#9

DataShed

vertical specialist

Geological data management software for drill-hole logging, sampling, QA/QC, and reporting.

6.8/10
Overall
Features6.8/10
Ease of Use6.8/10
Value6.8/10
Standout feature

Configuration-driven logging templates that enforce interval-aware validation across sample numbering and QA/QC insert points.

DataShed targets drill core logging workflows with a configuration-driven interface that maps logging tasks to depth intervals and structured attributes. Its focus on drillhole database style record management supports repeated QA/QC insert points, sample numbering alignment, and lab data exchange patterns used in core and assay pipelines.

Pros
  • +Template-based logging forms reduce drift across drillhole collar and interval records
  • +Interval depth-to-depth mapping supports consistent sample interval generation
  • +Import and export workflows support assay and laboratory data exchange patterns
  • +Built-in validation supports catching misnumbered samples before exports
Cons
  • –Advanced structural logging fields require careful template configuration
  • –Oriented core capture workflows feel less specialized than dedicated geotech tools
  • –Batch edits can become cumbersome for large projects with frequent revisions
  • –Integration depth depends on how lab formats align with supported import structures
Use scenarios
  • core logging teams

    Map logging tasks to depth intervals

    Fewer depth mapping errors

  • QA/QC coordinators

    Standardize repeated QA insert points

    Uniform QA coverage

Show 2 more scenarios
  • assay pipeline teams

    Move between logging and assays

    Lower manual re-entry

    Use imports, validations, and exports to shift data between logging, assays, and downstream reporting.

  • geology standards teams

    Enforce lithology coding templates

    Consistent coded attributes

    Standardize controlled review flows and template-based logging for lithology and structural coding across projects.

Best for: Fits when project teams need repeatable drill core logging templates tied to interval depth and controlled QA/QC.

Conclusion

After evaluating 9 drill core logging software, MX Deposit stands out as our overall top pick — it scored highest across our combined criteria of features, ease of use, and value, which is why it sits at #1 in the rankings above.

Our Top Pick
MX Deposit

Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.

Frequently Asked Questions About Drill Core Logging Software

How does MX Deposit handle interval logging when collar and survey context must stay consistent?
MX Deposit maps core runs and samples to depth positions so interval entries remain tied to project context. Its depth-range logging templates enforce repeatable sample capture across core runs, which reduces rework when multiple loggers write the same hole.
When teams need governed multi-round validation, which workflow fits best between Seequent Central and WellCAD?
Seequent Central uses role-based review steps in a shared project hub so lithology and structure picks follow controlled validation rounds. WellCAD focuses more on template-driven interval logging and coded observation capture, so it fits teams that prioritize consistent data entry and import rather than multi-round review governance.
What breaks if a drillhole database team imports lab results without a depth-aware mapping workflow like GeoBank?
In Geological Data Technologies GeoBank, lab and survey imports map into hole records aligned to depth context, so interval-level alignment stays coherent. Without that mapping approach, sample intervals and assay attributes can drift from the intended depth-from-depth-to windows and break downstream drillhole database ingestion.
How do drill core logging tools support drillhole collar and downhole survey linkage during edits?
LogChief keeps interval records aligned by importing collar and downhole survey context so depth-to-interval relationships remain coherent during changes. Maptek Drill Core Logging also aligns coded picks to core runs and depth-aligned interval data so the logging stream stays traceable to the underlying drillhole records.
Which tool’s admin controls focus on enforcing logging rules and template consistency across projects?
MX Deposit concentrates admin tooling on users, templates, and data entry rules to control how interval capture is performed. DataShed also emphasizes configuration-driven templates with interval-aware validation, but MX Deposit centers governance around template enforcement tied to project workflows.
How is QA/QC material handled in LogChief versus DataShed when QA insertion points must be repeatable?
LogChief implements QA steps by managing sample numbering patterns and inserting QA/QC materials into the logging stream for consistent coverage. DataShed supports repeated QA/QC insert points within configuration-driven interval tasks, which aligns QA placement with sample numbering and attribute capture rules.
What integration pattern matters most when core logging must connect to external lab and laboratory data exchange workflows?
GeoBank differentiates automation around importing and mapping external lab and survey data into hole records. Maxwell Geoservices LogChief uses import paths for laboratory data exchange tied to configurable coding schemes, which keeps lab-linked attributes consistent with its depth-aware interval logging.
How do WellCAD and acQuire GIM Suite differ in record structure for lithology and structural coding?
WellCAD emphasizes template-driven interval logging that links sample numbering and coded observations to run-length organization across core runs. acQuire GIM Suite centers governed reference-data-driven forms that enforce consistent lithology and structure coding patterns across intervals, which supports repeat logging with controlled coding behavior.
When oriented core data like alpha angle and beta angle must be captured with audit-ready traceability, which system handles it more directly?
Seequent Central is structured for disciplined review steps tied to shared project objects, which supports traceability as lithology and structural attributes evolve across iterations. acQuire GIM Suite focuses on governed reference-data-driven forms and controlled reference data for repeat coding, which fits teams that want consistent capture rules across multiple logging rounds.

Tools reviewed

Primary sources checked during evaluation.

Referenced in the comparison table and product reviews above.

How to Choose the Right Drill Core Logging Software

We see the biggest differences in drill core logging software come from how deep the data model goes, how reliably the system automates logging workflows, and how far the API and integration reach for moving data in and out. Those choices determine whether teams can keep core data consistent across runs and formats.

Automation for interval entry

Why it matters

Automation for interval entry reduces manual rework when lots or runs change, and it helps keep depth-aligned entries consistent across the log. In drill core logging software, that directly affects throughput and data quality.

How to check

Ask for a demo workflow that imports a run file and then generates intervals for editing. Confirm whether the system can apply defaults (for example, template fields) to new core intervals and how many clicks it takes to add or adjust a run.

Depth alignment across runs

Why it matters

Depth alignment across runs matters because drill core logs often span multiple runs and file conventions. If depths don’t stay consistent, downstream interpretation becomes difficult even when all other fields look correct.

How to check

Bring sample data with at least two runs that use different depth ranges or offset conventions. In the demo, verify how the system displays depth, whether it preserves original depth references, and how it handles edits that shift interval boundaries.

Data model flexibility for codes

Why it matters

Data model flexibility for codes determines how well the system represents real-world variability in logging fields and controlled vocabularies. In drill core logging software, rigid models create workarounds that break later analytics.

How to check

Request to see how the system handles custom fields and controlled codes (for example, new lithology or structure code sets). Then test by importing a file that uses a new code and observe whether it maps cleanly or requires manual correction.

API and export for lab handoff

Why it matters

API and export for lab handoff separates tools that stay locked into one UI from tools that can feed other pipelines. For drill core logging software, this is where extensibility and configuration show up.

How to check

Ask what the API can do beyond basic export: pull logs by run, push updates, and validate records. In the demo, check an export format and confirm it includes depth-aligned identifiers and preserves code values.

Provenance and audit trail

Why it matters

Provenance and audit trail matters when multiple people edit logs over time. In drill core logging software, auditability helps teams trace what changed and when, especially for imported intervals and corrected depth ranges.

How to check

During the demo, perform an edit to an interval field and then check whether the system records the user, timestamp, and prior value. Ask how it shows provenance for imported records and whether it supports viewing change history at run and interval levels.

Red flags

  • Edits break depth alignment when you adjust interval boundaries
  • Code values fail to map on import without heavy manual correction
  • Audit history doesn’t capture who changed what and when at interval level

Fit by situation

  • If we need to import run files repeatedly and keep logging consistent, prioritize automation for interval entry.
  • If our project spans multiple runs with different depth conventions, prioritize depth alignment across runs.
  • If we must move validated logs to other systems with traceability, prioritize provenance and audit trail.
Commissioned Research

Funding and competing interests

This study was co-funded by several of the vendors assessed in it. No single vendor funded it. Funders could propose the market studied.

They had no role in selecting vendors, setting or weighting criteria, analysing data or drawing conclusions, and they received the same factual-accuracy check as every other vendor assessed.

Market definition, inclusion rules and criteria weights were fixed by an editor before research began and did not change afterwards. Editorial process →

Keep exploring

FOR SOFTWARE VENDORS

Not on this list? Let’s fix that.

Our best-of pages are how many teams discover and compare tools in this space. If you think your product belongs in this lineup, we’d like to hear from you—we’ll walk you through fit and what an editorial entry looks like.

Apply for a Listing

WHAT THIS INCLUDES

  • Where buyers compare

    Readers come to these pages to shortlist software—your product shows up in that moment, not in a random sidebar.

  • Editorial write-up

    We describe your product in our own words and check the facts before anything goes live.

  • On-page brand presence

    You appear in the roundup the same way as other tools we cover: name, positioning, and a clear next step for readers who want to learn more.

  • Kept up to date

    We refresh lists on a regular rhythm so the category page stays useful as products and pricing change.