A drill result, a sampling programme, or a resource estimate is only as useful as the document that conveys it. If a report can't be relied on by the regulator, the QP, the auditor, the financing analyst, or the next consultant who picks up the file, the underlying work is partly wasted, and the cost of redoing it sits with the issuer.
We prepare technical reports and disclosure documents that hold up at each of those checkpoints.
The work is done by geologists who have logged the rocks, sat on the rig, or rebuilt the model. Not by writers working from a brief.
Where we're not the qualified or competent person, we work in support of one, and prepare the documentation so the QP or CP can sign without rework. Where we are the QP or CP, we sign.
Drilling, sampling, assay, survey, and supporting datasets are checked for internal consistency, QA/QC, chain of custody, and provenance. Standards, blanks, duplicates, and umpire labs are reviewed against expected performance. Anything that doesn't reconcile gets resolved before drafting begins. The report is built on a dataset we've verified, not on the issuer's working assumption that the data is clean.
Geological, geochemical, geophysical, and drilling results are translated into the technical narrative. Figures, sections, tables, and text are prepared together rather than retrofitted to the writing. Where modelling supports it, sections and 3D figures are built in Leapfrog or equivalent. Where assumptions are material to the conclusion, they are stated explicitly so the reader can test them.
Documents are drafted to NI 43-101, JORC 2012, PERC, or SAMREC as applicable, including all required disclosures, QA/QC tables, sampling procedure documentation, and material assumption sections. Each section is mapped to the specific clause it satisfies. We work with the QP or CP directly on sign-off requirements, so the document the geologist signs is the document the regulator reads.
The same dataset reads differently for a regulator, a QP, a financing analyst, and a non-technical board member. We write the document the audience actually requires. Technical sections in full technical language. Plain-English summaries where the audience requires them. Visualisation that supports the narrative rather than decorating it.
What You Receive
What You Receive
What You Receive
What You Receive
What You Receive
What You Receive
Technical reporting that's prepared to be reviewed, audited, and signed off. Not just published.
Technical reporting isn't documentation. It's the process of turning complex results into clear, structured, and compliant communication that can stand independent review.
01
Inputs
Geology. Geophysics. Geochemistry. Drilling. Sampling. Modelling.
02
The work in between
Validation. Interpretation. Code alignment. Audience calibration.
03
Outputs
Technical reports. MRE documentation. Press releases. Announcements. Investor materials. Data visualisation.
Three things every output has to be
Compliant
Aligned with the relevant CRIRSCO code and the disclosure jurisdiction.
Clear
Complex data translated into structured, defensible reporting.
Credible
Built so a QP, an auditor, a regulator, and an analyst can rely on it.
