Sign inRequest pilot access
Menu

Core logging and sample traceability

From drillhole to assay. One traceable record.

A hole, a depth and a sample number are entered once at the rig. CoreChain carries them through logging, sampling, custody, the laboratory and QA/QC, so nobody re-types them at the next hand-off.

Request pilot accessSee a sample project

Read-only, built on Alberta Geological Survey open data.

In development testing. Not yet released.

CDL-001

Cordillera porphyry sample (synthetic) · 302.5 m final

Logged
Core logged
302.5 m13 intervals
Core runs
10194.3% recovery
Core boxes
101recorded
Samples
7QC included

The same record on the web. Nothing re-typed.

CoreChain Field on an Android phone: drillhole CDL-001, 302.5 of 302.5 m logged, with its hole log of lithology, alteration and mineralisation.
Phone: CoreChain Field, Cordillera demo project. Web: the same hole on the team workspace, simplified.

Enter it once. Carry it forward.

Each step is recorded where the work happens and keeps what came before it. The laboratory result still knows its sample, depth and hole.

  1. 01

    Drill

    Hole, core boxes and runs, with recovery and RQD.

    • Hole ID
  2. 02

    Log

    Depth intervals with the project's own code lists, and photos.

    • Hole ID
    • Depth
  3. 03

    Sample

    Numbers from the phone's own block or a tag book. QC inserted at the project's rate.

    • Hole ID
    • Depth
    • Sample no.
  4. 04

    Custody and dispatch

    Every hand-over recorded and never edited, then dispatched to the laboratory.

    • Sample no.
    • Dispatch
  5. 05

    Laboratory

    Receives the batch, assays it and uploads the results against it.

    • Sample no.
    • Result
  6. 06

    Lab QA/QC

    Standards, blanks and duplicates judged against the results.

    • Result
    • Decision

Reviewers for core and logging, and for sampling and custody, check steps 01 to 04 as they happen, not only at the end.

One workflow, different people.

A team is the people around one drill rig. Each person works on the part that is theirs.

Android app

Field Geologist

Logs core, photographs it, takes samples and hands them over, at the rig or the core yard, with or without signal.

Web

QA/QC

The Senior Geologist reviews logging, the Core Shed Supervisor sampling and custody, and the Database Geologist laboratory results.

Web

Laboratory Supervisor

Receives dispatched samples by scan, then uploads the results file for the batch.

Web

Project Manager

Follows the team's holes, samples and activity, and keeps the code lists, standards and tags.

CoreChain Field · Android

Field logging that gives something back.

CoreChain Field is built for a geologist working alone, in sun and gloves. Every screen that takes an entry shows something back.

Graphic hole log of CDL-001: lithology, alteration, mineralisation, recovery and RQD columns by depth.

Graphic log

The hole as it is logged: rock, alteration, minerals, recovery and RQD against depth.

Collar map of six drillholes on terrain contours, with each hole's planned direction.

Collar map

The project's holes on terrain, with their planned direction, and where you are standing.

My work: 1446.2 m of core logged in the last seven days, with samples and custody steps.

My work

What was logged, sampled and handed over, by day, from what is on the phone.

Two drillholes in the project list; CDL-001 is marked Waiting to send.

Keep working when the signal drops.

Everything is saved on the phone first, in an encrypted database. Records wait, marked as waiting to send, and go up when there is signal again. Conflicting changes are shown for a choice, never silently overwritten.

Built for gloves and glare

Large targets, light and dark themes, and known depths offered as one tap, so a depth already entered is never typed twice.

Sample numbers never repeat

Each phone draws from its own block, or the geologist types the tag. A number is never issued twice or reused, even after a delete.

Traceability

Every sample has a story.

Open any sample on the web and its whole record is there, joined up from the phone and the laboratory. Here is one from the laboratory demo project.

When the hole has been logged, the geology at that depth and the core photos are shown with the sample too. QA/QC decisions are kept on the reviewer's page.

LQC-00005

QC-DDH-01 · 12.0–13.5 m · Field duplicate

  1. Hole and depthQC-DDH-01, 12.0–13.5 m
  2. QC linkField duplicate of LQC-00001, split from the same interval
  3. BaggedBy Maria Santos, field geologist
  4. Dispatched to labIn dispatch DSP-QC-01
  5. Received by laboratoryBy Ramon Cruz, checked in by scan
  6. ResultCu 1190 ppm · Zn 301 ppm, from the re-assay
The sample page, simplified. Names and values from the laboratory demo project.

Custody and laboratory

The chain does not stop when the sample leaves the field.

