Solutions

In-house Resource Team

The Table 1 your team produces goes into a Public Report. The board approved it. The market is relying on it. If it is queried in two years, the record that answers that query is whatever each technical author kept at the time. TableOne Flow makes the record consistent regardless of which project, which contributor, or which reporting cycle.

When the process is the geologist, not the company

Most in-house resource teams have a Table 1 process that lives in one senior geologist’s head. Different deposits, different project stages, and the process adapts accordingly — which means it is different each time. The Exploration Geologist handles sampling and QAQC the way they always have. The Resource Geologist handles estimation. The Mining Engineer handles modifying factors. The Competent Person reviews whatever arrives.

The process is not wrong. The problem is that when a prior estimate is queried by a regulator, an acquirer, or your own board, the record is whatever each contributor kept at the time they drafted it.

The process is the same. The record is complete

Every technical author on the team drafts into the same criterion structure, with the same “if not, why not” prompts. Evidence attaches to the criterion it supports. The structure is not negotiated project by project — it is consistent by default.

Geological and resource data is market-sensitive. On the Solo tier, project data stays on your device — nothing leaves without a deliberate export. For the cloud-hosted tiers (Pro and Business), Australian data residency for product data is our stated objective, with the storage region confirmed in the product terms before any cloud-hosted tier is activated. No AI drafts criterion responses or processes your content on any tier.

In Pro, every change to a criterion is logged against the named person who made it, with a timestamp. The CP reviews the work criterion by criterion, recording a decision for each — Endorse, Request change, Blocker, or Ask drafter.

In Business, multiple CPs per section and client workspace separation are planned. An internal reviewer QA gate (planned) will keep incomplete or inconsistent drafts out of the review queue. A portfolio view across all active projects is also planned: which are in draft, which are in CP review, which are ready to export.

The company’s prior reports, shared

Your team has estimated deposits across years and commodities. That body of work should not live in one geologist’s memory. A shared reference library (planned) will bring your prior published JORC reports into the next project — every geologist can see how the company approached a criterion before, as a read-only reference, with each response still specific to the current data. When a prior estimate is revisited, the earlier approach is visible alongside the project’s own record.

On Business, the reference library is planned to be shared across the team.

Tiers for in-house teams

Pro — one CP licence with a configured set of named drafters. Right for a small resource team managing one or two projects at a time with a single CP. See what’s included in Pro.

Business — multiple CPs, each responsible for their own Table 1 section, with observer roles for subject-matter experts. The shared team account, practice-level portfolio, client workspace separation and internal-reviewer role are planned. Right for a team running several projects per year with more than one CP. See what’s included in Business.

Enterprise (planned) — for organisations where geological data must remain on your own infrastructure: self-hosted deployment, scoped IT onboarding and bespoke procurement terms are planned. Contact us to discuss. See Enterprise.

Getting started

Register interest — tell us how many projects your team runs per year and how many people are typically involved. We’ll write back directly.