Your words, structured and signed

No one starts from a blank page. Every criterion opens with a structured prompt built from the JORC 2012 Code, with the “if not, why not” requirement enforced by the schema. Completeness signals flag unanswered criteria before they reach the CP — not during the review.

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

The verbatim JORC 2012 Code requirement for each criterion stays open in a rail beside your draft — the standard you are writing to is in view, not in a separate PDF. The Code text is held in the app and read-only; nothing is paraphrased or generated.

The JORC 2012 Code requirement for Sampling techniques, verbatim and read-only in the rail, beside your own words — with the AusIMM / AIG / MCA acknowledgement on the page. The verbatim Code text ships for all five Table 1 sections. · Sample data. · Scroll to see the full width.

Drafting the Sampling techniques criterion — the verbatim JORC 2012 Code requirement open in the left rail, the response in the centre, and Section 1 evidence on the right. · Sample data. · Scroll to see the full width.

Section 1 — Sampling Techniques and Data, list view. Twelve JORC criteria with completeness status tracked per criterion before the section reaches CP review. · Sample data. · Scroll to see the full width.

Competent Person review — in the app, on the record

The CP sees a complete document, not a first draft. By the time the Table 1 reaches CP review, completeness signals have already flagged incomplete criteria and unanswered “if not, why not” requirements. The CP reviews each criterion against its response and marks it Endorse, Request change, Blocker, or Ask drafter. The comment thread is anchored to the criterion — not to a paragraph in a Word document that has moved by the next round.

When a regulator asks how the Table 1 was drafted, the record is in the app — not in an email thread.

CP review — Prof James Lee (J. Lee Consulting) reviewing the QA/QC criterion. A “Request change” decision with a specific comment referencing procedure WGF-GEOL-008 and the CRM insertion rate — anchored to the criterion, not to an email. · Sample data. · Scroll to see the full width.

Evidence pinned to the criterion it justifies

Source documents, spreadsheets, drilling logs, QAQC files, sign-off PDFs — each piece of evidence is attached to the Table 1 criterion it supports. Evidence is content-hashed at link time on all tiers. Pro adds an identity-anchored submission record and full change attribution per criterion. Direct Excel cell and range linking is on the Pro roadmap.

Estimation stays in your existing tools — Excel, Vulcan, Surpac, Minescape. TableOne Flow holds the criterion structure and the evidence pinned to it; estimation tools stay where they are.

Section 1 evidence: each document — QA/QC data, sampling procedures, drillhole collars, the drilling contract — attached to the section it supports, and visible beside the verbatim Code requirement while you draft. · Sample data. · Scroll to see the full width.

Structured export

The Table 1 exports to Word (.docx) and Excel (.xlsx) on every tier including Solo. Criterion order, section boundaries, and “if not, why not” attribution are preserved exactly.

Bring your own template. Export onto the built-in Word template, or your organisation's own — your firm's letterhead, styles, and cover page carry through. You are not forced onto ours.

Pro adds two PDF exports: the Report PDF — the finished Table 1 as the CP signed it, in publication form — and the Audit Record PDF, the compliance-grade trail of review, change history and provenance behind it. TableOne Flow holds the record; your firm assembles and publishes the report — the PDF on the ASX platform is made from that published document.

The Report PDF and the Audit Record PDF — the two Pro exports, both signed off by the Competent Person. Quinn Downs Silver Prospect. · Sample data. · Scroll to see the full width.

These are representative sample documents only — not an actual JORC report or ASX announcement.

The record you produce when you sign it

Your name is on the report for the life of the Public Report, which may outlast the company that published it. Every change is logged against a named identity with a timestamp. Evidence is pinned to the criterion it justifies. When the report is published, you export the Table 1 and the evidence as a structured record independent of the tool that produced it.

The record protects you — so you should know exactly what it captures and who can see it. Every change is attributed and timestamped, but your private review notes stay yours: they are redacted from the file you send back, and never reach the drafter. A Blocker is a hard gate, not a suggestion — a report cannot be signed off while one is unresolved, so “I raised it” is on the record, not buried in an inbox. On Solo, the whole record lives on your device: you hold it, and 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 sign-off itself is on the record. 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 signed by a Competent Person (Clause 10). Clause 9 consent to the form and context of the Public Report itself is a separate act between the CP and the company — see how CP consent works. TableOne Flow does not verify credentials against a registry — it says so plainly, and names the legal weight of the affirmation. The CP review and sign-off workflow is part of Pro.

The CP sign-off — Prof James Lee signs in his own name, above a plain notice that TableOne Flow does not verify credentials. · Pro tier · Sample data.

When the report is signed, you can export the Audit Record — one PDF carrying the cover, every criterion as the CP 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. It is the structured record — independent of the tool that produced it — that the question years later asks for. The Audit Record export is part of Pro.

The exported Audit Record — cover, CP 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. · Pro tier · Sample data.

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

Published report — Quinn Downs Silver Prospect. Observer access: the completed Table 1 is readable by authorised stakeholders without edit rights after the CP signs off, with the sign-off on the record. · Sample data. · Scroll to see the full width.

Register interest →

A reference library of your prior reports

A Table 1 rarely starts from a blank page. Import your prior published JORC reports — in common formats including PDF and Word — into a persistent library, and keep them open beside your draft as a read-only reference. See how a criterion was approached before, while every response stays specific to the data in front of you.

The library does not generate or pre-fill anything. You draft every response; the prior report is there to read, not to copy. It is the difference between hunting for last year’s document in a folder and having it open beside the criterion you are writing.

On Solo, your library is held on your device. Pro will sync it across your devices, private to you (planned). On Business, a shared library lets your whole team draw on the same body of prior reports.

Drafting the Sampling techniques criterion with a prior report open beside it — the drafter’s own Eaglehawk Mine Coal Project annual statement, effective Nov 2025, read-only. The prior report is there to read, not to copy. · Sample data. · Scroll to see the full width.

Multi-CP coordination — Business tier

For consulting practices and in-house teams with several CPs across several projects: assign CPs by Table 1 section, run review rounds, and track a portfolio of reports across stages. Practice-level portfolio view, internal-reviewer QA gate, and admin controls are planned for the Business tier. See Business tier for full detail.

Portfolio view — six projects across pipeline stages, each with its lifecycle stage and lead Competent Person. · Sample data. · Scroll to see the full width.

Tiers

Solo

Windows desktop (online and offline). JORC 2012 Table 1 structure; your data stays on your device. Paid licence, single user. macOS and Linux — after Windows.

Pro

One CP licence, CP-centric. Full CP review workflow; identity-anchored audit trail. Configured supporting roles (drafters, observers). Encrypted cloud sync planned; Australian data residency is our stated objective, with the region confirmed before launch. Offline drafting already works in Solo. Excel cell linking planned.

Business

Multi-CP consultancies and in-house teams running multiple projects. External users (contract authors and clients). Portfolio view and internal-reviewer role planned.

Enterprise

Self-hosted on your own infrastructure. Scoped deployment and onboarding, bespoke SLA and procurement terms. All Business features.

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