The laboratory checks the batch in by scan, then uploads its results file. Problem rows are shown before anything is accepted.

  1. Samples are received by scan against the dispatch sheet. Anything missing is flagged.
  2. The results file is uploaded and its columns chosen: there is no single lab-certificate format.
  3. Rows that do not match a received sample, or have no value, are listed and left out.
  4. A re-assay is uploaded the same way. The latest result for each sample and element becomes the current one.
First results file2 problem rows

DSP-QC-01-results-first-run.csv

7 results across 7 samples ready to import.

  • Row 7, sample "LQC-0006": not a received sample on this dispatch
  • Row 8, sample "LQC-00007": no result value in any selected column
Re-assayNo problems

DSP-QC-01-results-reassay.csv

9 results across 9 samples ready to import.

The laboratory's upload, simplified. Copper column selected. Values from the laboratory demo project.

QA/QC

QA/QC happens at more than one hand-off.

Each reviewer owns one stage of the chain. CoreChain lays out the evidence; the reviewer decides to accept, hold or reject, with a note.

  1. Stage 1

    Core and logging

    Gaps and overlaps between runs, recovery over 100%, and runs past the hole's final depth, while the hole is being worked.

  2. Stage 2

    Sampling and custody

    QC inserted below the project's rate, overlapping samples, and custody that has stalled, before the results come back.

  3. Stage 3

    Laboratory assays

    Standards, blanks and duplicates judged against the returned results.

QC-DDH-01

Laboratory QA/QC sample (synthetic) · first results file

3 open

Open exceptions

  • Standard OREAS 45e failed for Cu: LQC-00004LQC-00004: Cu 612 ppm, certified 742 ppm ± 20 (-6.5 SD). Outside the 3 SD limit of 682 to 802 ppm.
  • Blank failed for Cu: LQC-00003LQC-00003: Cu 85 ppm, limit 10 ppm (Blank). Possible contamination during preparation; check the samples prepared just before it.
  • Duplicate failed for Cu: LQC-00005 against LQC-00001LQC-00001 1240 ppm, duplicate LQC-00005 610 ppm: 68% apart, limit 30% for field duplicates. Check the splitting, or a nugget effect in this interval.
The QA/QC review page, simplified. Values from the laboratory demo project, before and after its re-assay.

Standard

Warning beyond 2 SD. Fails beyond 3 SD, or on a second reading in a row beyond 2 SD on the same side.

First file
Failed612 ppm · -6.5 SD
Re-assay
Passed749 ppm · +0.3 SD

Blank

Fails above the team's limit for that element.

First file
Failed85 ppm · limit 10
Re-assay
Passedbelow 2 ppm

Duplicate

Fails when the pair is more than 30% apart.

First file
Failed68% apart
Re-assay
Passed3% apart

Missing results are flagged once the laboratory marks a batch complete, and results in the wrong unit are flagged too.

Records you can stand behind

Built around the records a report has to stand on.

CoreChain is structured around the records the Philippine Mineral Reporting Code (PMRC 2020) asks a company to be able to demonstrate: recovery, logging, sampling, QA/QC and chain of custody. It supports that work; it does not replace the judgement of your Accredited Competent Person.

No silent overwrite

When two people change the same record, the conflict is shown for a choice instead of one quietly replacing the other.

Custody is never edited

A mistake in a hand-over is corrected with a new step. The original stays on the record.

Every record has an author

Each entry keeps who made it and when, and edits are versioned.

Field work survives poor signal

Records are kept on the phone until the server has them.

Where the product stands.

CoreChain is in development testing and has not been released yet. This is what works in testing today.

StageCapabilityStatus
Field captureHoles, boxes, runs, logging, photographs, samples and QC, export to CSVWorking in development testing
Accounts and backupSign-in, encrypted storage, and cloud backup and sync of records and photosWorking in development testing
Custody and dispatchRecorded hand-overs, dispatch batches, and PDF or CSV dispatch sheetsWorking in development testing
QA/QC reviewThree review stages: core and logging, sampling and custody, laboratory assaysWorking in development testing
LaboratoryReceive dispatched samples, upload results, and flag problem rows before they are acceptedWorking in development testing
Manager dashboardThe team's holes, samples and activity, code lists, standards and tagsWorking in development testing

See a read-only sample project built on official open data from the Alberta Geological Survey.

Bring CoreChain into the field.

Accounts are set up by us; there is no public sign-up. Tell us which of these fits, and we will reply.

Test CoreChain Field

Try the field app on your own time with made-up data and tell us what gets in the way. Geologists, mining people and software people are all welcome. A few geologists have already signed up.

Android phones only. We set up your account and send you the install link.

Discuss a pilot

For an exploration or mining team that wants to see whether the workflow fits a real drilling programme.

We start with a conversation about your holes, your lab and how samples move today.

Request access

I want to

Your exploration record starts at the drillhole.

Keep it connected all the way to the assay.

Request pilot accessSee a sample project