Solutions

Contract Competent Person

Your sign-off travels with the report long after the engagement ends and long after the client has filed the document. The record that defends that sign-off is whatever you kept at the time. TableOne Flow is built for the Competent Person who needs that record to be complete, structured, and theirs to keep.

The engagement ends. The sign-off doesn’t

The junior company you signed for two years ago has been acquired. The new technical team is reviewing prior estimates. They contact you — not the company — because your name is on the report.

The Word document is somewhere on their server. The supporting data is in an email thread that predates the acquisition. You have a PDF and a memory of what you relied on.

That is the exposure that contract Competent Persons carry and that most drafting tools do nothing about.

Your record, independent of the client

Each client engagement is a separate project in TableOne Flow. Evidence links to the JORC section it supports. 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. The drafting record is yours — not the client’s shared drive, not an email thread, not a folder of files whose relationship to the Table 1 is not obvious.

On Solo your project data stays on your device today, and always can; on Team and above, reports are held in your TableOne Flow account today, with a fully local mode planned. Either way nothing leaves unless you export it, or opt in to the planned encrypted cloud backup or sync. Each client’s project sits in its own project file, isolated from every other.

When the engagement is complete, the Table 1 exports as a structured record independent of the tool that produced it, with the evidence and its fingerprints recorded alongside it. You retain your own copy of the complete project record, independent of what the client does with theirs.

When the question comes back years later, the record is there.

Your prior engagements, at hand

Across engagements in the same commodity or region, you have addressed many of these criteria before. A reference library keeps your prior published JORC reports open while you draft, so you can see how you approached a criterion last time — while every response stays specific to this engagement’s data. Each client project remains its own isolated record; the reference library is yours.

On Team, your library is planned to sync across your devices and, by default, to be readable only by you, so your own body of work travels with you from engagement to engagement.

Tiers for contract Competent Persons

Team — one Competent Person signing in the app, with per-project isolation. Right for a contract Competent Person running one or two client engagements at a time.

Business — for several concurrent client engagements. Naming a Competent Person per Table 1 section, client workspace separation, multiple client projects on one account and the portfolio view across active projects are all planned for Business and are not in the build today.

Getting started

Tell us how many client engagements you typically run at once and we’ll write back directly about the right tier for your setup.