← All briefings
Product guideUsing ProseID

What is ProseID? A practical guide to reusable compliance workflows

ProseID turns legal and regulatory interpretations into reusable forms, assessments, determinations, and checklists with a versioned record for every completion.

What is ProseID?

ProseID is a platform for turning legal, regulatory, and policy requirements into reusable digital workflows.

A legal or compliance professional defines the facts to collect, the conditions to apply, the conclusions to calculate, and the evidence to retain. That interpretation becomes a published schema. The same schema can then run as a form, guided assessment, determination, or compliance checklist.

When someone finishes the workflow, ProseID validates the answers and creates a protected Record tied to the exact published version that was used.

The short version is:

Define the interpretation once. Publish it as a fixed version. Use it repeatedly without losing the reasoning or history behind it.

You can try a working ProseID Flow without creating an account.

Why was ProseID created?

ProseID began with a recurring frustration in regtech: useful interpretations were difficult to find, their freshness was often unclear, and even a good interpretation was rarely structured in a way another person or system could reuse.

A requirement might be explained in a legal memo. Its operating steps might live in a procedure. The questions might sit in a form builder. Validation might be hidden in code. The final evidence might be stored in an email, PDF, ticket, or database.

Each piece can be useful. The problem is that the interpretation is split across all of them.

That creates repeated work. A business reads a requirement, gets advice, turns it into questions, adds conditions, decides what blocks completion, and chooses what evidence to retain. Another business later performs nearly the same translation from the beginning.

When the law or interpretation changes, the difficulty grows. Which workflow is current? What did an older case use? Can the earlier version still be inspected? Did a form change without the reasoning changing, or did the legal interpretation itself change?

ProseID was created to make the operational interpretation a first-class object. It can be inspected, tested, published, versioned, reused, and connected to the Records it produces.

The deeper category argument is covered in Why compliance workflows keep getting rebuilt. This guide focuses on the product that emerged from that problem.

What problem does ProseID solve?

Most compliance software begins at one of two ends.

At one end, documents explain what a requirement means. They preserve nuance, but they do not make the interpretation runnable.

At the other end, forms and applications collect information. They can be efficient, but the reasons behind their fields and rules may be difficult to inspect or reuse outside that one implementation.

ProseID sits between the written requirement and the finished process. It gives the interpretation a stable structure:

  • legal references and jurisdictions;
  • human-readable title, description, labels, placeholders, and guidance;
  • typed questions and answer options;
  • conditions that control what appears;
  • calculated conclusions;
  • blocking errors, warnings, and informative messages;
  • attestations and completion requirements;
  • legal time periods for changing rules; and
  • a permanent identity for every published version.

This structure can power several user experiences without creating several separate copies of the logic.

The four parts of ProseID

Four terms explain most of the product.

1. Schema

A schema is the reusable interpretation.

It contains the questions, rules, calculated values, messages, legal context, and time periods behind a process. A schema is not the page a respondent sees. It is the source from which that page is produced.

For example, an incident-reporting schema could contain:

  • when the organisation became aware of the incident;
  • which entities and services are affected;
  • the facts used to decide whether a reporting threshold is met;
  • the deadlines that apply;
  • information still unknown;
  • warnings about follow-up action; and
  • the conclusion shown in the final Record.

The official visual schema builder documentation shows how to create these decisions without writing code.

2. Published version

A working draft can change. A published version cannot.

Publishing freezes the schema so a Flow can depend on it. Later improvements become a new version instead of silently rewriting the old one. Completed Records remain connected to the version that actually produced them.

A version may be private to an organisation or public in the registry. Public versions can be discovered and evaluated by other organisations. Once public, a release does not become private again. It can later be deprecated, but existing users and historical Records do not lose it.

3. Flow

A Flow is the experience someone completes.

ProseID currently supports four Flow formats:

  1. Standard form: presents the relevant fields as one responsive document.
  2. Guided assessment: presents the process step by step so the person sees what is relevant next.
  3. Determination: keeps calculated conclusions prominent while the facts are entered.
  4. Compliance checklist: organises the work around explicit controls and their review.

The schema remains the source of the rules. Choosing a different Flow format changes how the work is presented, not the meaning of the interpretation.

4. Record

A Record is created when a Flow is successfully completed.

It keeps the responses, calculated results, exact schema version, Flow identity, completion time, and relevant delivery information together. The schema is validated on the server before completion, so the final Record is not based only on what a browser claimed was valid.

An abandoned attempt does not create a completed Record.

How does ProseID work from beginning to end?

The complete lifecycle is straightforward:

  1. Define the interpretation. Start with a requirement, policy, recurring assessment, or existing checklist.
  2. Build the schema. Add the facts, rules, outcomes, messages, sources, jurisdictions, and time periods.
  3. Test it. Run the schema through every compatible Flow format and try both ordinary and uncomfortable cases.
  4. Prepare a fixed version. Review what changed and describe the version in plain language.
  5. Publish it. Keep it private for internal use or list it publicly in the registry.
  6. Create a Flow. Choose the schema first, then the experience, presentation, signing option, access method, and delivery settings.
  7. Collect a completion. A person follows the Flow while the schema controls relevance, validation, and calculated results.
  8. Retain the Record. ProseID stores the result against the exact rules that produced it.

For a closer look at every stage, read How ProseID works, from requirement to versioned Record.

Who can use ProseID?

