Solutions

Consulting Practice

You deliver a Word document. The client files it and calls it the record. Three years later, if they need to demonstrate the evidentiary basis for that estimate, the Word document is what they have. TableOne Flow lets you deliver a Table 1 with the evidence attached to every criterion that relied on it.

The same process, every project

Consulting practices that run several concurrent Table 1 engagements usually run them differently — the process depends on who is leading the project and what template they prefer. Evidence ends up in a shared drive. The client gets a finished document and a folder of files. How those two things relate to each other is not obvious to anyone who wasn’t in the room.

One standard. Every client. Every project

Set the firm’s criterion structure once. The “if not, why not” prompts are consistent across every engagement. Each client project is kept in its own workspace (multi-client team workspaces are planned in Business); evidence attaches to the criterion it supports on that project. When the engagement is complete, the Table 1 and attached evidence export together as a single package the client can hold.

Client workspace separation is planned in Business: each client engagement in its own workspace, designed so one client’s project cannot be seen from another’s. On the Solo tier, project data stays on the device where it was drafted. For the cloud-hosted tiers, 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.

The Business tier is planned to give the practice lead a portfolio view across all active engagements — which projects are in draft, which are in CP review, which have been exported. No chasing for status updates.

The internal reviewer gate (planned)

In Business, a named internal reviewer will be able to check each project before it reaches the Competent Person. The reviewer works through the Table 1 criterion by criterion — flagging gaps, requesting evidence, or clearing sections — before the CP receives the review queue. This workflow is planned and not yet available.

Once available, the CP would receive a complete draft, not a first pass. It removes the rework cycle where the CP returns a draft for structural fixes that a senior reviewer should have caught. It also creates an internal QA record: who reviewed what, when, and what they flagged.

Contract and external CPs (planned)

Many consulting practices work with contract Competent Persons who are not on staff. The Business tier is designed to let a contract CP join a specific project without a paid TableOne Flow account of their own — receiving a review invitation, working through the criterion-by-criterion queue, with their decisions recorded against their identity. When the engagement ends, the project record — including the CP’s review record — stays in your system. This workflow is planned and not yet available.

When a CP leaves

If a CP leaves your practice, every Table 1 they worked on — the criterion responses, the attached evidence, and the review record — remains in your system, attributed to them. The institutional knowledge of that project does not leave with the person. A successor CP or a client coming back three years later can see exactly what was reviewed, by whom, and on what basis.

Your client deliverable is not a Word document that lives on someone’s laptop. It is a structured export tied to a complete project record that your firm holds.

The practice’s prior reports, shared

Your firm has drafted many Table 1s. That body of work usually lives across project folders and in senior geologists’ heads. A shared reference library (planned) will bring your prior published JORC reports into every new engagement: each drafter can see how the practice approached sampling techniques, geological interpretation, or modifying factors — as a read-only reference, with every response still drafted to the current data.

On Business, the reference library is planned to be shared across the team — the practice’s prior published work, available to everyone who drafts — while client project data is designed to stay in its own client workspace.

Tiers for consulting practices

Business — multiple CPs, each taking responsibility for their own Table 1 section. The shared practice account, client workspace separation, internal-reviewer role and practice-level portfolio are planned. Right for practices managing several concurrent client projects with more than one CP. See what’s included in Business.

Enterprise (planned) — for practices where client data must remain on your own infrastructure. Self-hosted deployment, scoped IT onboarding, and bespoke procurement terms are planned. See Enterprise or contact us to discuss.

Getting started

Register interest — tell us how many active client engagements you run at once and whether you have data residency requirements. We’ll write back directly.