TableOne Flow · JORC 2012 Table 1 · structured drafting
Your name is on the report.
Your workflow should match.
For the CP who signs it. For the geologist who drafts it. Free for both — pass the project file between you, no subscription on either side. One Pro account on the CP’s side adds the CP review trail when you need it. Free is a Windows desktop app; Pro and above also work offline and sync to the cloud.
TableOne Flow holds your Table 1 from first draft through Competent Person sign-off — structured to JORC 2012, evidence pinned to the criterion it justifies, every change recorded against the person who made it. Your words. Your record. Signed.
Early access
You’re on the list. We’ll write with early access timing when the product is ready.
More to share? Tell us about your setup →
TableOne Flow workspace — criterion editing with attached evidence files. Eaglehawk Mine Coal Project, Sampling techniques criterion. · Tap to enlarge.
The Competent Person signs what the Competent Person wrote.
What changes on your next Table 1
The part of the Table 1 cycle where evidence, comments, and “which version are we on” become an email thread — does not.
Never starting from a blank page. Every criterion has a structured prompt built from the Code, with the “if not, why not” requirement enforced. Quality signals flag gaps before the criterion reaches review — not during it.
The CP sees a complete document, not a first draft. Review stays in the app — each criterion marked Accepted or Needs revision, comments anchored to the criterion, not to a paragraph in a Word document that has moved.
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. If that report is queried and the drafting record is an email thread and a folder, the exposure is yours.
Built for the sole CP today. Designed for the full Table 1 team — same office, distributed teams, or different firms — when you need it.
Completeness is checked in the tool. Adequacy stays with the Competent Person. See how we think about JORC for the boundary that governs every decision in the product.
Product integrity
Structured to JORC 2012
Every criterion is mapped to the Code clause it answers. No free-text fields that fall outside the Table 1 structure.
Evidence pinned to criterion
Supporting documents attach to the criterion they justify, not to the Table 1 as a whole.
Edition-aware architecture
The JORC Code is updated periodically. TableOne Flow is designed to add new editions as they are ratified — records drafted under JORC 2012 remain intact. JORC 2026 support is a planned addition; the architecture is designed so that adding a new edition does not disturb existing records. Start structured now on JORC 2012 — when 2026 arrives, the transition will be incremental, not a rebuild.
Every change attributed
Edits are recorded against the identity of the person who made them, with a timestamp.
Register interest
Tell us about your setup and we’ll reply directly — usually within a week. Early access invitations go to registrants first; we’ll share pricing when it’s set.
See Pricing and tiers. · Privacy policy.
You’re on the list. We’ll write with early access timing when the product is ready.