Skip to main content
TableOne Flow

From first draft to signed Table 1 — one record, one place

TableOne Flow is a JORC 2012 Table 1 drafting tool for the geologists and Competent Persons who write and sign the documentation behind Exploration Results, Mineral Resource and Ore Reserve reporting.

It holds the Table 1 from first draft through Competent Person sign-off to the document your ASX announcement is built from. The report’s history is recorded against a name and a timestamp: status changes, evidence and export events.

At launch, Solo drafts the whole Table 1:

  • every criterion with the verbatim Code
  • “if not, why not” tracked criterion by criterion
  • evidence attached
  • the machine-readable change log
  • export to Word and Excel

A Competent Person can draft here and sign the way they sign today. The review workflow, the in-app sign-off, the Report PDF and the Audit Record are Team.

This page describes the product across all four tiers.

Live demo → (opens in a new tab) Register interest →

Explore the live app on a sample JORC 2012 Table 1 — no install; give a work email and we’ll send you a one-time link.

The document you hand on

The Table 1 as a Word document — the working file your company’s ASX announcement is built from, each criterion a heading with your commentary beneath. · Sample data.

You never start from a blank page

Every criterion opens with the verbatim JORC 2012 Code requirement, read-only in the reference panel below your draft. Nothing is paraphrased or generated.

“If not, why not” tracked criterion by criterion. See at a glance which are addressed, which are documented as not relevant or not material, and which are still neither.

Bring a Table 1 you have already started. New report seeds the draft from a part-finished Word or Excel file. Your words arrive as responses, never as a status, so every criterion still has to be marked by a person. On every plan, Solo included.

Only the sections your report needs. Exploration Results covers Sections 1 and 2; a Mineral Resource adds Section 3; an Ore Reserve adds Section 4. Criteria that do not apply are not shown at all.

You draft every criterion response. The Competent Person signs what they wrote, or what was written under their direction.

Your Table 1 content is not used for model training, evaluation, or any AI-adjacent work. Not for internal QA. Not for tuning the product against your data. This is a design constraint in the product, not a policy paragraph.

When the Code asks for a Table 1. Where Clauses 19, 27 and 35 apply — Exploration Results, Mineral Resources or Ore Reserves reported for the first time or materially changed — appended to the Public Report on an “if not, why not” basis.

Diamonds and gemstones add Section 5. Set the commodity when you create the report and the section set follows. Section 5 arrives whole — the Code does not scope it by report type — so its estimation and valuation criteria are yours to document “if not, why not”. The Code’s pointer to the Diamond Exploration Best Practices Committee guidelines is not reproduced here.

Swipe the workspace sideways to see its full width.

The Code requirement for Sampling techniques, verbatim and read-only in the reference panel below your own words — with the AusIMM / AIG / MCA acknowledgement on the page. The Code text ships for all five Table 1 sections; this sample reports Exploration Results. · Sample data.

Hand it over without the email chain

The Competent Person opens one file and sees what is outstanding — not a Word attachment and a chain of replies.

The gaps show up first. Unanswered criteria and missing “if not, why not” rationales arrive already flagged. The signals inform — they do not gate, and nothing stops an incomplete draft being sent.

A decision on every criterion. Endorse, Request change, Blocker, or Ask drafter — with the comment thread anchored to the criterion, not to a paragraph in a Word document that has moved by the next round.

One file, with a fingerprint. The Table 1, the evidence links and the report’s history travel as a single .t1f, carrying a content fingerprint so a file altered in transit shows up.

Solo drafts, Team reviews. Solo hands off the file; the Competent Person opens it and runs the review and sign-off on Team. Asked years later how the Table 1 was drafted, you have the history in the file, against a name and a timestamp.

Marguerite Ashcombe (Tarranby Geological Consulting) reviewing the QA/QC criterion — a “Request change” decision citing procedure WGF-GEOL-008 and the CRM insertion rate, anchored to the criterion rather than to an email. · Team tier · Sample data. · Scroll to see the full width.

Your working files stay attached to the report

Source documents, spreadsheets, drill logs, QA/QC files and sign-off PDFs link to the JORC section they support — not to a folder someone reorganised two reports ago.

Files are fingerprinted when you link them. Content-hashed at link time, on every tier, so a later change to the source file is detectable. Links, statements and folder references carry a recorded reference or a folder manifest instead, and the rail shows which is which.

Estimation stays where it is. acQuire, Excel, Leapfrog, Micromine, MineScape, Studio RM, Supervisor, Surpac, Vulcan. TableOne Flow is the drafting layer above them, and the files those tools produce link to the JORC section they support. Direct Excel cell and range linking is on the Team roadmap.

Team adds an identity-anchored submission record, and full change attribution per criterion.

Section 1 evidence — QA/QC data, sampling procedures, drillhole collars, the drilling contract — attached to the section it supports, and on screen beside your draft while the Code requirement sits in the reference panel below it. · Sample data. · Scroll to see the full width.

The files you hand on

Everything you draft leaves in a form you can open without us, and without a login, years from now.

