Compliance & Evidence

Evidence before the auditor asks.

Obligations, the evidence that each was met, and the decisions taken along the way — kept together and traceable to the procedures, training and sign-offs that produced them.

No certification is claimed. The platform helps an organisation organise its own obligations and evidence. It does not certify anyone, and no jurisdiction pack has yet been reviewed by counsel.

From control to evidence

Select any record to see what it connects to.

How a control relates to the policy, procedure, people, reviews and evidence around it. What is verified and what is outstanding stays visible.

Control · outstanding

CTL-07 Quarterly access review

Met only when every site's review is evidenced. Site B is outstanding, covered by an approved, time-limited exception.

Connected to

5 of 9 records verified; 4 outstanding or covered by an exception. Fictional records.

In the product today: a control links to the obligations it serves, and evidence records name their sources — a document, a system record such as a procedure revision or training record, or an external reference. The direct links drawn here from a control to a policy, procedure or training are a design preview, not built.

Walk through the compliance journey

The evidence chain

From an obligation to the record that proves it.

An obligation names what must happen and how often. Its evidence is not an upload of a spreadsheet; it is the governed records the rest of the platform already produced — the approved procedure revision, the verified training, the signed-off handover.

Illustration · fictional data

Obligation OB-031MONTHLY

Supplier reconciliation control

Approved procedure REC-0417 rev 3evidence
Verified training · D. Okaforevidence
Transition case TC-0088 signed offevidence
Exception · decided by a second personrecorded

Illustration · fictional data · not a product screenshot

How it works

Register, schedule, evidence, decide.

01Register obligationsName the obligation, where it applies, and who owns it. Sample rules help you start; they are examples, not legal advice.
02Schedule themA compliance calendar shows what is due and why, in each location's own calendar.
03Record evidenceAttach the records that show the obligation was met: procedures, training, sign-offs and reviews.
04Decide exceptions with two peopleAn exception is approved by someone other than the person asking, against the exact record it covers.
05Follow any decision backThe evidence and audit console traces a decision to its records, and a segment of the decision ledger can be verified.

What exists today

What is built, and what is planned.

Retention policies across every record type, organisation-wide legal hold, customer-managed keys and governed evidence exports are planned, not built.

Obligations, calendar and evidence records
Register obligations, schedule them, record the evidence that each was met, and explain why an item is due.
Built and tested
Exceptions decided by someone else
An exception is approved by a second person against the exact record it covers; nobody approves their own.
Built and tested
Evidence and audit console
Follow decisions, approvals and training to the records behind them, and export a verifiable segment of the ledger.
Built and tested
Legal hold on recordings
Place source recordings on hold so they cannot be deleted while a hold applies.
Built and tested
Retention policies, organisation-wide holds and evidence exports
Retention and legal hold across every record type, customer-managed keys, and governed evidence exports.
On the roadmap
Jurisdiction packs reviewed by counsel
Pre-built obligation packs for a country, reviewed by qualified counsel before any is offered. Which country comes first is still to be decided.
On the roadmap

Start with one obligation you already evidence by hand.

A pilot can model one recurring obligation end to end, so your compliance owner can judge the evidence chain on something real.

Apply for a controlled pilot Request an enterprise demo