ProseID is intended for people who repeatedly turn requirements into operational decisions.

A professional can turn a recurring interpretation into something clients or colleagues can use consistently. Instead of sending the same questionnaire and reconstructing the same decision every time, the professional can maintain one versioned schema.

Professionally verified authors can make public schemas easier to evaluate through a person profile. The organisation publishing the schema may attach an optional publisher fee when an eligible owner is verified. Verification identifies a reviewed professional credential; it does not turn every publication into official advice or guarantee that it fits every adopter.

An in-house team can create private schemas for incident intake, applicability checks, policy exceptions, supplier reviews, internal approvals, or other repeated processes. The team gets a consistent workflow and a Record of what was completed without publishing its interpretation publicly.

Operations teams

Operations teams can run clear processes without asking every participant to interpret a legal memo. Conditions reveal the relevant questions, messages explain what needs attention, and conclusions appear in a consistent form.

Product and engineering teams

Developers can use hosted Flow links, the API, webhooks, or the browser SDK rather than building validation, conditional presentation, Records, delivery, and version binding from scratch. The interpretation can remain owned by the appropriate legal or compliance professional.

What can ProseID be used for?

A strong ProseID use case has three qualities:

  • the process depends on structured facts;
  • rules or judgments determine what happens next; and
  • the organisation benefits from knowing exactly which interpretation was used.

Examples include:

  • incident and breach reporting;
  • regulatory applicability assessments;
  • customer or supplier due diligence;
  • policy exception requests;
  • whistleblowing intake and follow-up;
  • employee or contractor compliance declarations;
  • reporting-deadline assessments;
  • disclosure and notification workflows;
  • recurring control reviews; and
  • eligibility or classification decisions.

ProseID does not require every process to end in a yes or no. A schema can calculate several conclusions, require follow-up actions, surface warnings, or simply produce a complete structured Record.

What are the benefits?

The interpretation can be reused

The same published schema can support many completions and several Flow experiences. A team does not have to rebuild the logic because a different user needs a different interface.

Earlier Records keep their meaning

When a new version is published, old Records stay tied to the version they used. History does not change simply because the current workflow improved.

Decisions become easier to inspect

Questions, conditions, outcomes, messages, sources, and time periods travel together. A reviewer can understand more than the final answer alone.

The user sees only what is relevant

Conditional questions and guided experiences reduce unnecessary input. Helpful messages can explain a choice, while warnings and blocking errors remain distinct.

The interpretation is not buried only in code or only in prose. Legal and compliance professionals can work in the visual builder, while developers can integrate the resulting Flow.

Public expertise can become maintained infrastructure

The registry lets organisations inspect published work, its source, publisher, version, lifecycle, compatible experiences, and price before deciding whether to use it.

What ProseID does not claim to do

Structure does not automatically make an interpretation correct.

ProseID records who published a schema, which sources were cited, which jurisdiction was selected, which version ran, and what happened during completion. Those details make the work easier to evaluate. They do not replace professional judgment, fact-specific advice, or the adopter’s responsibility to decide whether a schema fits its situation.

ProseID also does not silently update every active Flow whenever a publisher changes something. Published versions are fixed. Flow owners choose whether to follow a compatible latest version or remain on a particular version, depending on their need for stability.

How do I start using ProseID?

There are three useful starting points.

Try an existing Flow

Try ProseID to see the respondent experience and the outcome without building anything.

Use a published schema

Browse the registry, inspect a schema’s publisher, references, version, jurisdictions, compatible Flow types, and price, then choose Use schema in a Flow.

Build your own schema

Create a schema and begin with one narrow decision. Add only the facts the decision genuinely needs, test both sides, and publish privately before deciding whether the work belongs in the public registry.

Frequently asked questions

Is ProseID a form builder?

ProseID can produce forms, but the reusable object is the schema behind the form. That schema can also power guided assessments, determinations, compliance checklists, APIs, and embedded experiences.

Does a published schema change when the publisher edits it?

No. Published versions are fixed. The publisher starts a new working version, prepares it, and publishes a new release. Existing Records remain tied to the earlier version.

No. A schema can be published privately to your organisation and used in your Flows without appearing in public registry search.

Can I use a public schema created by someone else?

Yes. Inspect its provenance, sources, jurisdiction, lifecycle, compatible Flow types, and price first. Public schemas can be selected when creating a Flow.

Does every attempt cost money?

No. ProseID charges when a Flow is successfully completed and creates its Record. The price is shown before the Flow is created. Optional publisher fees or supported signing and presentation surcharges are itemised separately when applicable.

Can I use ProseID without code?

Yes. The visual builder, hosted Flows, delivery settings, registry, and Records are available through the web application. API and embedding options are available when a team needs integration.

One interpretation, used with its history intact

The problem ProseID addresses is not that the world lacks legal prose. It is that the operational interpretation is repeatedly rebuilt and often loses its identity once it becomes a form or application.

ProseID gives that interpretation somewhere to live between the source and the completed work.

Run a real Flow, inspect a published schema, or create your first schema.

Important

This briefing is general information about workflow design, not legal advice. Check the current law, national implementation, regulator guidance, and your specific facts before acting.

From reading to operation

Turn the requirement into a versioned Flow.

Learn how executable compliance structures an interpretation, explore hosted compliance Flows, or inspect real releases in the public registry.

Privacy preferences

Privacy policy