
GITNUXSOFTWARE REVIEW
Construction & InfrastructureTop 10 Best Bore Log Software of 2026
Compare bore log software options for geologists and engineers, including gINT, TabLogs, and LogPlot, with key tradeoffs for selection.
How we ranked these tools
Vendors set the topic, but our editors set the inclusion criteria and the evaluation framework before research starts.
Search agents gather the source set and the review record, including transcriptions of video reviews and podcasts.
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
Choose gINT as the best overall for teams that want standardized interval logging because its interval rules automatically connect lithology and depth ranges to export-ready reporting across large borehole libraries, while TabLogs is a strong alternative for geotech reporting where interval-centric capture keeps lithology descriptions tied to depth ranges.
Editor’s top 3 picks
Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.
gINT
Interval rule processing that ties lithology and depth ranges to standardized reporting outputs across large borehole libraries.
Best for: Fits when standardized geotechnical logging forms and repeatable exports matter more than ad hoc data entry.
TabLogs
Editor pickInterval-centric data capture links lithology descriptions directly to depth ranges for export-ready well logs.
Best for: Fits when teams need structured depth interval logging and repeatable exports for geotechnical reporting.
LogPlot
Editor pickDepth-interval driven stratigraphic correlation that propagates into cross-section and fence-style diagram outputs.
Best for: Fits when geotechnical teams repeatedly author interval-based bore logs and generate consistent cross-sections.
Comparison Table
gINT
enterpriseGeotechnical borehole logging and subsurface data management software for civil and geotechnical engineering projects.
Interval rule processing that ties lithology and depth ranges to standardized reporting outputs across large borehole libraries.
gINT from Bentley is a bore log software used to capture geotechnical logging data and generate deliverables from structured templates. Its key strength is the combination of form-based borehole entry, depth-interval logic, and Bentley-style report and export workflows that support repeatable output across many boreholes.
gINT’s integration focus shows up most clearly in exchange targets used in geotechnical engineering work, including common interchange patterns for well and bore log datasets. Admin work typically centers on template-driven configuration so teams can standardize lithology descriptions and headers while keeping the same data capture rules across projects.
- +Template-driven borehole entry enforces consistent interval capture.
- +Strong depth-interval workflow reduces manual cleanup before exports.
- +Report generation supports repeatable deliverables across boreholes.
- +Export mappings align well with common geotechnical exchange needs.
- –Setup of templates and interval rules requires careful governance discipline.
- –Advanced automation can depend on Bentley-specific workflow components.
- –Cross-team configuration changes can slow without change-control habits.
- –For highly bespoke logging logic, customization effort can rise quickly.
geotechnical engineering teams
Standardize lithology interval capture
Fewer data-entry inconsistencies
Bentley workflow administrators
Configure report template deliverables
Repeatable office deliverables
Show 1 more scenario
data exchange coordinators
Export well and bore datasets
Cleaner downstream imports
Coordinators use exchange-friendly structures to support interchange patterns for geotechnical handoffs.
Best for: Fits when standardized geotechnical logging forms and repeatable exports matter more than ad hoc data entry.
TabLogs
vertical specialistCloud borehole logging software for geotechnical, environmental, and mining field data capture.
Interval-centric data capture links lithology descriptions directly to depth ranges for export-ready well logs.
TabLogs targets borehole and lithology logging workflows with depth-interval entry, structured lithological fields, and exportable well log outputs. It supports geotechnical log tabulation with recurring metadata like borehole ID, collar elevation, and total depth tied to each depth interval.
TabLogs focuses less on geologic modeling and more on disciplined capture of descriptions that can be shared with downstream formats like LAS. The product is positioned for teams that need consistent interval data across multiple boreholes and repeated logging sessions.
- +Interval-based logging keeps lithology descriptions tied to depth ranges
- +Borehole header fields reduce retyping across repeated entries
- +Exports fit common well log pipelines when LAS output is required
- +Cross-project consistency helps maintain structured attributes across boreholes
- –Stratigraphic correlation and multi-borehole visualization are limited
- –Automation requires a stronger API surface than tabular exports alone
geotechnical logging technicians
Record intervals with lithology fields
Consistent interval records
geotechnical data managers
Export LAS-ready well log outputs
Faster LAS handoffs
Show 1 more scenario
site investigation coordinators
Keep bore metadata uniform
Uniform borehole references
Coordinators enforce borehole ID, collar elevation, and total depth across repeated logging sessions.
Best for: Fits when teams need structured depth interval logging and repeatable exports for geotechnical reporting.
LogPlot
vertical specialistBorehole and well log visualization software for creating customizable log strip layouts.
Depth-interval driven stratigraphic correlation that propagates into cross-section and fence-style diagram outputs.
LogPlot fits teams that need repeated bore log production from consistent interval data and want stratigraphic correlation to drive downstream visuals. The interface focuses on entering lithological descriptions by depth interval and maintaining a borehole profile context such as collar elevation and total depth. For reporting, it can generate geologic cross-section style outputs and related diagrams using the logged dataset instead of rebuilding graphics from spreadsheets. This makes it practical for sites where many boreholes share comparable geologic units and where the same formats recur across projects.
A key tradeoff appears in governance and automation depth because LogPlot is primarily an interactive authoring tool rather than a headless service for high-throughput logging pipelines. Batch behavior and external integration surface are less central than manual editing and project-level exports, so large-scale re-processing can require a heavier operational workflow around the authoring steps. LogPlot works best when data volumes are manageable for interval-driven editing and when the team values repeatable graphical outputs over fully automated ingestion and validation.
- +Depth-interval editing keeps lithology and outputs linked during updates
- +Stratigraphic column and correlation workflows support consistent unit assignment
- +Cross-section style diagrams can be generated from the logged dataset
- +Borehole header fields support traceable context like collar elevation and depth
- –Less suited to headless automation for continuous high-throughput ingestion
- –External data exchange and automation require stronger surrounding workflow discipline
- –Complex projects can require careful project configuration to avoid export drift
- –Advanced governance controls are not a primary focus for multi-admin environments
Geotechnical logging teams
Create lithology logs for many boreholes
Fewer rework cycles across reports
Site investigation analysts
Correlate units and generate sections
More consistent cross-section interpretation
Show 1 more scenario
Consultancy report producers
Repeat standard diagram outputs
Report formatting stays consistent
Exports reuse the same logged inputs to generate fence diagrams and cross-section visuals.
Best for: Fits when geotechnical teams repeatedly author interval-based bore logs and generate consistent cross-sections.
OpenGround
enterpriseCloud-based geotechnical information management platform with borehole logging and data collaboration features.
Depth-bound photo attachments that stay linked to the exact logged interval for later review.
OpenGround’s core workflow centers on building a borehole as a set of depth intervals with consistent attributes and repeatable entry forms. Logs can include lithology descriptions and field photos that remain associated with each depth range. For organizations exchanging borehole information with other systems, OpenGround provides import and export support for standard well log and bore log interchange.
- +Depth-interval entry model keeps lithology and notes consistently organized
- +Photo capture can be linked to specific depth ranges for auditability
- +Import and export support covers common bore log exchange needs
- +Reusable workflow configuration reduces rework across logging projects
- –Highly free-form commentary does not map cleanly to interval fields
- –Custom downstream formatting often requires tighter agreement on templates
Geotechnical logging teams
Interval logging with photo evidence
Cleaner internal QA reviews
Engineering data coordinators
Bore data exchange for reports
Less manual retyping
Show 1 more scenario
Geoscience analysts
Standardized logs for correlation work
More consistent cross-bore comparisons
Use consistent interval attributes to support stratigraphic interpretation workflows.
Best for: Fits when geotechnical teams need interval-based bore logging with repeatable exports.
WellCAD
vertical specialistBorehole log acquisition, processing, and visualization software for geophysical and geotechnical wireline data.
Depth-interval templates with stratigraphic correlation keep log edits and section outputs synchronized.
WellCAD supports structured borehole logging with depth-interval entry for lithological description and geotechnical parameter fields, then ties those intervals back to borehole identifiers like collar elevation and total depth. The data flow is geared toward generating standard deliverables such as stratigraphic views and cross sections without re-entering content in a separate modeling step. Library-based templates and controlled vocabulary reduce variation when many boreholes share the same geology codes and measurement conventions.
- +Interval-first logging ties every observation to borehole depth
- +Reusable libraries standardize lithology codes and parameter conventions
- +Stratigraphic correlation drives section-style outputs from one dataset
- +Export workflows reduce rework between logging and deliverables
- –Advanced customization can be slower than editing free-form documents
- –Integration depth outside the WellCAD workflow may require manual reformatting
- –Large projects can feel constrained by desktop-file organization
- –Complex cross-section rules often need careful configuration discipline
Geotechnical site investigation teams
Rapid borehole logging for multiple rigs
Fewer inconsistencies in deliverables
Engineering consultants
Section packages for planning submissions
Reduced rework during revisions
Show 1 more scenario
GIS and geology data managers
Consolidating project borehole records
Cleaner downstream data handoffs
Structured borehole headers and interval tables support controlled data organization for reporting cycles.
Best for: Fits when geotechnical teams need consistent interval logging and repeatable section exports across many boreholes.
HoleBASE SI
enterpriseGeotechnical data management and borehole logging system for site investigation projects.
Template-driven borehole interval capture with consistent well header fields for repeatable multi-site logging.
HoleBASE SI captures lithology and interval logs for borehole records with depth-based entries and structured well header fields. It supports export workflows for downstream geotechnical deliverables by mapping logged intervals into common well data outputs.
- +Depth interval logging keeps lithology descriptions aligned with recorded depths
- +Export-oriented workflow supports consistent handoff to geotechnical deliverables
- +Template-driven data entry reduces manual rework across large borehole sets
- +Well header fields reduce ambiguity in borehole identity and elevations
- –Advanced stratigraphic correlation workflows require tighter configuration discipline
- –Complex cross-section style outputs can need external processing steps
geotechnical consultants
Capture lithology with depth-based entries
Traceable stratigraphy records
data handoff coordinators
Map intervals to common outputs
Higher downstream compatibility
Show 1 more scenario
project managers
Reuse templates for fast re-entry
Quicker logging cycles
Managers rely on repeatable templates to keep attribute standards consistent across many boreholes.
Best for: Fits when geotechnical teams need template-based bore log capture and reliable interval exports to other tools.
BoreDM
vertical specialistBorehole data management software for logging, storage, and report generation.
Interval-based bore log capture with consistent structured formatting for repeatable log generation.
BoreDM, accessed at boredm.com, is a bore log workflow tool focused on capturing interval-based geology data and producing shareable log outputs. It centers on structured depth intervals with lithology fields and consistent formatting for project exports.
- +Interval-first entry reduces depth alignment errors during geotechnical logging
- +Consistent output formatting supports repeatable bore log reporting
- +Project-level organization keeps borehole records grouped by job context
- +Export-friendly record structure supports downstream document workflows
- –Limited evidence of deep schema controls for multiple organization-wide standards
- –API and automation surface is not clearly documented for high-throughput integrations
- –Advanced stratigraphic correlation features appear constrained for complex interpretation
- –Cross-section and fence outputs may need manual downstream formatting
engineering field teams
Maintain consistent borehole identifiers
Fewer identifier errors
geotechnical report producers
Generate shareable outputs reliably
More consistent report formatting
Show 1 more scenario
geotechnical documentation coordinators
Export standardized interval geology data
Cleaner cross-tool handoffs
Coordinators export interval-based geology with consistent formatting so logs remain usable across tools.
Best for: Fits when teams need consistent bore log entry and formatted exports for geotechnical reports.
acQuire GIM Suite
enterpriseacQuire GIM Suite manages geoscientific data including drillhole, sampling, assay, and logging records.
API-driven provisioning and interval data workflows with governance controls for consistent multi-project borehole logging.
acQuire GIM Suite captures bore log data in structured field tables and supports multi-stage geotechnical workflows across projects. It provides configuration for well header details, depth interval entries, and controlled lithology attributes that can be exported for downstream drafting and analysis.
- +Interval-level logging supports consistent lithology and attribute control
- +API surface enables automation for data loading and project workflows
- +Governance-friendly controls support multi-project administration
- +Exports maintain borehole ID and depth alignment for drafting
- –Setup needs careful configuration for interval schemas and required fields
- –Bore log entry UI can feel heavy for quick one-off logging
- –Core drafting outputs lag specialized bore log authoring tools
- –Cross-project consistency checks require more manual review
geotechnical program teams
Provision structured bore projects
Repeatable project setup
geoscience analytics staff
Export interval data for analysis
Better analysis consistency
Show 1 more scenario
drafting and documentation teams
Generate deliverables from exports
Fewer manual remaps
Drafting teams take exported bore log fields to maintain consistent formatting across downstream documents.
Best for: Fits when teams need interval-structured bore log data managed across many projects.
LogChief
vertical specialistLogChief captures and manages geological drillhole logging data for exploration programs.
Depth-interval templates that enforce consistent lithological descriptions across the same borehole schema.
LogChief targets geotechnical logging workflows that need structured borehole entry plus export-ready deliverables. Its core focus is lithology and interval capture tied to well header metadata, with configurable templates for consistent field and office logging.
- +Structured interval capture keeps lithology tied to depth ranges
- +Template-driven logging reduces formatting drift across projects
- +Export workflows support common well log exchange patterns
- +Project-level organization helps teams manage shared borehole libraries
- –Advanced automation needs more configuration than spreadsheet-based workflows
- –Complex stratigraphic correlation workflows take extra setup time
- –Cross-section outputs are less flexible than dedicated modeling tools
- –Integration depth depends on defined import and export mappings
geotechnical office teams
Standardize template-based interval capture
More uniform log datasets
project data administrators
Manage shared borehole libraries
Controlled logging collaboration
Show 1 more scenario
geotechnical data exchange coordinators
Export aligned deliverables
Fewer depth-structure mismatches
Coordinators produce export-ready deliverables that keep interval structure aligned with reports and standard formats.
Best for: Fits when geotechnical teams need consistent borehole interval logging and repeatable exports across many projects.
GeoDin
enterpriseSubsurface database and reporting software used for borehole management, geology, and geotechnical documentation.
Interval-first logging workflow that binds lithology descriptions to each depth range for export-ready records.
GeoDin focuses on geotechnical bore log workflows with a browser-based form for capturing borehole details, intervals, and lithological notes. The system organizes logging records around depth intervals and produces structured outputs for sharing and downstream use.
- +Depth interval entry reduces inconsistent borehole stationing
- +Interval-based capture keeps lithology and measurements linked
- +Exports support common geotechnical document interchange patterns
- +Browser-first workflow supports fast capture without local tooling
- –Cross-section and correlation tooling is less extensive than dedicated modeling suites
- –Advanced governance requires careful configuration of templates and roles
- –Automation depth is limited versus systems with broad API-first integration
- –Complex custom report layouts can need manual post-processing
field-to-office logging teams
Capture interval notes in browser forms
Reduced reformatting work
geotechnical report producers
Share AGS-oriented log shapes
Cleaner cross-team handoffs
Show 1 more scenario
data integration specialists
Import and export LAS-style depth logs
Less spreadsheet manipulation
Integration specialists move depth-interval content between systems using LAS-oriented outputs and inputs.
Best for: Fits when teams need consistent interval logging and repeatable exports for geotechnical deliverables.
Conclusion
After evaluating 10 bore log software, gINT 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.
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 Bore Log Software
How do WellCAD, LogPlot, and gINT handle interval-based editing tied to a borehole header?
When teams need section exports and stratigraphic views from the same logged data, how do LogPlot and WellCAD compare?
Which tools support bore log data exchange workflows using common geotechnical interchange patterns?
What breaks if interval templates and stratigraphic correlation rules are not configured consistently across a borehole library?
How does OpenGround keep core photo attachments tied to specific depth intervals for later review?
How do acQuire GIM Suite and HoleBASE SI support admin control and multi-project governance?
When a team needs API-driven automation and provisioning for bore log environments, which tool fits best?
How do GeoDin, TabLogs, and BoreDM handle structured exports for interval-level reporting without manual reformatting?
Which tools emphasize interval-centric data capture for producing export-ready well logs, and where does their focus differ?
Where does LogChief’s admin control model most directly affect borehole library sharing and consistency?
Tools reviewed
Primary sources checked during evaluation.
Referenced in the comparison table and product reviews above.
How to Choose the Right Bore Log Software
Teams doing bore log documentation usually differ most on how well their uploads and templates maintain a consistent data model from raw field notes to reports. The biggest separations tend to show up in Data import mapping, Report output control, and Audit log coverage for edits over time.
Data import mapping from field formats
Why it matters
Data import mapping matters because bore log software must translate your existing formats into the same depth-linked structure every project expects. When mapping is shallow, teams retype or repair values and the log history becomes unreliable.
How to check
Ask the demo to import one sample dataset from a common field-export style and show how each column maps to lithology intervals and depths. Then verify whether unmapped fields are flagged and whether reruns keep the same interpretation rules.
Depth interval consistency across edits
Why it matters
Depth interval consistency is critical because bore logs are read as continuous geology through depth. If interval edits silently shift, reports can contradict the original field measurements.
How to check
Have them create two adjacent intervals, edit one interval’s top or bottom, and then regenerate a cross-project report. Check whether overlaps/gaps are highlighted and whether version history shows exactly what changed.
Report output control and templates
Why it matters
Report output control affects how consistently bore logs come out in the formats your stakeholders expect. Good template support reduces last-minute formatting and makes outputs repeatable between projects.
How to check
Request a demo of generating at least two report styles from the same bore log record. Confirm you can control key layout items (interval tables, labels, and page elements) and that exports include the same data after template tweaks.
Automation and API for repeat workflows
Why it matters
Automation and API surface matter when you run similar bore log sets repeatedly across sites. Without it, teams spend time clicking instead of validating content, and handoffs between tools break down.
How to check
Ask what automation exists: batch import, scheduled checks, and an API endpoint or file-based workflow. In the demo, run a scripted or repeatable import for two datasets and confirm the same validation rules and outputs are produced.
Audit log and provenance for changes
Why it matters
Audit log and provenance are how teams trust bore log revisions when field data gets corrected. If you can’t see who changed what and when, review meetings turn into guesswork.
How to check
On the same record, perform an edit to interval boundaries and a separate edit to descriptions, then show the audit trail entry details. Confirm you can filter by user and time, and that exports can reference the latest approved state.
Red flags
- Imports succeed on a demo sample but fail to map depths and intervals consistently
- Interval edits allow overlaps or gaps without clear warnings or validation output
- Audit history shows minimal details, making it hard to justify changes in reviews
Fit by situation
- If you already have field-export spreadsheets, prioritize Data import mapping from field formats.
- If your projects go through multiple revision cycles, prioritize Audit log and provenance for changes.
- If you repeatedly generate stakeholder reports from similar bore logs, prioritize Report output control and templates.
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 →
- Review · 2026 · Construction InfrastructureBorehole Log Software
- Review · 2026 · Construction InfrastructureBoring Log Software
- Review · 2026 · Construction InfrastructureBorehole Logging Software
- Review · 2026 · Mining Natural ResourcesDrilling Software
- Review · 2026 · Construction InfrastructureConstruction Daily Log Software
Keep exploring
Comparing two specific tools?
Software Alternatives
See head-to-head software comparisons with feature breakdowns, pricing, and our recommendation for each use case.
Explore software alternatives→In this category
Construction & Infrastructure alternatives
See side-by-side comparisons of construction & infrastructure tools and pick the right one for your stack.
Compare construction & infrastructure tools→