QA/QC Showcase
Domain, completeness and cross-dataset findings in one comprehensive example.
Released — Available NowAutomated Borehole Data Quality
Find Data-Quality Issues Before Logs Are Issued
WinLoG Validation & QA/QC applies domain-specific and cross-dataset rules to borehole and well information, then documents the results in a detailed validation report.
Use errors, warnings, completeness, quality and confidence indicators to focus professional review on the fields and depth intervals that require attention.
Available NowReleased WinLoG capability
Depth-Linked FindingsFields and intervals identified
Cross-Dataset RulesRelated evidence compared
Detailed ReportsReview results documented
Validation Workflow
From Structured Data to Reviewable Findings
WinLoG keeps the validation result connected to the underlying borehole record and the rule that produced it.
1
Read Context
Identify the template, application, datasets, fields and depth intervals present in the log.
2
Apply Rules
Run only the checks whose data and applicability conditions are satisfied.
3
Create Findings
Record severity, rule, affected dataset, field, actual value and depth context.
4
Summarize Quality
Calculate validation status, completeness, quality and confidence indicators.
5
Review and Report
Correct invalid data, assess warnings and retain the validation report with the deliverable.
Rule Coverage
Checks Designed for Subsurface Data
Validation evaluates individual values and the relationships between lithology, samples, laboratory results, groundwater, construction and application-specific datasets.
Domain and Range
Detect invalid values, impossible relationships and measurements outside configured limits.
Completeness
Identify expected identifiers, descriptions, results and supporting fields that are missing.
Cross-Dataset Consistency
Compare related evidence such as lithology, recovery, samples, laboratory results and groundwater.
Environmental and Laboratory QC
Check sample identity, field screening, laboratory relationships, qualifiers and applicable criteria.
Groundwater and Well Construction
Evaluate water levels, monitoring data, component depths and sampling relationships.
Application-Specific Rules
Use relevant checks for geotechnical, transportation, mining, environmental, groundwater and oil-and-gas logs.
Finding Severity
Errors, Warnings and Information Have Different Meanings
Severity helps the reviewer prioritize the result; it does not determine the engineering interpretation by itself.
Error
Invalid or Materially Incomplete
A required relationship has failed or essential data is invalid. Correct the data or document why the rule does not apply before issue.
Warning
Professional Review Required
The condition may be valid, but it is unusual, incomplete or inconsistent enough to require review and possible explanation.
Information
Context or Advisory Notice
The finding provides context, confirms an observed condition or identifies an item that may improve the record.
A warning is not automatically an error. Review the source data, field context, rule applicability and supporting evidence before correcting or accepting the condition.
Quality Indicators
Four Different Views of the Validation Result
The indicators answer different questions and should be interpreted together.
Validation Status
Summarizes whether the run passed, contains warnings or contains errors.
Completeness
Measures the presence of expected data for the applicable template and datasets.
Quality
Classifies the overall condition of the data using the validation findings and available evidence.
Confidence
Expresses how strongly the available and internally consistent evidence supports the assessment.
What the Validation Report Documents
- Borehole and project identification
- Validation date and result summary
- Errors, warnings and informational findings
- Rule identifiers, descriptions and severity
- Affected dataset and field
- Depth from and depth to
- Expected condition and actual value
- Completeness, quality and confidence
- Information needed for correction or review
Rule Applicability Matters
A rule should run only when its required dataset, field, template context and application conditions are present. This prevents unrelated checks from being applied to the wrong type of log.
- Template and application context
- Required source dataset exists
- Required measurement was explicitly recorded
- Depth relationship is relevant
- Comparison evidence is compatible
- Default or placeholder values are not mistaken for observations
Reviewer responsibility: if a finding is not applicable, confirm the rule context and source data rather than changing technically correct information merely to clear a warning.
Supported Applications
Validation Across Multiple Borehole and Well Workflows
Rule coverage is selected according to the log’s application, template and available datasets.
Geotechnical and Transportation
Lithology, USCS, SPT, recovery, RQD, water content, Atterberg limits, density, strength, CBR and pavement-related data.
Environmental
Sample identification, field screening, odour and staining, laboratory results, qualifiers and criteria relationships.
Groundwater and Wells
Water levels, component depths, screens, seals, sampling information, field parameters and laboratory results.
Rock Core and Mining
Core runs, recovery, RQD, SCR, TCR, rock descriptions, mineralization, samples and assay information.
Oil and Gas
Formation tops, drilling curves, hydrocarbon shows, staining, lithology and cross-dataset formation relationships.
Specialized Logs
Rules can evaluate relevant data in water-supply, geophysical, vapour, landfill-gas, recovery-well and sediment-core workflows.
Validation in Practice
Review Application-Specific Examples
Each example combines a professional log, underlying data and a validation report showing how findings relate to the project context.
Common Questions
Validation & QA/QC Questions
Is validation available now?
Yes. Standard WinLoG Validation & QA/QC has been released and is available now.
Does validation replace professional judgment?
No. It identifies conditions requiring correction or review. Qualified professionals remain responsible for interpretation and acceptance.
Is every warning a defect?
No. A warning can identify an unusual but valid condition. Review applicability and supporting evidence before deciding whether a correction is required.
Can existing logs be validated?
Existing structured WinLoG records can be evaluated when the applicable data, fields and template context are available.
Can findings be documented?
Yes. The validation report records the rule, severity, dataset, field, depth context, expected condition and actual value.
Are governance workflows included?
Governed QA/QC is a planned future capability and is not currently available. The features described on this page apply only to the released WinLoG Validation & QA/QC functionality.
Technical Guidance
Continue with Validation Resources
Use detailed examples and Knowledge Center articles to understand specific rules and QA/QC practices.
Automated QA/QC Rules
Learn how borehole rules identify missing, invalid and inconsistent data.
Read the rule guideSPT and N-Value QA/QC
Review common SPT consistency, completeness and cross-dataset checks.
Read the SPT guideRecovery and RQD
Understand recovery, RQD, SCR and TCR relationships used in core validation.
Read the core guideEvaluate WinLoG Validation with Representative Data
Use the demonstration and validation examples to compare rule coverage, findings and reports with your borehole and well workflows.
GAEA Technologies develops and distributes geoscience and engineering solutions worldwide. Our solutions have been used for over 30 years by companies and organizations around the world.
© 2026 GAEA Technologies. All Rights Reserved.