Positions

How we think about JORC

The JORC Code itself warns against the term “JORC compliant”. The warning is one sentence in the guideline to Clause 6. That warning shapes how TableOne Flow is built.

The JORC Code is a Code for Public Reporting not a Code that regulates the manner in which a Competent Person estimates Mineral Resources or Ore Reserves. The term JORC compliant therefore refers to the manner of reporting not to the estimates. Use of the words JORC compliant to describe resources or estimates is potentially misleading.

01 What the Code is saying.

The Code is a Code for Public Reporting. It governs how a resource or reserve is communicated to the market, not how a Competent Person derives the underlying estimate. Calling an estimate “JORC compliant”, the Code says, conflates the two — and the Code calls that conflation potentially misleading.

The implication for software is direct: a drafting tool cannot make an estimate “JORC compliant”, because compliance does not attach to the estimate in the first place. What the tool can do is hold the structure of the Public Report so the Competent Person can sign it, defensibly, against the criteria the Code lists.

02 What TableOne Flow does, in those terms.

TableOne Flow’s output is structured to the JORC 2012 Table 1 criteria. The structure is the product — the criterion grid, the “if not, why not” prompts, the evidence pinned to the criterion it justifies, the audit trail that survives review. Adequacy of any specific criterion response stays with the Competent Person, where the Code places it. We do not apply the phrase the Code itself warns against — not to our tool, not to a Table 1 drafted in it.

The boundary is operational. The completeness check the tool runs — every criterion has a response, every “if not, why not” recorded — is a useful gate before CP review. It is not a compliance verdict. It is not a substitute for the CP’s professional judgement on whether each response is adequate to the underlying estimate.

03 The audit trail is built to survive the question that comes years later.

A Table 1 is a long-lived, regulator-facing record. The interesting question is rarely the one asked on publication day; it is the question asked five years later, when the deposit has been developed, the orebody behaved differently from the resource model, and someone — a successor CP, an auditor, the ASX — is reading the Table 1 to understand what was known and when. The audit trail TableOne Flow holds is built for that read. Every status change is timestamped against the identity that made it; every piece of evidence is fingerprinted at submission.

Whether the record is sufficient for a given audit is a determination for the auditor and the Competent Person. The tool’s job is to make the determination possible.

04 The words a CP signs are the CP’s words.

The product does not put AI between you and the criterion responses a Competent Person signs. You draft every response.

The boundary on customer content is binding. We do not use customer Table 1 content for any AI-adjacent work — not for model evaluation, not for internal QA training sets, not for search-index training, not for tuning the product against your data. By default your Table 1 content stays on your device, and we do not use it to train, evaluate, or tune AI or machine-learning models — as set out in our Privacy Policy. The use we make of AI is on our writing, our tooling, and our tests; never on yours.

05 No body certifies software against the JORC Code.

No regulator, professional body, or industry organisation accredits drafting software in this domain. TableOne Flow is not certified against JORC, ASX, ASIC, SOC 2, ISO 27001, or IRAP. Where we have adopted a specific control — evidence content-hashed at link time, every change attributed to a named identity — we name the control itself, and we do not imply certification we have not earned.

Buyers should read any JORC certified, JORC compliant, or regulator-approved claim from a drafting tool as a marketing claim, not as a verifiable certification. Our posture is to use the language the Code itself uses, and to leave compliance language to the Competent Person and the Public Report.

06 JORC 2026 is planned for the transition period, not claimed today.

JORC 2026 is moving through the formal review, consultation and transition process. TableOne Flow supports JORC 2012 Table 1 work today. Our roadmap is to support JORC 2026 during the transition period once the final Code and ASX settings are known. Existing JORC 2012 records remain tied to the Code version they were drafted under. We do not claim present alignment with a draft or provisional Code.

The discipline above is enforced by specific structural choices in the product. See the product for what that looks like in use, and the solutions pages for the segments these choices were designed around.