Foundational Modules Roadmap

Trust Registry

Trust Registry is on the roadmap and can't be deployed or priced. If it's built, it would keep one record for every certificate, calibration, attestation and sign-off.

Book a demo All Modules

How it works

Would keep every verification in one record

Today, certificates sit in email, attestations in binders, and sign-offs in someone’s memory. The design would put each one in a single record a workflow could check before it acts, so nobody has to go asking around.

  • Verification record Quality certification Current Material certificate Current Insurance Expiring Site audit Lapsed
  • Concept, not shipped

Check record

Would record what was checked, by whom, and when

Each entry would attach to the part or supplier it verifies and show whether it’s still current. Picture a calibration on a critical gauge: the entry would show who signed it off and when it expires.

  • What was verified, and on which part or supplier
  • Who signed it off, on what date, against which document
  • Whether it is current, expiring inside the window, or already lapsed
  • Batch releaseSite audit lapsed Held
  • Raised to quality

Release step

Would let a release step read the check itself

A step that depends on a verification would read the record directly. Picture a batch release waiting on a supplier certificate: the step would check the record and move on its own. A lapsed entry would hold the step and raise it to quality.

  • A release step reads the record before the batch moves
  • A lapsed entry holds the step and raises it to quality
  • The result is written to the record either way
  • 21 days left30 Sep Insurance expires
  • Warning window: 30 days

Expiry window

Would flag expiry before the job needs it

Certificates, calibrations, and audits run out. The design would carry an expiry date on every entry, so a lapse would show up while there is still time to renew.

  • An expiry date on every entry that carries one
  • A warning window that opens before the date passes
  • A lapsed entry stays on the list until it is renewed
  • Trust RegistryModule, on the roadmap

Build status

Nothing here is built yet

There is no Trust Registry in the platform today: no screen, no record, nothing to turn on. Everything above is design intent, and the shape may change before any of it gets built.

  • No screen, no record, nothing to turn on
  • Nothing described on this page can be deployed or priced today
  • It sits on the roadmap without a date attached
  • Use these today Supplier Registry Shipped Form Builder Shipped Historian Shipped
  • Trust Registry: roadmap

Modules today

Use the Modules that already do this today

Parts of this already live in Modules you can use today, so you don’t have to wait on a build. The Supplier Registry holds the supplier record, Form Builder captures the check, and the Historian keeps the timestamped record.

  • Supplier Registry holds the supplier record, the scorecards, and the feedback
  • Form Builder captures the check itself, and the response keeps its version
  • The Historian keeps a timestamped record of what happened, per asset
  • Record the checkApproval Queue routes it Its job

Running record

Would record the check and leave the rest alone

Recording the check would be the whole job. Approval routing would stay with the Approval Queue, and it wouldn’t stand in for the certificate or the audit itself.

  • Recording the check is the whole of the job
  • Approval routing stays with the Approval Queue
  • It would not replace the certificate or the audit itself

FAQ

Tell us what you need verified.

It's on the roadmap. Nothing here can be deployed or priced yet, so tell us what you'd need.

Book a demo