Solutions

Competent Person & Drafter Team

The JORC 2012 Table 1 arrives in your inbox as a Word document. You send comments. A revised version comes back. By the time you’re reviewing the final draft, you’re not reviewing a record — you’re reconciling one. TableOne Flow makes the Competent Person’s review the final step in a structured process, not a reconstruction of one.

What the Competent Person actually needs at sign-off

The Exploration Geologist drafted sampling and QAQC. The Resource Geologist drafted geological interpretation and estimation. The Mining Engineer drafted modifying factors. By the time those drafts reach the Competent Person, they’ve usually been through two or three email rounds and the evidence is somewhere in a shared drive that not everyone can navigate.

The problem is not the team. The problem is that Word documents cannot show the Competent Person who wrote which criterion, what evidence was attached when, or what changed between the version they saw last week and the one in their inbox today.

Each criterion has a history. The Competent Person can read it

Evidence links to the JORC section it supports as the draft is built. Incomplete criteria are flagged before the draft reaches the Competent Person — gaps are a drafting problem, not a review problem.

On Solo your project data stays on your device today; on Team and above, reports are held in your TableOne Flow account today, with a fully local mode planned. The Competent Person signs what the team wrote.

The report’s history — status changes, evidence and export events, each recorded against a name and a timestamp — exports as NDJSON or CSV with a SHA-256 fingerprint on every tier. Team adds the Competent Person’s review rounds and sign-off to that history, and the in-app change history: when a drafter updates a criterion, the change is logged against their identity with a timestamp.

In Team, the Competent Person works through the Table 1 criterion by criterion, recording a decision for each — Endorse, Request change, Blocker, or Ask drafter — with a structured comment returned to the drafter.

At sign-off, the Competent Person has reviewed the record, not just the output.

Prior work, in front of the drafter

When a drafter returns to a criterion they last addressed on a different project, the on-device reference library brings the prior published report forward — open while they draft, as a read-only reference. The drafter sees how the criterion was approached before, keeping the team’s approach consistent, while every response stays specific to the current data.

On Team, the Competent Person’s reference library is planned to sync across their devices, private to them. A library shared across the whole team is part of Business.

Tiers for Competent Person and drafter teams

Team — one Competent Person signing in the app, with a configured set of named drafters and the full Competent Person review workflow. Right for a Competent Person working with a small team.

Business — naming a Competent Person per Table 1 section, the shared team account, the practice-level portfolio, client workspace separation and the internal-reviewer QA gate are all planned for Business and are not in the build today. Intended for larger teams or practices managing several projects at once.

Getting started

Tell us how many drafters typically work on a report and how your current review process works. We’ll write back directly.