TableOne Flow · JORC 2012 Table 1 · Exploration Results · Mineral Resources · Ore Reserves
Your name is on the report.
Your workflow should match.
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.
For the CP who signs it and the drafter who prepares it — whether they work in the same office or exchange a file across firms.
Register interest
You’re on the list. We’ll write with early access timing when the product is ready.
Free to start · cloud sync on Pro
Section 1 — Sampling Techniques and Data, list view. Twelve JORC 2012 criteria, each tracked to completion before the section reaches CP review. Eaglehawk Mine Coal Project. · Sample data. · Tap to enlarge.
Every change attributed. Every criterion answered. Every piece of evidence pinned — before the sign-off.
What changes on your next Table 1
The Table 1 email chain stops here.
Never starting from a blank page. Every criterion is mapped to the Code clause it answers. The “if not, why not” requirement is enforced — sign-off is blocked until every criterion is addressed or documented as not material.
The CP sees a complete document, not a first draft. Review stays in the app — each criterion receives a decision (Endorse, Request change, Blocker, or Ask drafter), with 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 as a structured record independent of the tool that produced it. When that record is read — by a successor CP, an auditor, or the ASX — the drafting history is in the record, not in an email thread.
Your prior reports are at hand. Import your earlier published JORC reports into a reference library and keep them open beside your draft — see how a criterion was approached before, while every response stays specific to the data in front of you.
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. Where a criterion is excluded, the “if not, why not” reason is required before the report reaches the CP — not flagged after.
Evidence pinned to criterion
Supporting documents attach to the criterion they justify, not to the Table 1 as a whole.
Edition-aware architecture
Records drafted under JORC 2012 remain intact when a new Code edition is adopted. The architecture is designed to extend — adding a new edition does not rebuild your existing records.
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. 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.