Word and Excel, on every tier including Solo. The Table 1 as .docx and .xlsx, with criterion order, section boundaries and “if not, why not” attribution preserved exactly.

Bring your own template. Export onto the built-in Word template, or — on Team and above — your organisation's own, so your firm's letterhead, styles and cover page carry through.

Two PDFs on Team. The Report PDF — the finished Table 1 as the Competent Person signed it, in publication form — and the Audit Record PDF, the trail of review, change history and provenance behind it.

TableOne Flow holds the record; your firm assembles and publishes the report.

The Report PDF — the same Section 1 criteria you saw as a Word file above, in publication form, as the appendix to the announcement rather than the announcement itself. Signed off by the Competent Person. Quinn Downs Silver Prospect. · Sample data — a representative document, not an actual JORC report or ASX announcement.

Answer “how was this drafted?” years later

Your name is on the report for the life of the Public Report, which may outlast the company that published it. You export the Table 1 as a structured record independent of the tool that produced it, with the evidence and its fingerprints recorded alongside it.

What the record captures

Every change against a name and a timestamp. The report’s history is logged against a named identity as you work, and evidence stays linked to the JORC section it justifies.

A Blocker stays on the record. The strongest decision you can record: it holds on the criterion until it is resolved, so “I raised it, on this date” is on the record rather than buried in an inbox. It is a signal to the people running the report, not a lock on the sign-off button.

On Solo, it lives on your device. Nothing is synced to our servers unless you opt in to a cloud feature. The Audit Record is the artefact you choose to produce and hand over — the working history stays with you until then.

The change log exports on every tier, Solo included. As NDJSON or CSV with a SHA-256 fingerprint. Team adds the Competent Person’s review rounds and sign-off to that history, and the change history in the app.

The sign-off, and the record you hand over

On Team, the Competent Person signs the completed Table 1 in their own name — the documentation a Public Report is based on, which the Code requires to be prepared by, or under the direction of, and signed by, a Competent Person (Clause 10). Clause 9 consent to the form and context of the Public Report is a separate act between the Competent Person and the company — see how Competent Person consent works. TableOne Flow does not verify credentials against a registry.

What it refuses to sign.

  • A criterion left unaddressed, or an “if not, why not” exclusion with no rationale (Clause 19, 27 or 35, according to what is being reported).
  • Exploration Targets with no cautionary statement, or whose tonnage or grade is a single figure rather than a range (Clause 17).
  • A Competent Person whose recorded relevant experience is under five years (Clause 11).
  • Anyone but the named Competent Person signing their own sections.

It does not judge whether your answer is adequate — that is yours, and it stays yours.

We do not claim compliance, and the Code says why. The guideline to Clause 6: it “is a Code for Public Reporting not a Code that regulates the manner in which a Competent Person estimates Mineral Resources or Ore Reserves”, and it warns that describing resources or estimates as compliant with the Code is “potentially misleading” — JORC Code, 2012 Edition, © JORC (AusIMM, AIG, MCA). We describe TableOne Flow’s output as structured to JORC 2012 Table 1 criteria. See our positions.

On Team, signing lets you export the Audit Record: one PDF carrying the cover, every criterion as the Competent Person signed it, the evidence, whether AI was used in drafting (it was not), and a build-and-schema fingerprint, with a SHA-256 sidecar to detect any later change. That is the record the question years later asks for.

The exported Audit Record — cover, Competent Person sign-off, the no-AI disclosure, and the provenance fingerprint, with a SHA-256 sidecar to verify it is unaltered. Sample reports carry the “demonstration” watermark. · Team tier · Sample data.

Later, on Team, authorised stakeholders read the published Table 1 without edit rights — the Competent Person sign-off on the record beside it.

Your prior reports, open while you draft

Import your prior published JORC reports — PDF or Word — alongside your work instructions and other reference material, and keep any of it open while you write.

Three tabs, one search. Find anything in the library by name, by criterion, or by matching text inside the document itself — plain full-text matching, not a ranked or AI-assisted search.

Nothing is copied in. Prior reports are there for precedent, work instructions for procedure — you draft every response yourself. Nothing in the library is presented as citable; that decision is made on the criterion itself.

Point it at a folder. On Solo and above, the library scans a folder on your device for new or changed files each time you open the tab — a convenience for pulling material in, never an automatic link into your Table 1.

A part-finished Table 1 is a different path. That one is New report, above.

Your library open in the reference panel below the draft, read-only — showing the drafter’s own earlier answer to this criterion, from their announcement on the same prospect published Nov 2025, with the verbatim Code beside it. · Sample data. · Scroll to see the full width.

Where this sits

Everything on this page is in Solo except where marked. The Competent Person review workflow, the in-app sign-off, the Report PDF and the Audit Record are Team. Naming a Competent Person per Table 1 section, multiple client projects on one account, external users, the shared reference library, the practice portfolio and the internal-reviewer gate are planned for the Business tier and are not in the build today.

Pricing for all tiers is announced at launch; Solo launches first, with a small pilot group.

Compare all tiers → · Find your situation → · Download for Windows → · Cost your current process →