Solutions

Contract CP

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 CPs 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 attaches to the criterion it supports. Every change is logged against your identity with a timestamp. 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.

Your project data stays on your device on the Solo tier — nothing leaves unless you choose to export it. Each client’s project sits in its own local project file, isolated from every other.

When the engagement is complete, the client receives the Table 1 and the attached evidence as a complete export package — the Table 1 and its attached evidence together in one deliverable. 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 beside your 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 Pro, your library will sync across your devices and, by default, only you can read it, so your own body of work travels with you from engagement to engagement.

Tiers for contract CPs

Pro — one CP licence with per-project isolation. Right for a contract CP running one or two client engagements at a time. See what’s included in Pro.

Business — if you are running several concurrent client engagements at once, with client workspace separation and multiple CPs per section. Portfolio view across active projects is planned. See what’s included in Business.

Getting started

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