Solutions

In-house Resource Team

If a Table 1 your team published is queried in two years, the record that answers is whatever each contributor happened to keep. TableOne Flow makes that record the same on every project, from every author, every 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.

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. Each source is linked to the criteria where it was used. The structure is not negotiated project by project — it is consistent by default.

Geological and resource data is market-sensitive. On Solo your project data stays on your device today, and nothing leaves it without a deliberate export, or an opt-in cloud feature you switch on (planned). On Team each report is held once in your TableOne Flow account and opens only to the people added to it — a new report starts out open to the person who created it, and nobody else. A fully local mode is planned for organisations that can’t run a hosted service. Where hosted product data is stored is set out in our Privacy Policy. Nothing processes your content on any tier.

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. In Team the Competent Person reviews the work criterion by criterion, recording a decision for each — Endorse, Request change, Blocker, or Ask drafter.

On Team, name a Competent Person for each section; each signs only the sections they cover. In Business, client workspace separation is 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 Competent Person 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

Team — name a Competent Person for each section; each signs only the sections they cover. A configured set of named drafters and commenters works around them. Right for a small resource team managing one or two projects at a time.

Business — the shared team account, the practice-level portfolio, client workspace separation and the internal-reviewer role are all planned for Business and are not in the build today. Intended for a team running several projects per year across the company.

Enterprise (planned) — for organisations where geological data must remain on your own infrastructure. Self-hosted deployment, onboarding support and contract terms that suit your organisation are all planned.

Getting started

Tell us how many projects your team runs per year, how many people are typically involved, and any procurement, deployment or data-residency requirements. We’ll write back directly.