Hosted compliance Flows
One rule set.
The right way to use it.
Turn a published compliance interpretation into a working form, guided assessment, determination, or checklist—without rebuilding its rules.
Four experiences
Fit the screen to the work.
A Flow is the respondent-facing experience. The schema remains the source of the questions, constraints, time periods, decisions, and messages. Choosing another experience does not create a second interpretation to maintain.
Standard form
Collect a complete set of facts in one responsive document. Useful for reports, applications, declarations, and structured intake.
Guided assessment
Show one relevant question at a time. Earlier answers determine the next step, so people do not have to interpret the branching logic themselves.
Determination
Apply published rules to a known set of facts and return a calculated, reviewable outcome such as eligibility, classification, or required action.
Compliance checklist
Walk through explicit controls and keep the completed check as evidence of what was reviewed, by whom, and against which release.
Why version binding matters
A result should not outlive its reasoning.
Typical workflow tools preserve the answers but make it difficult to prove which legal interpretation produced the result. ProseID keeps the release with the completed record, so a later edit cannot silently rewrite history.
Before completion
Guide the person through the relevant facts.
- Required answers are visible and validated.
- Conditional questions appear only when they apply.
- Long answers, dates, choices, and calculated values use the appropriate controls.
- The organisation can use a ProseID theme and its own public identity.
After completion
Keep a record that can be explained later.
- Answers, outcome, schema identity, and exact version stay together.
- Proof-v2 records can be checked against ProseID’s published verification keys.
- Email and webhook delivery can move the result into the surrounding process.
- A retry cannot create a second charge or duplicate record for the same completion.
A completed Flow uses one base credit. Publisher fees and supported signing surcharges, when present, are shown separately before creation. Unfinished attempts do not consume a completion credit.
Where the rules come from
Use your own interpretation or adopt a public one.
Create a private schema for an internal process, publish your own fixed release, or choose work from the compliance schema registry. Every public page shows its publisher, release, compatible Flow experiences, jurisdiction, and price. Learn how the underlying model works in the guide to executable compliance.
From requirement to record