Is this what you want RuleState to check in this policy?
2 Then
Best for approval policies, mandate rules, and decision texts that describe who may approve what, up to which limit, and in which situation.
Test version. Submitted text may be processed using an AI extraction service. Do not paste confidential, personal, regulated, or commercially sensitive information.
A decision-ready policy must answer:
Who may approve?
Up to what amount?
In which currency?
What happens above the limit?
What happens if the normal approver is unavailable?
When must the decision stop instead of proceed?
RuleState checks whether these answers are explicit enough to export a ClearState package.
Longer text may take longer to check. For best results, paste the section that explains who may approve, limits, and who takes over.
Next: choose a decision type above, then paste your policy here.
0 / 40,000
Changing the decision type means RuleState will check the policy against a different purpose. Run the check again.
Result
RuleState checked this policy for:
RuleState check
RuleState checks whether this policy is explicit enough to be used by ClearState.
Your policy text — found items and gaps are marked inline
RuleState output · read from your textWhat RuleState foundRuleState read these out of your policy. Confirm each part before it goes into the record.
Confirm each part separately. If RuleState read your policy incorrectly, use "Correct this". If information is missing, add it in the fields below and check the updated policy.
The policy text has been updated. Run the check again to verify everything is correct before creating the record.
Prohibitions found in your policy — confirm each explicit "may not" before they are included in the record
Each prohibition below was read from the text and starts unconfirmed. Review it against the source span, then confirm. A confirmed prohibition becomes a deny rule; nothing becomes part of the record until you confirm it.
RuleState output · gapsWhat is missingInclude the missing information in your policy text, then check the updated policy before creating the record.
Needs your judgementNeeds confirmationRuleState is not certain about these. Confirm what your policy means.
Also worth noting— worth clarifying, but does not block readiness
What needs clarification or confirmation
Your actionConfirm and save RuleState recordThis saves what you confirmed above as a RuleState record. Nothing is sent anywhere else.
Confirm and save RuleState record
A RuleState record is the saved version of your checked policy — including the final policy text, what RuleState found, what you confirmed, and who confirmed it. Fill in your details below to complete it.
What this record contains
The confirmed policy information RuleState found in your text.
What it does not contain
This record does not independently check legal, regulatory, risk or external data requirements. If such requirements are written in the policy, RuleState can record them as policy text. Other control layers can be added in ClearState.
Later in ClearState
This record covers the policy part only. ClearState can later combine it with decision data, legal/regulatory checks, risk rules and external data checks before a real decision is evaluated.
Final policy text to be saved
What would you like to do next?
Before you save: You are confirming that RuleState read the policy correctly. You are not approving a real-world decision.
What will be included in the review version
Decision type—
Final policy text—
Change summary—
RS findings—
Open confirmations—
Prepared by—
Timestamp—
Open this draft in ClearState to test it — auto-generated or your own decision input.
Developer details
Save your ClearState package
Enter your work email. We’ll send a 6-digit code to verify your identity before saving.