01 · The mental model

Build from facts to a conclusion.

A schema is a reusable interpretation. It asks for facts, checks those facts, reaches useful conclusions, and preserves what happened. The visual builder separates that work into four understandable parts.

1Schema details

Explain the obligation, choose its recommended Flow language, where it applies, and the law or source behind it.

2Fields

Collect facts a person can know or provide: dates, amounts, choices, text, or confirmations.

3Rules

Show guidance, ask for more information, or stop an invalid completion when a condition is met.

4Calculated values

Turn the answers into a conclusion such as “Applies,” a deadline, a score, or a next step.

ResponsesWhat the person entered

The facts collected by your fields.

Calculated valuesWhat the schema concluded

Results created automatically from those facts.

RecordWhat ProseID preserves

The responses, results, exact schema version, time, and proof.

Language is a recommendation, not a jurisdiction.

Choose English or Swedish in Schema details. A Flow starts in that language unless the visitor has chosen another preference before. They can switch at any time; your own labels and legal wording remain exactly as authored.

02 · Build an outcome

Make an applicability decision in four steps.

Imagine the conclusion should be Applies when the organization has at least 50 employees and performs a covered activity. Otherwise, it should be Does not apply.

01

Add the facts people can answer
Open Fields. Add a Number field named “Employee count” and a Yes / no field named “Performs a covered activity.” Mark them required if the decision cannot be made without them.

NumberEmployee countRequired

Yes / noPerforms a covered activityRequired
02

Name the conclusion
Open Calculated values and choose Add calculated value. Use a short name such as “applicability.” This is the result ProseID will fill automatically.

Value nameapplicabilityAuto
03

Describe the decision
Under Calculation method, choose If this, then that. Build the “If” side with Every condition is met: employee count is at least 50, and covered activity equals Yes. Use “Applies” as the result. Under “Otherwise use,” enter “Does not apply.”

IfEvery condition is met

Employee count is at least 50

Covered activity equals Yes

Use this resultApplies

Otherwise useDoes not apply
04

Make the result understandable
Under How the result is saved, choose Text or Choice list. Set the display label to “Applicability.” Keep Show in completed records on so the conclusion is visible in a Determination and its final record.

Display labelApplicability

Show in completed records

“READY” is not your legal or compliance outcome. It only means the answers are complete and valid enough to create a record. Put conclusions such as “Applies,” “Eligible,” “Notify within 24 hours,” or “Needs review” in a calculated value.

03 · Rules or outcomes?

Use each tool for one clear job.

Rules guide or protect the completion. Calculated values answer the question the schema was built to decide.

Use a rule when…Use a calculated value when…

You need to reveal another question.

You need to state whether something applies.

An answer needs a helpful message.

You need to calculate a deadline or amount.

A missing or conflicting answer must block completion.

You need to choose a route, category, score, or next step.

A field becomes required only in certain circumstances.

You want the conclusion included in the completed record.

Do not use an error to mean “Does not apply.”

“Does not apply” can be a perfectly valid conclusion. Errors are for answers that are incomplete, impossible, or inconsistent.

04 · Test your work

Try both sides before you publish.

Choose Test schema, then select a Flow experience. A Determination is the clearest way to check a calculated conclusion because it keeps the result visible beside the questions.

Test A50 employees · covered activity: Yes

Expected outcome: Applies

Test B12 employees · covered activity: Yes

Expected outcome: Does not apply

Test C50 employees · covered activity: unanswered

Expected behavior: ask for the missing required answer.

Why might Determination be unavailable?

A Determination needs at least one question a person can answer and at least one calculated value that is shown in completed records. Both must work in every legal time period.

05 · Useful patterns

One schema can produce more than one useful answer.

Add separate calculated values when each conclusion has a distinct meaning. This keeps records readable and makes your logic easier to review.

ApplicabilityDoes this obligation apply?

Applies · Does not apply · Needs review

DeadlineWhen must action be taken?

Calculated date or a named time window

RoutingWho should handle it?

Privacy team · Security team · Local counsel

Next stepWhat should happen now?

Notify · Document only · Gather more information

06 · Plain-language glossary

The few terms worth knowing.

Schema: The reusable questions, conditions, conclusions, sources, and legal periods behind a Flow.
Field: One fact to collect or one result to display.
Rule: An instruction that takes effect when certain answers meet a condition.
Calculated value: A conclusion ProseID creates automatically from answers or other calculated values.
Flow: The experience people complete: a form, guided assessment, determination, or checklist.
Record: The protected result of one completed Flow, tied to the exact schema release used.

Ready to build?Start with the question you need the schema to answer.

Create a schema

Build from facts to a conclusion.

Make an applicability decision in four steps.

Add the facts people can answer

Name the conclusion

Describe the decision

Make the result understandable

Use each tool for one clear job.

Try both sides before you publish.

One schema can produce more than one useful answer.

The few terms worth knowing.